The path from IC to senior PM is not more certifications — it is deliberate practice on observable patterns

The path from IC to senior PM is not more certifications. It is deliberate practice.

There is a particular kind of advice mid-career PMs get that is well-intentioned and mostly wrong. The advice is get certified — PMP, PRINCE2, SAFe, CSM, the CAPM — and the implicit theory is that certifications signal capability, capability gets noticed, the promotion follows.

Certifications signal something, but it is not what the advice implies. They signal that the holder studied for a test and passed it. They signal familiarity with a vocabulary. They do not, by themselves, signal capability — and the people who promote PMs to senior roles know this. What they look for is a different signal: a pattern of decisions, made over years, that demonstrates judgment in ambiguous situations. The certifications are at best a side-effect of the underlying work; at worst, a substitute for it.

This piece is the long-form anchor for the Personal & Professional Growth pillar. It walks the IC-to-senior-PM career arc honestly, names the specific skills that gate each transition, treats certifications as the modest signal they are, and ends with the deliberate-practice patterns that produce measurable improvement over a measurable timeline.

§1 — The career arc, honestly

The progression from IC to senior PM is not linear, but the gating skills at each level are surprisingly consistent across orgs.

Junior PM (0-2 years). The work is execution against a charter someone else wrote. The gating skill is reliability — the work you commit to gets done, the status updates land on Friday, the meetings start on time. There is no shortcut here. You cannot replace reliability with cleverness; orgs that promote junior PMs who are clever-but-unreliable regret it.

Mid-level PM (2-5 years). The work is owning a project end-to-end, including the charter. The gating skill is judgment under ambiguity — when the requirements are unclear, when a stakeholder is hostile, when the schedule is at risk, mid-level PMs are evaluated on the call they make in the moment. The certifications are most relevant at this stage as a vocabulary baseline; they are necessary but not sufficient.

Senior PM (5-10 years). The work is owning multiple projects or a complex one with significant political surface. The gating skill is judgment about people — who is reliable, who is selling a story, who needs to be developed, who needs to be moved off the project. The technical PM skills are assumed; the differentiator is the read on humans.

Staff / lead PM (10+ years). The work is shaping how PM is done in the org — methodology choices, hiring, mentoring junior PMs, defining the artifact set. The gating skill is taste — the accumulated judgment about what good looks like at the discipline level. This skill is hard to articulate and harder to teach; the people who get it watch enough projects across enough contexts that the patterns become legible.

§2 — Certifications, treated honestly

Certifications are useful for two specific purposes and useless for everything else.

Useful purpose 1: vocabulary baseline. A PM who has passed the PMP knows the terminology that other certified PMs use. If your industry or org uses that vocabulary heavily (regulated industries, government work, large-enterprise consulting), the cert lowers translation cost. The cert does not make you a better PM; it lets you communicate more efficiently with other certified PMs.

Useful purpose 2: hiring filter. Some orgs use certifications as a hiring filter. Without the PMP (or the PRINCE2, or the SAFe, or whichever the org cares about), the resume does not pass HR screening. If you are interviewing in those orgs, the cert is necessary. The cert is not making you a stronger candidate on the merits; it is opening the door to the merit conversation.

Useless purpose 1: substitute for experience. A PM with five years of running difficult projects is more capable than a PM with one year and four certifications. Hiring managers know this; the cert does not bridge the experience gap.

Useless purpose 2: signal of judgment. Judgment is demonstrated by decisions made under uncertainty. Tests cannot demonstrate judgment because tests have correct answers. The fact that you passed a test means you know what the test thinks the right answer is — not that you would make a good call when the answer is not in the textbook.

The practical recommendation: get the cert your industry actually uses, once, early. Do not collect them. The energy spent on a third certification would have been better spent on a difficult project.

§3 — Deliberate practice, applied to PM

Deliberate practice — the term comes from K. Anders Ericsson's research on expertise development — has three properties: specific, feedback-rich, and at the edge of current ability. Most PMs do not deliberately practice; they accumulate experience, which is different.

Two concrete deliberate-practice patterns work for PM growth:

Pre-mortem journaling. Before each project meeting where a non-trivial decision will be made, write down — for yourself, in 30 seconds — what you predict will happen and what call you would make if you were leading the meeting. After the meeting, compare to what actually happened. Over six months, the gap between your prediction and reality narrows; the pattern of where you are systematically wrong becomes visible. The discipline is the comparison, not the prediction.

Decision logs. For every meaningful project decision, write three lines — what was decided, why (the reasoning, not the conclusion), and what would change my mind. Keep these in a private log. Six months later, review them: which decisions held up? Which were wrong? Why? The decision log is the closest thing PM has to the airline industry's flight-incident reports — it is the artifact that makes invisible work visible enough to learn from.

The orgs and individuals that improve fast tend to do something like one of these patterns deliberately. The orgs and individuals that improve slowly accumulate experience without the feedback loop, which produces years of doing the same thing rather than years of getting better at it.

§4 — Productivity systems, in moderation

The productivity-system genre — GTD, time-blocking, calendar discipline, deep work, OKRs-for-individuals — has produced more advice than any working PM can use. Most of it is overkill. A small set of disciplines covers most of the value; the rest is optimization at diminishing returns.

The disciplines that matter:

• A consistent inbox-zero practice. Email and Slack inboxes that drift past a week of unread items become information graveyards. The PMs who run their projects cleanly almost universally process inboxes daily. Not perfectly; just consistently. The system varies; the consistency is what holds.
• Calendar-as-source-of-truth. Meetings get scheduled on the calendar; commitments to do work get scheduled on the calendar; the calendar is the artifact that says what is happening when. The PMs who let things float in I will get to it without putting them on the calendar tend to drop things at month four.
• A weekly review. Once a week, 30-60 minutes, look at the projects, the inbox, the calendar, the commitments. Adjust. The weekly review is the cadence at which a PM catches drift in their own work — independent of the project's status review.

Beyond these three, the productivity-system genre is mostly preference. If a system works for you, use it. If it requires a third tool and a weekly migration of data between tools, it has stopped being productivity work and started being its own project.

§5 — The four most common career-stall patterns

The career-progression failures we hear about in customer interviews cluster.

Cert-grind without difficult-project exposure. A PM with eight certifications who has never run a project that materially could have failed. The cert collection signals study, not capability. Hiring managers read it as exactly that. Fix: take a project where the right answer is not obvious. Volunteer for the messy one.

Specialist trap. A PM becomes the best-in-org at one thing — JIRA configuration, a specific methodology's ceremonies, a particular tool. The org values them; promotions slow because they cannot move between contexts. Fix: rotate to a different kind of project deliberately, even if it costs you the specialist premium.

Visible-work avoidance. A PM is good but consistently takes on the projects that are unlikely to fail — and unlikely to be visible. Promotions go to PMs who took the riskier projects and shipped. Fix: pick one visible project per year, even if it is uncomfortable; volunteer to be the one to present it.

Mentorship absence. A PM has no senior PM watching their work and giving feedback. They cannot tell when their judgment is off because no one is telling them. Self-improvement asymptotes. Fix: find a senior PM (in the org or out of it) and ask for monthly feedback on real decisions. The 30 minutes per month produces years of compressed learning.

§6 — How to use this pillar

The rest of the Personal & Professional Growth pillar walks the certification landscape (which to get if any), the deliberate-practice patterns in operational detail, the productivity-system minimum-viable approach, and the mentorship-acquisition playbook. If you are early-career, start with the deliberate-practice piece. If you are mid-career and stalled, read the four stall-patterns piece.

The meta-rule: the work is the work. Difficult projects, deliberate practice, and a feedback loop on your own decisions — over years — produce the senior PM that certifications cannot.