"I want a promotion" is a wish. A 30-60-90 plan is a wish with dates on it — and dates are what move you up.
Why ninety days, and why three phases
Most people try to do everything at once: learn the job, look impressive, and deliver big results, all in week one. That is exhausting and it shows. The 30-60-90 plan spreads the work across three phases that build on each other. First you learn, so you are not guessing. Then you become visible, so the right people know what you are working on. Then you deliver results you can actually point to. Skip a phase and the next one wobbles. You cannot be visible for work you have not learned, and you cannot show results for work nobody knew you were doing.
One rule sits over all of it: show impact, not just activity. "I attended every meeting" is activity. "I cut our onboarding time from X days to Y" is impact. Hold every plan item up to that test.
Days 1–30: Learn (get your bearings)
The first month is for information, not heroics. You are mapping what "good" looks like one level up, and quietly closing the gaps. Resist the urge to volunteer for everything — you do not know yet what is worth volunteering for.
- Get the real criteria. Ask your manager what specifically separates your level from the next one. Write it down word for word.
- Find the gap. List two or three skills the next role needs that you do not have yet. Pick one to start.
- Watch the people one rung up. What do they do differently? How do they talk in meetings? What do they say no to?
- Read the room's metrics. Learn which numbers your team is judged on. Those are the numbers your results will eventually have to move.
"I'd like to grow into a [next-level role] over the next while. Could we spend 15 minutes on what 'ready' looks like to you? I want to aim at the right things instead of guessing — and I'd rather hear it now than at review time."
Days 31–60: Get visible (do the work where people can see it)
By day 31 you know what matters. Now make sure your work is not a secret. Visibility is not bragging — it is making your contribution legible to busy people who are not watching you closely. Quiet competence is lovely and routinely overlooked.
- Volunteer for one cross-team thing. Pick a project where people outside your immediate manager will see your name on it.
- Share progress in writing. A short weekly or biweekly update — what you shipped, what is next, what is blocked — does more than you think.
- Speak up in the room you are already in. One useful question or summary per meeting. You do not need a TED talk.
- Help one teammate publicly. Credit them too. Generous people get remembered.
Here is the difference visibility makes in something as small as a status update:
"Worked on the reporting stuff this week. Made some progress."
"Shipped the new weekly report — it replaces the manual pull that took the team about X hours every Monday. Next: automating the second half. Blocked on access to the billing data; flagged to [name]."
Days 61–90: Show results (point at something)
The final stretch is where the plan earns its keep. You want one or two things you can point at and say "I did that, and here is what changed." It does not have to be enormous. It has to be finished and measurable.
- Close out your day-30 skill gap. Name the skill, name the proof — a project, a certificate, a thing you now do solo.
- Quantify one win. Time saved, errors reduced, revenue touched, customers helped. Use real numbers; if you do not have exact figures, estimate honestly and say so.
- Write your two-line story. "I owned X. It moved [metric] from A to B." Memorize it — you will use it in your review and your next interview.
- Ask the direct question. Name what you have done and ask what is left between you and the next level.
When you bring it to your manager, frame the past as evidence and the future as a question:
"I feel like I've been doing a lot lately. Do you think I could get promoted soon?"
"Over the last quarter I owned the reporting project and cut Monday's manual work from X to Y hours, and I closed the gap we talked about on [skill]. What's the remaining gap between where I am and [next level], and what timeline feels realistic to you?"
"Three months ago we talked about what 'ready for [next level]' looks like. Here's what I did: [result 1 with a number], [result 2 with a number]. I'd love your honest read — am I close, and if not, what's the one thing you'd want to see next?"
Asking is not pushy. A follow-up is not begging, it is professional signal — it tells your manager you are serious and saves them from having to read your mind.
Make it real (and keep it light)
Write the plan somewhere you will actually look at it — a note, a doc, the back of a receipt, whatever you will not lose. Three headers, a few bullets each. Check it weekly. If a phase slips, slide the dates; do not scrap the plan. And if you want to ground your "what changed" numbers in real wage and role data, Canada's Job Bank is a free place to check what your title and the next one typically pay and require.
Open a blank note and write three headers — Days 1–30 (Learn), 31–60 (Visible), 61–90 (Results). Under each, write just one bullet you could start this week. That rough draft is your 90-day plan. Refine it later; start it now.
Useful: Government of Canada Job Bank — wage and outlook data for your role and the one above it.
Comments