A certification path is a sequence attached to a role, a sector, and a calendar you can fund. It is not a Pokédex. Choose the next stamp that unlocks a conversation you cannot have today — then go back to delivering something someone can point at.
Start from the role, not the catalogue
Write one paragraph: the role you want in two to three years, the sector and country, and the methods that room already speaks. Then list the credentials that appear on real adverts for that role — frequency, not folklore. Your path is that list, in an order you can become eligible for. Everything else is a distraction with a coupon code.
Typical honest sequences, not laws: an early-career generalist might take CAPM or a Scrum credential before PMP eligibility exists. A UK government delivery manager might need PRINCE2 Practitioner before anyone cares about PMP. A Scrum Master who already runs teams might sit PSM and skip PMI entirely. A programme manager moving toward PMO leadership might want PMP plus the organisation's local governance dialect. Copy the sequence that matches the paragraph, not a generic '101 to Pro' fantasy ladder.
Do one credential at a time. Parallel prep for two exams is how both get a half-effort and a resit. Finish, apply it for a quarter, then decide whether the next stamp is still the bottleneck. Often the bottleneck has moved to experience, a security clearance, or a domain (data, construction, clinical) that no PM exam covers.
Eligibility is a project. Evidence is the product.
Work backwards from the handbook. If PMP needs documented hours you do not have, the next 'certification' is a project where you lead — or CAPM, or a wait. If a Scrum course is the constraint, book the course when you can practise the week after, not three months before a busy release. Treat eligibility gaps as scope, not as personal failure.
Keep an evidence file as you go: charters, PI plans, risk registers, a before-and-after board, a note from a sponsor. Hiring conversations and some applications will ask you to talk about work, not logos. The file also stops you from applying to PMP with a memory of hours that will not survive an audit.
Ask your employer what they will fund and what they will count as development time. Get it in writing. A verbal 'we support certification' that dies at the purchase-order stage is a risk you should have logged. If they will not fund it, that is information about whether the stamp is for their filter or only for your next filter.
Stop collecting. Start compounding.
Set a kill rule. If a credential will not change the conversations you can enter this year, do not sit it. If you already have the stamp the market asked for, further entry-level badges are diminishing returns. Advanced levels in the same family can be worth it when the work got harder — not when you are bored on a Sunday.
Revisit the path when the role changes. Moving from team-level Scrum into a train or a PMO changes the dialect. Doubling down on a third Scrum logo while your new job is portfolio governance is nostalgia. Update the paragraph. Update the sequence. That is change control for your career, which is a project you are allowed to re-baseline.
Measure the path the way you would a benefit: interviews reached, scope of roles you are trusted with, and whether your week looks more like the job you wanted. Do not measure it in logos per year. A quiet year in which you ran a nasty integration and wrote a clean lessons-learned note will outrank a noisy year of exam receipts. The receipts are easier to photograph. The work is what the next sponsor remembers.
Course complete — what's next
Build a path from role, sector, and live eligibility rules. One credential at a time, evidenced by work you can show. Stop when the next badge would not change a conversation.
You now have an honest map of why certs exist, how CAPM and PMP differ, how Scrum stamps split by organisation, where PRINCE2 actually travels, and how to sequence without becoming a collector. Check the current issuer handbooks before you spend, then pick one next action — a handbook page, a conversation with your manager about funding, or a project assignment that creates hours you can defend.