The Accountability Allergy
What happens when a named standard meets an old norm, and what senior leaders owe the managers holding the line
A frontline manager sits across from me, not in crisis but in a particular kind of exhaustion.
They describe a direct report who hasn’t completed a routine assignment in three weeks. According to the employee, the manager hasn’t provided enough clarity on the objective. A second direct report calls out sick with remarkable regularity, every Tuesday, which happens to be the designated in-office day. The work shows no pattern. The absences show a perfect one.
The manager hasn’t done anything unusual. They have made expectations visible, and for some employees that alone is enough to trigger a response.
I hear versions of this from a cross section of leaders who spend a disproportionate share of their time managing a small number of people. The industry changes and the structure doesn’t. What follows is about the playbook some employees reach for when a standard is named that doesn’t match their preferences, and about what that playbook asks of the senior leaders above the managers who encounter it.
The environment built this
Before naming what the employee is doing, the senior leader has to name what the organization permitted.
Many organizations spent years operating with standards that were stated but not enforced: metrics without follow-through, expectations without consequence, and in some cases distributed work without the accountability infrastructure to support it. Over time that redefined the baseline. What gets called a performance problem today was, functionally, yesterday’s operating standard. The employee didn’t invent those rules. They learned them.
When a new manager, a new leadership team, or a return-to-office decision arrives, it rarely introduces a new standard. It exposes the gap between what was always expected and what was actually enforced. That is why the Accountability Allergy is better understood as a conditioned response than as a character defect.
The senior leader who inherited this system didn’t create it. The leader who lets it persist, who flinches when the friction arrives, owns what happens next.
The playbook
The pattern is rarely resistance to work. Most employees who display it have the skills and experience the role requires. The response is specific to an expectation that has been named and then enforced. While the standard stays vague, everything is stable. Once a manager makes it explicit and holds to it, a recognizable playbook tends to appear, usually in three moves.
The first is manufactured dependency. “I can’t complete this until you provide X, Y, and Z.” The task is routine and has been done before without escalation, but now that the expectation has been named, the manager has been repositioned as the obstacle. The manager ends up defending their own competence instead of holding the standard, and the burden of proof has quietly shifted.
The second is compliance with the letter of an expectation and none of its intent. The employee is present, technically. Absences cluster on in-office days. Deliverables arrive on the deadline, below the standard, with a paper trail documenting every ambiguity. This version is more expensive to manage than open resistance, because each individual instance is easy to explain away.
The third is escalation. When the first two moves fail to dislodge the standard, the language of micromanagement appears, and sometimes a formal complaint follows. This is the move that stops most managers, and the organization’s first instinct is often to examine the manager rather than the history.
Telling the playbook from a real concern
This is where precision matters most, because the same surface behavior can have very different causes.
A recurring absence may reflect a medical or family situation the manager knows nothing about, and the employee may be entitled to protections that keep it private. A complaint may describe real harassment, discrimination, retaliation, or genuinely poor management. Every such concern deserves to be heard and investigated on its merits, and a leader who treats complaints as tactics by default has created a different and more serious problem.
The playbook is something else: a sustained, documented pattern of responses that appears when a reasonable, clearly stated, consistently applied expectation is introduced, and that tracks the expectation rather than any underlying need. No single incident establishes it. It becomes visible only over time and only through documentation, which is exactly why the infrastructure below protects both the organization and the employee who has a legitimate concern.
The micromanagement label
Micromanagement is real. It is the over-supervision of competent people doing work they are qualified to own, and it corrodes trust and initiative.
The word also gets applied to something very different: a manager holding a clear standard for the first time in years. An employee who has worked without accountability infrastructure often can’t feel that difference, because from where they sit, any enforced expectation feels like an intrusion.
The manager needs to understand this so they don’t internalize the accusation. When a clearly documented, consistently applied expectation is labeled micromanagement, the right response is to hold the standard with greater precision, while staying open to the possibility that something about how it was set does need adjusting.
The infrastructure
Negotiating with the pattern feeds it. What works is infrastructure that makes the standard clear and makes the pattern, if there is one, visible.
That starts with expectations in writing: a specific deliverable, deadline, and format rather than “timely completion”. Clarity at that level is what makes accountability possible and makes complaints answerable, in either direction.
It requires consistent enforcement. One missed deadline that passes without consequence resets the baseline, and a manager who enforces a standard once and then retreats has established a new negotiating floor.
It also means engaging HR early, as a partner in setting and documenting standards, rather than as a last resort once a complaint has been filed. HR brought in at that stage can also make sure any legitimate concern surfaces and is handled properly before it becomes adversarial.
What it asks of the senior leader
The Accountability Allergy is a systems problem that presents as a personnel problem. The employee’s response was shaped by an environment that taught them what the real standard was, and that environment was built, permitted, or inherited by the leadership above them.
That makes the senior leader’s role decisive. Frontline managers can hold a standard only as long as the leaders above them are willing to back it. When the first complaint arrives and leadership quietly signals that the standard is negotiable, the manager learns the same lesson the employee did, and the pattern moves up a level.
The senior leader’s job is to make sure the standard is fair, clearly stated, and consistently applied, to make sure every real concern is heard, and then to stand behind the manager who is holding the line.
When one of your managers holds a fair standard and the first complaint arrives, do they know you will stand behind them?
The Echelon Advisory begins this work with a 30-minute scoping conversation.
The next issue, in your inbox.
One structural problem in leadership. Named precisely. Once a month.