Effort Expands to Fill Ambiguity

Category: Incentives, metrics, and consequences Unclear goals invite wasted energy.

A manager once asked an analyst to “take a look at our churn and see what’s going on.”

The analyst was good. He took the request seriously. He pulled two years of customer data and built a cohort model. Then he wondered whether churn varied by region, so he added a regional breakdown. Then by acquisition channel, because that seemed relevant. Then by product tier, contract length, and support-ticket history, because each new cut raised another question that felt irresponsible to ignore.

Three weeks later he delivered a forty-slide deck. It was thorough. It was, in places, genuinely clever. It contained eleven charts, a glossary, and an appendix.

The manager flicked through it, paused, and said: “This is great. But I just wanted to know whether the new pricing was driving people away before the board meeting on Thursday.”

That single sentence — the one that was never said at the start — would have taken the analyst an afternoon. Everything else was effort poured into a space where the question should have been.

Nobody was lazy. Nobody was careless. The analyst worked hard for three weeks, and almost all of that work was real. It was simply aimed at a target that had never been drawn.

And here is the part that stings. If you had asked the analyst, at any point during those three weeks, what he was doing, he could have answered with complete confidence. He was investigating churn. He could have justified every chart. Each cut of the data raised a fair question, and answering fair questions felt like the job. From the inside, it never looked like waste. It looked like rigour. The waste was only visible from the one vantage point he did not have — the manager’s, where a specific decision was waiting for a specific answer.

The Principle

When a goal is unclear, effort does not pause to wait for clarity. It expands to cover every plausible interpretation at once.

A vague instruction does not produce less work. It produces more. Faced with ambiguity, a conscientious person does not stop; they hedge. They cannot tell which version of the task is the real one, so they attempt all of them. They add scope to be safe, depth to be thorough, and caveats to be defensible. The work grows outward in every direction because no edge tells it where to stop.

This is the quiet cost of an unclear brief. It is not that the work fails to happen. It is that far too much of it happens, most of it answering questions nobody asked.

Why It Is Inevitable

Ambiguity creates a vacuum, and effort is what rushes in to fill it.

Put yourself in the analyst’s position. You have been handed something open-ended. You do not want to come back having done too little — that looks like you did not care. You cannot easily ask three more clarifying questions without seeming as though you cannot work independently. So you make a rational trade: when in doubt, do more. Covering every angle feels safer than guessing the one that mattered and getting it wrong.

The incentives reinforce this at every turn. Visible effort is rewarded. A thick deliverable signals diligence. Nobody is ever criticised in the moment for being too thorough; the criticism, if it comes, arrives later and quietly. Meanwhile the cost of the wasted effort is borne mostly by the person doing it, and often invisibly even to them.

There is also a deeper reason. Ambiguity transfers a decision that should have been made by the person setting the task onto the person doing it. The manager did not decide what “look at churn” meant, so the analyst had to. But the analyst lacked the context to decide well — he did not know about Thursday’s board meeting or the pricing question behind it. So he did the only thing an honest person can do without that context: he tried to satisfy all of it. Effort became a substitute for a decision that was never handed down.

This is why it is not a failure of character. Drop a careful, capable person into an unclear task and watch the same thing happen. The work spreads to fill the ambiguity because nothing in the situation tells it where the boundary lies.

It is worth noticing how cleanly this inverts the usual story we tell about effort. We tend to assume that more effort is a sign of more care, and that a person who delivers a great deal has worked hard on the right thing. Ambiguity breaks that link. Under an unclear goal, the volume of effort tells you almost nothing about whether the right work was done. It may even run the other way: the vaguer the brief, the larger the output, because there is more empty space to fill. A sprawling deliverable is sometimes a sign not of diligence but of a question that was never properly asked.

How It Shows Up

• Briefs that begin with “have a look at,” “explore,” “tidy up,” or “see what you can find”
• Deliverables far larger and more elaborate than the question warranted
• People answering several possible versions of a request because they cannot tell which one is live
• Long preambles, glossaries, and appendices added to cover interpretations nobody needed
• Scope quietly widening over time with no decision ever recorded to widen it
• A late, deflating moment where the real question finally surfaces and most of the work proves irrelevant
• Teams unable to say cleanly what “done” would look like, even mid-task

Why It Causes Damage

The most obvious damage is wasted effort, and that alone is expensive. Three weeks of a skilled person’s time is not a rounding error. But the deeper damage is subtler and worse, and it is the part organisations almost never account for.

First, it disguises itself as productivity. The forty-slide deck looks like a triumph of diligence right up until the moment its purpose is questioned. Because the effort is real and visible, it is hard to call it waste. The organisation sees activity and concludes that work is being done, when much of what is being done is filling a vacuum that better instructions would have removed.

Second, the cost lands on the wrong person. The analyst absorbs three weeks of sprawl that originated in a single under-specified sentence from someone else. The person who created the ambiguity rarely pays for it. This quietly teaches the wrong lesson — that clarity is the responsibility of whoever receives the task, not whoever sets it — and the pattern repeats.

Third, it erodes trust in a way that feels unfair to everyone involved. The manager comes away faintly disappointed, having received a deck instead of an answer. The analyst comes away deflated, having worked hard and somehow missed the point. Neither did anything obviously wrong, yet both feel let down. Repeat this a few times and a capable person starts to believe they are not good at “reading what’s wanted,” when the truth is that nothing readable was ever written.

Finally, the genuinely important question gets buried. When effort spreads thin across every interpretation, the one that mattered receives the same shallow attention as the ten that did not. Ambiguity does not just add waste; it dilutes the work that should have been concentrated. The pricing question — the one the board actually needed answered — got one slide out of forty, the same as the regional breakdown nobody had asked about. The thing that mattered most was treated exactly like the things that did not matter at all, because nothing in the brief said which was which.

How To Counter It

• State the decision the work is meant to inform, not just the topic. “Look at churn” becomes “tell me whether the new pricing is driving people away before Thursday.”
• Name the deliverable and its size up front. An afternoon’s answer and a three-week study are different commissions; say which one you are asking for.
• Define what “done” looks like before anyone starts. If you cannot describe the finished state in a sentence, the brief is not ready to hand over.
• Make clarifying questions cheap and expected. The cost of asking three questions is minutes; the cost of guessing wrong is weeks. Build a culture where asking is treated as competence, not weakness.
• Set a boundary on scope explicitly, then let people exceed it only by choice. “Just the pricing question, nothing else unless you flag it first” gives effort an edge to stop at.
• When you catch yourself broadening a task, pause and ask which actual question each addition answers. If you cannot name one, you are filling ambiguity, not doing the work.
• Put the responsibility for clarity where the context lives. The person with the board meeting in their diary is the one who can make the goal clear; expecting the analyst to infer it is asking him to decide something he cannot see.

What Good Looks Like

Work that begins with a sharp question and ends roughly where the question runs out. The brief names a decision, an audience, and a shape, so the person doing the work knows not only what to do but what not to do. Clarifying questions are asked early and answered quickly, treated as a normal part of starting rather than a sign of confusion.

The deliverable is proportionate. Nobody is surprised by its size at the end, because its size was agreed at the beginning. When someone widens the scope, it is a visible choice with a stated reason, not a silent drift. And the deflating moment — the one where the real question finally appears too late — simply does not happen, because the question was the first thing on the table.

In an organisation like this, effort is not heroic. It is aimed. People do less and deliver more, not because they work harder, but because the target was drawn before they started running toward it.

None of this requires anyone to become less thorough. Thoroughness is not the enemy; it is one of the best qualities a person can bring to work. The point is only that thoroughness needs a direction. Pointed at a clear question, it produces depth. Pointed at a vacuum, it produces sprawl. The same instinct, the same care, the same long hours can land as either, and the only thing that decides which is whether someone bothered to draw the edge first.

A Reflective Question

The last time someone delivered far more than you needed and somehow still missed the point, whose job was it to make the goal clear — and was it ever actually done?