Why Accountability Fails When Expectations Are Vague

Most accountability problems get diagnosed as character problems. Someone did not follow through, so the conversation turns to ownership, urgency, or commitment. Occasionally that diagnosis is right. Far more often the person did exactly what they understood they had agreed to, and the agreement itself was the defective part.

Edwin Locke and Gary Latham spent more than three decades building the evidence base for goal-setting theory, and the central finding is unusually blunt for organizational research: specific, difficult goals produce higher performance than vague encouragement to do your best. Not because specificity motivates. Because “do your best” cannot be failed. There is no standard to fall short of, which means there is also no standard to organize effort around. Vague expectations do not lower the bar. They remove it.

What the Research Shows

Specificity Beats Effort

The counterintuitive part of Locke and Latham’s work is that a specific goal outperforms a vague one even when the vague one asks for maximum effort. Telling someone to do their best sounds like the higher ask. It performs worse, consistently, because effort without a target gets spent on the wrong things. People self-select a difficulty level, usually a comfortable one, and have no way to know whether they have arrived.

This matters for accountability because accountability requires a comparison. You cannot hold someone to a standard that was never stated. What happens instead is that the standard gets constructed retroactively, after the work comes back, from the manager’s unspoken expectations. That conversation feels like accountability to the manager and like a moving target to everyone else.

The Commitment Has to Be Mutual and Explicit

Goal-setting research also finds that goal commitment moderates the whole effect. A specific goal only produces higher performance if the person actually accepts it. This is why accountability conversations that begin with an assignment and end without a confirmation tend to fail quietly. The manager believes an agreement was formed. The employee heard a request, understood it as one of several, and prioritized accordingly.

You cannot hold someone accountable to a standard that was never stated. When expectations are vague, the standard gets constructed after the fact, from the manager’s memory. That is not accountability. It is retroactive judgment.

Roughly Half the Workforce Does Not Have the Baseline

Gallup’s long-running finding that only about half of employees strongly agree they know what is expected of them sets a ceiling on how well accountability can possibly work. If half the workforce is uncertain about the expectation, then a substantial share of accountability conversations are, structurally, about a disagreement over what was agreed. We covered the clarity side of this in how great managers create clarity without micromanaging.

Why This Matters for Teams

Vague expectations produce a specific and recognizable failure pattern, and it is worth naming because it looks like something else.

The first symptom is surprise. Work comes back and it is not what the manager pictured. Nobody was negligent. Two people held different mental models and neither had a reason to discover the difference until the work was finished. The cost is the whole cycle, and it repeats because the diagnosis lands on the individual rather than the handoff.

The second symptom is uneven enforcement. When the standard is implicit, it gets applied inconsistently, and people notice. The same missed deadline draws a hard conversation from one manager and nothing from another. Worse, within the same team, it draws different responses depending on who missed it. That inconsistency reads as favoritism even when it is just the absence of a written standard, and it damages trust faster than the missed work ever did.

The third symptom is the one that ends careers quietly: accumulation. Nobody addresses the small ambiguity, so it happens again. And again. Eventually the manager has a pattern rather than an incident, and the conversation that follows is disproportionate to any single event because it is really about six months of unaddressed drift. The person on the receiving end experiences it as an ambush, and reasonably so. This is exactly the dynamic our feedback script for addressing underperformance is designed to prevent.

The Gap the Data Reveals

Goal-setting theory tells us specificity works. Where it goes thin is the translation into daily managerial practice, and that is where the failures actually happen.

The research is largely built on discrete, measurable goals: units produced, calls handled, targets hit. Most knowledge work does not decompose that cleanly. “Improve the onboarding experience” resists a number, and forcing a number onto it produces the familiar pathology of teams optimizing a metric that has drifted from the intent. The practical translation is not always a number. It is a description precise enough that two people would recognize the same result as finished.

There is a second gap around who bears the cost of ambiguity. In most organizations, the cost lands on the person doing the work. They guess, they guess wrong, and they redo it. The manager’s ambiguity is externalized. Until that asymmetry is corrected, there is no pressure on the person best positioned to fix the problem, which is the person setting the expectation.

And there is a timing gap. Accountability is treated as a downstream activity, something that happens at review time or when something goes wrong. Almost all of the leverage sits upstream, in the ninety seconds when the work is assigned. Organizations invest heavily in performance management systems and almost nothing in the quality of the handoff those systems eventually adjudicate.

What This Looks Like in Practice

Fixing this is not a process rollout. It is a small number of habits applied at the point of assignment.

Write the Agreement, Not the Task

An assignment says what to do. An agreement says what will exist, by when, and what “good” means. It takes two or three sentences. The discipline is that it gets written where both people can see it later, because the entire purpose is to remove the memory contest that otherwise happens at review time.

Ask for the Playback

After the assignment, ask the person to state what they are going to do and when. In their words, not yours. This feels redundant and it is the single highest-yield thirty seconds in management. Roughly a third of the time, the playback reveals a gap. That gap was going to surface anyway, either now or three weeks from now with the work already built.

Name the Tradeoff in Advance

Every commitment displaces something. Make the displacement explicit at the moment of agreement: if this is the priority, what is now not getting done, and who needs to know? Without this, people accept commitments they cannot keep, not out of dishonesty but because the arithmetic was never done out loud. Then the missed deadline gets treated as an accountability failure when it was a capacity failure with a polite front end.

Address the First Instance

The moment to raise a gap is the first time it happens, when the stakes are low and the conversation is small. Managers avoid it because it feels disproportionate to mention something minor. The alternative is not avoiding the conversation. It is deferring it until it has compounded into something that requires a much harder one. Our guidance on delivering a tough performance conversation without destroying trust applies here, but the better outcome is never needing it.

The reframe worth holding onto is this: accountability is not a personality trait you look for in hiring, and it is not a value you post on a wall. It is a property of agreements. Clear agreements produce it almost automatically, because both parties know what was promised and can see whether it happened. Vague agreements make it impossible, and then the organization goes looking for people with more of it, which is a search that never ends.

Related Reading

• The Feedback Script That Prevents Surprise Performance Reviews
• Accountability Without Micromanaging: A Weekly Rhythm
• How to Deliver a Tough Performance Conversation Without Destroying Trust
• Setting Expectations When Priorities Shift Midweek
• Radical Candor at Scale: Building Feedback Systems That Work Across Teams