Skip to content
unfsckd
← Guides

The 10-out-of-10 method, explained

Define what “right” would actually look like, score where you are, and the gap between them becomes the work — priority-ranked, by you.

By Antony Loomans · The Deliverators · 6 min read

Most diagnostic questions are unanswerable. “Is the project on track?” invites a defensive paragraph. “Are we managing risk well?” invites a shrug. The 10-out-of-10 method replaces the paragraph with a number — and the number does work the paragraph never could.

The two questions

It’s two questions, asked in order. First:

“If this were delivering at 10 out of 10 — what would that actually look like?”

Not aspirational. Concrete. What would 10/10 budget tracking look like? 10/10 stakeholder alignment? When you force a team to describe 10/10 in specifics, the nice-to-haves fall away and the things that actually deliver the benefit come into focus. The definition of “right” gets honest.

Then the second:

“Where are we now? And what’s the gap?”

The gap between your score and 10 is the work. Not the original plan. Not the inflated scope nobody had a reason to remove. The actual, honest, priority-ranked work that would move this from where it is to where it needs to be.

Why a number beats a narrative

  • It’s safe. “I’d rate us a 6” opens a conversation. “I think this project is in trouble” closes one. The number lowers the cost of telling the truth.
  • It’s comparative. When one person says 8 and another says 5, you don’t have a disagreement — you have a diagnostic. The spread points straight at the conversation that needs to happen.
  • It’s forward-looking. Most reporting looks backward. The 10/10 framing asks what “right” looks like from here, given what you now know — not what the plan said a year ago.
  • It tightens scope. Defining 10/10 in terms of the promised benefit makes the bloat visible.

The five steps

Running it is deliberately mechanical:

  • 1. Pick the template that matches the situation — start with the one that feels most urgent.
  • 2. Share it independently. Same template, given to each person separately. Not a committee.
  • 3. Compare the answers. Lay them side by side; the divergence is the signal.
  • 4. Define 10/10 together. With the scores on the table, agree what 10/10 means from here.
  • 5. Decide. Continue, rescope, or stop — with evidence.

Where it came from

This isn’t a worksheet someone invented on a Tuesday. It’s how we work — thirty years of walking into projects already in flight and needing, fast, an honest read that a room of people would actually say out loud. The number is the trick that makes honesty cheap enough to share.

Every unfsckd template runs on it, and the 5-minute diagnostic is the method applied to delivery confidence — score eight dimensions, watch the gaps, get a verdict. The fastest way to understand the method is to run it once.

See it on your own project.

Five minutes, no sign-up. The gap is the work.

Run the diagnostic →