Kenny's Thinking Garden

PO Learning Journey

5 min read

PO Learning Journey

Core Idea

Build a structured learning journey to grow as a stronger Product Owner by deepening core capabilities (Product, Agile, Data, UX) and expanding into complementary areas (behavioral science, leadership).

Why This Approach

  • Learning should be structured into Core and Supplementary areas
  • A strong Product Owner requires multi-disciplinary capability
  • Growth is achieved through:
    • Certifications (structured knowledge)
    • Books (conceptual depth)
    • Practical application (current role)
  • Learning should be done in phases (quarterly focus)
  • Build on existing certifications rather than restarting

My Current Baseline (Experience + Certifications)

Work Experience Strengths

  • Strong in Agile execution and backlog management
  • Experience in SaaS product (EntriWorX Insights)
  • Exposure to:
    • Data/analytics (user adoption, engagement metrics)
    • UX improvements (conversion, retention)
    • Cross-functional collaboration (SAFe environment)
  • Background across:
    • Engineering → Web → Product Owner

Existing Certifications

  • Certified Scrum Product Owner (CSPO) – foundational
  • SAFe Product Owner/Product Manager (SAFe POPM)
  • ITIL Foundation (Service Management)
  • PRINCE2 Practitioner (Project Management)

Current Level Assessment

  • Strong in:
    • Delivery and execution
    • Agile practices
    • Stakeholder coordination
  • Developing in:
    • Product strategy
    • Data-driven decision making
    • UX depth
  • Limited in:
    • Advanced product thinking
    • Behavioral science
    • Leadership influence

The Plan

Core Disciplines (Primary Focus Areas)

1. Advanced Product Management

What It Is

The discipline of defining product vision, strategy, roadmap, and delivering value across the product lifecycle.

Why It Is Relevant to Me
  • Core to transitioning from Product Owner → Product Manager
  • Needed to move from:
    • Execution → Strategy
  • Directly applicable to:
    • SaaS product development (EntriWorX Insights)
Key Concepts
  • Product vision and strategy
  • Roadmapping and prioritisation (RICE, WSJF)
  • OKRs and product metrics
  • Product-market fit
Applications in My Work
  • Define clearer product direction beyond backlog
  • Align stakeholders on long-term roadmap
  • Improve prioritisation decisions
Learning Resources
  • Certifications:
  • Books:
    • INSPIRED – Marty Cagan
    • Escaping the Build Trap – Melissa Perri
My Current Level
  • Intermediate (execution-heavy, strategy-light)
Next Step
  • Strengthen product strategy thinking
  • Move beyond backlog ownership

2. Agile and Scaled Agile (SAFe)

What It Is

Frameworks for delivering value iteratively and coordinating multiple teams.

Why It Is Relevant to Me
  • Already working in SAFe environment
  • Needed to handle:
    • Cross-team dependencies
    • Large-scale coordination
Key Concepts
  • Scrum, Kanban
  • SAFe ART, PI Planning
  • Continuous delivery
Applications in My Work
  • Improve backlog alignment with PI objectives
  • Better manage dependencies across teams
Learning Resources
  • Certification:
    • Already have SAFe POPM
  • Books:
    • Essential Scrum
My Current Level
  • Strong (operationally experienced)
Next Step
  • Move from execution → influencing system-level decisions

3. Data-Driven Product Ownership

What It Is

Using data to guide product decisions, validate hypotheses, and measure success.

Why It Is Relevant to Me
  • Already using analytics for:
    • User engagement
    • Conversion
  • Need deeper capability to:
    • Drive decisions with data
Key Concepts
  • A/B testing
  • Product metrics (conversion, retention)
  • Analytics tools (Amplitude, GA)
Applications in My Work
  • Improve feature validation
  • Use data to prioritise backlog
Learning Resources
  • Certifications:
    • Google Analytics
  • Books:
    • Lean Analytics
My Current Level
  • Intermediate
Next Step
  • Improve experimentation capability
  • Strengthen data interpretation

4. User Experience (UX)

What It Is

Designing intuitive, user-centered product experiences.

Why It Is Relevant to Me
  • Already worked on:
    • Conversion improvements
    • Retention improvements
  • UX directly impacts product success
Key Concepts
  • User journeys
  • Usability testing
  • Information architecture
Applications in My Work
  • Better collaboration with designers
  • More informed prioritisation
Learning Resources
  • Certifications:
    • UX Design Institute
  • Books:
    • Don’t Make Me Think
My Current Level
  • Intermediate
Next Step
  • Deepen UX understanding beyond surface-level improvements

Supplementary Disciplines and Approaches

1. Behavioral Economics

What It Is

Understanding how users make decisions and behave.

Why It Is Relevant
  • Helps influence user behaviour
  • Supports better product design decisions
Key Concepts
  • Nudge theory
  • Loss aversion
  • Anchoring
Applications
  • Improve onboarding flows
  • Influence feature adoption
Learning Resources
  • Books:
    • Nudge
    • Predictably Irrational
My Current Level
  • Beginner
Next Step
  • Build foundational understanding

2. Design Thinking

What It Is

User-centered problem-solving approach.

Why It Is Relevant
  • Helps with innovation and ideation
Key Concepts
  • Empathy
  • Ideation
  • Prototyping
Applications
  • Workshops for feature ideation
  • Early validation of ideas
Learning Resources
  • IDEO U courses
  • Change by Design
My Current Level
  • Beginner
Next Step
  • Apply in workshops

3. Leadership and Stakeholder Management

What It Is

Influencing and aligning stakeholders.

Why It Is Relevant
  • Critical for scaling impact as a Product Owner
Key Concepts
  • Communication
  • Negotiation
  • Conflict resolution
Applications
  • Align cross-functional teams
  • Influence product direction
Learning Resources
  • Books:
    • Crucial Conversations
    • Never Split the Difference
My Current Level
  • Intermediate
Next Step
  • Improve influence without authority

Execution Strategy

Learning Approach

  • Combine:
    • Certifications (structured learning)
    • Books (conceptual depth)
    • Work application (practical)

Learning Cadence

  • Focus on 1–2 areas per quarter
  • Apply learning directly to current product

Priority Order

  1. Advanced Product Management
  2. Data-Driven Product Ownership
  3. UX
  4. Supplementary areas

Signals to Watch

— not yet defined —

Open Questions

  • Am I focusing on the right core areas?
  • Is certification the best way to learn?
  • Should I go deeper instead of broader?
  • What differentiates a strong Product Manager from a Product Owner?
  • How do I prioritise between these areas effectively?

Thinking Trace

  • Started from certification-driven thinking — initial instinct was to stack more certifications
  • Realised certifications alone were not enough to grow meaningfully as a PO
  • Expanded into multiple disciplines: UX, data, behavioural science, leadership
  • Introduced structure to manage breadth: core vs supplementary categories
  • Prioritised focus areas rather than treating all disciplines equally
  • Trigger: desire to move towards Product Manager role surfaced a gap — current scope was execution-heavy and strategy-light
  • Realisation: growing beyond PO execution required exposure to broader product expectations — strategy, UX, data
  • Desire for career progression and higher impact drove the shift from certification accumulation to multi-disciplinary structured learning

What changed?

v1

— skip —

Why it changed?

v1

— skip —

Connections

Changelog

  • v1 — Initial node

Graph View

Backlinks