This article was originally published on davidohnstad.info. I cross-post here to reach the Dev.to community.
The Tuesday David Ohnstad Almost Turned in His Resignation
David Ohnstad had the email drafted. Subject line: "Notice – Transition Plan." Body: professional, brief, exit date nine weeks out. The cursor hovered over Send for about forty seconds. Then his phone rang — the VP who'd been pushing for a new rotational leadership track, asking if David wanted the first slot in a six-month product-to-engineering rotation before making any "big career moves." He closed the draft. Six months later, he was running a data infrastructure initiative he didn't know existed when he almost quit. According to Gallup's 2023 State of the Global Workplace report, 44% of employees worldwide are actively watching for new job opportunities — but fewer than 12% of organizations offer structured internal mobility programs that let people pivot without leaving. That gap is expensive: external replacement costs run 1.5x to 2x annual salary. Internal rotation costs a tenth of that and retains institutional knowledge most companies hemorrhage during turnover.
The choice David faced is playing out in thousands of mid-career professionals right now. You're five to ten years into a role. You're competent. Maybe even respected. But you've hit a plateau — not because you stopped growing, but because your current function has a ceiling and the next logical step is either a lateral move into someone else's lane or a management track you don't want. The external job market looks appealing until you calculate what you'd lose: the network you spent years building, the credibility you earned, the institutional shortcuts that make you effective. Rotational leadership programs are designed to solve this exact problem — but most people don't know they exist until they're already halfway out the door.
Why Mid-Career Professionals Leave When Internal Mobility Could Have Kept Them
The failure mode here is visibility, not opportunity. Most organizations have more internal mobility options than employees realize — but those options live in HR decks, leadership development memos, and skip-level conversations that never happen. By the time a high performer starts job hunting, they've already emotionally exited. The rot starts earlier: when someone realizes they've stopped learning, and nobody in their direct reporting chain has offered a path forward. According to McKinsey's 2022 analysis on employee engagement and retention, lack of career development is the number one predictor of voluntary turnover among employees with 3-10 years tenure — outweighing compensation, work-life balance, and manager relationships.
David saw this firsthand at a SaaS company where three senior product managers left within five months. All three cited "limited growth opportunity." Two of them had been informally offered rotation into data architecture and customer success engineering — but those conversations happened in hallways, not in formal development plans, and none of the three took them seriously because the offers felt offhand rather than strategic. The company replaced all three externally at significant cost, then six months later launched a formal rotational program. The irony was not lost on the team that stayed.
Here's the tactical breakdown of what goes wrong: managers assume high performers know about internal opportunities because leadership talks about them in all-hands meetings. High performers assume internal opportunities are reserved for people in a different tier or function. HR assumes managers are having career development conversations. Managers assume HR owns that process. Meanwhile, the best people on the team are texting recruiters because nobody explicitly said, "Here's a rotation path, here's the timeline, here's what you'd own, and here's how we make sure you don't lose ground in your current domain while you build a new one."
The Rotation-Before-Resignation Model: How to Structure a Mid-Career Pivot Without Leaving
This is a four-phase model that treats internal rotation as a formal product launch, not a favor or a side project. The framework is called the Rotation-Before-Resignation Model, and it's built around the insight that most people leave not because they want to, but because staying feels like stagnation and nobody offered a structured alternative with clear milestones and measurable outcomes.
Phase 1: The Explicit Offer (Week 0)
Rotational opportunities must be presented as formal offers with written scope, timeline, success metrics, and a named executive sponsor. The conversation cannot be "Maybe we could find you something in another department." It has to be "We're offering you a six-month rotation into [specific function], you'd own [specific outcomes], your current role would backfill with [name or plan], and at the end we'll evaluate three paths: return to your original role with expanded scope, transition fully to the new function, or design a hybrid role." The formality is the signal. Informal offers get declined or ignored because they feel like distractions, not investments.
Phase 2: The Protected Transition (Weeks 1-8)
The first eight weeks are about onboarding into the new function without abandoning the old one. This is the phase most rotations get wrong — they either fully pull someone out (creating chaos in their original team) or leave them half-in (so they're doing two jobs badly instead of one well). The fix: assign a transition lead in the original function who owns handoff documentation and stakeholder communication, and assign a rotation mentor in the new function who owns onboarding and context-building. David Ohnstad's rotation into data infrastructure included weekly check-ins with both a product mentor (his original domain) and an engineering lead (his rotation target). That dual accountability kept him from falling through the gap between teams.
Phase 3: The Ownership Milestone (Weeks 9-20)
By week nine, the person in rotation should own a discrete project or initiative in the new function — not shadow someone else's work, but own an outcome with their name on it. This is where rotations either prove their value or reveal they were a mismatch. For David, the milestone was leading a database schema redesign for a customer-facing analytics product. It required him to learn query optimization, collaborate with engineers he'd never worked with, and present technical tradeoffs to stakeholders who didn't know him. The project shipped in week eighteen. The credibility he built in that window became the foundation for everything that followed.
Phase 4: The Decision Gate (Weeks 21-24)
The final month is evaluation and decision architecture. Three questions get answered: Did the rotation achieve its stated outcomes? Does the person want to continue in the new function, return to the old one, or build something hybrid? Does the organization have a role that matches that preference? The mistake most companies make here is treating the decision as binary — stay in the new role or go back — when the real value often emerges in hybrid designs. David's rotation led to a newly created role: Senior Data Product Manager with shared accountability across product and engineering. That role didn't exist before the rotation. It exists now because the rotation surfaced a gap the organization didn't know it had.
What Happened When David Chose Rotation Over Resignation
The decision to take the rotation instead of sending the resignation email wasn't obvious at the time. David had been a product manager for six years. He knew the role. He was good at it. But he'd hit the point where every sprint felt like a variation on the last one — different features, same process, same stakeholders, same constraints. The external offers he was evaluating promised new challenges, better titles, more money. What they didn't promise was continuity. He'd have to rebuild his network, re-prove his credibility, and relearn the institutional context that makes senior work efficient. The rotation offered something different: a chance to expand his skill set without abandoning the organizational capital he'd spent years accumulating.
The first month was disorienting. David sat in engineering standups where half the terminology was unfamiliar. He reviewed pull requests he couldn't fully evaluate. He asked questions that revealed how much he didn't know about database architecture and schema design. The team was patient, but he felt the gap between his product expertise and his engineering fluency every day. The thing that kept him from bailing: the executive sponsor checked in weekly, the rotation mentor normalized the learning curve, and the transition lead in his old team made sure nothing critical fell apart while he was ramping up.
By month three, something shifted. David started contributing to technical discussions — not just asking questions, but offering perspectives shaped by his product background that the engineering team hadn't considered. A debate about query performance turned into a conversation about which user workflows actually required sub-second response times and which could tolerate latency if it meant better data accuracy. That's a product question, but it required engineering context to ask it well. The synthesis of both domains became David's new advantage. When the rotation ended, the organization created a role that didn't fit neatly into either product or engineering — it sat at the intersection, bridging business requirements and technical architecture. That role exists because David stayed long enough to prove the value of the hybrid skill set the rotation revealed.
Stop Treating Rotations as Perks — They're Retention Infrastructure
Most organizations position rotational programs as development opportunities for high performers, which makes them sound optional and aspirational. That framing is wrong. Rotations aren't perks — they're retention infrastructure for the people you can't afford to lose. The professionals most likely to leave mid-career aren't the ones struggling; they're the ones who've mastered their current role and see no path forward. External offers look appealing because they promise growth. If your organization doesn't offer a structured internal alternative, you're choosing to lose those people.
According to Korn Ferry's 2023 talent mobility research, organizations with formal rotational programs report 27% lower voluntary turnover among employees with 5-10 years tenure compared to organizations that rely on informal development conversations. The difference isn't the quality of the opportunities — it's the structure. Informal conversations feel like maybes. Formal programs with named timelines, success metrics, and executive sponsorship feel like investments. People stay when they believe the organization is investing in their growth, not just managing their retention risk.
Here's the contrarian part: rotations should be hardest to access for your lowest performers, not reserved exclusively for your highest. The instinct most leadership teams have is to offer rotations only to people who are already exceeding expectations — but those people are also the most likely to have external options. The better filter is readiness, not performance rating. A mid-performer who's plateaued because they've outgrown their role is a better rotation candidate than a high performer who's still learning in their current function. The goal isn't to reward past success; it's to prevent future attrition by giving people a growth path before they start looking externally.
How Rotational Programs Intersect With Broader Strategic Skill Gaps
One often-overlooked advantage of rotational programs is that they surface and fill skill gaps the organization didn't know it had. When David rotated into engineering, it became immediately clear that the product team didn't understand how data architecture decisions constrained or enabled product features — and the engineering team didn't understand how customer workflows shaped database query patterns. Both gaps were expensive. Product roadmaps included features that were technically impractical. Engineering optimizations solved problems customers didn't have. The rotation didn't just develop David — it created a bridge between two functions that had been operating with incomplete context.
This matters particularly as AI reshapes technical roles across organizations. Professionals who understand both the business strategy and the technical implementation have become critically scarce. David Ohnstad's data product management writing explores this gap in depth — the best product managers now need fluency in data architecture, AI/ML capabilities, and technical feasibility in ways that weren't required five years ago. Rotational programs are one of the few scalable ways to build that fluency without waiting for the external hiring market to produce candidates who already have it. You grow the hybrid skill sets internally, in people who already understand your organization's strategy, customers, and constraints.
Another intersection worth noting: professionals in rotational programs often become the organization's earliest adopters and most effective evaluators of new tools and platforms. When you rotate someone from product into engineering, they start asking questions like "Why are we building this manually when there's a tool for it?" or "Why are we using this tool when it doesn't match how our users actually work?" Those questions come from seeing both sides. The answers often lead to better tooling decisions, faster adoption, and fewer expensive pilot programs that fail because nobody bridged the gap between technical capability and business need. For more on how technical AI capabilities influence product and organizational decisions, the broader conversation about AI/ML implementation continues to reshape what mid-career professionals need to learn to stay competitive.
What Leaders and Practitioners Should Do Differently Starting This Quarter
For leaders: stop treating rotational programs as experimental or reserved for future cohorts. If you're losing mid-career talent to external offers, you already have a rotation problem — you just haven't formalized the solution. Identify three high-performing professionals who've been in their role for 4-7 years and ask them directly: "If we offered you a six-month rotation into [adjacent function], with a clear scope and a decision gate at the end, would that change your thinking about staying?" If the answer is yes for two out of three, you've just validated demand. Build the structure: timeline, success metrics, executive sponsor, transition plan. Treat it like a product launch, not a favor.
For practitioners: if you're feeling plateaued and considering external offers, have the rotation conversation before you start interviewing. The script is: "I've been in this role for [X] years, I'm ready to grow, and I'd like to explore a rotation into [specific function] for [specific timeline]. Can we design that as a formal program with clear outcomes and a decision point, or is that not something the organization is set up to support?" If the answer is no or vague, that's useful data — it tells you whether the organization is serious about internal development or just managing retention. If the answer is yes, you've created an option that didn't exist before. Most people never ask, so they never know whether the rotation path was available.
One more tactical note: rotations work best when they're tied to real organizational priorities, not just individual development goals. David's rotation succeeded because the company needed someone who could bridge product and engineering on a data infrastructure redesign — the rotation solved a business problem, not just a career development request. If you're proposing a rotation, frame it around what the organization needs, not just what you want to learn. The pitch is: "You have [specific gap or challenge], I have [current expertise], and a rotation into [target function] would let me build [hybrid capability] that solves [business problem]." That's a business case, not a personal favor. It's much harder to say no to.
What is a rotational leadership program and how does it work?
A rotational leadership program is a structured internal mobility initiative where employees spend a defined period (typically 6-12 months) working in a different function, team, or role within the same organization. Participants maintain their employment and benefits while gaining new skills, expanding their network, and building cross-functional expertise. The program includes formal onboarding, success metrics, executive sponsorship, and a decision gate at the end to determine the participant's next role.
How do rotational programs reduce employee turnover?
Rotational programs reduce turnover by offering high-performing mid-career professionals a structured growth path without requiring them to leave the organization. According to Korn Ferry's research, companies with formal rotation programs see 27% lower voluntary turnover among employees with 5-10 years tenure. The programs solve the "plateaued but competent" problem — where employees have mastered their role but see no advancement path, making external offers more appealing than staying.
When is the right time to propose a rotational opportunity?
The right time is before you start seriously interviewing externally but after you've identified a specific skill gap or adjacent function you want to learn. Rotational proposals work best when framed around organizational needs rather than personal development alone. If you've been in your current role 4-7 years, are performing well, but feel plateaued, and can identify a cross-functional business problem your rotation would help solve — that's the signal to start the conversation with leadership.
When did you last evaluate whether your organization's internal mobility options are visible and structured enough to compete with external offers — or are you losing people who would have stayed if someone had simply asked? For more on how to build systems that retain talent while driving strategic outcomes, see the full resource on Leadership, Mentorship & Career Development. And if you're interested in how David thinks about building systems outside of work — from data pipelines to furniture — his approach to iterative making is documented at David Ohnstad's woodworking and making.
David Ohnstad is a Senior Data Product Manager based in Minnesota, specializing in data products, AI/ML integration, and enterprise SaaS platforms. Follow his work at github.com/davidohnstad40-netizen.
Top comments (0)