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

You take ownership at work by owning the outcome rather than the task — and the fastest way to make that ownership real, and visible to everyone around you, is to raise the altitude of the questions you ask.

Own the outcome, not the task

A task tells you what to do; an outcome makes you responsible for whether it works. Taking ownership means living at the outcome. You don't just deliver the designs, the report or the fix — you hold yourself responsible for whether the thing actually solved the problem, and you keep steering until it does. This is the receiving end of the line between delegating a task and delegating an outcome, and it starts with the mission. If the mission was written by someone else, you do not simply inherit it — you interrogate it until it is yours, because once you own the work you own whether its direction is right. This is a narrower cousin of the extreme ownership Jocko Willink and Leif Babin drew from military command — leaders owning everything in their world, including their team's failures¹ — scaled down to the specific outcome you hold rather than the whole organisation.

"A recommendation you are half-sure about is more useful than a description you are fully sure about." — The Control Standard

Altitude: the visible signal of ownership

You cannot tell who owns the work by watching people work; everyone looks busy. You can hear it in their questions. Picture a scale of altitude, from task-touching at the bottom to the boardroom at the top:

• Lowest — task level: "Do you have existing branding for the app?"
• Higher: "Who are your competitors?"
• Higher still: "What does the product actually do, and what problem does it solve?"
• Near the top: "What's the mission? Who is this really for?"
• Highest: "What pain is driving this — for the business and for the people in the room?"

Low-altitude questions signal low ownership by definition: they are aimed at finishing a task, not steering an outcome. High-altitude questions show you are trying to get to what really matters. The rule is simple — start at the highest altitude you can reach, then descend. Get the pain and the mission first; the button colours come last, not because colour doesn't matter, but because you cannot judge the colour well until you know what the work is for.

Climb to the pain before you do anything else

At the very top of the altitude scale sits the thing most people never ask about: what is emotionally driving the work. Almost everything a stakeholder does is solving a pain or reaching for something better, in the present or the future — and present pain is the strongest driver of all. There is business pain ("we've had a bad quarter") and personal pain (the finance director who privately fears for his job if the board doesn't see progress fast). Until you understand those, you can deliver exactly what was asked and still aim the whole effort in the wrong direction.

This is why decades of organisational research treat psychological ownership — the feeling that a piece of work is mine — as a distinct driver of how hard people fight for an outcome, not a synonym for being assigned it.² Owners reach for the pain because that is where the real goal lives. Once you have it, you can sit on the stakeholder's side of the table and help them rewrite the plan — push a six-month timeline down to a quick win, or move something into version one because you now understand why it matters to them.

Confirm you're actually enabled

Ownership without clear decision rights is a trap. If you are handed work mid-flight, there is a baseline you must have before any of the detail is worth discussing — above all, the mission. Don't assume the people around you have it right; assume the whole team could be running confidently in the wrong direction and that you might be the one to catch it. Ask the highest-altitude question you can — "I think the position is X; am I right?" — and watch the answer.

A good test: someone who truly understands the work can debrief you in about two minutes and leave you feeling clear about where the gaps are. If they can't, the legwork hasn't been done — and that, not your inexperience, is the problem to solve. Go back to the source materials or the client. This is the same delegation that has to hold in both directions: if it hasn't, treat it as a system fault, not a personal one.

Match your intervention to the constraints

Owning the work does not mean steamrolling it or calling a two-hour meeting for every decision. Once you've asked a high-altitude question, the right level of intervention is usually obvious. If the person clearly has it, a 30-second steer — "it's not A, it's B, for this reason" — is enough, and they crack on. If they don't, you zoom out and do the real work. In your own area of expertise, drop the unhelpful belief that they're already all over it and adopt the helpful one: your judgement is the one that has to be disproven. The level of intervention flexes with the constraints of the project; the altitude of your thinking should not.

Done consistently, this is what makes other people say that was great ownership — and it is the same instinct that keeps work under control rather than drifting while everyone stays busy. When you want to manage it upward so the people above you can act, pair it with a useful status update. If you'd like a fast read on where your own work is routing through you and quietly drifting, the free Drift Report below scores it in about five minutes.

1. Jocko Willink & Leif Babin, Extreme Ownership: How U.S. Navy SEALs Lead and Win (St. Martin's Press, 2015).
2. Pierce, Kostova & Dirks, "Toward a Theory of Psychological Ownership in Organizations," Academy of Management Review (2001).