Kenny's Thinking Garden

PO to PM Transition - Learning Strategy

4 min read

PO to PM Transition - Learning Strategy

Core Idea

At this stage, I believed PO and PM were meaningfully different roles. I recognised I already had some PM-relevant skills, but felt I needed to identify the gaps and commit to a focused set of bets to close them — acquiring tangible evidence of PM capability that the market could see and evaluate.

Why This Approach

  • Learning must be career-outcome driven, not knowledge accumulation
  • Certifications are tools for signalling + structuring thinking, not the goal
  • Prioritisation is critical:
    • Few high-ROI bets > many scattered efforts
  • Depth in strategic product + platform/data > breadth across disciplines
  • Learning must translate into:
    • Stronger market positioning
    • Clearer product identity
    • Interview narrative advantage

Strategic Positioning Goal

Move from:

Execution-focused Product Owner

To:

Strategic Platform / Data Product Manager

  • Owns product direction, not just backlog
  • Thinks in systems (platforms, data, architecture)
  • Uses data & AI to drive decisions
  • Influences at organisational level

The Plan

Core Capability Stack (Reprioritised)

1. Product Strategy & Ownership (Primary Lever)

  • Shift from execution → decision-making ownership
  • Focus:
    • Product strategy & vision
    • Outcome-based prioritisation
    • Platform product thinking

Key Certifications

  • PSPO II (signal + depth)
  • Pragmatic Product Management (strategy grounding)

2. Data & Platform Product Thinking (Differentiator)

  • Build identity as platform/data PM
  • Focus:
    • Event-driven systems
    • Data pipelines & telemetry
    • Internal platform enablement

Key Move

  • Formalise and articulate platform/data narrative

3. AI Product Capability (Future Leverage)

  • Prepare for AI-driven product landscape

Focus

  • AI product lifecycle
  • Evaluation & experimentation
  • Applied AI use cases

Key Certification

4. Leadership & Influence (Scope Expansion)

  • Move from:
    • Stakeholder alignment → decision leadership

Focus

  • Influence without authority
  • Strategic communication
  • Coaching mindset

Key Move

  • ICF Coaching (strategic, not “nice-to-have”)

Learning Structure (Updated)

  • 70% Core
    • Product strategy
    • Platform/data thinking
    • Decision-making
  • 30% Supporting
    • AI
    • Leadership
    • UX / behavioural

Execution Model (Sequenced Learning)

Phase 1 (0–6 months)

  • PSPO II
  • Pragmatic PMC-I
  • Apply directly in current role

Phase 2 (6–12 months)

  • AI Product Management
  • Strengthen positioning (resume, interviews)

Phase 3 (12–24 months)

  • Coaching (ICF)
  • Demonstrate org-level influence

Signals to Watch

— not yet defined —

Open Questions

  • How do I prove strategic product ownership externally (resume, interviews)?
  • What real projects or outcomes can strengthen my platform/data positioning?
  • How deep should I go technically in:
    • Data systems?
    • AI?
  • When should I:
    • Transition into a PM role vs deepen further?
  • At what point does:
    • Leadership (coaching, org influence) become critical vs premature?

Thinking Trace

  • Realisation: the PO Learning Journey plan was too broad and academic-heavy — it tried to cover too many disciplines equally
  • Observed gap: strong execution capability but weak external perception of strategy
  • Trigger: career goal sharpened — target became PM / Senior PM / Platform roles, not just “better PO”
  • Insight: the market values strategy, platform/data thinking, and AI — not breadth of certifications
  • Shift: from “learning everything” to focused positioning bets — fewer areas, higher impact
  • Reduced emphasis on overlapping certifications and academic stacking (Master’s too early, A-CSPO unnecessary)
  • Key realisation: credentials do not automatically lead to PM roles — market values clear product ownership and system-level thinking, not certification count
  • Perception vs reality gap identified: already working on data platform and influencing systems, but market still sees “Product Owner / delivery”
  • Learning must fix external signalling, not just internal capability
  • Market shift toward AI + data + platform roles made future-proofing the positioning urgent
  • Academic paths (Master’s, stacked certs) too slow and expensive for the immediate career move needed

What changed?

v1

— skip —

Why it changed?

v1

— skip —

Connections

Changelog

  • v1 — Initial node

Graph View

Backlinks