Product Management lifecycle
Understand the product-management journey from framing to learning review.
The lifecycle is a decision journey, not a mandatory waterfall. Stop when the current decision is sufficiently clear, or hand off when another skill owns the next action.
Stages
| Stage | Main question | Initial module or handoff |
|---|---|---|
| Frame | What problem, user, outcome, and context are actually in scope? | problem-framing |
| Discover | What is observed, inferred, assumed, or still unknown? | discovery-and-evidence |
| Decide | Which method fits this decision and evidence quality? | prioritization-and-method-selection |
| Define | What outcome, guardrail, and learning signal would show progress? | metrics-and-outcomes |
| Deliver | What bounded change can be planned after the decision is accepted? | Handoff to feature-planning |
| Learn | What changed, what was learned, and what should be revisited? | Planned learning-review; use observability-review for the current measurement review |
A safe progression
- Treat a requested solution as a clue, not as a problem statement.
- Establish the decision object and the evidence available for it.
- Select one primary method path; reject methods that require unsupported precision.
- Define outcomes and guardrails before calling activity a success signal.
- Hand off only the bounded information the next skill needs.
- Keep investment, roadmap, and irreversible trade-offs with the responsible human or governance layer.
Stakeholder alignment, strategy and opportunity, roadmap and sequencing, and learning review are part of the target family design. Their dedicated modules are planned follow-ups in the initial rollout; current contracts remain the source for the existing companion skills.