Skip to main content
Most agile teams have a delivery problem masquerading as a process problem. They’re good at shipping - sprints run, velocity is tracked, releases go out. What they’re not good at is making sure what they’re shipping is worth shipping. Dual-track agile is the structural answer to that 🔄

​
The two tracks

Discovery track - the team is continuously working to understand problems, generate ideas, and validate solutions before they go into development. This is product discovery running as an ongoing practice, not a phase that happens before a project starts. Delivery track - the team is building and shipping things that have already been validated in discovery. The input to delivery isn’t “ideas from the backlog” - it’s “solutions we’ve already tested and have confidence in.” The tracks run in parallel. Discovery is always one step ahead of delivery, feeding it a steady supply of validated work 💡

​
Why it matters

Without dual-track, teams face a choice between two bad options: do all the discovery upfront (waterfall by another name) or do no discovery at all and just build based on assumptions (feature factory). Dual-track is the escape hatch. Teresa Torres describes a closely related model in Continuous Discovery Habits - the product trio running weekly discovery cycles in parallel with delivery sprints. The cadence is what makes it sustainable rather than heroic.

​
What it looks like in practice

  • PMs and designers are always running interviews, experiments, and prototype tests - not only when a project kicks off
  • Stories entering the sprint have already been tested at some level of fidelity
  • The backlog isn’t a wish list; it’s a validated queue
  • Engineering is involved in discovery, not just handed specs at the end
The last point matters. Continuous discovery works best as a product trio activity - PM, designer, and engineer together, not sequentially 🙌

​
The common failure mode

Teams adopt the language of dual-track without the practice. Discovery becomes a separate team or a separate phase that hands off to delivery, recreating the waterfall handoff with agile vocabulary. The point is that the same team does both, continuously. Lesson learned: the signal that dual-track is working isn’t the process - it’s when an engineer pulls a story from the backlog and says “I already know why we’re building this, I was in the interview.”