When productivity slips, the instinctive diagnosis usually points toward something structural — insufficient staffing, inadequate tools, unclear processes. These matter, but a quieter, less frequently named cause tends to have an outsized effect on how much effort people actually bring to their work: whether they feel their contribution is genuinely noticed, and whether they understand clearly what’s actually expected of them. Both are cheap to fix, relative to their impact, and both are surprisingly easy for a well-intentioned organisation to neglect.
Why This Cause Is Easy to Miss
Under-appreciation and unclear expectations don’t show up as a single, dramatic failure — they show up as a slow, cumulative decline in discretionary effort. People still show up, still complete their assigned tasks, but the extra care, the willingness to go beyond the strict minimum, gradually erodes. Because the decline is gradual and the cause is invisible on any dashboard, it’s easy for leadership to misattribute the resulting productivity dip to something else entirely — insufficient headcount, inadequate tools, market conditions — while the actual, more addressable cause goes unaddressed.
The Two Specific Problems Worth Naming
Effort that goes unrecognised. When people consistently invest real effort without any acknowledgement that it’s been noticed, a rational, if unconscious, recalibration tends to happen: if the extra care isn’t making a visible difference to how the work is received, why keep investing it? This isn’t laziness — it’s a reasonable response to an environment that isn’t signalling that the extra effort matters.
Ambiguity about what’s actually expected. When someone genuinely doesn’t know what “doing this well” looks like — what standard they’re being measured against, what the priorities actually are — it becomes considerably harder to invest confident, purposeful effort, regardless of motivation. Vagueness about expectations doesn’t just create occasional confusion; it creates a chronic, low-grade uncertainty that saps energy that would otherwise go toward the actual work.
Both problems compound each other. Someone who’s unclear about what’s expected and doesn’t feel their effort is noticed has very little to anchor their motivation to — no clear target to aim for, and no evidence that hitting it would even be recognised if they did.
Why Formal Performance Reviews Aren’t Enough on Their Own
Many organisations assume that periodic, formal performance evaluation covers this ground adequately. In practice, formal reviews happen too infrequently to address either problem well. Recognition that arrives only once or twice a year, disconnected from the specific moment of effort it’s meant to acknowledge, does considerably less to sustain motivation than more frequent, specific, informal recognition offered close to when the effort actually happened. Similarly, expectations clarified once a year, in a formal review, don’t remain equally clear for the following eleven months as priorities inevitably shift.
What Actually Addresses Both Problems
Make recognition frequent, specific, and close to the moment it’s earned. Waiting for a formal review cycle to acknowledge good work loses most of its motivational power by the time it arrives — timely, specific acknowledgement does considerably more.
Revisit expectations regularly, not just at the start of a role or project. Priorities shift, and expectations that were clear six months ago may have quietly drifted out of alignment with what’s actually being asked for now — a brief, regular check-in keeps this from silently accumulating into genuine confusion.
Ask directly whether expectations are actually clear, rather than assuming they are. What feels obvious to a manager, who has full context, often isn’t nearly as obvious to someone without that same visibility — a direct question surfaces gaps that would otherwise go unspoken.
Distinguish between effort and outcome when giving recognition. Genuine effort that didn’t produce the hoped-for outcome, due to factors outside someone’s control, still deserves acknowledgement — recognising only successful outcomes teaches people to avoid the kind of ambitious, uncertain effort that sometimes doesn’t pay off but is often exactly what’s needed.
Watch for the specific, quiet signs of eroding discretionary effort. A team that’s technically meeting its targets but has visibly stopped going beyond them is often already experiencing this dynamic, even before it shows up as a missed deadline or a formal complaint.
A Practical Scenario
A manager notices her team’s output has been technically adequate but has lost the extra polish and initiative that used to be routine — nothing dramatic enough to flag as an obvious problem, but a difference she can sense. Reviewing her own recent behaviour honestly, she realises she’s been almost entirely focused on operational firefighting for several months, with recognition and check-ins about expectations both quietly falling by the wayside.
She reintroduces both deliberately: brief, specific acknowledgement of good work as it happens, rather than saving it for a quarterly review, and a short, regular check-in on whether current priorities are genuinely clear to everyone. Within a few weeks, without any change to the team’s actual workload or resourcing, the extra care and initiative that had quietly faded begin to return — a clear signal that the earlier decline wasn’t about capacity or skill at all, but about exactly the two, quietly neglected factors that had drifted out of view.
Common Mistakes
Assuming formal performance reviews adequately cover recognition and expectation-setting. Both need more frequent, informal reinforcement than an annual or semi-annual cycle can provide.
Only recognising successful outcomes, not genuine effort. This discourages the kind of ambitious, uncertain effort that doesn’t always pay off but is often exactly what’s needed for genuine progress.
Assuming expectations are clear because they were stated once. Priorities shift, and clarity given at one point doesn’t automatically remain accurate months later without being revisited.
Misattributing a productivity decline to capacity or skill, when the actual cause is unrecognised effort or unclear expectations. This leads to solutions — more headcount, more training — that don’t address the actual, more addressable root cause.
Action Steps
- This week, give specific, timely recognition for a piece of genuine effort, not just for a successful outcome.
- Ask your team directly whether current priorities and expectations actually feel clear, rather than assuming they do.
- Build a brief, regular check-in on expectations into your existing routine, rather than relying solely on periodic formal reviews.
- Identify one team member whose extra effort or initiative seems to have quietly faded, and consider whether unrecognised effort or unclear expectations might be contributing.
- Before attributing a productivity dip to capacity or resourcing, honestly rule out unclear expectations and unrecognised effort as contributing causes.
Key Takeaways
- Unclear expectations and unrecognised effort quietly erode discretionary effort well before they show up as a visible productivity problem.
- Formal, infrequent performance reviews don’t adequately substitute for regular, informal recognition and expectation-setting.
- Recognising genuine effort, not just successful outcomes, encourages the kind of ambitious effort organisations actually need.
- Expectations that were clear at one point can drift out of alignment as priorities shift, without anyone noticing until real confusion has set in.
- A productivity decline is often misattributed to capacity or resourcing when the actual, more addressable cause is unrecognised effort or unclear expectations.
Conclusion
Two of the more common, and more addressable, drivers of declining productivity aren’t structural at all — they’re a lack of clarity about what’s actually expected, and a lack of visible acknowledgement that effort has been noticed. Both are inexpensive to fix relative to their impact, and both are easy to overlook precisely because their effects show up gradually, as a quiet erosion of discretionary effort rather than a single, obvious failure. Addressing them directly, and regularly, tends to restore far more productivity than most structural interventions ever do.
Frequently Asked Questions
How can I tell if declining productivity is due to unclear expectations rather than a capacity issue?
Ask directly — a genuine conversation about whether current priorities and standards feel clear often reveals this quickly, and it’s worth ruling out before assuming a resourcing or staffing problem.
How often should recognition happen to be genuinely effective?
Frequently and close to the moment it’s earned — recognition delayed until a formal review cycle loses much of its motivational power by the time it arrives.
Should effort be recognised even when the outcome wasn’t successful?
Generally yes, when the effort itself was genuine and the shortfall was due to factors outside the person’s control — recognising only successful outcomes discourages the kind of ambitious effort organisations need.
How often should expectations be revisited with a team?
Regularly, rather than only at the start of a role or project — priorities shift, and clarity given at one point doesn’t automatically remain accurate as circumstances change.
Is it possible to over-recognise effort, making it feel less meaningful?
Recognition that’s given for genuinely minor or routine work, indiscriminately, can dilute its impact — the key is proportionate, specific acknowledgement tied to real effort or achievement, not blanket praise regardless of substance.
What’s the fastest way to check whether my team’s expectations are actually clear?
Ask each person directly to describe, in their own words, what’s currently expected of them and what success looks like — and compare the answers against what you actually intended.