← Back to the full chapter
Lesson

What to build

Connect offers, prices and retention to constraints, experiments and measured outcomes.

1 min read40 hours / case practice planApplied extensionUpdated
Read source ↗

A business decision system with an evidence report. Choose one guide and follow the delivery plan. Publish the decision brief, data contract, model comparison, policy comparison, experiment protocol, batch/API contract, monitoring and rollback artifacts. For private business data, publish code and synthetic examples instead of customer records.

Keep three evidence levels separate in the report:

EvidenceWhat you may claim
Synthetic simulator with known effectsThe pipeline and policy work under the simulator's assumptions
Retrospective public or business dataPredictive performance on that held-out population; causal effects only when the design supports identification
Valid randomised policy experimentAn estimated effect of that policy in the tested population, period and operating conditions

A finished prototype can have an experiment proposal and a rehearsed rollout. A measured live profit lift needs executed assignments and observed outcomes. Say this plainly.

Something unclear or out of date? Suggest a correction ↗

Find your next idea

Loading local search…

Search is built from this edition. No account needed.