Skip to content

VOOCS · Element 2 of 5

Outcomes: measure it.

What does done look like, and how will we know?

By Russ ReederUpdated October 2026

Outcomes is the second element of VOOCS, the execution framework Russ Reeder built. It answers: what does done look like, and how will we know? Every initiative gets three things before the work starts: a metric that defines success, a target specific enough to be falsifiable, and a deadline that creates urgency. The verb is measure it, because if you cannot measure it, you cannot close it.

What breaks without outcomes

Russ Reeder's rule for Outcomes, the second element of VOOCS, is that nothing starts without a definition of done specific enough to be proven wrong. Without it, teams report effort instead of results, and at the end of the quarter nobody can say whether the work succeeded.

Most companies track activities instead of outcomes. "We shipped 47 features" sounds impressive until you realize only eight are being used. Activity masquerades as impact.

If the team is busy but not finishing, you have an outcomes problem. The fix is to define what "done" looks like before anyone starts.

What to build

  • MetricThe one number that says whether the initiative worked, chosen before the work starts. Not a list of activity counts, and not a number picked afterward to fit the result.
  • TargetSpecific enough to be proven wrong. "Improve customer satisfaction" is not an outcome. "Increase NPS from 32 to 45 by Q3" is.
  • DeadlineThe date that turns an aspiration into a commitment and gives the cadence something to close against.

How you know outcomes is working

In my experience, you know Outcomes is working when "done" stops being a debate. Every initiative has a number the whole team can point to and say: that is what we are building toward. Status meetings get shorter, because the question is no longer how busy everyone was. It is whether the metric moved, against the target, before the deadline.

Defining outcomes forces clarity about what actually matters, and most organizations prefer comfortable ambiguity.

Where outcomes fits in VOOCS

VOOCS runs in order: Vision, Outcomes, Ownership, Cadence, Systems. The mantra is the same five verbs: define it, measure it, own it, close it, scale it. Start with the element where the pain is, fix it, then move to the next.

  1. 01VisionWhat are we doing, and what are we saying no to?
  2. 02OutcomesWhat does done look like, and how will we know?
  3. 03OwnershipWho owns it? One name, not a team.
  4. 04CadenceWhat rhythm forces closure?
  5. 05SystemsWhat runs without a hero?