Finish-to-Start (FS)
Predecessor must finish before successor starts.
- Term
- Finish-to-Start (FS)
- Field
- Product Management
- Category
- Growth & Lifecycle
The short definition
Predecessor must finish before successor starts.
In product management, this concept guides how products are scoped, prioritized, built, measured, and iterated. It typically affects roadmap decisions, feature trade-offs, and definitions of success.
Finish-to-Start (FS) is a growth & lifecycle term for a lifecycle concept. Agree the scope and two people stop talking past each other.
Where the mechanics matter
Think of Finish-to-Start (FS) as context-bound. A small shop reads it simply; an enterprise reads it with more nuance. That is normal -- Finish-to-Start (FS) is shaped by audience and channel mix. Read Finish-to-Start (FS) without care and the plan wobbles; be precise and the read holds.
The working rule is plain. Agree what Finish-to-Start (FS) covers first, then act on it. Skip that order and Finish-to-Start (FS) loses its shared meaning, and two teams end up measuring two different things. Look at it this way.
Where it shows up
Use Finish-to-Start (FS) when it changes an outcome. For growth & lifecycle teams, that tends to be three recurring moments. With no choice live, Finish-to-Start (FS) is good to know, not to chase.
- Setting budget. Finish-to-Start (FS) points to where the next dollar should go.
- Choosing a metric. Finish-to-Start (FS) flags whether the number you report is causal.
- Comparing options. Finish-to-Start (FS) evens out a comparison that would otherwise mislead.
A worked example
Look at Duolingo. In a streak-driven retention loop, Finish-to-Start (FS) drove the decision rather than sitting in a footnote. A baseline came first, then a single agreed meaning of Finish-to-Start (FS), then the read: D30 retention improved 14 points.
| Stage | The step taken | The reason |
|---|---|---|
| Baseline | Logged where Finish-to-Start (FS) stood before the test. | A fixed point of truth. |
| Define | Fixed one meaning of Finish-to-Start (FS) for the test. | A shared definition up front. |
| Act | A streak-driven retention loop — one variable. | Cause and effect, isolated. |
| Result | D30 retention improved 14 points | An outcome you can trust. |
These Finish-to-Start (FS) numbers are illustrative -- RGM analysis. The structure travels; the specific figures do not.
Failure modes to watch
- One blanket rule. Applying Finish-to-Start (FS) the same way everywhere. Split it by audience, channel, and business model.
- Bare numbers. Showing Finish-to-Start (FS) on its own. Context is what makes it readable.
- Chasing the word. Optimizing Finish-to-Start (FS) for its own sake. Check it tracks a real outcome.
- Bad compares. Benchmarking Finish-to-Start (FS) with no adjustment. Account for the model differences first.
Quick answers
What is Finish-to-Start (FS)?
Why does Finish-to-Start (FS) matter?
How is Finish-to-Start (FS) used in practice?
What is the most common mistake with Finish-to-Start (FS)?
- What is Finish-to-Start (FS)?
- Predecessor must finish before successor starts. In short, fix that meaning before any tactic is debated.
- Why does Finish-to-Start (FS) matter?
- Finish-to-Start (FS) matters because vague vocabulary breaks strategy. A precise, shared definition keeps a team aligned.
- How is Finish-to-Start (FS) used in practice?
- Finish-to-Start (FS) supports a real choice: where money goes, what gets measured, which option wins. The Duolingo case traces it.