For over a decade, I managed a core set of financial systems, gradually taking on more responsibility across the organization. Over time, though, comfort became a kind of trap. I realized I needed new challenges — a role that would test me, stretch me, and put my skills to fuller use.
That opportunity came quickly: I was asked to lead the migration of a financial reporting platform into a modern, cloud-based data warehouse and analytics system.
Stepping into the new role felt as if someone had taken a beating heart out of one body and transplanted it into another. The rhythms were unfamiliar. The surrounding ecosystem — people, processes, team culture — did not yet trust this new entity. Every beat had to harmonize into a new rhythm.
Transitions Are Hard and Messy
Even senior leaders underestimate:
- How messy transitions feel — the identity shift, the unfinished business from the old role
- How hard it is to build trust without seeming like an outsider
- How distracting lingering responsibilities from the previous role can be
Having worked across platforms from z/OS to SAP EPM to Windows Server distributed systems, I thought I’d seen it all. Yet stepping into an unfamiliar environment was genuinely disorienting.
A few things stood out:
- The terminology differed sharply from what I considered industry standard.
- The team had matured into deep specialization — subject-matter experts who excelled in their own domains but were often reluctant to operate beyond them. The result was a capable but rigid organization.
- As systems matured and operating budgets tightened year over year, the teams using the application had absorbed more and more technology functions, blurring the line between business and technology responsibilities.
- It was hard to keep track of everything the team was doing without appearing to micromanage.
- Documentation reflected the siloed, application-specific style of an earlier era.
My Three-Phase Strategy for Transitions
Phase 1: Deep Immersion
Objective: Learn faster than the organization expects you to.
- Daily or near-daily touchpoints with the new team in the first 60–90 days
- Be visible, present, and genuinely curious
- Resist the temptation to “fix” everything immediately — focus first on understanding the rituals, roles, interactions, and expected business outcomes
Phase 2: Stakeholder Interviews
Objective: Map the power lines and emotional currents.
- Interview cross-functional leaders, frontline staff, and the unofficial influencers
- Ask: “What’s working? What’s not? How can I help you succeed?”
- Use these conversations to surface blind spots and inherited tensions
Phase 3: Hands-On Engagement
Objective: Earn credibility by doing, not just directing.
- Join the daily workflows — reviews, stakeholder calls, post-mortems
- Show you value the details as much as the strategic picture
- This is where early wins can be identified and celebrated
The Balancing Act
- Emotional regulation: staying calm when everything is new sends a signal of safety.
- Structure over reactivity: well-formed plans beat reactive decisions.
- Empathy: your arrival changes their identity as much as yours.
The research backs this up. William Bridges’ transition model describes the journey through an ending, a neutral zone, and a new beginning. Francis Frei’s trust triangle — authenticity, logic, empathy — maps closely to what earns a new leader credibility. And cognitive-load theory explains why carrying old and new responsibilities at once causes such decision fatigue.
Closing Reflection
A transplant doesn’t succeed because the heart pumps harder. It succeeds because the new heart and the body learn to sync their rhythms.
Leadership transitions are the same. It’s not just about proving you can lead — it’s about proving you can belong.