ship-decisions
Binary go/no-go shipping decisions using reversibility analysis (one-way vs two-way doors) and technical debt trade-offs. Use when user asks 'should we ship this now,' 'ready to ship,' 'one-way door,' 'two-way door,' or 'tech debt vs shipping.' For defining craft levels and deciding what to polish vs defer, see quality-speed. This is the ship decision methodology.
Nodig
- decision — The call to be made
- deadline — When the decision stops being useful
- reversibility — reversible | costly-to-reverse | irreversible
- artifact — Thing being assessed for readiness to ship
Zo vraag je het
- Should we ship this feature or iterate more?
- Is this a one-way door or two-way door decision?
- Balance the technical debt against shipping speed
- Help me decide: ready to ship or needs more work?
Oplevert
- hold-decision (markdown)
- readiness-brief (markdown)
- ship-decision (markdown)
Niveaubeginner
Invoerconversation
Uitvoerdocument
Vereist[none]
Rollen[CEO / Founder, Product Manager]