Design a 90-day plan for starting a new role
Most 90-day plans are too generic to be useful past day 10. This prompt builds a role-specific plan with concrete milestones and the right questions to ask in each phase.
You are a career strategist helping me build a 90-day plan for a new role. Here is my context:
Role title and level: {{ROLE_TITLE}}
Organization type and size: {{ORG_CONTEXT}}
My background (what I am bringing in): {{MY_BACKGROUND}}
What I know about why the role was created or what problem it solves: {{ROLE_CONTEXT}}
The single most important thing I need to achieve in the first 90 days per my manager: {{PRIMARY_GOAL}}
Follow these steps:
1. Split 90 days into three phases: Listen (days 1–30), Orient (days 31–60), Act (days 61–90). Write a one-sentence purpose for each phase specific to this role.
2. For each phase, write:
- Three concrete actions I should take
- Two questions I should get answered (name the type of person to ask)
- One deliverable or artifact that proves I completed the phase
3. Flag the top two ways someone in this role typically fails in the first 90 days, based on what I described.
4. Identify where my background is a disadvantage in this role and suggest how to compensate.
5. Write a 30-60-90 summary I could share with my manager on day 3 to align expectations — keep it under 150 words.
Do not include generic onboarding advice that applies to every job. {{ROLE_TITLE}}{{ORG_CONTEXT}}{{MY_BACKGROUND}}{{ROLE_CONTEXT}}{{PRIMARY_GOAL}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{ROLE_TITLE}}{{ORG_CONTEXT}}{{MY_BACKGROUND}}{{ROLE_CONTEXT}}{{PRIMARY_GOAL}}. - Paste it into one of the recommended tools below.
- Iterate: tighten constraints in the prompt if the output is generic.
Why this prompt is structured this way
The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.
Pair this prompt with a tool
Notion AI
$8/user/mo add-onAI baked into the docs/wiki/projects tool you already use.
Notion AI is unremarkable as a standalone writer but indispensable if Notion is your team's source of truth — it works on the docs and databases you already have.
Perplexity
$0/mo (Pro at $20)AI search engine with citations.
Perplexity is the answer engine Google would build if it weren't protecting search ad revenue. Cited answers, follow-up questions, focused source modes.
Claude (Anthropic)
$0/mo (Pro at $20)Frontier model with long context and strong reasoning.
Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.
ChatGPT (OpenAI)
$0/mo (Plus at $20)The category-defining general-purpose AI assistant.
ChatGPT has the broadest feature surface: image gen, voice, custom GPTs, web browsing, code execution. Often the right default; sometimes beaten on specific tasks by Claude or Perplexity.
The PlaybookPrompts weekly
One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.
Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.