Example Product Lifecycle

A healthy software product moves through a recognizable set of phases. They are not strictly sequential. Most of these activities recur throughout a product's life, often concurrently, and a mature team is doing many of them at once. But the list describes the activities a healthy product organization is set up to perform, and is a useful checklist for sanity-checking whether a team has all the muscles it needs.

1. Problem Discovery

Understanding the problem the product is meant to solve, for whom, and what makes it hard today. Activities include user interviews, observed workflows, support-data review, and competitive analysis. The output is not a specification; it is a working understanding of the problem space, articulated clearly enough that the team can evaluate proposed solutions against it. See Exploring the Problem Space.

2. Workflow Analysis

Mapping how the work being addressed by the product is currently performed, including the informal workarounds users have developed. The workarounds are signal: they show what the real problem is and constrain what solutions will actually be adopted. Skipping this step produces solutions that fight the existing workflow rather than replacing it.

3. Prototype Exploration

Generating multiple candidate solutions and testing the most promising ones cheaply, before committing significant engineering investment. Prototypes can be sketches, clickable mockups, or thin slices of working software. The goal is to learn what is wrong with each candidate while changes are still cheap.

4. Product Validation

Testing the chosen direction against real users, real workflows, and real constraints. Includes usability studies, prototype testing, small pilots, or early-access programs. The output is evidence about whether the team's hypothesis is right; the most useful results are the ones that change the plan. See User Behavior Testing.

5. Implementation

Building the product. The bulk of the engineering work, but rarely the bulk of the lifetime cost. Best done in small increments, integrated continuously, with quality designed in rather than inspected in at the end. See Trunk-Based Development and Quality Is Designed In.

6. Testing

Verifying that what was built does what it was meant to do, including automated tests, exploratory testing, and pre-release validation. Testing reveals defects; it does not create quality. The discipline runs throughout implementation, not as a separate phase at the end. See Testing Is Not Quality.

7. Deployment

Moving the working software into production. In mature organizations, deployment is routine: small, frequent, automated, and recoverable. The strategies (blue-green, canary, rolling, feature-flag-gated) are how the team makes shipping low-risk. See Deployment Strategies.

8. Monitoring

Observing the running system in production. Catches what no test environment can predict and produces the evidence the team needs to operate, debug, and improve the product. Mature systems are continuously observed. See Observability.

9. Support

Helping users when something does not work as expected, and feeding what support hears back into engineering and product. Support is one of the highest-signal sources of product feedback available; treating it as a downstream cost is one of the most common ways to lose that signal. See Support and Triage.

10. Iteration

Using what the team has learned (from analytics, support, incidents, user research, and direct observation) to improve the product. This is where most of the product actually gets built; the initial release is usually a small fraction of the eventual system. See Launch Is the Beginning.

11. Continuous Improvement

Investing not just in the product but in how the team produces the product. Includes retrospectives, postmortems, structural fixes to recurring problems, and the ongoing reduction of friction in the team's own work. The product gets better when the team gets better at producing it. See Continuous Improvement.

Core principle

Software products are living systems. The lifecycle is not a sequence the team walks through once; it is the set of activities a healthy team is continuously performing throughout the life of the product.