Skip to content

M03 / EXPLORATION & DELIVERY

How much should you learn first?

Spend a finite week understanding the work—or doing it. Both teach you something.

Allocate ten effort points each week

Drag the bars. Arrow keys also work. A change replays all 20 weeks.

ResearchBuild & ship
Try a pattern

Start with a baseline, then shift effort into the early weeks.

Useful output
Built & shippedpoints before fit is considered
Research effortof 200 available points
Technical mismatchat the end of week 20

What the team knows

World markers are visible to you as the model observer. The team never reads them directly.

Useful output over time

Challenge the assumptions What can each action learn?

Changes apply from week 1 to both plans, using the same seeded world and observations.

Research observes what users need, with noise and diminishing returns. It does not resolve technical uncertainty. Shipping exposes technical mistakes and gives a weaker signal about needs; those observations arrive after the selected delay.

Useful output = build effort × exp(−2.8 × need error − 2.4 × technical error). This is an illustrative fit score, not a forecast or financial value. No staffing, rework, task sizes or learning between team members.

All observations and weights used by the team are shown above. Your plan stays in this browser. Read the engine.