Outcome-Based Performance Contract
Agree on measurable outcomes before visibility distorts evaluation
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 4
- Confidence
- 97%
Knowledge work is difficult to observe directly, so managers can default to visible proxies: who talks most, works on prominent projects, sends the most messages, or appears busiest. Those behaviours are easy to see but do not reliably indicate impact or leadership. The Outcome-Based Performance Contract moves evaluation upstream. At the beginning of a quarter or half-year, manager and employee agree on clear business outcomes and the tangible evidence that will show progress. The employee then tracks that evidence and uses it as the stable foundation for every performance discussion. This does not eliminate judgment, but it constrains hindsight bias and makes it harder for a recent anecdote or a false perception to replace the work actually delivered. It also stops efficiency from being punished merely because it looks like less effort.
Origin
Orr contrasted objective grades in school with corporate reviews, where creative efficiency was penalized because effort was less visible and managers lacked agreed measures of impact.
Core principles
- 01Judge work by outcomes rather than visible effort
- 02Ambiguity invites anecdotes and bias into evaluation
- 03Agree on evidence before the review period ends
- 04Use the same measures in every performance conversation
How to run it
- 1
Specify the outcomes
At the start of the review period, agree on the concrete business results the role should produce. Keep the focus on impact rather than performative behaviours.
Pro tip Use a quarter or half-year horizon when the work takes time to become visible.
Watch out Do not substitute activity counts for outcomes unless the activity itself creates the value.
- 2
Choose evidence
For each outcome, decide what measurement or observable proof will indicate progress. Record the agreement while expectations are still prospective.
Pro tip Combine a quantitative measure with a defined quality threshold when volume alone can mislead.
- 3
Track impact consistently
Collect examples and measurements against the agreed outcomes as work happens. Make invisible or delayed contributions legible without turning visibility itself into the goal.
Watch out Do not wait until the final review and reconstruct evidence from memory.
- 4
Anchor the review
Use the agreed outcomes and evidence as the foundation for each performance conversation. Address anecdotes only in relation to that shared record.
Pro tip Return to the original measures when a conversation drifts toward personality or hours observed.
In the wild
A strategist agrees that the quarter's outcome is an approved sales narrative that improves pitch conversion, rather than two weeks of visible desk time. She produces a stronger draft in two days and tracks approval and conversion evidence. At review time, the shorter production window is treated as efficiency rather than low effort.
→ Performance is judged by the agreed business effect instead of time visibly spent.
Common mistakes
Agreeing on measures after the work
Retrospective measures can be selected to justify an impression the manager already holds.
Rewarding visible busyness
Messages, meeting dominance, and observed hours become proxies even when they do not correlate with impact.
Is it for you?
Best for
It is best for knowledge workers and managers whose valuable work is ambiguous, delayed, creative, or hard to observe.
Not ideal for
It is not ideal when outputs are already counted directly and the existing measure reliably captures quality as well as quantity.
From the transcript
“instead of measuring people on the outcome of their work we measure them on how they behave um on the way to that outcome”
“ask them for very clear tangible outcomes that they want for the quarter”
“use that as a foundation for every single performance conversation”
From the episode
Marissa Orr: Lean Out - Women, Power and the Workplace
Marissa Orr