What Does It Mean for Work to Be 'Under Control'?

Ask ten people whether a piece of work is "under control" and you will get ten gut feelings. The phrase usually means little more than "I haven't heard anything alarming lately" — which is not the same as control at all.

Here is a sharper definition. Work is under control when uncertainty has been converted into a usable control point. Concretely, that means four things are in place:

• An owner — one named person accountable for the outcome, not the whole team.
• A dated next step — the very next action, with a date. A next step without a date is a sentiment, not a plan.
• A decision or escalation date — the point by which a choice must be made, or the issue goes up.
• A fallback — what happens if the plan does not work.

When those four are present, the work might still go wrong — but it can no longer drift quietly, because the next missing piece is always obvious.

Key takeaways:

• Work is under control when it has a named owner, a dated next step, a decision or escalation date, and a fallback.
• Control is not surveillance — it is a standard that makes work easy to trust, so people can act without being chased.
• Busy is not the same as controlled: a team can be fully occupied and still be drifting toward a surprise.
• The failure that matters is surprise, not difficulty — controlled work can still go wrong, but not silently.

Control isn't surveillance — it's a standard for trust

Control is often misheard as surveillance: dashboards, status meetings, someone checking whether you are really working. That is the opposite of what the word means here. Control is the practical operating standard that makes work easy to trust — so people can act on their own without being chased, and so you can look away from a piece of work knowing it will not quietly fall over.

At the level of a single task, that standard is the four-part control point above. At the level of a team or a whole organisation, it is the same idea written as five habits:

• Ownership is named — every important outcome has one accountable person, not a committee.
• Next steps are dated — commitments carry a date, so "soon" cannot hide a slip.
• Decisions are scheduled — choices have a point by which they will be made, rather than drifting until someone finally forces them. Deciding who may make which call in advance is a matter of clear decision rights.
• Drift is visible early — the signals that work is sliding reach someone who can act while it is still cheap to correct.
• Repeated pain becomes system improvement — when the same problem recurs, it gets fixed at the source rather than rescued again.

None of that requires watching people. It requires making the state of the work legible. That reframing — from oversight to legibility — is how The Control Standard defines control, and it is the standard the diagnostics on this site measure real work against.

Why "busy" fools us

Busyness fools us because drift hides inside effort: everyone is working, tasks are moving, and the work feels handled. But, as covered in the drift tax, busyness is exactly the camouflage under which work slides sideways. Control is not a feeling of busyness; it is the ability to predict and steer the outcome. That distinction is why the project-management profession treats monitoring and controlling as ongoing work rather than a status report — the Project Management Institute's A Guide to the Project Management Body of Knowledge (PMBOK Guide) defines a dedicated Monitoring and Controlling process group whose job is to track, review and regulate progress against the plan, not simply to record that people are busy.

What it looks like in practice

Work under control looks like a vague status turned into four concrete answers. Take "the supplier integration is in progress." That is not a control point; it is a feeling. Putting it under control means answering the four questions out loud: Priya owns it. The next step is her sending the test payload by Thursday. If the supplier hasn't confirmed by the 28th, we escalate to their account manager. If they can't deliver in time, we ship with the manual import as a fallback. Nothing here guarantees success — the supplier might still be late — but the work can no longer drift, because the moment any of those four answers stops being true, it shows.

That is the whole move: turning "in progress" into an owner, a dated next step, a decision date and a fallback. Do it for the handful of things that actually matter and the rest of the noise gets quieter on its own.

Surprise is the real failure

Surprise is the real failure, not difficulty: a controlled project is not one where nothing goes wrong, but one where nothing goes wrong without warning. Difficulty is normal. Surprise means the signals that something was drifting never reached anyone who could act — and the evidence is that most projects come unstuck this quiet way rather than through dramatic collapse. The Standish Group's long-running CHAOS research has for decades found that fewer than a third of projects finish on time, on budget and on scope; the majority slip gradually, which is exactly the kind of failure control is meant to surface early.

"Bad news early is not a failure. Surprise is." — The Control Standard

When the same thing keeps drifting

The last of the five habits — repeated pain becomes system improvement — is what separates a controlled team from one that is merely good at firefighting. A control point puts one piece of work right once. But when the same drift keeps returning — the same chase, the same late sign-off, month after month — patching it again is just paying the drift tax on a standing order. The durable move is to systemise the recurring pain: decide whether that repeated work deserves a clearer process, an automation, or purpose-built software, rather than another rescue. Drift tends to collect in a handful of predictable places, so the same few pains are usually the ones worth systemising first.

That reframing — from "did anything go wrong?" to "were we surprised?" — is the heart of how The Control Standard defines control. The book works through how to build and run those control points across real, messy work, and the free Drift Report below scores where your own work is drifting right now in about five minutes.