Do you avoid using 7/10 when giving feedback?

"7/10" feels like an answer, but it isn't one. It's a number that lets you avoid saying whether something is actually good enough - a way to sound engaged while committing to nothing.

Why 7/10 is a cop-out

When someone asks "how was it?" or "is this good?", a 7/10 score:

• Doesn't say what's wrong
• Doesn't say what's right
• Doesn't say what to do next
• Sounds polite, but is really just sitting on the fence

It protects the reviewer from an uncomfortable conversation, but it leaves the person asking with nothing they can act on. If it's not good enough to ship, say so - and say why. If it's good, say that too - specifically.

Note this isn't a rule against numbers - a score like 8 or 9 out of 10 is fine, and can even be a great way to compliment someone. The problem is the bare, non-committal middle number with no reasoning attached. A decisive score paired with specific feedback is just as good as a pass/fail.

Bad example

❌ Figure: Bad example - A vague score gives the team nothing to act on

Good example

✅ Figure: Good example - A decisive score plus specific feedback the team can act on

What to do instead

• Use pass/fail (or ship/don't ship) when the question is really binary
• If you give a score, make it decisive - an 8 or 9 (or a 2 or 3) says something; a 7 usually doesn't
• Always justify the score - explain exactly what's standing between the score given and a 10
• Lead with the action, not the number - "Not ready to ship because X" beats "7/10"
• Be specific - name the exact things that need to change