The meeting was in a conference room overlooking our sprawling parking lot. Surrounded by trees, paths, and tennis courts, it resembled a high-end resort more than our corporate headquarters. I didn't realize it at the time, but I was going to spend a lot of my time over the next few years staring out of those windows trying to work out where things went wrong.

It was my second week. The CEO had called a leadership team meeting to introduce me, properly, officially, and with an intention to drive excitement, and relief. Before I sat down, I heard our CEO. "Jon is here because we have to change how we operate technology in this company. We've been reactive for too long. That ends now." Around the table, people nodded with positive affirmation. Some with enthusiasm as they breathed a sigh of relief and anticipation. Some with the particular expression of a person who has heard this speech before, waiting to see how long this leader will last, quietly confident that this time will be no different.

I genuinely thought it could be different. I had done the diligence through the extensive hiring process. I had heard repetitively the themes of 'legacy tech', 'too slow, too expensive'. The mandate was explicit, the authority was real, and the budget was committed. The pain that had driven the hire was caused by a failure that had cost the organization months of revenue and exposed a fragility in their infrastructure. Everyone seemingly was aware of the gaps but perpetual planning iterations had failed to address them. Some just voiced concerns that it wasn't their place, or didn't want to point fingers. The pain was still fresh enough that there was an unwritten understanding that this was the company's highest priority. For now, people were just grateful the bleeding had stopped.

That was the window of opportunity. And it closed faster than anyone expected.

The Honeymoon May Be Shorter than You Hoped

Organizations in genuine operational pain tend to hire differently than organizations in a comfortable planning cycle, where growth and momentum drive an excitement and enthusiasm. The candor that emerges during a crisis interview, with the CEO transparently admitting how the board feels, the COO describing the failure in clinical detail, the CFO acknowledging the financial cost and implications were real, are all a function of the pain itself. Not necessarily because of some organizational commitment to honesty, transparency and accountability. Denise Rousseau's work on psychological contracts documented this dynamic in 1995. The implicit agreements formed during periods of vulnerability are unusually specific. And unusually brittle. When you are hired into a burning building, the promises made at the door are not the same as the promises kept once the fire is out.

I have watched this sequence play out time and time again. Partly because I am typically hired as a corporate troubleshooter. But sometimes it's because executives know the current process isn't working, and they need something different. It hasn't been unknown in my career to receive a call at 2pm on a Sunday and be on a First Class flight that evening. Travelling halfway around the world for a strategy session Monday morning.

The first phase feels like confirmation. Every observation you make during the honeymoon period is received as insight. Every structural problem you identify is affirmed by your peers, with others openly professing where the problems are, detailed narratives of repetitive failures and lack of change. The mandate you were hired to execute is not just permitted, it is actively cleared of obstacles, calendar slots open up whenever you ask and everyone is bending over backwards to make themselves available to you. Decisions that would normally take three months of navigation, constant back channeling and negotiation, happen in days. The traits that make change agents useful, our directness, our pattern recognition, our willingness to name dysfunction, are experienced as assets. This is the honeymoon, and it is not an imaginary state of consciousness. The change agent who dismisses it as performance is wrong. It is a genuine state of reality. It is also time-bound by something the organization does not disclose during the interview process. Its actual tolerance for the discomfort that change produces.

The timeline varies. I have seen the honeymoon last three months and I have seen it last twelve. What brings it all to an abrupt end, is not failure. What ends it? Early success, executed with precision. This is the mechanism that Kotter identified in 1995 as the single most common cause of transformation failure. Organizations treat early wins as evidence of completion rather than as foundations for the deeper structural work. The reality is the work has only just begun, change has only just started. The transformation must continue. The acute pain that drove your hire begins to subside. The immediate problems are resolved with precision and clarity. The incidents start to reduce, and the team starts to stabilize. The organization's interpretation of "done" and the change agent's interpretation of "started" quietly diverge. Nobody announces this divergence. It emerges as a shift in conversational register. The reality is permanent change is hard. Teams resort to their bad practices. Leaders downplay the risks of bad decisions. You made it look easy, and therefore the organization's belief is we don't really need to change after all, we just need to be more careful.

The Pivot You Don't See Coming

The questions change. The time people make available on their calendars becomes sparse. The language changes subtly and that is the tell.

Early in an engagement, the questions are expansive. What do you need? What's blocking you? What would it take to do this properly? These are the questions of an organization that has assigned you a mission and wants it accomplished. The pivot — and it is always a pivot, never a reversal — shows up in the compression of those questions. How long will this take? Can we phase this differently? Do we need all of this in year one? Each question is individually defensible. A CFO asking whether a capital expenditure can be staged is not exhibiting mandate withdrawal. An operating committee asking whether a platform migration needs to be completed before next quarter is raising a legitimate constraint. The pattern is only visible in aggregate. The questions that were once about what is needed have become questions about what can be deferred. Without fail, in my experience, organizations have underestimated the root cause of their original problem. There's an unwritten assumption and narrative that prevailed prior to your hire. Leaders were often looking outward from their own teams, seeing dysfunction and challenges with the team that you now run and lead. But often, this is only 50% of the story. The dysfunction is often bidirectional. Unfortunately the ownership for resolution isn't.

Rizzo, House, and Lirtzman described this structural condition in 1970 as role conflict. The state of being simultaneously subject to incompatible expectations from different organizational sources. What they could not have anticipated was how often that conflict would be experienced not as contradiction but as gradual reframing of your role once the emergency subsides. The organization doesn't tell you that your mandate has changed. Instead, it's passively communicated across dozens of small interactions. The original scope was perhaps "too ambitious." The "organization moves at its own pace" and "you need to slow down". That transformation is a journey, not a destination and "you need to bring others with you". It says all of this while technically maintaining that you were hired to transform.

The result is a specific kind of cognitive dissonance. The mandate you were hired to execute is still on the books. The immediate resolution brought clarity and is only the beginning. But the authority to execute is now being slowly reduced conversation by conversation. And because neither of these facts is stated explicitly, there is no moment at which you can name the discrepancy without appearing to be the one now creating conflict.

The Reframe

At some point, the organizational narrative shifts its weight. The transformation initiative, which was "our initiative" during the honeymoon, becomes associated with you personally. Your architectural modernization program, which was approved and funded by the same leadership team now questioning it, starts to be described as "Jon's approach." The vendor rationalization project, which was explicitly requested by the CFO in month three, with documented rationale, is recast as a preference you have imported from previous companies. What was agreed initially as "must haves" are now downgraded to "nice to haves".

The hard part to reconcile as a transformation leader is that none of this is malice. It's such an important point to understand clearly, because the temptation to reach for malice as an explanation is strong but wrong, and often underpins the reason why we suddenly take the failure of finishing the transformation personally. What is happening is that the organization is resolving its own cognitive dissonance. If the mandate was real, then withdrawing it requires acknowledging that the organization changed its mind. This then requires examining why, which opens questions nobody wants to acknowledge. The reframe is organizational self-protection, not conspiracy. It's a desire to keep the peace. A desire for everyone to get along. Accountability is reframed as YOU holding yourself accountable, not others.

Rousseau's framework describes this as psychological contract breach. It's the point at which one party's interpretation of the implicit agreement diverges enough from the other's that the contract no longer functions. What makes the mandate particularly damaging is the directionality. The breach of implied contract and authority runs from the organization toward the change agent. But the narrative that crystallizes almost always runs the other way, often in the guise of "lack of trust", or "isn't a team player".

What Single-Loop Learning Costs

The exit, when it comes, resolves the immediate discomfort, for both parties. It also, reliably, prevents the organization from learning the thing it most needs to learn, with an almost uncanny ability to repeat exactly the same mistakes.

Argyris and Schon distinguished between single-loop and double-loop learning. Adjusting behavior within existing assumptions. While double-loop learning requires examining the assumptions themselves. The departure of a change agent is almost always processed as single-loop. "This person was not the right fit". "This approach was too aggressive". "We need someone who can work within our culture". "We need someone to truly understand we are different". The structural question, 'why does this organization consistently produce pain-driven mandates that dissolve before transformation completes', never seems to get asked. Leaders of consensus driven organizations suffer from this repetitive pattern more than others. Their desire is peace, and harmony, with a longing to eventually assemble the right combinations of leaders that will just gel together and solve all the problems. They tend to steer clear of the reality that leaders set the tone and provide empowerment, instead hoping their team will work it out.

I remember driving out of that parking lot for the last time. I remember thinking about the conversation the leaders never wanted to have. The one about why the organization kept arriving at this point. Not just with me. I was not naive enough to think I was the first, and I knew I was one of 4 leaders in 4 years brought in to resolve these problems. I lasted longer than most, some only 3 months. The infrastructure I had inherited was several generations of deferred decisions, each one a monument to a previous transformation initiative that had ended before it finished. The same pattern, repeating, with different people assigned to the outcome each time.

That is the trap for all transformative leaders, and why senior technical leaders tend to stay for 18 months before moving onto the next fire. Not the mandate itself, the mandate is usually genuine when it forms. The trap is the structural conditions that guarantee it will not survive contact with recovery. Organizations that hire for change during pain and withdraw permission as the pain subsides are not being cynical. They are following a pattern so deeply embedded in their culture and how crisis hiring works that most of them cannot see it clearly enough to interrupt it. Many protect the culture that allowed the emergency to form, preferring to continually look for the perfect Unicorn of a leader. The mandate forms under pressure and the psychological contract is implicit. The pivot is incremental and the reframe is self-protective. The exit is clean. And somewhere, in a role the organization is about to post, a change agent is reading a job description that sounds exactly like the one that started this story.

The diagnostic tools to recognize a fragile mandate, before accepting it, exist. The structural interventions to make mandates survive pain-tolerance decay exist. But they only become available after you understand that the trap is not personal, it is architectural. And that is what this series is for.

If you are contemplating a role in an organization, and it feels mandate driven, I encourage you to take a look at the framework assessments I've created throughout my career to provide an objective data point. https://nocelion.com/assessments.

References

• Rousseau, D. M. (1995). Psychological Contracts in Organizations: Understanding Written and Unwritten Agreements. Sage Publications.
• Kotter, J. P. (1995). Leading Change: Why Transformation Efforts Fail. Harvard Business Review, 73(2), 59-67.
• Rizzo, J. R., House, R. J., & Lirtzman, S. I. (1970). Role Conflict and Ambiguity in Complex Organizations. Administrative Science Quarterly, 15(2), 150-163.
• Argyris, C., & Schön, D. A. (1978). Organizational Learning: A Theory of Action Perspective. Addison-Wesley.

---

This is Part 1 of the "Performance or Personality" series, examining the structural patterns behind technical leadership derailment. Part 2 examines how to distinguish organizational dysfunction from personal failure during mandate withdrawal.