Chapter 7 - Moving from Projects to Value Streams

Introduction

Value streams are the lowest-viscosity way for organisations to turn strategy into lasting results, and they work alongside portfolio management, line management, and enterprise governance. Their boundaries, responsibilities, and characteristics are defined, and they provide a more stable response to volatile environments than fragmented functional or project-based approaches.

One of the most important practical changes organisations face when adopting value stream thinking is the movement away from a mainly project-based delivery model toward a value stream operating model.

Most organisations rely heavily on projects to deliver change. Projects are familiar and easy to manage, they fit well with annual budgets, established governance processes, and clear reporting structures, and they provide a visible story of progress. However, in environments where change is continuous rather than occasional, heavy reliance on projects can reinforce the structural resistance organisations are trying to remove.

Historical and Institutional Foundations

Projects became popular because they worked well in situations where work could be clearly defined and completed within a fixed timeframe. Large infrastructure programmes, regulatory compliance initiatives, major technology replacements, and capital investments all fit this model. In these cases, planning the work in advance and managing it through milestones and completion stages provided control and predictability.

Professional standards strengthened this approach. Organisations developed widely used methods based on clear scope definition, risk registers, stage gates, and formal accountability. These methods remain valuable in stable environments and are still necessary for certain types of work.

However, the assumptions behind the traditional project model are increasingly challenged in modern markets. Strategy changes more frequently, customer expectations evolve quickly, regulations shift unexpectedly, and digital platforms allow faster responses. In this environment, the idea that change can always be defined in advance and completed once and for all becomes less realistic.

Financial Architecture and Incentive Structures

Projects have remained dominant partly because of how organisations manage funding. Most enterprises allocate budgets annually or semi-annually and attach funding to specific initiatives supported by business cases. Governance groups review proposals, approve budgets, and track delivery against cost, time, and scope.

This system creates strong incentives. Work must be presented as a project in order to receive funding, improvements are framed as temporary initiatives rather than as ongoing development of capability, and when a project ends, teams are usually reassigned, even if the underlying capability still needs improvement.

Projects also provide clear reporting. They produce dashboards, milestones, and visible achievements. However, they can break the link between work and long-term value. Because projects are temporary, no permanent structure owns the full flow from stakeholder need to realised outcome.

Over time, organisations become dependent on projects not because they are always the best option, but because the funding and governance systems recognise little else.

Organisational Identity and Visibility

Projects also fit well with traditional ideas about career recognition and achievement. Major initiatives, programme launches, and large transformation efforts create visible milestones, senior leaders gain recognition for sponsoring large projects, and delivery leaders build reputations by completing them successfully.

Value streams operate differently. They are ongoing structures that focus on steady performance, improved flow, and consistent results for stakeholders.

Because they do not end with a visible “go-live” moment, their achievements can appear less dramatic, even though they require more sustained leadership.

In organisations that value visible transformation more than reliable continuity, projects can seem more attractive even when they create additional friction.

The Psychological Comfort of Defined End States

Projects also provide psychological comfort, offering a clear narrative: a problem is identified, a plan is created, a team is formed, and delivery finishes with formal approval. This structure can feel reassuring in uncertain environments.

However, when circumstances change during delivery, the fixed scope of a project becomes a problem. Plans must be revised, change requests accumulate, and governance groups become involved in resolving differences. These control mechanisms can create extra reporting, approvals, and oversight, increasing organisational viscosity.

The appearance of control can therefore hide growing structural resistance.

Temporary Constructs Serving Permanent Needs

Projects are temporary by design. Value streams, in contrast, exist to deliver ongoing value for stakeholders.

When temporary project teams are used to improve capabilities that must operate continuously, tension appears. Knowledge gained during delivery is often lost when the project closes, architectural decisions may not align across different initiatives, and operational teams inherit solutions quickly, sometimes without full context.

Each new project must relearn parts of the same domain, which leads to duplication and inconsistency.

Customers, however, experience the organisation as a continuous provider of services. Without a stable structure responsible for maintaining that service, fragmentation gradually builds and performance eventually declines.

Handoffs and Local Optimisation

Projects usually operate within clearly defined boundaries, and teams optimise work within those boundaries, but once delivery is complete responsibility passes to operational teams with different incentives.

This creates handoffs between design and operations. Feedback loops can be slow, especially when organisational silos exist. Each handoff introduces coordination effort and additional review cycles.

Over time, these structural breaks interrupt the flow of work and change becomes something that requires formal approval and new project proposals rather than something that can happen continuously within a capability.

The organisation gradually reinforces the idea that projects are the only way to introduce change.

Common Transition Patterns

Few organisations move directly from a fully project-based model to a mature value stream operating model. Instead, transitions usually occur gradually and unevenly.

Project Clustering and Thematic Programmes

A common first step is grouping related projects into programmes or themes. This can improve coordination and reduce duplication, but funding and governance often remain project-based. Fragmentation is reduced but not fully removed.

Persistent Cross-Functional Teams

A more meaningful shift occurs when organisations keep cross-functional teams together over time, focusing them on specific domains or services. These teams continue working even after individual initiatives end.

This approach reduces knowledge loss and supports architectural consistency. However, if funding and governance still treat change as project-based, the organisation may continue to view improvement as occasional rather than continuous.

Product-Centric Operating Models

Some organisations move toward product operating models influenced by agile practices. Instead of fixed project plans, teams manage prioritised backlogs and deliver work iteratively.

This approach moves closer to flow-based thinking, however, if product teams focus mainly on features rather than on stakeholder outcomes, they may still optimise locally rather than across the full value flow.

End-to-End Value Stream Accountability

The most coherent approach assigns accountability for a complete stakeholder outcome across the full flow of activity. Funding supports the ongoing operation and improvement of this flow rather than individual projects.

Governance moves away from stage-gate approvals and toward regular performance reviews focused on outcomes, flow health, and strategic alignment.

Projects still exist, but they operate as improvements within the value stream rather than as the main structure for delivering change.

Risks and Misconceptions in the Shift to Value Streams

Large structural transitions inevitably create uncertainty, and several misunderstandings often appear.

One common misconception is that projects will disappear completely. In reality, some work will always remain temporary, such as regulatory initiatives or major infrastructure projects. The goal is not to eliminate projects but to rebalance the organisation so that value streams handle ongoing delivery while projects address clearly bounded work.

Another misunderstanding is that adopting agile practices automatically creates value streams. Agile frameworks can improve iteration and coordination, but they do not automatically change funding structures or accountability. Organisations can run agile teams within a project-based system and still experience high viscosity.

Funding misalignment is another major risk. If financial approval continues to depend on individual project business cases, value streams struggle to function as permanent structures. Teams must repeatedly repackage ongoing work as new projects, recreating fragmentation.

Role confusion also causes problems. Project managers, programme managers, and portfolio leaders must adapt their responsibilities. Their focus shifts from controlling scope to managing value flow, architectural coherence, and strategic priorities.

Finally, retaining old governance processes alongside new flow-based metrics can increase resistance. Instead of simplifying oversight, organisations accidentally add more reporting and approval layers.

Designing the Transition Deliberately

A successful move from projects to value streams requires coordinated change across organisational structure, funding, governance, roles, and culture.

Value streams must be clearly defined around stakeholder outcomes, and boundaries should support accountability without breaking the flow of work.

Funding models must gradually move toward supporting stable capacity rather than isolated initiatives. Governance should focus on regular evaluation of value delivery and strategic alignment instead of strict compliance with predetermined scope.

Cultural reinforcement is equally important. Organisations must recognise and reward steady performance and healthy flow, not just visible transformation events. Without this change in recognition, temporary initiatives will continue to dominate organisational behaviour.

Moving from projects to value streams is therefore not simply a relabelling exercise. It is a structural shift in how organisations think about change, continuity, and accountability. When implemented carefully, it reduces organisational viscosity and improves the organisation’s ability to translate strategy into sustained performance.