PM professional development fails when it's a pile of bookmarks. I'd treat it like a product: goal, bets, review cadence.
Areas I'd develop on purpose
- Discovery & product sense — interviews, prototypes, kill criteria
- Execution — roadmaps, delivery hygiene, stakeholder management
- Analytics fluency — enough to challenge numbers
- Leadership — writing, conflict, coaching without authority
- Domain depth — the market you serve
A simple quarterly plan
| Input | Example |
|---|---|
| One craft bet | Run 5 customer interviews with notes others can use |
| One feedback loop | Ask an EM what to stop doing |
| One artifact | Strategy memo or teardown published internally |
| One learning block | Course module or book—finished, not wishlisted |
Review the plan at month's end. Keep what moved your work; drop vanity learning.
What I'd skip
- Collecting certificates with no practice
- Only consuming Twitter threads
- Waiting for your company to "send you to training"
A PM Certification works best as structure inside a practice plan—not as the whole plan. The newsletter is an easy weekly input.