Skip to content

Change 4 of 6

Funding

Fund the customer value stream.

Give persistent value streams a funding horizon that allows them to learn and improve.

The change

Continuity for the team. Choices for leaders.

Project funding asks an organization to commit to a solution before it has learned much about the problem. Each new feature then becomes another negotiation over scope, resources, and approval. The people doing the work may be assembled and reassigned repeatedly.

Fund a persistent value stream against outcomes instead. The team has continuity to understand the customer problem and improve the product, while leaders retain the ability to decide which scopes deserve capacity and whether the investment is producing useful results.

Faster AI-assisted delivery makes a feature-by-feature funding process harder to sustain because leaders face more frequent funding decisions.

What changes in practice

  1. Fund a clearly bounded scope.

    Define the bounded part of the customer journey the team owns and the outcome it should improve. Make clear where its responsibility ends and another team’s begins.

  2. Allocate capacity from strategy.

    Use the importance of the value stream to guide the investment. Let the team decide which work is most likely to improve its agreed outcome.

  3. Review the investment on evidence.

    Set an annual capacity baseline and review allocation quarterly against strategy, cost, outcome trends, and health measures. A weak result can call for a different solution, more capability, or a narrower scope. Diagnose it before deciding to reduce or end the investment.

A practical example

Fund the Booking Team as its approach changes.

The Booking Team owns reservation and payment, with an objective to help more customers confirm their booking. Its first idea is to simplify the booking form. Research then shows that customers get stuck after a failed payment: they cannot tell whether to retry or whether their reservation is still held. A project budget tied to redesigning the form would make it harder to act on that evidence.

Funding the booking scope lets the team test clearer payment status and recovery options within its agreed capacity. It measures completed bookings alongside payment errors and support requests. Quarterly investment reviews examine cost, outcome trends, and these health measures. The solution changes within the same reservation-and-payment boundary, without a fresh project approval.

The Booking Team has persistent funding for reservation and payment. Its approach changes from a simpler form to payment recovery to the next experiment as it learns. Quarterly investment reviews decide whether to continue, redirect, or rebalance.

Funding in practice

Fund lasting teams. Keep financial accountability.

Delta Air Lines logo

Product funding for ongoing technology teams

Delta Air Lines moved from project funding to product funding, with ongoing teams delivering successive improvements.

Business and technology worked together to define product portfolios and priorities, refining them as they learned. Examples included loyalty products and letting passengers select meals before their flight.

The funding change supported teams continuing to improve a product beyond a single project.

Handelsbanken logo

Local authority with a long profitability record

Decentralized funding also works outside technology, in one of the most heavily regulated industries.

Handelsbanken replaced annual budgets with decentralized branch decisions and resource requests as needs arose. Branch managers remained accountable for financial performance, with measures tied to the bank’s goals.

The bank achieved a higher return on equity than its peers in 46 of the 47 years to 2019.

In ZeroBlockers, fund the team’s bounded customer scope, let it adapt the solution as it learns, and review whether the investment is producing useful outcomes.

Common objections

Funding teams instead of projects means we pay for idle time
A team that owns a customer journey rarely runs short of useful work, because there is usually a next problem worth solving. What persistent funding does is make capacity and operating cost visible in one place. Leaders still decide which customer journeys deserve investment, and they review cost, outcome trends and health measures to check that decision over time. If results stall, look at the problem, the team's capability and its scope before you change the allocation. A failed idea is a normal part of learning, so it shouldn't be a reason to disband the team. Equally, a stable team can still have its funding reduced when the evidence points that way.
We can't create a separate, long lived team for each part of our product. That would be prohibitively expensive
You don't need to. There's no requirement for a one-to-one mapping between the Value Streams you identify and your Stream Teams, and one Stream Team can own several Value Streams. Your product strategy decides how many Stream Teams you need and how big they are, so you can start small and add teams where the investment makes sense.
Our finance team capitalizes software spend against project codes
You can still capitalize software spend with persistent teams. They keep records that separate the activities and costs your accounting policy cares about, and funding a value stream doesn't change which software costs can be capitalized. The best route is to agree the treatment and the supporting evidence with your finance team and auditors under the accounting framework you already use. It's also worth avoiding a fixed capitalization percentage based on a team's role or budget, because the right figure depends on the work the team does. The operating model gives teams more freedom over the solutions they choose, with clear accountability for the investment, and your accounting requirements stay the same.
Are we committing to fund a team indefinitely?
No. Persistent means the team stays together when a piece of work finishes, so you keep the knowledge it has built up. Its scope and investment are still reviewed regularly, and leaders can change the allocation, or close the team, when the strategic need or the evidence changes.
All common objections ↗