Dual-track discovery & delivery
It was articulated by Marty Cagan and Jeff Patton, among others, and Teresa Torres incorporates it into her continuous product discovery.
The two tracks
Discovery track
Investigate and validate opportunities before committing development capacity. Typical activities include user interviews, low-fidelity prototyping, experiments, and data analysis. The output is validated learning—a better understanding of opportunities and tested assumptions—which informs the product backlog. This work is carried out by the same team that handles delivery, rather than by a separate team that simply hands off a batch of user stories to another group.
Delivery track
Builds and implements the opportunities already validated by the discovery track. It operates in sprints, with all the standard Scrum events. Its output is product increments in production.
Relationship between the tracks
The key to the model is the intentional time offset: while delivery builds what discovery validated in previous sprints, discovery prepares what will come next. The team does not "pause" development to do research: it researches continuously, in parallel.
| Discovery track | Delivery track | |
|---|---|---|
| Central question | "Is this worth building?" | "Is it built correctly?" |
| Output | Validated learning that informs the backlog | Increments in production |
| Cadence | Continuous (weekly) | Iterative (sprint) |
| Uncertainty | High: exploring | Low: executing the known |
Relationship with the AI double track
Dual-track discovery & delivery is a model for organizing product work; the AI double track is a technical execution model. They are complementary: within the delivery track, the team can use the double track to manage the differential speed between AI prototyping and production code.
Common mistake
Treating discovery and delivery as sequential phases instead of parallel tracks. When discovery precedes delivery instead of coexisting with it, the team repeats the waterfall cycle under another name: a research phase, followed by a planning phase, followed by a development phase. What sets dual-track apart is that discovery never ends: it is a continuous practice that permanently feeds delivery.
Resources
🏦 Customer discovery and validationState of the art and guide · Skill Arena
- Cagan, Marty. (2017). Inspired: How to Create Tech Products Customers Love. Wiley.
- Torres, Teresa. (2021). Continuous Discovery Habits. Product Talk LLC.
See also
Want to advance in agility? You can search for course and exam calls, or go at your own pace by becoming a member of the Agile Club. This membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills at your own pace.