Home – News & Article

Career Progression Plan Example: Mapping Your Next Moves

Career progression plan example: a professional climbing stairs in a bright modern office

A career progression plan example answers the question every ambitious professional eventually asks: what, concretely, are the steps between where I am and where I want to be? Progression — moving through levels of seniority, responsibility and reward — rarely happens by accident or by time served alone. It happens when someone maps the stages ahead, identifies what each stage demands, and prepares for the next one before it opens. This article walks through a complete progression plan for a realistic professional, then shows you how to build the same map for your own career.

Progression Planning Is Different From General Development

Development is about getting better at your work; progression is about moving to bigger work. The two overlap, but a progression plan is specifically organised around levels: the expectations of your current grade, the grade above it, and the evidence that decision-makers need to see before they move you. That focus changes what you prioritise. Instead of learning a little of everything, you target the exact capabilities the next level rewards.

Thinking in stages also protects your motivation. A distant goal like “reach senior management” becomes a sequence of near, winnable steps, each with its own milestone. It is the long view described in our article on lifelong career development, applied to the specific mechanics of moving up.

Career Progression Plan Example: From Analyst to Senior Analyst

Our example is Priya, a data analyst with two years in her role, aiming for a senior analyst position within about eighteen months. Her plan, written after her mid-year review, looks like this.

Current stage: Analyst. Proven at: building accurate reports, answering ad-hoc data questions, reliable delivery. Next stage: Senior Analyst. What changes at that level: owning analysis end to end, advising stakeholders rather than just supplying numbers, quality-checking others’ work, and presenting findings to leadership.

Milestone 1 (months 1–6) — Depth: become the team’s recognised expert on the customer dataset; document her methods so others can reuse them. Evidence: two reference guides adopted by the team.

Milestone 2 (months 4–10) — Influence: present one analysis per quarter to the leadership forum; translate findings into a recommendation, not just a chart. Evidence: presentation record and one adopted recommendation.

Milestone 3 (months 8–14) — Leverage: review junior analysts’ work, run one training session on reporting standards. Evidence: reviewed projects and session feedback.

Milestone 4 (months 12–18) — Readiness: lead one cross-team analysis project from scoping to delivery. Evidence: completed project with stakeholder references.

Alongside the milestones sit two supporting habits: a monthly skills log, and a quarterly check-in with her manager to test whether the evidence is landing. The staged structure mirrors the frameworks in our overview of the career development model, simplified for one person’s use.

Reading the Example: What to Steal for Your Own Plan

Notice that every milestone produces evidence, not just activity. “Attend a course” is an activity; “present an adopted recommendation” is evidence. Progression decisions are made on evidence, so plan backwards from what a panel or manager would need to see. Notice also the sequencing: depth first, then influence, then leverage over others’ work, then a flagship project. That order reflects how trust is actually granted — you are given people and projects after you have shown judgement, not before.

Your stages will differ by profession, but the pattern travels. A teacher progressing to head of department, a nurse to sister, a developer to tech lead — each path has the same anatomy: deepen expertise, widen influence, multiply your effect through others, then prove readiness on something with your name on it. The techniques in our guide to career advancement techniques will help you execute each stage once your map exists.

Building Your Own Progression Map

Start by finding the real criteria for the level above you: the job description, your organisation’s competency framework, or a direct conversation with your manager about what distinguishes the next grade. Write down the four or five capabilities that define it. Then audit yourself honestly against each one — where is your evidence already strong, and where is it missing entirely?

Convert the gaps into staged milestones spread over twelve to twenty-four months, each with its evidence test attached. Anchor the milestones to goals you can control; our article on personal development work goals covers how to phrase them so they stay actionable. If your organisation offers structured routes — acting-up assignments, secondments, sponsored qualifications — weave them in; employers build such routes deliberately as part of workforce upskilling, and using them signals that you are progressing on purpose.

Reviewing and Adjusting Your Progression Plan

A progression plan should be reviewed on the same rhythm as your milestones: briefly every month, properly every quarter. At each quarterly review, test three things. Is the evidence accumulating — can you point to new artefacts, feedback and results since last time? Are the milestones still aimed at the right level, or has the role above you changed shape? And is the timing still realistic, given what has actually happened in your team?

Adjust without drama when the answers demand it. Moving a milestone by a quarter because a project was cancelled is maintenance, not failure. What you should not do is let the plan drift silently — unreviewed plans expire, and the professionals who progress are the ones whose maps stay current. If your manager changes, make re-agreeing the plan one of your first conversations; a new manager who inherits your evidence file and your milestones can champion you far sooner than one who has to guess at your ambitions.

When Progression Stalls

Even a good plan meets obstacles: a frozen vacancy, a new manager, a restructuring. Distinguish a delayed plan from a dead one. If the milestones keep producing evidence and your reviews keep happening, a delay is survivable — readiness compounds. If the route itself has closed, the same evidence makes you competitive elsewhere, and a change of employer or direction becomes a progression decision rather than a defeat, a theme we explore in our piece on management growth opportunities.

The deeper point of this career progression plan example is control. You cannot control when a vacancy opens, but you can control whether you are visibly ready when it does. Map your stages, build your evidence in order, and review the map quarterly. Progression then stops being something that happens to other people and becomes the predictable result of a plan you are already following.

Finally, keep a copy of every version of your plan. Looking back at last year’s map — at milestones that once felt distant and are now ordinary parts of your job — is the clearest proof that the system works. Progression feels slow from inside a single quarter and unmistakable across a few years. Your only task is to keep the map current and keep walking it.