Research
Build a feature matrix from dated source material
A feature comparison needs a consistent definition and a snapshot date.
OfficeCubs · · 2 min read
A feature comparison needs a consistent definition and a snapshot date. Otherwise absence from a page can be mistaken for absence from the product.
Define the evidence boundary
Give the research teammate a bounded set of documents or an explicit source scope. Request references next to claims and keep observation separate from interpretation. An AI summary is not independent verification of a source. Where live web access is unavailable, work from the supplied snapshot and label its date rather than describing the findings as current.
Inputs for this workflow: Approved competitor documentation snapshots and comparison criteria.
Work through the task
- Define each feature row.
- Record supported, not found or unclear with source links.
A brief you can adapt
Create a feature matrix with a source date for each column. Use Not verified where the supplied material does not establish support.
The filenames above are examples. Replace them with your actual inputs and destination before submitting the task.
Review the deliverable
Verify a sample of positive and negative entries against the source snapshots.
Where this approach can fail
Not mentioned is not the same as not supported. Do not invent current pricing or capabilities.
For the related desktop setup, see write task brief.