What is Ship/No-Ship Decision?
The Ship/No-Ship Decision is the judgment call on whether a software release is ready for production deployment, given the known bugs, risks, and trade-offs.
The Ship/No-Ship Decision is the judgment call on whether a software release is ready for production deployment, given the known bugs, risks, and trade-offs. It is the most critical judgment engineers make — and the skill most under-tested in traditional hiring.
The Audit Interview Protocol specifically evaluates Ship/No-Ship judgment because it reveals:
- Risk tolerance: Does the candidate understand which bugs are showstoppers vs. acceptable? - Customer empathy: Does the candidate consider the user impact of known issues? - Business awareness: Does the candidate weigh the cost of delay vs. the cost of defects? - Communication: Can the candidate explain their decision to non-technical stakeholders?
Why It Matters
In the AI era, Ship/No-Ship decisions are more consequential than ever. When AI generates code, the verification step — determining whether the output is safe to ship — is the highest-value skill in engineering.
Richard Ewing's Audit Interview tool tests this exact skill: candidates review AI-generated code with hidden flaws and must make a Ship/No-Ship decision with justification.
How to Measure
Track the correlation between Ship/No-Ship decisions and outcomes: did shipped releases cause incidents? Did blocked releases have real issues? Over time, calibrate decision quality.
Frequently Asked Questions
What makes a good Ship/No-Ship decision?
The best decisions are evidence-based (citing specific bugs and their severity), risk-aware (considering blast radius), and time-bounded (acknowledging the cost of delay). The worst decisions are gut-feel without analysis.
Related Terms
Need Expert Help?
Richard Ewing is a Product Economist and AI Capital Auditor. He helps companies translate technical complexity into financial clarity.
Book Advisory Call →