“I want to get better at my job” is a feeling, not a plan. A 30-60-90 turns that feeling into thirteen weeks of moves you can actually point to — what you learned, who saw it, and what changed because you were there.
Why a vague goal fails you
Most people set a career goal once a year, usually the week before a review, and it sounds like “take on more responsibility” or “develop my skills.” Then twelve months pass, the calendar fills with other people’s priorities, and at review time you’re scrambling to remember what you actually did. The goal didn’t fail because you were lazy. It failed because nobody can do “take on more responsibility.” There’s no Tuesday-afternoon version of it.
A 30-60-90 plan fixes that by splitting one fuzzy ambition into three short, different jobs. The first 30 days you learn — you earn the right to have opinions. The next 30 you build visibility — the right people start to know what you’re working on. The final 30 you deliver a result — one thing that’s measurably better because of you. Same plan whether you just started somewhere new or you’ve been in your seat for three years and want to climb. The clock just starts on a different day.
“This year I want to grow into a more senior role and take on bigger projects.”
“By day 90 I’ll have shipped the new client-onboarding checklist, cut onboarding from twelve days to five, and presented the before-and-after to the team.”
Days 1–30: learn enough to be useful, fast
The first stretch isn’t about impressing anyone. It’s about absorbing how things actually work, which is rarely how the org chart says they work. Resist the urge to “add value” in week one with a deck full of suggestions. You haven’t earned the context yet, and confident newcomers who reorganize things they don’t understand are how good ideas get a bad name.
Instead, spend these 30 days doing three things. First, map the work. What does your team produce, who consumes it, and where does it get stuck? Second, learn the one skill that’s blocking you — the spreadsheet function, the tool, the part of the codebase, the process everyone seems to know but you. Third, book short conversations. Ask the people around you what “good” looks like in your role and what they wish someone would just handle. That last question is gold: it’s a map of unclaimed wins.
Keep a running note from day one. Every time something confuses you, write it down before you get used to it: fresh eyes are a one-time asset, and a tidy list of “here’s what tripped me up” becomes your first visible contribution in month two. This is also where you start documenting your wins, because the small early ones are the easiest to forget and the easiest to lose.
“I’m still learning how everything fits together here. If you could wave a wand and have someone reliably take one recurring headache off your plate, what would it be?” — ask three people. The answer that comes up twice is your day-90 project.
Days 31–60: get visible without being a megaphone
Here’s the uncomfortable truth quiet, competent people learn too late: the work doesn’t speak for itself. Someone has to make it legible to the people who decide raises and projects. That’s not bragging; it’s translation. The goal of this stretch is that by day 60, your manager and one or two people beyond your team can describe what you’re working on without checking.
The simplest tool is a short, regular update. A three-line Friday message — what moved this week, what’s next, what you need — does more for your reputation than any single heroic late night, because it’s repeated and it’s easy to forward. This is the whole engine behind learning how to become more visible at work: make your progress something other people can see and share without effort.
Visibility also means raising your hand for the right thing. Not every stretch task — the one that touches the headache you heard about in week one. And it means letting your face be known beyond your immediate team, which is just networking without feeling fake applied internally: a coffee with the person whose work feeds yours, a thoughtful question in a meeting where you usually stay quiet.
You quietly fix the broken weekly report every Monday. Nobody knows it was ever broken, and nobody knows you fixed it.
“Heads up — the weekly report was double-counting refunds, so our numbers were off by about 8%. I’ve patched it and added a check so it can’t happen again.”
Days 61–90: ship one result you can name
The final stretch is where the plan earns its keep. By now you understand the work and the right people know your name. Now you finish one thing — not five half-things — that someone outside your head can see the value of. One clear result beats a long list of busywork every time, because people remember outcomes, not activity.
Pick the project you’ve been circling since week one and drag it across the line. Then do the part most people skip: capture the before and the after in plain numbers. “I rebuilt the onboarding checklist” is forgettable. “New hires used to take twelve days to make their first sale; with the new checklist the last three did it in five” is a sentence your manager will repeat in a room you’re not in. That’s the whole point.
If you’re aiming higher than just doing the job well, this result becomes evidence. It’s the spine of how to prepare for a promotion conversation and, when the timing’s right, the proof behind how to ask for a raise — because you’re no longer asking on the strength of being a nice person who tries hard. You’re asking on the strength of a number.
“In the last quarter I worked on onboarding, helped with the report fixes, and supported a few other projects across the team.”
“I shipped the onboarding checklist that cut new-hire ramp from twelve days to five — and presented it so the rest of the team could reuse it.”
Using it in a brand-new role
If you’re starting somewhere new, the plan maps perfectly onto your first quarter, and it doubles as a thing you can literally hand to your manager in week one. Saying “here’s how I’m thinking about my first 90 days — does this match what you need?” is one of the strongest first impressions you can make, because it signals you’ll drive your own ramp instead of waiting to be steered.
Just calibrate the result down. In a new job, day 90 doesn’t need to be a transformation. A solid “learned the systems, took one recurring task fully off my manager’s plate, and earned trust” is a genuine win. Trying to overhaul the department in your first quarter is how new hires become cautionary tales.
Using it to grow where you already are
If you’ve been in the same seat for a while, the 30-60-90 is your antidote to drift. The trap of a stable job is that you get good enough to coast, and coasting feels fine right up until you realize three years passed and your resume says exactly what it said before. Starting a fresh 90-day clock — pick one skill, one visibility habit, one result — turns a flat stretch back into a climb.
The deepest version of this is to run the plan against the job above yours. Spend your learning stretch figuring out what that role actually does, your visibility stretch being seen doing pieces of it, and your results stretch delivering one thing that role would own. By day 90 you’re not asking to be promoted into the next job. You’re pointing at evidence that you’re already doing it.
Grab The 30-60-90 Career Growth Plan (PDF) — a one-page worksheet with a slot for each stretch. Print it, fill in your one skill, one visibility habit, and one result, and stick it where you’ll see it on a Monday.
Open a blank note and finish one sentence out loud, in real words — for example, “By day 90, the thing that will be measurably better because of me is our new-hire onboarding: I’ll have cut it from twelve days to five.” Don’t worry if it’s rough — just name the one result. Then put a recurring reminder on day 30 and day 60 to check your progress. Pair it with a weekly wins habit and you’ve started the clock.
References: Government of Canada Job Bank for Canadian role expectations and wage data. This is practical advice drawn from how growth plans actually play out at work — not a promise of a promotion, raise, or any particular outcome.
