Ask a team whether they are ready for a review they have to pass and you will usually get a hedge. Nearly ready. Mostly there. One or two things to tidy up. That answer feels polite, and it is the most expensive thing a team can tell itself, because reviews do not grade on a curve. A gated review behaves like a vehicle inspection: one worn part fails the whole thing regardless of how clean everything else is. The reviewer is not weighing your effort. They are looking for a missing piece of evidence, and finding one is enough.
So the argument is this: a readiness check is only worth using if it refuses to give you a maybe. A tool that returns a percentage, a colour-coded dashboard or a reassuring "you're on track" is doing you a disservice, because it lets you leave with the same comfortable ambiguity you arrived with. What you actually need is a blunt verdict, and a verdict is only credible if one of its possible outcomes is "not ready, and here is the single thing that is missing."
The three answers that matter
A useful check has to be able to send you somewhere else. If every path leads back to the same next step, the questions were decoration. The honest outcomes are narrow: you are ready and you know roughly where you would start; you are not ready and you know which one gap is holding you back; or this is not the right kind of work for the people asking, and there is a better place to take it. That third answer is the one most tools omit, and its absence is what makes the other two untrustworthy. A check that can never turn you away is not assessing you, it is qualifying you.
The same logic applies to the questions themselves. Each one should map to a fact that a build gets sequenced around, not a box to tick. If you cannot answer one, that is not a neutral gap. It is a finding, and it belongs in the result.
Why the not-knowing is the finding
Teams tend to treat an unanswerable question as a reason to come back later. Which review applies here? Who inside the company signs it off? Has a supplier failed this before? These feel like admin, so they get deferred. But a reviewer will ask exactly these things, and a blank where an owner should be is the most common way a pack stalls. Not knowing which review you are facing usually means you have not yet worked out who is asking, and that single unknown reshapes everything downstream.
The temptation is to soften the question, to let "not sure yet" pass as a valid answer and move on. Sometimes it genuinely is one, because one later question settles it. But the check still has to hold you to the consequence: an unresolved review type is a result in itself, not a footnote.
What a good result looks like
A good result is short, unflattering where it needs to be, and specific. It names the band you would most likely start in, or the one thing that is missing, or the honest reason this is not your work. It asks nothing of you before it gives you that. No account, no email, nothing stored or sent. That last part is not a privacy gimmick; it is what lets you answer truthfully instead of answering the way you would want a vendor to see.
If you want the verdict turned into a plan, that is a conversation you choose to start. Nobody chases you for it. The full six questions, the three possible answers and what each one costs to close are laid out in the review readiness check, which is where the actual method lives.
Top comments (0)