Skip to main content
Use this page to turn the course’s completed decisions into the next 90 days of work. Copy the definitions, boundaries, and source dates from their owner pages. When an input is missing, record the dependency that must be resolved. When it does not apply, write not applicable and why. Day 30, 60, and 90 are decision dates. The work between them depends on the business’s actual starting point; the calendar does not promise that validation, profitability, or scale will arrive on a standard schedule.

​
Open the planning window

Plan owner: ___ Start date: ___ Day 30: ___ Day 60: ___ Day 90: ___ Chosen role from Chapter 6.3: ___ Next scale-review date: ___ Reliable business hours or blocks: ___ Protected life boundary: ___ The question this plan must answer by Day 90: ___

​
Bring forward the current state

Bring forward the final outputs you will actually use during this planning window. Leave a missing input visible as a dependency rather than rebuilding its rule here. Keep each value’s original unit, period, definition, and date. A stale market, fee, carrier, platform, tax, benefit, or similar input returns to its owner record for replacement. Carry the updated value and source date here rather than creating a second source record.

​
Choose the active work

Schedule the unresolved decision that matters now and any dependency it genuinely requires. A business still testing its basic offer uses the validation owner first. A mature operation may be testing sourcing, venue, demand, or a diagnosed capacity constraint. Park work whose question, budget, or operating capacity is not yet clear. Complete one record for each active experiment or decision:
Owner and question: ___ Baseline: ___ One change being tested: ___ Cash budget: ___ Time budget: ___ Capacity dependency: ___ Outcome measure: ___ Validity rule: ___ Boundary that cannot be crossed: ___ Prewritten result branches: Pause/stop if ___; repair/extend if ___; continue if ___; change ___ if ___. Review owner: ___ Review date: ___

​
Put the work in dependency order

The rows below are calendar slots, not prescribed phases. Add or remove rows to fit the active work.

​
Set the operating rhythm

​
Keep a small decision scorecard

Use only measures tied to the work and branches in this plan.

​
Commit the branch order

Apply these rules in order at every review:
  1. A hard boundary breach or unresolved required record invokes pause/stop, even when the test is incomplete.
  2. If no hard boundary was crossed but the test was invalid or incomplete, use repair/extend.
  3. Only a valid test that stayed within its boundaries can reach continue or change one variable, according to the result written before launch.
Pause/stop: ___ crosses ___, a required record remains unresolved, or ___ occurs. Next action: ___; owner/date: ___. Repair/extend: The validity failure is ___. Repair: ___. New budget: ___. New review date: ___. Continue: The valid result remains within ___ and produces ___. Next action/owner/date: ___. Change one variable: The valid result shows ___. Change ___; hold ___ constant; owner/date: ___.

​
Record the three decisions

The plan is complete when every active action appears in the schedule with an owner, budget or boundary, measure, branch, and date—and every missing dependency is visible. The first scheduled action is ___, owned by ___, on ___.