Handing work over
Say why, not just what
The purpose governs a hundred decisions nobody will review. One specific sentence, naming who asked and what they will do with it.
Decisions this page is about, and where the line actually was
Changing the wording on a customer-facing error message
4 → 1It had been yours all along
Picking the library for the new parser
1 → 4The architect had a standing view
Rescheduling the weekly review
2 → 2Changing a database column type
1 → 1- 1Decide it alone and say nothing
- 2Decide it alone and mention it afterwards
- 3Check with one colleague first
- 4Check with the person who assigned it
- 5Needs a decision one level up
- 6Cannot be decided here at all
four decisions · one of them you had more room than you thought · one gave you less · two you had exactly right · the median gap was three steps on the scale
Four of the nine decisions counted on this site, two of them exact.
When responsibility is handed over without enough context, Monitask productivity insights can help a team compare project time and workload before treating delay as an individual failure.
For an independent perspective on management and working practice, consult World Economic Forum.
The receiver is about to make a hundred small decisions that nobody will see: where to stop, what to leave rough, which edge case to ignore, how much detail is enough. They will resolve every one of them using their understanding of why the work is wanted.
So that understanding is the most leveraged sentence in the handover, and it is the one most often replaced by a plausible substitute.
The test for whether you have written it
Read your purpose sentence back and ask whether it rules anything out.
"Improve the import reliability" rules nothing out. Every approach improves reliability somewhat, so the sentence constrains none of the hundred decisions it was supposed to govern, and the receiver is exactly where they were before reading it.
"A named customer complained twice and the renewal is in March" rules out a great deal. It rules out the architectural rewrite. It rules out anything the customer will not see. It rules out finishing in April.
That is the whole test and it takes four seconds to apply. If the sentence would be equally true of three completely different pieces of work, it is a goal rather than a purpose, and the person reading it will have to guess anyway.
The usable form is almost always a named party and a date. Those two together do more work than any amount of explanation.
The sentence
Name who asked and what they will do with it:
This is for the board pack in March, because they asked a question in January that nobody could answer. It needs to be readable by somebody who does not know the system.
Two clauses of reason and one of consequence. The consequence clause is what converts the purpose into something actionable.
Why people write the dignified version instead
Three reasons, all ordinary:
- It feels like politics. Naming a customer, a renewal or an executive's discomfort reads as less professional than naming a goal, so the professional version gets written.
- It feels obvious. The person handing over sat in the meeting where it was discussed and cannot reconstruct not having been there.
- It is genuinely unknown, because the work has come down through two people and the purpose was lost at the first handover.
The third deserves saying out loud rather than papering over: "I do not actually know who asked for this" is useful information, and it tells the receiver to go and find out before making a hundred decisions on a guess.
The half test
If you cannot write the sentence, try this instead and write down your answer:
If we could only do half of this, which half matters?
Nobody can answer that without revealing the purpose. The answer is usually a better purpose statement than anything produced by trying to write a purpose statement, because it is forced to be specific about what the work is for.
When the real purpose is awkward
Sometimes the honest sentence is uncomfortable. The work exists because an executive was embarrassed, or because a customer threatened to leave, or because somebody senior has a theory that nobody has tested.
Three reasons to say it anyway.
The receiver is operating inside that politics regardless. Withholding the map does not keep them out of the territory; it means they navigate it blind and make choices that look naive to everybody who knows.
The awkward purpose is usually the one that governs the trade-offs most sharply. "The renewal is in March" tells you exactly what to cut. "Improve reliability" tells you nothing.
And the receiver will work it out. They always do, around week four, from context — at which point they also learn that it was not said, which costs more trust than the saying would have.
Where the real reason genuinely cannot be shared, the usable compromise is to give the consequence without the cause: "this has to be done by March and it has to be visible to that customer — I cannot say more than that." That is honest, actionable and considerably better than a substituted reason, which is the option most often taken and the only one that actively misleads.
What it costs to leave out
On the record counted on this site, the purpose was the slot that produced the most expensive single failure: a piece of work that had already shipped went back four stages, to the brief, because the audience turned out to be different from the assumed one.
Nothing in the first version was wrong. Every decision in it was correct for the reader it assumed. The gap was one sentence, and the sentence would have taken about fifteen seconds to write.
That is the whole argument for this slot, and it generalises: the purpose does not change what the work is, it changes every judgement inside it, which is why its absence is invisible until the end.