Fifty-one out of a hundred.
That was the score on a piece of writing I was about to send. I had read it twice. It was fine. It was clear, it was polite, it said what it needed to say, and if you had shown it to me in a meeting I would have nodded and moved on.
Fifty-one.
The reason came with it, and it is nine words long:
The email reads like it could be sent to anyone.
I want you to notice what happened there, because it's the entire chapter.
I couldn't argue with that. Not because the machine has authority, it doesn't. Because the sentence was specific enough to check. I read the thing again with that one accusation in my head and it was true, obviously true, true in a way I had read past twice.
Fine isn't a standard. Fine is what work looks like when nobody has measured it.
Nobody has ever told you where the line is.
Think about that. You have produced work for years. Somebody occasionally said it was good, somebody occasionally sent it back, and in between you developed an instinct for good enough that has never once been calibrated against anything.
That instinct is mostly a measure of how much time you had.
And it's the single biggest cap on what you produce, because you stop when it feels done, and it feels done long before it's finished. Not through laziness. Through having no signal that tells you otherwise.
You can now have that signal, in the time it takes to read a paragraph, on anything you make. Almost nobody asks for it.
The instruction is this simple.
Score this out of 100 on five dimensions: hook, audience, proof, emotion, call to action. For each one give the score, one sentence on why, and one fix. Then tell me how many points each fix would gain, and rank them highest first.
That is it. That is the technique. What comes back isn't a compliment or a criticism, it is a structure you can act on · the difference between this could be stronger and your opening assumes they remember the last conversation, and they don't.
Four things in that instruction are doing the work.
Named dimensions, because one overall score tells you nothing about where to spend the next ten minutes. Mine are the five above and I have reused them for a year:
Hook. Does the first line earn the second. Audience. Is this written for the actual reader or for a general one. Proof. Is there evidence, and is it near the claim. Emotion. Does it acknowledge what they're worried about. Call to action. Is the next step obvious and easy.
Use different ones if your work needs them, but choose ones that mean something. Clarity and quality aren't dimensions, they're moods, and a score against a mood is a mood with a number on it.
A reason per dimension, because a number without a reason is just an opinion with a decimal point on it. If it scores your opening 60 and can't say why, the 60 is noise.
One fix, not three. Ask for three and you get a wish list. Ask for one and you get the thing that actually moves it.
And a price on every fix, which is what turns feedback into triage. This could be stronger is advice, and advice is a thing you nod at. Fix the opening and you gain fourteen points, tighten the close and you gain three is a decision about where the next ten minutes go, made before you have spent any of them.
One more, worth stealing for anything that arrives as a list: make every row end in a verb. A scored list is information. A scored list where each row says what to do about it · `fix now`, `fix if time`, `note it`, `leave it` · is a decision already made, and you are executing a queue somebody sorted rather than reading a report and deciding. Options, risks, candidates, suppliers, findings. Never accept a ranked list without a verb on every row, because a ranked list still leaves the whole decision with you, which is the work you were trying to hand over.
I have described this without showing you one. The 51 at the top of this chapter came back as a single number and one sentence, which is what you get when you ask for a score and nothing else, and it is why the rest of this chapter exists.
So here is the fuller thing, on a different piece of work · a follow-up email to somebody who turned down a proposal six months ago and is being approached again. Run against five named dimensions, with normal defined.
| Dimension | Score | Why | One fix | Points | > |---|---|---|---|---| > | Hook | 42 | The first line explains who you are. The reader knows who you are. | Open on the thing that changed since you last spoke. | +14 | > | Audience | 51 | Written for a general commercial reader, not for someone who has already turned this down once. | Name the objection they raised last time in the second line. | +9 | > | Proof | 68 | The claim about turnaround sits three paragraphs from the only number supporting it. | Move the number next to the claim. | +6 | > | Emotion | 44 | Does not acknowledge that the last attempt failed and they are being asked again. | One sentence naming it before the ask. | +11 | > | Call to action | 60 | Asks them to “let me know your thoughts”. | Replace with one dated, binary ask. | +8 | > > Overall 51. Ranked: Hook +14, Emotion +11, Audience +9, Call to action +8, Proof +6.
Look at what that is and is not. It is not a critique, and it is not encouragement. It is a queue, sorted, with the arithmetic already done, and the top line is worth nearly three times the bottom one.
Now watch what most people would have guessed. Ask anybody which line of that email is weakest and they say the call to action, because it is the visible one, the one everybody has been told about, and the one they know how to fix. It scores 60 and it is worth eight points. The opening is worth fourteen, and the opening is the part that had already been read twice and approved.
That is the pattern, and it is why the ranking column earns its place. You are drawn to the problems you already know how to solve, and your instinct about which problem matters is wrong in a direction you cannot catch from the inside, because the problems you cannot see do not announce themselves as problems. They read as finished.
Do the top-ranked fix. Do not do the list · the list is how you spend an hour and gain twenty points that a re-score will not give you credit for, because you will have broken something else on the way through.
And then the part that's genuinely uncomfortable: you have to be willing to act on a bad score for work you already liked.
There is a problem with everything I have just told you, and it is the reason the scoring habit fails for most people who try it.
Ask a thing to score its own work and it drifts high. Most of the time it hands you ninety-one. The number is sincere and it's worthless, because nothing has told it what the range means.
The fifty-one at the top of this chapter is the exception, and the exception is why I went looking. An uncalibrated score that comes back low is worth paying attention to precisely because the pull is the other way.
The fix is one sentence and it is the most valuable clause in this chapter.
95 and above is exceptional and rare. Most first drafts land between 76 and 88. Score accordingly.
That is calibration. You have supplied the distribution, so the score now sits inside a scale that exists rather than floating in one it invented. A 79 means something. A 91 has to be earned against a stated bar rather than awarded out of politeness.
Use whatever numbers match your world. The specific figures matter far less than the fact that you gave it any, and the difference in what comes back is not subtle — the same piece of work that scored 91 unprompted has, in my experience, come back in the high seventies once normal was defined.
That number in the high seventies is the useful one. It is the one that was scored against a stated bar.
Then close the loop from score to action, because a low score you have to interpret is a task you will not do.
For any dimension scoring under 82, give me one question that would fix it. Maximum twenty words. No preamble. One ask.
Not a paragraph of advice. One question, under twenty words, which you can answer in thirty seconds and act on immediately. That constraint is doing the work. Given room, it will hand you a considered essay about your opening, and you'll read it, agree with it, and change nothing.
Here is the trap, and everyone falls into it once.
You score something, it comes back 62, and you think: well, 62 is not bad for this kind of thing.
You just moved the bar. You moved it after seeing the score, which means the bar is now whatever your work happens to be, which means you have built an elaborate mechanism for confirming that everything you do is acceptable.
Decide the threshold before you see the number. Write it down if you have to. And set it above the top of the normal range you just described. If ordinary first drafts land in the eighties, a bar of 75 passes everything and measures nothing. And a bar of 88 is no better, because 88 is the top of the range you just called normal. This doesn't go out below 92.
We do this structurally, and I want to give you the rule before the numbers, because the numbers are only the rule made checkable.
The rule is one sentence and I have been saying it to people for years. We only write to somebody if there is a value add · if we are serving the person receiving it, telling them things they did not know, and going past what they expected of us.
That is easy to agree with and impossible to enforce, because on a Thursday afternoon everything you write feels like it serves the client. So it became three tests, and nothing goes to a client until it passes all three.
Does it serve them? Above 75. Does it serve us? Below 20. A message that is mostly working for you is an advertisement, and the person opening it can feel that in the first line whether or not they could name it. Does it tell them something they did not already know? Above 60. If they finish it no better informed than they started, we have taken their time and given them a feeling.
All three. Any one fails and the thing does not go, no matter how well written it is · which is the whole point, because well written is exactly how a self-serving message gets sent.
Read the middle one again, because it is the one nobody builds. Everybody has some version of is this good. Almost nobody has is this actually for them, and that is the test that separates a firm people stay with from one they tolerate.
There were four for over a year. The fourth required the serving score to beat the self-interest score by at least 40. It is still in the file. It has never once rejected anything, and it never could have: the first gate puts serving above 75 and the second puts self-interest below 20, so the gap is never less than 55, and 55 always clears 40. A gate that can't fail isn't a standard. It is a decoration that makes a list look more rigorous than it's, and it survived a year of use because nobody applied the question this chapter is about to the mechanism doing the checking.
There is a smaller structural version of the same idea. For our most sensitive category of outbound writing, the system is capped at 60 and cannot score itself higher. Not because that work is worse. Because a system that can award itself top marks on its most consequential output will, eventually, do exactly that.
Count your own gates. Then work out which of them has ever actually stopped anything, and which of them is about the reader rather than about you.
The instruction that sits above those gates is one line, and it's the whole posture of this chapter:
HONEST SELF-ASSESSMENT: reject your own work if it's mediocre.
You won't do this reliably by intention. Intention is what fails at 6pm on a Thursday. You do it by writing the threshold down first, when you're calm and nothing is at stake, and then treating it as though somebody else set it.
One thing this chapter deliberately does not cover, because it belongs next door. How much to trust the number the tool gives you about its own confidence is chapter 7's problem, not this one. Here we're setting your bar, not testing its certainty.
A scoring system that grades itself against its own opinion of good is a closed loop, and closed loops drift somewhere pleasant and stay there.
So one thing in ours isn't negotiable. Every day, a job sends me three variants of a piece of writing. I reply with three integers between 0 and 100. That is the whole interaction. Thirty seconds.
Those numbers go into a file that shapes how everything downstream is weighted, and the rule sitting at the top of that file is written in blunt language on purpose:
GROUND TRUTH RULE: John's scores are the truth. Not Claude's opinion.
If the reply can't be parsed, it asks again. It never silently drops a score, because a missing score that quietly becomes an average is worse than no score at all.
Thirty seconds a day, at exactly one point in the process, and that point is the scoring point. Everything else runs without me.
That is the shape to aim for in your own work. You aren't trying to check everything. You are trying to be the ruler that the measuring is calibrated against, and to be that in as few minutes as possible.
I have given you a technique. Now the reason it matters, which is not accuracy.
A number is something you can hand to another person.
I think this is good is not transferable. It ends the conversation or it starts an argument about taste, and in either case the most confident person in the room wins.
This scored 51, and the reason was that it reads like it could be sent to anyone is a completely different object. Your colleague can disagree with the dimension. They can disagree with the weighting. They can say the score is wrong and explain why. All of that is progress, and none of it is available when the alternative on the table is somebody's feeling.
This is what your senior people actually want and rarely get. Not certainty. Something they can push on. A recommendation that arrives with its own scoring, its alternatives, and what those alternatives scored, hands them the ability to interrogate it in ninety seconds instead of asking you to go away and think again.
That is the difference between being someone who submits work and being someone who is trusted with decisions. And it isn't a personality trait. It is a habit of attaching numbers to things.
There is one way to do all of the above and get nothing from it, and it is common enough to be worth naming.
You start scoring things. You enjoy it. Six months later there is a drawer full of numbers and nobody has ever checked whether the high-scoring work actually did better than the low-scoring work.
A scoring habit that has never been tested against an outcome is a ritual. It feels like rigour and it is decoration.
The fix costs twenty seconds a time. For one month, write down the score and write down what happened · the reply, the decision, the silence. That single column is the difference between measuring something and performing measurement, and almost nobody keeps it.
One thing, on the next piece of work you were about to call finished. Score it before you send it.
The first time you do this you'll find something. Everybody does. And the version of you that ships the fixed one isn't the same professional as the version who shipped the first one, which is what the last chapter of this book is going to be about.
But there is a step before that, and it's the one people skip because it looks like extra work rather than the thing that makes all of this affordable.
Because so far I've had you asking one system, checking one system, scoring one system. And the whole time, the person sitting next to you has been getting worse answers for more money by doing exactly that.
---
### ▪ DO THIS > > Score the next thing you were about to send, before you send it. > > 1. Write your threshold down first, and put it above your normal range rather than inside it. This does not go out below 92. A bar set inside the range passes everything and measures nothing. > > 2. Paste this under your work. > > > Score this out of 100 on five dimensions: hook, audience, proof, emotion, call to action. > > > > 95 and above is exceptional and rare. Most first drafts land between 76 and 88. Score accordingly. > > > > For each dimension give the score, one sentence on why, and one fix. Tell me how many points each fix would gain and rank them highest first. > > > > For any dimension under 82, give me one question that would fix it. Maximum twenty words. No preamble. > > 3. Do only the top-ranked fix. Not the list. The one worth the most points. > > 4. Re-score. If it meets your threshold, send it. If not, do the next fix. And stop after two. A third pass on the same piece is the too-deep failure. > > Takes four minutes. > > When it scores below your bar and the deadline will not move: send it, write the score down, and fix the pattern next time. A rule that only works on unhurried days is not a rule. > > > You will know it worked when a piece of work you had already decided was fine comes back under your own threshold. And you fix it anyway.