Gantt Chart for Product Discovery

Run product discovery on time with a Gantt chart. Timeline covers problem framing, user research, synthesis, prototyping, and go/no-go decision.

Gantt Chart for Product Discovery

Product discovery is the work that happens before engineering starts — the research, testing, and decision-making that determines whether you are building the right thing. Done well, discovery prevents teams from spending three months building a feature no user needs. Done poorly, it becomes an endless loop of interviews and workshops that never produces a decision.

A Gantt chart gives discovery a shape: defined phases, parallel research tracks, explicit dependencies, and hard dates for the go/no-go decision that sends the work to engineering. This guide walks through a full product discovery timeline from problem framing to handoff.

Phase 1: Problem Framing (Weeks 1–2)

Discovery starts with a problem, not a solution. The problem frame determines every research question, prototype test, and prioritization decision that follows. Investing two weeks in a precise problem statement prevents three months of work on the wrong opportunity.

Opportunity assessment tasks:

Deliverable: A one-page opportunity assessment document. It frames the problem, sizes the opportunity, maps the competitive context, and states why this is worth solving now versus later. This document requires sign-off from the product leader and at least one engineering lead before research planning begins.

Phase 2: User Research Planning (Weeks 2–3)

Research without a plan produces data without insight. Before recruiting a single participant, document:

Phase 3: Participant Recruitment and Scheduling (Weeks 3–4)

Recruitment is always slower than planned. Build in buffer.

Recruitment channels:

Scheduling tasks:

Phase 4: Research Execution (Weeks 4–6)

The quality of research execution determines the quality of insights. Common failure modes:

Interview facilitation protocol:

Debrief after each session: 15-minute team debrief immediately after each interview to capture hot observations before memory fades.

Phase 5: Insight Synthesis and Affinity Mapping (Weeks 6–7)

Raw interview notes are not insights. Synthesis transforms data points into patterns and patterns into product-relevant findings.

Affinity mapping process:

Insight validation: Cross-reference qualitative findings with quantitative data (analytics, survey results). An insight that appears in interviews and is confirmed by usage data is much stronger than one that appears in interviews alone.

Deliverable: A synthesis document with: key findings (what is true about users and their problems), implications (what this means for product decisions), and open questions (what remains unknown).

Phase 6: Opportunity Prioritization (Weeks 7–8)

Multiple opportunities will emerge from research. Prioritization frameworks turn a list into a ranked order.

RICE scoring:

RICE Score = (Reach × Impact × Confidence) / Effort

Jobs-to-be-Done mapping: Map each opportunity to the functional, social, and emotional job the user is trying to accomplish. Opportunities that address the core functional job with a strong emotional component outperform those that address peripheral jobs.

Prioritization outputs to a stack-ranked list of opportunities with a clear recommendation for which one to move into solution ideation.

Phase 7: Solution Ideation (Weeks 8–9)

Ideation is structured divergence — generating many possible solutions before converging on the most promising ones to prototype.

Design sprint structure (optional but high-value for complex problems):

Even without a full design sprint, run a structured sketching session: 30 minutes of individual ideation (Crazy 8s) followed by gallery review and dot voting. Diversity of perspective matters — include engineering and CS representation, not just product and design.

Phase 8: Prototype Testing (Weeks 9–12)

Prototypes should be the minimum fidelity required to test the specific question. Over-engineering a prototype is wasted work; under-engineering it produces invalid results.

Prototype types by test:

Test types:

Aim for 5 moderated sessions minimum per prototype iteration. Two or three prototype iterations are normal — discovery is inherently iterative.

Phase 9: Finding Documentation and Stakeholder Presentation (Weeks 12–13)

Discovery ends with a presentation, not a conversation. Formal documentation forces synthesis and creates a record that engineering can refer to during build.

Deliverables:

Phase 10: Go/No-Go Decision (Week 13)

The go/no-go gate is the most important moment in discovery. It requires a decision from product, engineering, and business leadership that this opportunity is worth building.

Go criteria:

No-go criteria:

No-go is not failure — it is discovery working as designed. Killing a bad idea in week 13 of discovery is far cheaper than killing it in month 6 of engineering.

Phase 11: Handoff to Engineering

If go, create discovery-done acceptance criteria:

Building Your Discovery Gantt Chart

In gantt-chart.io, build one row per phase with realistic durations. Mark the go/no-go decision as a hard milestone — no engineering work should start before it. Track participant recruitment separately from research execution. A visible discovery timeline protects the work from being compressed to fill space before a pre-announced launch date — the most common way good discovery produces bad products.