Source Report
Research Question
Research the canonical definitions and frameworks for the product management lifecycle as established from roughly 1980–2021, focusing on software and digital technology products. Trace the evolution from waterfall-era stage-gate models through agile/lean/continuous delivery approaches, covering frameworks like the PDLC, Pragmatic Marketing, dual-track agile, and Jobs-to-be-Done. Identify the core stages (discovery, definition, development, launch, iteration, sunset) as described in foundational texts, major PM certification bodies (AIPMM, Pragmatic Institute), and widely-cited pre-2022 articles and books. Produce a structured comparison table of how different frameworks defined each phase and what competencies they assigned to PMs.
Waterfall-Era Stage-Gate Models (1980s-1990s)
Robert Cooper's Stage-Gate model, first published in 1988, mechanized new product development (NPD) as a gated funnel: cross-functional teams execute parallel tasks in discrete stages to build critical information (e.g., market viability, technical feasibility), passing through decision gates where senior leaders approve incremental investments only if value exceeds risk thresholds like Expected Commercial Value—preventing "zombie projects" that drain 40% of resources in ungated chaos. This shifted software/digital products from ad-hoc coding to disciplined NPD, applicable to IT alongside physical goods, by embedding Voice of Customer (VOC) early to slash failure rates from 60% to under 30%.[1]
- Canonical 5-stage/5-gate structure: Stage 0/1 (Scoping/Concept: idea screening, preliminary assessment); Stage 2 (Build Business Case: deep market/technical study); Stage 3 (Development: prototype); Stage 4 (Testing/Validation); Stage 5 (Launch).[1]
- PM competencies: Lead cross-functional teams, prepare gate deliverables (e.g., business cases, risk assessments), integrate VOC across stages; no siloed handoffs.[1]
For competitors: Stage-Gate demands upfront rigor others lack—new entrants must invest in gate criteria/tools or risk portfolio bloat.
PDLC and AIPMM Foundations (1990s-2010s)
AIPMM's Certified Product Manager (CPM) framework, rooted in the ProdBOK (pre-2022 editions), operationalized PDLC as a 7-phase phase-gate lifecycle explicitly from Conceive to Retire: PMs orchestrate cross-functionally, modeling projects per phase (e.g., business cases in Plan, specs in Develop) to align product specs with market data, using gates for go/kill on viability—ensuring software products hit lifecycle profitability gates that pure devs ignore, as seen in their emphasis on launch plans and EOL modeling.[2]
- Phases: Conceive (idea gen), Plan (business case), Develop (specs/prototype), Qualify (test), Launch, Deliver (growth), Retire (sunset).[3]
- PM competencies: Market/competitive analysis, lifecycle modeling, phase-gate implementation, launch planning per phase.
For entry: Certifications like CPM provide defensible process IP; without it, PMs default to dev-led chaos.
Pragmatic Marketing/Institute Framework (1990s-2021)
Pragmatic Institute's 37-box Framework (ex-Pragmatic Marketing, pre-2022) blueprints end-to-end PM as a horizontal swimlane: left-side strategy boxes (e.g., Market Problems via customer interviews) feed portfolio/roadmap, flowing right to execution (Positioning, Launch, Retention)—uniquely blending PM/marketing to make software "market-driven" by quantifying problems' pervasiveness before dev, yielding 3x higher win rates vs. feature factories.[4]
- Categories map to stages: Market/Focus (Discovery: problems, personas, roadmap); Business/Planning (Definition: requirements, positioning); Programs/Enablement (Development/Launch: sales enablement, nurturing).
- PM competencies: Win/loss analysis, pricing/profitability modeling, stakeholder comms, revenue retention metrics.
To compete: Adopt its data moat (e.g., validated problems) or get commoditized.
Agile/Lean Shifts: Dual-Track and Continuous (2010s-2021)
Marty Cagan/Jeff Patton's Dual-Track Agile (2012) bifurcates PDLC into parallel tracks—Discovery (PM-led validation of backlog via prototypes/Lean UX) feeds Delivery (build/test ship)—bypassing waterfall's "mini-waterfalls" (PM specs → design → dev handoffs) that waste 50% on rework; PMs embed in trios (PM/designer/engineer) for continuous validation, enabling software firms to "fake it till we make it" at 10x speed.[5]
- Tracks map stages: Discovery (ongoing: ideation/validation/iteration); Delivery (development/launch).
- PM competencies: Collaborative hypothesis testing, rapid prototyping, backlog validation (not just prioritization).
Implication: Legacy PMs must upskill in UX/eng collab or cede to empowered teams.
Jobs-to-be-Done Overlay (2000s-2021)
Tony Ulwick/Clayton Christensen's JTBD (1990s-2003 popularization) isn't a linear PDLC but a lens refracting all stages through customer "jobs" (progress in context): PMs map 8-84 job steps (Define→Execute→Monitor→Finish) to uncover underserved outcomes via interviews, prioritizing features that "get hired" over competitors—proven in ODI to predict 5x innovation success by making discovery job-centric, not solution-led.[6][7]
- Applies across: Discovery (job ID), Definition (outcomes), Iteration (job map metrics).
- PM competencies: Job statements, segmentation by underserved jobs, value prop testing.
Differentiator: Without JTBD, PMs chase personas/features; with it, they own predictable demand.
Framework Comparison Table
| Core Stage | Stage-Gate (Cooper, 1988)[1] | AIPMM PDLC/CPM (ProdBOK)[2] | Pragmatic Framework[4] | Dual-Track Agile (Cagan 2012)[5] | JTBD (Ulwick/Christensen)[6] |
|---|---|---|---|---|---|
| Discovery | Stage 1: Scoping/Concept (idea screen, VOC) | Conceive (idea gen) | Market Problems, Win/Loss, Personas | Discovery Track (validate ideas/prototypes) | Job ID + interviews (core job map) |
| Definition | Stage 2: Business Case (feas., market study) | Plan (business case) | Positioning, Requirements, Roadmap | Discovery (hypothesis→backlog) | Job outcomes/segmentation |
| Development | Stage 3: Prototype/Build | Develop (specs) | Use Scenarios, Innovation | Delivery Track (build/test) | Solution ideation vs. job steps |
| Launch | Stage 5: Commercialization | Launch | Launch, Sales Enablement | Delivery (ship) | Value prop testing (hire/fire) |
| Iteration | Post-launch review (adaptive gates) | Deliver (growth) | Revenue Retention, Measurement | Continuous Discovery/Delivery | Job metrics/monitor/modify |
| Sunset | N/A (focus pre-launch) | Retire | Product Portfolio (kill) | N/A (ongoing) | Job evolution/resegment |
| PM Competencies | Cross-team lead, gate deliverables, risk mgmt | Lifecycle modeling, specs/launch plans | Market analysis, pricing, enablement | Trio collab, rapid validation | Job mapping, outcome prioritization |