Plan Your First 90 Days as a New Manager with Weekly Goals

Get a 90-day plan split into listen, decide and deliver phases, with weekly goals, named one-on-ones, one early win and checkpoints at days 30, 60 and 90.

You getOne-line plan summary, one-on-one table and each phase as a table

Prompt

Prompt
You are a leadership coach who has onboarded many first-time and newly hired managers. Help me plan my first 90 days as a manager.

Before writing anything, ask me these questions in one message and wait for my answers:
1. What team do I manage (size, function), and am I new to the company or promoted from within?
2. Who are the key people: my boss, direct reports, peers, stakeholders?
3. What problems or expectations were mentioned when I took the role?
4. Any fixed dates in the next 90 days (launches, reviews, deadlines)?

Rules:
- Use three phases: Listen (days 1-30), Decide (days 31-60), Deliver (days 61-90).
- Give every week one goal that starts with a verb and can be marked done or not done.
- Name each one-on-one by person or role, with cadence and one opening question.
- Pick one early win I can finish by day 45, and say why it is low-risk.
- Set one checkpoint at days 30, 60 and 90, each with a number or a yes/no test.

Output format:
1. One-line plan summary
2. One-on-one table: Person | Cadence | First question
3. Each phase as a table: Week | Goal | Done when
4. Early win: what, by when, why
5. Checkpoints: day 30, 60, 90

End with one line naming the plan's biggest assumption and what to confirm with my boss.

Example output

At a glance90-day plan: listen, decide, deliverNew mobile team lead with a week-10 release
  1. ListenDays 1-30One-on-ones with all 5 reports, map review times
  2. DecideDays 31-60Agree 24-hour review rule, set release scope
  3. Early winDay 4524-hour review rule plus daily review slot
  4. DeliverDays 61-90Ship the release in week 10, run a retro
  5. Day 90 checkpointWeek 13Present 90-day results to Dana

Example for: a senior engineer promoted to lead a 5-person mobile team, with a release due in week 10 and complaints about slow code reviews.

Plan summary: Earn trust as the new lead by listening first, fix code review speed, and ship the week-10 release on time.

One-on-ones
PersonCadenceFirst question
Dana (my manager)Weekly, 30 minWhat does success look like for me at day 90?
Priya, Tom, Leo, Mia, Sam (reports)Weekly, 30 minWhat should I keep, start and stop as your lead?
Raj (product manager)BiweeklyWhere does our team slow you down?
Ana (QA lead)BiweeklyWhich bugs reach you that shouldn't?
Listen (days 1-30)
WeekGoalDone when
1Hold first one-on-ones with all 5 reportsNotes logged for each
2Map review times for the last 50 pull requestsMedian time recorded
3Meet Raj and AnaTop 3 pain points listed
4Share what I heard with the teamSummary posted, feedback asked
Decide (days 31-60)
WeekGoalDone when
5Agree a 24-hour review rule with the teamRule written in team doc
6Hand my coding tasks to Priya and TomTickets reassigned
7Set release scope with RajScope signed off
8Draft growth goals with each report5 goals agreed
Deliver (days 61-90)
WeekGoalDone when
9Freeze release featuresNo new tickets added
10Ship the releaseLive in app stores
11Run a release retro3 actions owned
12Recheck review timesNew median recorded
13Present 90-day results to DanaMeeting held
Early win

Introduce the 24-hour review rule plus a daily review slot by day 45. Low-risk because it changes habits, not tools, and the team already named it as their top frustration.

Checkpoints
  • Day 30: All 5 one-on-ones running weekly (yes/no).
  • Day 60: Median review time down from 3 days to under 1.
  • Day 90: Release shipped within 3 days of target.

Biggest assumption: that the release date is fixed. Confirm with Dana whether scope or date flexes if risks appear.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Asking about team, people and deadlines first means the plan fits your real situation instead of generic advice.
  • Listen, decide, deliver phases stop new managers from changing things before they understand the team.
  • Weekly done-or-not goals and numbered checkpoints give you and your boss a clear way to measure progress.

Use this in your first week or just before you start. Have your team size, key names or roles, and known deadlines ready. Works in ChatGPT, Claude or Gemini; answer its four questions in one reply.

Common edits

  • Add a column for which goals your boss should see in your weekly update.
  • Ask for a 30-day version if you are taking over mid-quarter.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Career & Job Search