A digital service does not stop changing because the project that delivered it has closed. Yet many organisations still fund improvements as though every change needs a new project.
One of the more interesting shifts in enterprise technology is the move from project-based delivery towards product-based operating models. Deloitte's 2026 report, From Project to Product, argues that the change goes beyond how teams are organised. It affects how work is funded, who is accountable and how organisations measure value over time.
Consider a digital customer onboarding platform. The implementation team delivers the agreed features, completes testing and hands the system over. But after launch, customer behaviour reveals steps people abandon, operations identifies delays and compliance requirements change. Improving the service becomes an ongoing responsibility, not a one-off delivery exercise.
In a purely project-based arrangement, each significant improvement may need a separate proposal, budget and temporary team. That can make it difficult to respond quickly to what users and the business are learning. A product-based approach instead gives a continuing team responsibility for the service, with a prioritised backlog and measures linked to outcomes such as onboarding completion, processing time, reliability and customer experience.
This is not a case for abandoning project or programme management. A major platform replacement, regulatory deadline or enterprise-wide integration may still need a time-bound project or coordinated programme. The important question is which work needs a defined delivery endpoint and which needs continuous ownership and investment.
Gartner's April 2026 research describes the project-to-product transition as a significant operating-model change for CIOs and warns that it can stall without leadership across the business, not just IT. That makes sense: changing team names achieves little if funding, decision rights and performance measures still reward only completed deliverables.
For programme and portfolio professionals, this creates an important responsibility: deciding how finite change initiatives and long-lived digital services fit together, and how investment decisions account for both.
A successful launch remains important. But for digital services that customers and employees use every day, the more revealing question may be how effectively the organisation can keep improving what it has launched.
Good ideas get better in conversation.
