A 10 Is Built Down, Not Up.
Ask anyone to make something excellent and you get a feature list. More polish, more structure, more rigor. None of it wrong. None of it a ten. The list adds weight without adding judgment, because it never says what the thing is defending against.
A ten is not built up. It is built down.
The move
Name the failure modes a mediocre version of this would have. Then design each feature as a defense against one named failure mode. Now every component has a reason to exist that you can point to. The ones that don't defend against anything, you cut.
Four ways AI pilots die
I watch AI pilots die of the same four failure modes. A strong deployment is designed against all four before a single feature gets built.
It doubles as a review method
This is also the fastest upgrade I know for giving feedback. "Make it better" gets you a polite nod and nothing changes. "Name the failure modes a typical version of this would have, then show me how each one is defended" gets you a different plan and a sharper person.
The tell that a plan is a five: it can list its features, but it can't say what it would do badly if it were average. Strong work knows what it is refusing to be.
It works on briefings too
A typical executive briefing fails in known ways. It runs as a product tour. The wrong people are in the room. Nothing is decided at the end. Design the day against those three and most of the agenda writes itself.
A plan that can't name what it refuses to be isn't a ten. It's a list.
If you run customer programs or executive engagement and you are working through this inside your own team, I'd like to compare notes.