Most stalled work is not lazy. It is vague. Nobody decided what done actually means, so the work drifts.
This lesson is about turning one vague thing into one clear thing.
Outcome versus task
- A task is something we do.
- An outcome is what should be true when the work is done.
Task: make a report. Outcome: leaders can see blocked orders each Friday and act before delays grow.
Tasks keep people busy. Outcomes tell you whether the busyness mattered.
What “done” means
“Done” has to be a specific, observable thing. The test:
If two reasonable people could disagree about whether it is done, it is not yet defined.
Settle that disagreement now, in the planning, not three weeks later in a stand-up.
A goal with a measure
Use this pattern:
We will improve [thing] so that [result]. We will know it worked when [measure].
The measure is the part people skip, and it is the part that matters.
A goal without a measure is a wish. A goal without tradeoffs is a wish list.
Pressure-test your measure with one question: Could a neutral observer from outside the team tell whether this outcome was met? If the answer is no, the measure is still too soft.
Name the tradeoff
Strategy is choice. Before you start, name at least one specific thing this work will not try to solve this round. If the “not doing” list is empty, the goal is probably still too big.
Try it on real work
Take one project your team is starting or restarting, and write it as an outcome: the outcome sentence, the measure, the owner, the first check-in date, and the one thing you are choosing not to do. The Outcome Brief below walks you through exactly those fields.
Open the Outcome Brief (opens in a new tab)
Check yourself
Did it land?
Quick self-check. Nothing is scored or saved — it is just a way to test your own understanding before you move on.
Saved in your browser only. Nothing is uploaded.