Glossary

Touching the Task vs Carrying the Outcome

Touching the task vs carrying the outcome is a distinction from The Control Standard. Touching a task is doing the obviously-yours bit and handing it on; carrying an outcome means keeping your attention on what the work was meant to produce until it is secure. The one-line test: would this still count as done if the result never landed?

Touching the task vs carrying the outcome is a distinction coined in The Control Standard (Chapter 3) to make the difference between doing your bit and owning the result observable rather than abstract. Touching a task is doing the obviously-yours piece — completing the ticket, attending the meeting, sending the deck — after which it leaves your hands; if the next person drops it, that is their problem. Carrying an outcome means keeping some of your attention on the thing the work was meant to produce, noticing when it drifts even after your task is technically done, and only letting go once the result is secure.

Why it matters

It matters because most ownership failures are not failures of effort. Everyone can deliver their part, on time and to a reasonable standard, and the outcome can still quietly fail because nobody was carrying it across the line. That is how a feature ships exactly to spec, sits unused for three weeks, and becomes a "failed investment" in the client's mind — not because anyone was lazy, but because the work was held as a set of tasks rather than as one outcome with a named carrier. Touching is what the system produces on its own; carrying is the standard you have to choose.

The one-line test

Would this still count as done if the result never landed?

If the honest answer is "yes — my part is finished either way", you are touching the task. If the work is not finished in your head until the thing it was supposed to produce has actually happened, you are carrying the outcome. The supporting research on outcome ownership says the same thing in plainer language: the Center for Creative Leadership defines good delegation as giving someone the authority and support to achieve expected results, not merely to complete tasks.

Where it leads

This distinction is the entry point to the four behaviours of real ownership and the posture shift the book builds on next. To put it into practice, see how to take ownership at work and how to delegate outcomes, or the wider ownership pillar. To see where your own work is being touched rather than carried, the drift score is the quickest read — and the full method sits in the book.

Frequently asked

What is the difference between touching a task and carrying an outcome?

Touching a task is completing the obviously-yours bit — the ticket, the meeting, the deck — and assuming the rest will hold once it leaves your hands. Carrying an outcome means keeping part of your attention on what the work was supposed to produce, noticing drift after delivery, and only letting go once the result is secure. Both can be courteous and responsive; only one finishes the job.

How can I tell which one I'm doing?

Run the one-line test: would this still count as done if the result never landed? If finishing your part feels like the finish line regardless of whether the outcome happened, you are touching the task. If the work isn't finished in your mind until the thing it was meant to produce has actually happened, you are carrying the outcome.

Isn't touching the task just normal, sensible work?

Often, yes — and that is the trap. Touching is what most workplaces train for: tickets close when the obvious work is done, sprints measure delivery not adoption, and nobody's calendar has room for 'check the thing three weeks later'. Carrying the outcome is a deliberately higher standard, not a personality trait, which is why it has to be chosen rather than assumed.

Guide

How to Take Ownership at Work: Raise the Altitude of Your Questions

To take ownership at work, own the outcome rather than the task and raise the altitude of the questions you ask. Low-altitude questions handle the detail; high-altitude questions reach for the mission and the pain driving the work. Start at the highest altitude you can, confirm you are enabled, then descend to the specifics.

Guide

How to Delegate Outcomes, Not Just Tasks

To delegate an outcome rather than a task, hand over four things together: the outcome the person owns, the standard it must meet, the constraints they must respect, and the check-ins you'll use. Task-handing tells people what to do; outcome-handing makes them responsible for whether it actually works.

Topic

Ownership: How to Own the Outcome, Not Just the Task

Ownership is holding yourself responsible for whether the work succeeds — not just for finishing your part of it. An owner believes in the mission, steers toward the outcome, and asks questions at the altitude of someone driving the work rather than being driven by it. The book treats it as a visible behaviour, not a job title.

← Back to the glossary