This is family, not rivalry. Lean Startup, continuous discovery, and Dual-Track Agile gave the industry the idea that progress is validated learning — and Scaleflow is, in large part, a way to run a team on exactly that idea.
What they got right — and what Scaleflow took from them
- Lean Startup (Eric Ries): build–measure–learn, the MVP, validated learning, the pivot. Scaleflow makes Learning rate the team’s real KPI — validated learning turned into the weekly unit of progress.
- Continuous discovery (Teresa Torres): keep a steady drumbeat of customer contact, and let opportunities — not features — drive the work. Scaleflow’s working-backwards-from-the-customer and the customer voice on the Product BoardProduct BoardTwo or more stakeholders who see the team's weekly demo and coach it — the human in the loop, with no single lead. are the same instinct.
- Dual-Track Agile: discovery and delivery run in parallel, not in phases. In Scaleflow the four discovery risks — desirability, usability, feasibility, viability — are the key Uncertainties, and assigning them to weeks is what makes the two tracks run at once.
The difference
These are philosophies and practices; Scaleflow is a full operating method. Lean Startup tells you to learn fast; continuous discovery tells you how to keep listening; Scaleflow gives both a place to live — the Initiative DocumentInitiative DocumentThe PR/FAQ-shaped document where an initiative's context lives — customer, solution, plan, business case, and success metrics., the Uncertainty ListUncertainty ListThe team's living list of open unknowns — sized 1/3/5, phrased as questions, reviewed daily and in planning, chipped away each week., the weekly demo, the roles — and a way to scale past a single team.
How they fit together
Use continuous-discovery techniques — interviews, opportunity mapping, prototypes — to feed the Initiative Document and the UncertaintyUncertaintyWhat the team does not yet know — sized and tracked deliberately rather than hidden inside estimates. List. Treat each weekly demo as one turn of the build–measure–learn loop. You lose nothing by running Scaleflow on top of a discovery practice; you give it a cadence.