duo-experiment-velocity

Drive the marginal cost of an experiment toward zero so a team runs hundreds of tests a quarter instead of three. Covers experimentation as shared internal infrastructure rather than a per-test project, how the cost of the marginal test quietly selects which ideas get tried at all, taking domain owners off the engineering queue for whole classes of test, judging internal analytics tools by non-analyst adoption, building tools that can disconfirm your own beliefs, and curating report templates with standing guardrails that may veto a win. Use when asking why we only run three experiments a quarter, should we build or buy an experimentation platform, how do we let PMs and designers run their own tests, what belongs in every experiment readout, when do we instrument a metric versus compute it by hand, or is a customer-specific fork worth the permanent drag on test velocity.

Version

2.0.0

License

MIT