Skip to content

Iteration

Iteration improves the Startup one change at a time: one number, the worst step, and one change a week.

Outcome

PartThis Process
OutcomeEach week ends with exactly one recorded change and a note on how to undo it.
ReadsMetric
LeavesDecision, Change, Issue
Runs inEach Startup

Accountable

Founder, Founding Team.

Workflows

WorkflowRunsTeam
Weekly reviewevery weekFounding Team

Who does each step

Iteration: who does each step6 steps in 1 Workflow, across 2 Roles: Founder, Strategist. The table below lists every step.FounderAveryStrategistStellaWorkflowWeekly review1 · Metric.queryRead the one number for the Startup’s kindof Product: activations before firstrevenue, outside revenue growth after.2Find the step where the most buyers leak.3Keep, tune, or stop each live Play by itsown Metric on outside revenue.4Choose exactly one change: a strategyedit, a Play test, a field test, or an Issue tobuild.5 · Decision.createRecord the change as a Decision, with anote on how to undo it.6 · Issue.createOpen an Issue for the Legal Team when thechange touches the legal floor.Iteration: who does each step6 steps in 1 Workflow, across 2 Roles: Founder, Strategist. The table below lists every step.WorkflowWeekly reviewFounder1 · Metric.queryRead the one number for the Startup’s kind ofProduct: activations before first revenue, outsiderevenue growth after.Strategist2Find the step where the most buyers leak.Strategist3Keep, tune, or stop each live Play by its ownMetric on outside revenue.Founder4Choose exactly one change: a strategy edit, aPlay test, a field test, or an Issue to build.Founder5 · Decision.createRecord the change as a Decision, with a note onhow to undo it.Founder6 · Issue.createOpen an Issue for the Legal Team when thechange touches the legal floor.
Each box is a step, numbered within its Workflow, with the Verb it calls, under the Role it runs as. The table below adds approvals.
WorkflowStepRoleCallsApproval
Weekly review1. Read the one number for the Startup’s kind of Product: activations before first revenue, outside revenue growth after.FounderMetric.queryNone
Weekly review2. Find the step where the most buyers leak.Strategist
Weekly review3. Keep, tune, or stop each live Play by its own Metric on outside revenue.Strategist
Weekly review4. Choose exactly one change: a strategy edit, a Play test, a field test, or an Issue to build.Founder
Weekly review5. Record the change as a Decision, with a note on how to undo it.FounderDecision.createNone
Weekly review6. Open an Issue for the Legal Team when the change touches the legal floor.FounderIssue.createNone

Events

DirectionWhenWhat happens
InEvery weekStarts Weekly review
OutMetric.queriedRaised by step 1 of Weekly review
OutDecision.createdRaised by step 5 of Weekly review
OutIssue.createdRaised by step 6 of Weekly review

Plays

No Play names this Process.

Controls

No Control names this Process or a Workflow of it.

Settings

SettingTypeDefaultSaySet with
iteration.daystringmonRun the weekly test on MondaysSetting.update
iteration.changesinteger1Make one change a weekSetting.update

Failure

A failed step retries; when retries run out, the Action goes to the Founder.

Loop

StepValue
HypothesisChanging only the worst step each week lifts weekly outside revenue growth more than changing several steps at once.
MeasureWeekly outside revenue growth over 28d, at least 4 observations
LearnThe learn step reads the Readout, records Evidence and a Decision, and drafts the next Variant.

Code

Text
Turn on iteration

Enable

On by default for every Product Template. Process.pause stops new Actions; Actions in progress finish.

Text
Run the weekly test on Mondays

Example

A key-management API grows 2% a week. Weekly review finds 60% of trial users stall at API key setup, so the week's one change is a setup Issue with an undo note. The next week, growth reads 6%.