Project to Product
What is Project to Product?
Project to product is the shift from organizing and funding work as temporary projects to organizing and funding it around long-lived products and teams that own outcomes over time.
Updated November 2026 · 5 min read
For decades, most organizations delivered technology change through projects. A project would be approved with a defined scope and budget, a team would be assembled to deliver it, and when the project ended the team would disband and the result would be handed to an operations group. This model works for one-off efforts, but it fits poorly with software and digital services that need continuous improvement. Knowledge is lost when teams disband, success is measured by delivery rather than outcomes, and every new improvement needs a new project and a new approval. Systems also suffer, since the people who built them are rarely the ones who maintain them.
The project to product shift replaces this with stable, cross-functional teams aligned to products, platforms or value streams. These teams are funded on an ongoing basis, own their products for the long term and are measured by the outcomes they achieve. The idea was popularized by Mik Kersten's 2018 book Project to Product and is closely linked to agile and DevOps practices. For portfolio leaders and IT finance teams, the shift changes how investment is planned, funded, tracked and governed.
Definition of Project to Product
Project to product is an organizational and financial transformation in which work is planned, funded and managed through persistent product teams and value streams rather than through temporary projects with fixed scope and end dates.
It is closely related to agile portfolio management and lean budgeting, which provide the portfolio and funding practices that a product model needs.
Key Differences Between Projects and Products
Duration differs. Projects end when their scope is delivered. Products continue for as long as they provide value.
Teams differ. Project teams are assembled and disbanded. Product teams are stable and keep their knowledge over time.
Funding differs. Projects are funded individually for a defined scope. Products are funded for capacity over a period, with priorities set within that capacity.
Success differs. Projects are judged on delivery against scope, schedule and budget. Products are judged on outcomes such as customer adoption, revenue, cost or satisfaction.
Ownership differs. Projects hand their results to operations. Product teams build, run and improve what they own.
What Changes in the Organization
Structure changes as teams are organized around products, platforms or customer journeys instead of technical functions or projects.
Roles change, with product managers responsible for outcomes and priorities, and fewer project managers coordinating temporary teams.
Planning changes from annual project approval to regular reviews of product priorities and outcomes.
Governance changes from stage gates on individual projects to guardrails and outcome reviews for products and value streams. Reporting changes too, with dashboards showing outcomes and flow by product rather than status by project.
Importance of Project to Product in Strategic Portfolio Management
The product model improves continuity. Stable teams keep their knowledge of systems and customers, which improves quality and speed over time.
It focuses on outcomes. Measuring products by the value they create, rather than whether a project was delivered on time, keeps attention on what matters to customers and the business.
It also makes the portfolio more responsive. Priorities within product teams can change quickly without the overhead of starting and approving new projects.
Project to Product and Financial Management
Product funding is based mainly on the cost of persistent teams, which is more predictable than the costs of many separate projects.
Finance teams need new ways to track spending, such as by product or value stream, and to apply capitalization rules when work is not organized into projects. Recording effort by feature or initiative is a common solution, using rules such as ASC 350-40 for internal-use software.
Linking product costs to outcomes allows leaders to compare the value delivered by different products and adjust funding accordingly.
Total cost of ownership becomes easier to see, since product teams own both building and running their products.
Common Challenges
Finance, audit and budgeting processes are often built around projects and need to be redesigned before product funding can work.
Defining products and value streams can be difficult in organizations with many shared systems and complex dependencies.
Some work, such as one-off migrations or regulatory changes, still suits a project approach, so most organizations end up with a mix. The aim is to use the product model where continuous improvement matters and projects where the work genuinely has an end.
How to Make the Shift From Project to Product
Making the shift involves defining products and value streams, forming stable teams, changing funding and governance and measuring outcomes.
Most organizations start with a few products and expand as they learn. Products with clear customers, stable demand and relatively few dependencies are usually the best candidates to start with.
Defining Products and Teams
Identify products, platforms or value streams that deliver value to customers or internal users, using a business capability map or customer journeys as a guide.
Form stable, cross-functional teams for each product, with the skills to build and run it. Keep teams together long enough to build real ownership.
Appoint product owners or managers accountable for outcomes, with authority to set priorities within their team's capacity.
Changing Funding and Governance
Fund products for capacity over a period, such as a quarter or a year, and review funding regularly based on outcomes and strategy.
Agree with finance how spending will be tracked, reported and capitalized under the new model.
Replace project stage gates with outcome reviews and guardrails, keeping project-style governance for the work that still suits it.
Examples of Project to Product in Strategic Portfolio Management
The examples below show the project to product shift in practice.
Both use illustrative figures. The first moves a digital channel to a product model, and the second changes how funding is tracked.
In each, the product model improved delivery and focus on outcomes.
Moving a Digital Channel to Products
A bank delivers changes to its mobile app through about 20 projects a year, each with a separate team that disbands at the end.
It forms four stable product teams, each owning part of the app, with quarterly funding reviews based on customer adoption and satisfaction.
The time from idea to release falls from about six months to six weeks, and app ratings improve as teams fix issues continuously rather than waiting for the next project.
Changing How Funding Is Tracked
A healthcare company's finance team worries that moving to product funding will make it impossible to capitalize development costs.
It agrees a simple approach with auditors: product teams record effort by feature, and features that create new capabilities are treated as capitalizable.
The company keeps capitalizing about the same share of development costs as before, and the finance team gains clearer reporting of cost by product.
Conclusion
Project to product is the shift from funding and managing work as temporary projects to organizing it around long-lived products and teams that own outcomes. It changes team structure, roles, planning, funding and governance.
In strategic portfolio management, the product model improves continuity, focuses attention on outcomes and makes the portfolio more responsive. Defining products and value streams, forming stable teams, changing funding and capitalization practices with finance and keeping project approaches where they still fit help organizations make the shift successfully.
Related terms
Agile Portfolio Management
Agile portfolio management is an approach to managing a portfolio of work that applies agile principles, such as short planning cycles, incremental funding and continuous prioritization, to decisions about what to fund and deliver.
Lean Budgeting
Lean budgeting is a funding approach that allocates budgets to long-lived value streams rather than individual projects, with spending guided by guardrails and budgets adjusted at regular intervals based on results and strategy.
Stage-Gate Process
The stage-gate process is a method for managing projects and new product development that divides work into stages separated by decision points, called gates, where leaders decide whether to continue, change or stop.
Project Selection
Project selection is the process of evaluating proposed projects and choosing which ones to approve and fund, based on criteria such as strategic fit, value, risk, cost and the organization's capacity to deliver.