Most performance problems aren't performance problems. They're expectation problems wearing a performance problem's clothes.
A sales rep is told her numbers are off. She didn't know what "on" looked like — the targets shifted in March, and nobody walked her through how the new comp plan would land against her actual book. A customer-success manager is flagged for low NPS scores. He didn't know NPS was the metric his manager was watching most closely; he'd been optimizing for renewal rates because that's what the previous quarterly review had emphasized. A marketing director gets a critical mid-year about her team's lack of focus. The team had been juggling six initiatives because the leadership team kept asking for new ones, and nobody had said which two were actually load-bearing.
In each of these cases, the manager will describe the situation as a performance issue. The report will describe it as a clarity issue. Both descriptions are accurate; they're just naming different parts of the same problem. The manager noticed the outcome. The report noticed the missing premise.
This post is about why most underperformance is, on closer inspection, miscommunicated expectations — and what changes when clarity becomes the operating standard rather than something HR runs once a year.
Ambiguity is the productivity killer most managers underestimate
Ambiguity is the cheap form of performance management. It costs the manager nothing in the moment to leave the picture vague — there's no awkward conversation, no risk of getting the framing wrong, no commitment to track against. It costs the report a great deal in the days and weeks after.
The cost isn't visible until you trace it through the report's actual workflow. An account executive who isn't sure whether her manager wants her optimizing for deal volume or deal size will spend the quarter splitting effort across both, doing each badly. A nurse manager who isn't sure whether her director values throughput or patient-experience scores will rotate between both, picking the wrong one in any given moment. A regional retail manager who can't name her boss's top three priorities for the quarter will respond to each new request as if it's the priority, exhausting her team on inputs that don't compound.
The compounding cost isn't just rework. It's the cognitive load of deciding what to prioritize without a reliable signal from the manager. Every decision has to be defended in the report's own head against an imagined conversation with the manager about whether they made the right call. The defending is exhausting and produces nothing.
There's a compounding pattern here that mirrors delayed feedback: the small clarity gap on Monday becomes a misallocated week by Friday and a wasted month by the next 1:1. The conversation that finally happens has to address not just the original ambiguity but the cumulative cost of working in the dark. By then, the issue has the texture of a performance problem — the work isn't where it should be — even though the root cause was never about the report's effort or skill.
Managers reliably underestimate this cost because the cost lives entirely on the report's side of the relationship. The manager kept their options open. The report carried the ambiguity. Both feel like they did their jobs.
The alignment gap between what the manager wants and what the report hears
Even when managers think they've been clear, the alignment is usually weaker than they assume.
The reason isn't that managers communicate poorly. It's that the communication of expectations is unidirectional by default — the manager talks, the report nods, both leave the meeting believing they're aligned. The check that the report has actually understood what the manager wanted almost never happens.
A simple test exposes the gap. Ask any manager what their direct reports' top three priorities should be this quarter. Then ask each direct report the same question, separately. The lists rarely match. Even when the lists overlap on words, the rankings differ. Even when the rankings match, the operational interpretations vary.
Three patterns produce most of the divergence:
The manager assumed context. The manager has a richer model of what's happening at the org level — a board conversation, a customer escalation, a strategy shift — and uses it to weight priorities. The report doesn't have that context, and the priorities they hear feel arbitrary or interchangeable.
The manager hedged. Instead of saying "X is the priority and the others can wait," the manager said "X is important, but Y also matters, and we should keep an eye on Z." The hedge protected the manager's optionality. It also produced a report who can't tell which of X, Y, or Z is the actual priority and tries to do all three.
The report received signal that contradicted the stated priority. The manager said the customer-renewal program was the priority. They then spent the 1:1 asking about progress on three new-business deals. The report concluded — correctly — that whatever the manager said, the new-business pipeline is what's actually being measured.
These aren't communication failures in the traditional sense. They're alignment failures. The information was technically transmitted; the shared mental model wasn't.
The remedy isn't more talking. It's more mutual checking — the manager actively confirming that the report's understanding matches the manager's intent, and adjusting the framing until it does.
How frequent feedback creates clarity, not pressure
Most managers worry that giving frequent feedback will feel like surveillance to their reports. The worry is reasonable in the abstract. In practice, the opposite is true: reports who get frequent, specific feedback report feeling more autonomous, not less.
The reason has to do with what frequent feedback actually communicates. When a manager comments specifically on what a report did this week — what worked, what didn't, what to consider for next time — the report is receiving a continuously updated map of what the manager values and how the manager evaluates work. The report can navigate by the map.
Without frequent feedback, the report has to guess. They construct a mental model of what the manager probably wants from indirect signals: which projects the manager mentions most often, which questions the manager asks, what the manager praised six months ago. The model is approximate and gets out of date the moment the manager's priorities shift.
The contrast is sharp. Frequent feedback gives the report:
Calibrated autonomy. They can make decisions independently because they have a current sense of what the manager would say. Their decisions converge on the right answer because the calibration is fresh.
Lower meeting overhead. They don't need to schedule a sync to get a read on a question the manager could answer in a quick message, because the trust to ask quickly was already established by the cadence.
Clearer priorities. They know which work the manager is paying attention to and which is allowed to recede. The work that gets noticed gets effort; the work that doesn't gets less.
This is the opposite of surprise feedback: the report is never wondering what the manager is going to say at the next review, because they have a current read on the relationship. The conversation about the year's work happens in real time, distributed across small interactions, instead of compressed into a high-stakes meeting.
Managers who shift from quarterly to weekly feedback consistently report that their teams ask fewer clarifying questions, miss fewer deadlines, and operate with more independent judgment. The pattern looks paradoxical from the outside — more feedback, more autonomy — and is mechanical from the inside. Clarity is autonomy's prerequisite.
Aligning goals continuously, not annually
The conventional pattern is to align goals at the start of the year, document them, and check in at quarterly milestones. The pattern doesn't survive contact with how work actually changes.
A 200-person company sets goals in January. By March, two of the planned initiatives have been delayed and a new one has been added. By June, market conditions have shifted enough that the most important question of the year is one nobody anticipated in January. By September, the formal goals are largely a fiction — useful as historical context, useless as current alignment.
This is the cadence mismatch we've covered before. The goals document was written for the cadence of the budget cycle, not for the cadence of the work. When work changes faster than the goal-setting cadence, the alignment goes stale and the manager and report end up operating against different — and outdated — pictures of what success looks like.
Continuous goal alignment looks different. It runs at the cadence of the work:
Goals get revisited every cycle. What "this quarter's priorities" means shifts as the quarter unfolds. The conversation about priorities happens monthly or biweekly, not annually. The goal document is a living artifact, not an archive.
Mid-cycle adjustments are explicit. When something changes, the manager names the change explicitly — what's being deprioritized, what's being added, what the trade-off looks like. The report doesn't have to infer the shift from changing meeting agendas.
The picture of success stays current. The criteria the work will be evaluated against in three months are the criteria both parties agree on this week, not the criteria that were written down in January and quietly drifted out of relevance.
The technical machinery for this isn't novel. Continuous goal alignment is what most agile teams do at the team level — short cycles, regular check-ins, mid-cycle replanning. Software teams have been doing this for decades; many sales, customer-success, marketing, and operations teams now run similar cadences. The new move is doing the same thing at the individual-development level, with the manager-report relationship as the unit of alignment.
Goals at the cadence of the budget cycle produce alignment for the budget cycle. Goals at the cadence of the work produce alignment for the work.
What real-time coaching for clarity actually looks like
Coaching for clarity is a small set of moves that any manager can practice and that most managers were never taught. The moves don't take much time. They take some discipline about when to use them.
Three coaching moves, in order of frequency:
Reflect back what you heard. When a report describes what they're working on, restate the priority back to them in your own words and ask whether you got it right. The reflection is the alignment check. Most of the time the report will adjust your reading slightly, which is the moment alignment happens. Used a few times a week, this single move closes most of the alignment gaps that would otherwise compound.
Name the trade-off. When asked which of two things matters more, don't hedge. Name the trade-off directly: "If I have to choose between hitting Q3 revenue and shipping the new pricing tier, I'd rather hit revenue this quarter and ship pricing in Q4." The report can plan against the answer. Hedging doesn't give them anything to plan against; it gives them a maze.
Specify what success looks like in measurable terms. "I want this to be great" is not actionable. "I want every account in your book to have a documented success plan by end of Q2, with a check-in cadence the customer signed off on" is actionable. The specificity isn't pedantic; it's what makes the difference between a report who delivers and a report who tries.
These three moves are the coaching equivalent of the coaching prompts we covered for managers who were never trained to coach. The category is small. The practice is the work.
Most managers worry that being this direct will feel commanding rather than collaborative. The opposite is true: reports who get clear direction trust their managers more, because the manager is doing the work of being legible instead of pushing the legibility burden onto the report. Clarity isn't authoritarianism. It's respect for the report's time.
Frequently asked questions
Why is clarity important at work?
Clarity is the substrate that makes performance possible. When employees understand what's expected, what success looks like, and how their work will be evaluated, they can work autonomously and make trade-offs independently. When expectations are ambiguous, employees spend cognitive energy guessing — which costs time, produces miscalibrated work, and makes the conversation about performance much harder later. Most "performance problems" are downstream of clarity problems.
What's the difference between a performance issue and an expectation issue?
A performance issue is when an employee fails to meet expectations they understood and agreed to. An expectation issue is when an employee fails to meet expectations they never clearly received. Most situations described as performance issues are actually expectation issues — the employee did what they thought they were supposed to do, based on the picture they had of what success looked like. The fix is to align expectations explicitly before treating the situation as a performance failure.
How can managers set clearer expectations?
Reflect back what you heard from the report in your own words and ask whether you got it right. Name trade-offs explicitly when asked to prioritize. Specify what success looks like in measurable terms rather than abstract qualities. Revisit goals continuously rather than once a year. Most clarity work happens in 1:1s and short follow-ups, not in elaborate goal documents.
Why do employees feel unclear about expectations?
Three patterns produce most of the unclarity: managers assume context the employee doesn't have; managers hedge instead of stating priorities; and managers' actions contradict their stated priorities (saying X is the priority, then asking about Y in every meeting). Each of these is correctable, but only with deliberate practice. The default state of expectation-setting in most companies is implicit and approximate.
How does continuous feedback improve clarity?
Continuous feedback gives employees a current map of what the manager values and how they evaluate work. The employee can make decisions independently because the calibration is fresh, ask fewer clarifying questions because the cadence already established trust, and prioritize correctly because they know what the manager is paying attention to. Without continuous feedback, employees have to guess — which produces miscalibrated work and slower decisions.
What we know — and what we're refining
If you manage people and you've felt the pattern this post describes — a report missing the mark on something you thought you'd been clear about — the move this week is small: at your next 1:1, ask the report to describe their top three priorities for the quarter in their own words. Don't lead. Just listen. If their answer matches what you would have said, you have alignment. If it doesn't, you've found exactly the gap that was about to become a performance issue, and you can close it in twenty minutes.
Clarity is the cheapest, most underused performance lever a manager has. We've built Performance Blocks around making the alignment work happen in flow rather than in formal goal-setting cycles. Henry surfaces the priorities a manager and report have actually been talking about, captures the trade-offs they've named explicitly, and produces summaries the report has already seen — so the picture of success stays current and shared. The fewer surprises in the relationship, the less of the manager's time gets spent on adjudication and the more gets spent on actual development.
The detail we're still refining is how often the alignment check should run. Some teams find that a weekly priority restatement is too much overhead; others find that monthly is too rare for fast-moving work. The right rhythm probably depends on how quickly the work changes — fast-moving sales and product teams might need it weekly, regulated-industry teams might do fine quarterly. We're still mapping the breakpoints. If you've found a rhythm that works for your team, we'd genuinely like to hear what you settled on.
Most performance problems are clarity problems with another label on. Fix the clarity, and most of the performance issues either resolve themselves or become legitimate performance issues — which are vastly easier to address when they're isolated from the noise of mismatched expectations. The job of the manager isn't to communicate harder. It's to make sure both sides are operating from the same picture of what success looks like. Everything else gets easier from there.