By Michael Nagorski, Founding Partner, Double Loop Performance
Your New Hire Isn’t the Problem. Your System Is Defending Itself.
Sarah spent eight years building a book of business the modern way — CRM as the system of record, multi-threaded accounts, structured discovery. She joins a new company in month two and sits next to Frank, who has closed the same territory for eleven years off a Rolodex and instinct. Frank calls the CRM “big brother.” Someone tells Sarah, gently, to just watch how it is done here first.
Six months later, Sarah is running Frank’s motion. Badly. Leadership wants to know why onboarding did not work.
Onboarding worked fine. Sarah just landed in a team that had no intention of letting her use any of it.
The team didn’t reject her skills. It protected itself.
Most onboarding failures get filed under a training gap — more ramp content, another certification, a sharper 30-60-90 plan. That diagnosis puts the problem on the new hire’s knowledge. It rarely lives there.
Social psychologists have a name for what is happening on Frank’s side of the desk: system justification. People defend and rationalize the systems they depend on even when those systems work against them. The stronger the longer a system’s been in place, the more stuck someone feels inside it, and the less control they believe they have over changing it. Frank’s Rolodex is not nostalgic. It is how he copes with a system he cannot reshape, so he defends it instead.
That is the part most transformation plans miss. You can install a new process in a week. Getting someone to admit the old one was ever wrong takes a lot longer, if it happens at all.
Sarah’s real options, and why the team pushes her toward the worst one
Hirschman gave us the original language for this, and Withey and Cooper sharpened it later: when someone is unhappy inside an organization, they land on exit, voice, loyalty, or neglect. Voice means speaking up to fix the thing. Exit means leaving. Loyalty means staying quiet and hoping it gets better on its own. Neglect means staying but checking out, letting standards slip because nothing feels worth the effort anymore.
Withey and Cooper also mapped which conditions push people toward each response. Voice shows up when someone believes change is possible and feels some control over the outcome. Exit shows up when speaking up is costly, satisfaction is already thin, and something better exists somewhere else.
Here is the trap built into Frank’s team: every time Sarah suggests logging a touchpoint or mapping a second stakeholder, she is not just proposing a task. She is implying Frank’s method is missing something. In a system wired to defend itself, that reads as a threat, and threat is what makes people cling harder to what they already believe. The team does not argue with her point. It quietly folds her into the norm until the point disappears.
Sarah has options elsewhere and a strong sense that she can shape her own outcomes. That combination points toward exit, not loyalty. What leadership thinks it is watching is a skills gap closing. What is really happening is a clock running.
What must happen before anyone touches the process
This is exactly the gap our frameworks are built for — but not to redesign the sales motion first. The system needs a different relationship to voice before any new methodology has a chance of sticking.
A few things must happen, and the order matters:
Call out what is being defended, in specific terms. Not “resistance to change” — closer to “Frank calls the CRM big brother because it makes his work visible in a way he’s never had to account for before.”
Someone senior must go first. Lower the cost of speaking up before you ask a new hire to do it — a leader raises a hard question in the room and survives it publicly, so it is no longer a hypothetical risk when Sarah tries the same thing.
Give the new approach an ally with standing. Sarah’s ideas need someone with tenure backing them early, or the room defaults to protecting whoever has been there longest.
Skip that sequence and you get a transformation initiative with new fields in the CRM and nothing else is different underneath it. What decides whether Sarah’s approach survives contact with Frank’s floor is the behavior sitting under the process, not the process itself.
What it looks like when this goes unaddressed
Structured onboarding cuts ramp time and lifts productivity but only paired with a room willing to let new methods take hold. Without that, the same program produces flat numbers no matter how good the content is. Poor onboarding experiences already sit near the top of why reps leave in year one, and a system that punishes voice just tightens that timeline.
Sarah won’t file a complaint. She will go quiet, hit her numbers just enough to avoid a hard conversation, and start taking calls from recruiters. Neglect first, exit not long after — the two responses that crowd out voice and loyalty once someone decides speaking up costs more than it is worth.
The fix was never a better 30-60-90 plan. It was building a system that could hear what she already knew how to do.
About The Author
Michael Nagorski is the Founding Partner of Double Loop Performance, an organizational development and leadership consulting practice based in Newark, Delaware. He works with executive teams, change leaders, and facilitators who are tired of talking about the right things and ready to actually do them.
Michael has spent more than 15 years helping organizations at inflection points — when they need to move differently without losing what made them good. That has ranged from designing decision-making frameworks for Fortune 500 sales organizations to building facilitation systems for senior leadership teams navigating strategy execution, technology adoption, and culture change.
His work lives at the intersection of facilitation design, behavioral science, and organizational accountability — with a strong bias toward the practical over the theoretical.
He holds graduate degrees from the University of Delaware in Organizational Development and Change and Business Administration, and is the developer of the MEET Funnel methodology for structured decision facilitation.
Contact Double Loop Performance or contact Mike directly through LinkedIn.