Career change action plan prompt

When to use it

Use this when you need a focused career transition plan and want a concrete starting point rather than generic advice. Replace the fictional details with your own confirmed facts before using the result in a real setting.

The prompt

## Role
Act as a career development coach. Apply professional judgment while keeping your reasoning understandable to someone who is not a specialist.

## Context
Alex is a fictional retail operations manager with eight years of experience who wants to explore project coordinator roles. Alex has led store openings, trained supervisors, and tracked vendor deliveries but has no formal project management certification. They can spend four hours weekly for eight weeks and cannot leave their current job before securing another role.

## Objective
Create a realistic exploration and positioning plan that tests fit before committing money to training.

## Audience
The primary users are mid-career professionals. Make the deliverable usable in their day-to-day work, with enough explanation to support decisions but no unnecessary background lecture.

## Requirements
Map existing experience to likely coordinator responsibilities, identify evidence gaps, and propose weekly actions. Include informational interviews, job-description analysis, one small portfolio artifact using fictional data, and targeted application preparation. Provide sample achievement bullets without inventing metrics. Include a checkpoint after week four and alternative actions if interviews reveal a skills mismatch, while keeping every week within the four-hour limit.

## Constraints
Do not guarantee employment, recommend expensive credentials as a prerequisite without evidence, fabricate titles, or encourage sharing confidential employer information. Work only with the scenario and any material explicitly supplied. Label assumptions and distinguish proposed actions from confirmed facts.

## Tone & style
Be direct, thoughtful, and specific. Prefer plain English, concrete examples, and short paragraphs. Match the language to the intended reader rather than relying on jargon or generic motivational phrasing.

## Output format
Present the requested deliverable first, using descriptive headings and tables only where they improve usability. Keep supporting notes separate from copy intended for publication or direct use. Finish with a short checklist of outstanding decisions or verification steps.

## What to avoid
Avoid filler, unsupported certainty, and details invented to make the result seem more complete. Do not let a polished presentation conceal missing information or conflicting requirements.

## Success criteria
Alex finishes with a clearer target role, examples of transferable experience, feedback from real conversations, and a defensible next decision. Check the result against the stated constraints before presenting it and correct any inconsistencies you find.

## Clarifying questions
Ask up to three focused questions only if missing information would materially change the result. Otherwise proceed with the fictional scenario, state any necessary assumptions briefly, and identify what a real user should confirm before relying on the output.

Why it works

• The scenario gives the model concrete facts and boundaries instead of asking it to invent a brief.
• The requirements specify the actual deliverables and the important edge cases for this task.
• The constraints make unsupported claims and unapproved commitments harder to slip into the result.
• The success criteria turn review into a practical check: alex finishes with a clearer target role, examples of transferable experience, feedback from real conversations, and a defensible next decision.

Make it yours

Build a tailored version with PromptDeck by replacing the fictional scenario with your own context, audience, and constraints. Keep the verification steps so the final result reflects what you actually know.