ProductManager ResearchPhase

ResearchPhase builds the evidence base for feature candidates. It answers: what does the product do, where does it feel weak, what do adjacent products teach us, and which user problems appear worth exploring?

Workflow

1. Frame the run. Identify the product, target user, repo, live URL or dev command, and any user-stated goals.
2. Read local context. Inspect README, AGENTS.md, docs, screenshots, issues, analytics exports, feature specs, and relevant source directories.
3. Mock-use the product. Run the app or inspect an existing environment when feasible. Walk the primary workflows as a plausible user. Capture screenshots or notes for each friction point.
4. Visually inspect. Look for missing states, unclear hierarchy, awkward empty/loading/error states, hidden affordances, mismatched language, and workflows that require unnecessary memory.
5. Research outside context. Browse current competitors, category norms, pricing or packaging, app-store/review complaints, docs, and relevant product patterns. Cite URLs and access dates.
6. Synthesize evidence. Separate observations from inferences. Mark confidence and source quality.

Evidence Log

Maintain evidence-log.md during the phase:

# Evidence Log