Map the career paths open to an IT project manager and write a development plan for the skills your next role needs.
Why it matters
You have now covered the full range of an IT project manager's job, from choosing a delivery approach to recovering a failing project. This last lesson looks forward. IT project managers grow in several directions, and the skills that got you here are not all the skills the next role needs. A deliberate plan beats waiting to be noticed. This lesson maps the common paths, the skills each one needs, and how to build them while you are still doing your current job.
Common next steps
| Path | What changes | Skills to build |
|---|---|---|
| Senior project manager | Bigger, riskier, more political projects; often vendor-heavy | Contract and commercial skills, executive communication, recovery experience |
| Program manager | Coordinates several projects for shared benefits | Benefits management, roadmaps, dependency management, organisational change |
| Technical program manager (TPM) | Common in tech companies; leads cross-team engineering programs | Deeper technical understanding (systems design, APIs, cloud), engineering metrics |
| PMO lead or portfolio manager | Runs governance, methods and portfolio decisions | Portfolio prioritisation, financial analysis, capacity planning, coaching |
| Delivery manager or agile coach | Focus on team flow and agile practice | Coaching, facilitation, flow metrics, agile at scale |
| Product manager | Owns what to build and why, rather than how to deliver it | Customer research, product strategy, data analysis |
None is "higher" than the others; they are different jobs. Choose the one whose daily work you would enjoy.
What changes when you move to program management
Program management is the most common next step, and it changes how you spend your time:
- From outputs to outcomes. A project delivers a portal. A program is judged on whether patients actually book online and whether call volumes fall. You spend time on benefits, measures and adoption, often after projects close.
- From one plan to a roadmap. You sequence several projects, decide what each must deliver for the next, and change the roadmap as you learn.
- From managing tasks to leading leaders. Your direct counterparts are project managers, engineering managers and directors. Influence without authority matters even more.
- From one budget to trade-offs between budgets. You move money and people between projects to protect the overall benefit.
- From team change to organisational change. You plan communications, training and new ways of working across departments.
How to build the skills now
You do not need the title to start practising the work:
- Volunteer for cross-project work: shared environments, a joint release, a dependency map for your department.
- Own the benefits on your current project: define them, measure the baseline, and track them after go-live.
- Ask to attend (or take notes at) portfolio or investment board meetings to see how decisions are made.
- Lead a recovery. Few experiences teach more, and they make strong interview stories.
- Build technical depth if you are aiming for a TPM role: system design basics, cloud fundamentals and how your company's software is built and deployed.
- Find a mentor one level above where you want to be, and a peer group of other project managers to swap lessons with.
- Keep your experience log and stories: for each project, note one example each of influence, a hard decision, a recovery and a measurable result.
Worked example: a development plan
Sam has led the Northside portal project and wants to become a program manager within two years.
| Skill gap | Evidence of the gap | Action in the next 6 months | Measure |
|---|---|---|---|
| Benefits management | Has never tracked benefits after go-live | Own the portal's benefit tracking for 6 months after rollout; report to the steering committee monthly | Benefit report delivered; call abandonment trend shown |
| Roadmapping several projects | Has only planned single projects | Draft a combined roadmap for the Digital Access projects with the PMO | Roadmap reviewed by the program sponsor |
| Executive communication | Steering packs are long | Ask the sponsor for feedback on each pack; cut to one-page summaries | Sponsor feedback; meetings finish early |
| Credential | Has the experience but not the certificate | Apply for the PMP using the experience log | Exam booked |
The plan is specific, tied to real work, and measurable. Sam reviews it with a mentor every quarter.
Common mistakes
- Waiting for a promotion before practising the next role's work.
- Collecting certificates instead of experience.
- Choosing a path because of the title rather than the daily work.
- Not telling your manager what you want. They cannot support a plan they do not know about.
Quick recap
- IT project managers can grow into senior PM, program, TPM, PMO, delivery or product roles.
- Program management shifts the focus from outputs to outcomes, from one plan to a roadmap, and from tasks to leading leaders.
- Practise the next role's work now through benefits tracking, cross-project work, recoveries and mentoring.
- Write a specific, measurable development plan and review it regularly.
Try it
Open the Do tab and write your own development plan.