Product Pipeline
How products go from discovery, ideation, prioritization, investment, design, implementation, deployment, early access, general release, and finally to maintenance.
Last updated
How products go from discovery, ideation, prioritization, investment, design, implementation, deployment, early access, general release, and finally to maintenance.
Last updated
The goal of the product pipeline is to gain confidence along the path to product production that we are developing the things that deliver the maximum business value at any given time while reducing the greatest amount of risk for failure along the way.
We are not interested in pushing products (being productive) as this inflates our user experience to being a bloat of features that fulfill a lot of distinct requests but compromises the key user engagement that leads to business outcomes. Instead, we are interested in increasing measurable outcomes (being effective) that drive our core business values (revenue, most likely). Often, the optimal effective solution is to build new products/features. Often, it is to improve our existing performance, security, accessibility, maintainability, and usability. We weigh each proposal against the others on a regular basis to validate that the currently most valuable ideas float to the top and are worked on.
We desire to do this as quickly and confidently as possible. We do this through focused upfront analysis, breaking up development into small, testable, measurable batches that we can iterate on. We welcome input from any source, as input leads to inspiration; however, we make decisions based on feedback and data from the people who are closest to the problem.
Timelines/deadlines should be bottom-up. Priorities should be top-down.
