Every "Difficult" Employee is Running an Old Program

Their reaction doesn't match you because it isn't actually about you. It's about the last person who did this to them.

There's a particular kind of frustration that builds when someone reacts to you in a way that seems wildly disproportionate to anything you actually did. You give straightforward feedback and get a defensive wall. You extend a reasonable amount of trust and watch it get tested, again and again, as if the person is waiting for you to prove you don't mean it. You ask a routine question and receive an answer built for a much more hostile conversation than the one you're actually having. 


The natural conclusion is that this person is simply difficult - reactive, hard to manage, thin-skinned. That conclusion feels earned in the moment, because the reaction genuinely doesn't match your input. But that mismatch is exactly the clue worth paying attention to, because it's usually accurate: the reaction doesn't match you, because it isn't actually about you. 


People Respond to Patterns Before They Respond to People 

Everyone arrives at a new working relationship carrying a template built from every authority relationship that came before it - a previous manager, a previous employer, sometimes an institution or an experience that predates their career entirely. That template runs quietly in the background, and it does something specific: it primes a person to expect a given category of behavior from "someone in this role," before they've gathered enough evidence about you specifically to know whether that expectation applies. 


If a previous manager was volatile, ambiguous feedback reads as the prelude to an outburst, even from a manager who has never once raised their voice. If a previous employer punished honesty about mistakes, admitting an error feels dangerous here too, regardless of how this particular leader has actually responded to mistakes in the past. If a previous authority figure was inconsistent - warm one day, cold the next, for reasons that were never explained - a new leader's ordinary variation in mood or bandwidth gets read through that same lens of unpredictability, and the employee starts managing you the way they learned to manage someone else entirely. 


This is not a character flaw, and it's not something the person is doing on purpose. It's simply how people generalize experience - using the past as a reasonable, efficient predictor of the present, right up until it stops being accurate and nobody has told the underlying template that yet. The employee in front of you reacting to something that isn't actually happening is, in a real sense, still finishing a conversation with someone who isn't in the room. 


What This Looks Like in Practice 

The pattern tends to show up in a few recognizable shapes. There's the employee who reacts to ordinary, direct feedback as though it were an attack - bracing, deflecting, or escalating in response to something delivered calmly and factually. There's the employee who tests boundaries repeatedly, almost as if checking whether this time the consequence will finally match what they've come to expect, or whether the rules really are different here. There's the employee who withholds information reflexively, even when transparency would clearly serve them, because somewhere the lesson was that information given to leadership gets used against you. And there's the employee whose trust seems to reset to zero after every minor disagreement, as though each new instance of friction reactivates the original template rather than building on an accumulating track record with you specifically. 


In every one of these shapes, the through-line is the same: the intensity of the reaction is calibrated to a history you didn't create, applied to a present situation you did. 


Why This Recognition Changes Everything 

Once a leader can see this pattern for what it is, the entire emotional tenor of the interaction shifts - not because the behavior stops being frustrating to deal with, but because it stops being a referendum on the relationship you're actually building. Reacting to someone's defensiveness with your own defensiveness treats their old program as new evidence against you, which usually confirms the old template rather than challenging it: you got defensive too, just like the last one did. 


Recognizing the pattern also changes what kind of response actually works. Arguing with someone's disproportionate reaction rarely helps, because you're arguing with a template, not with the immediate situation, and the template isn't listening to the specifics of your case. What helps is treating the reaction as information about history rather than as an accurate read of the present moment - responding to the person calmly, consistently, and without matching the escalation, over enough repetitions that the old pattern starts to lose its predictive power. 


This is also, frankly, a kinder read of the person than "difficult." Difficult implies a stable trait, chosen and enduring. Running an old program implies something a leader can actually work with: a learned expectation, formed for good reason somewhere else, that simply hasn't yet been updated with better data. 


Distinguishing the Old Program From an Accurate Read of You 

A necessary caution here: not every disproportionate-seeming reaction is a leftover from someone else. Sometimes an employee is responding accurately to something real happening in the current relationship, and the honest, harder work is admitting that possibility before reaching for the more comfortable explanation that they're simply reacting to their past. Ruling that out is a discipline, not an assumption. 


A useful test is consistency and origin. If the reaction shows up in response to a wide range of your behaviors - including ones that are demonstrably neutral or even generous - and especially if it shows up early, before there's been much interaction to actually generate that level of distrust, the old-program explanation gets stronger. If the reaction is narrowly tied to specific things you've actually done, and especially if it intensified after a particular incident with you, the honest answer is that this one is about you, and it deserves to be treated that way - with accountability, not a diagnosis. 


The other useful signal is trajectory. A genuine old program tends to soften gradually as a person accumulates enough contradicting evidence about you specifically - not instantly, but measurably, over months, as trust rebuilds on a new foundation. A reaction that isn't softening despite consistent, contradicting evidence on your part is worth revisiting as possibly not the old-program explanation after all, or worth examining for something you may still be doing that's reinforcing it without realizing it. 


What Leaders Can Actually Do With This 

Patience calibrated to evidence, not to a single interaction, is the first move. If you suspect someone is running an old program, expect the recalibration to take time measured in months, not one good conversation. That's not weakness on your part or theirs - it's simply how long it takes for a new template to accumulate enough weight to compete with an old one. 


Consistency is the second, and it's the actual mechanism that does the work. The old program gets updated by repeated, boring, reliable evidence that this time is different - the same calm response to the same kind of test, over and over, until the pattern of predictability itself becomes the new data point. One generous gesture won't out-argue years of a different lesson. A hundred small, consistent ones eventually will. 


And explicit naming is the third, underused far more than it should be. Sometimes the most direct route is simply saying, plainly and without accusation, that you've noticed a reaction that seems bigger than the moment, and asking - genuinely, not rhetorically - whether something from a previous experience might be shaping how this one lands. Many employees have never been offered the chance to name this themselves, and the invitation alone can do more to interrupt an old pattern than months of quiet, patient consistency ever could. 


The employee reacting to you as though you were someone else is not, in most cases, being difficult on purpose. They're operating on the best data they've had until now. Recognizing that doesn't excuse every behavior that follows from it, but it does change the job in front of you - from managing a difficult person to patiently becoming the new data point sturdy enough to finally outweigh the old one. 


The Payoff for Getting This Right 

There's a compounding return here worth naming explicitly. An employee who successfully updates their template with you - who learns, through accumulated evidence, that this working relationship genuinely operates on different rules than the one that damaged their trust originally - doesn't just become easier to manage. They frequently become one of the more loyal, invested people on a team, precisely because the contrast between the old program and the new reality is so vivid to them. People who have been proven wrong about expecting the worst from leadership tend to remember exactly who proved them wrong. 


The inverse is true as well, and it's worth sitting with as a caution. A leader who reacts to this pattern with impatience, or who treats the employee's defensiveness as confirmation that they were right to be wary in the first place, doesn't just fail to fix the immediate friction. They add a fresh, current data point to a template that was already primed to expect exactly that outcome - making the next new leader's job, and every leader after that, measurably harder. Old programs don't only get updated. Left unaddressed, or handled carelessly, they get reinforced, and they travel with the person into whatever comes next. That's the real stake in getting this right: not just the relationship in front of you, but every one this person will carry the template into afterward.


Brian Wallace • September 13, 2026
By Brian Wallace September 13, 2026
The employee who won't take a risk already ran the math. The math wasn't wrong. The system was.
By Brian Wallace September 13, 2026
You cannot coach 'want it more.' You can fix clarity, incentive, history, and load - which is exactly why leaders skip straight to the first one.
By Brian Wallace September 13, 2026
Discretionary effort doesn't show up as a missed deadline. It shows up as a resignation you didn't see coming.