# Executive Career Transition Strategy

Build a structured career transition plan for a senior-level move, covering positioning, narrative, network activation, and risk mitigation.

## Prompt

Act as an executive career strategist. I am planning a career transition with the following details:
{{transition_details}}

Build a transition strategy covering:

1. Narrative arc — craft a 3-sentence professional narrative that explains this transition in a way that sounds intentional and forward-moving, not reactive or vague.
2. Transferable strength mapping — identify the 4-5 skills or achievements from my current/past role most relevant to the target role, and how to frame each concisely.
3. Credibility gaps — identify what a hiring manager or board might be skeptical about in this transition, and how to preemptively address each concern.
4. Network activation plan — outline a prioritized order for reaching out to my network (who first, and why), and a short template for the first message.
5. 90-day proof plan — if I get the role, outline 3 early wins that would validate the transition was the right call.
6. Risk mitigation — identify the single biggest risk to this transition succeeding and one concrete step to reduce it.

Present this as a structured strategy document.

## Best for

Senior professionals and executives planning a significant career pivot (industry change, level change, or function change) who need a rigorous positioning strategy rather than generic resume tips.

## Compatible tools

- Claude
- ChatGPT

## How to use

- Replace {{transition_details}} with your current role, target role, and any relevant background or gaps you're aware of.
- Use the narrative arc as the foundation for your LinkedIn headline, resume summary, and interview opening statement.
- Work through the network activation plan in the suggested order rather than reaching out randomly.
- Revisit the 90-day proof plan once you land the role to track against it.

## Customization tips

- Mention any specific companies or industries you're targeting so the credibility gap analysis is more precise.
- Ask for the narrative arc to be rewritten in a shorter, elevator-pitch version for networking conversations.
- Follow up by asking the model to draft the actual first outreach message for your top 3 network contacts.

## Example input

Act as an executive career strategist... Transition details: I'm a VP of Engineering at a mid-size fintech company, moving toward a Chief Product Officer role. I have strong technical background but limited formal product management title experience, though I've led cross-functional product decisions for 4 years.

## Example output

1. Narrative arc: 'After leading engineering teams that shipped products directly shaping company revenue, I'm moving into product leadership to own that impact end-to-end. My technical depth means I can bridge product vision with real delivery constraints in a way pure product leaders often can't.'
2. Transferable strength mapping: (a) 4 years of de facto product decision-making, framed as 'product strategy ownership without the formal title', (b) direct P&L visibility from engineering roadmap prioritization, (c) cross-functional stakeholder management with sales and customer success...
3. Credibility gaps: a board may question lack of formal 'Product Manager' title history; address this by leading with specific product outcomes (metrics, launches) rather than titles, and by securing one or two references who can speak directly to your product judgment.
4. Network activation plan: start with former product peers who've seen your product judgment firsthand (highest credibility signal), then move to your engineering network for referrals into product-adjacent roles, then cold outreach to target companies last.
5. 90-day proof plan: (a) ship one visible product decision within the first 60 days, (b) build a lightweight prioritization framework the team adopts, (c) establish a clear relationship with sales/customer success leadership.
6. Risk mitigation: biggest risk is being perceived as 'still an engineer' rather than a product leader; mitigate by deliberately shifting language in early meetings toward customer and market framing rather than technical framing.