How to Drive Projectless Innovation
Many organisations initiate projects with the intention to innovate. Yet rarely, in my experience over the past 20 years, have these efforts led to structural value creation. This is not accidental, but a direct consequence of how organisations are designed.
This article explores the value-driven organisation often referred to as a digital organisation, and contrasts it with traditional, project-driven models.
The difference is not in ambition. It is in structure.
The hidden assumption behind projects
In project-driven organisations, projects are the primary mechanism to drive change. This creates a deeply embedded assumption: that change is something temporary, exceptional, and externally organised.
A project has a beginning and an end. It is funded separately. It is staffed separately. It is governed separately. And therefore, it is disconnected from the system it is meant to improve.
This is the paradox: organisations attempt to create continuous value through temporary structures.
Why projects fail to create structural value
Projects are not inherently ineffective but they are structurally misaligned with how value is created. Value creation is continuous, contextual, and owned. Projects are temporary, abstracted, and often detached from ownership.
This leads to predictable outcomes:
- Learning is not retained, because teams dissolve
- Ownership is unclear, because responsibility is temporary
- Decisions are delayed, because governance sits outside the value stream
- Improvements are episodic, not compounding
Over time, organisations tend to fall into a pattern of recurring interventions, where the same problems resurface, are analysed again, and are addressed with newly designed solutions that often look remarkably similar to what was done before.
This is usually not a failure of execution or intent, but a consequence of how the organisation is structured. It simply lacks the ability to accumulate and retain learning over time.
The shift: from initiatives to ownership
Digital organisations operate differently. Rather than organising change through discrete initiatives, they organise around value itself. Change is not something that is temporarily introduced through projects, but something that is continuously owned and evolved as part of the organisation’s core structure.
This requires a different architectural foundation:
- Value is owned, not temporarily assigned
- Teams are persistent, not assembled per initiative
- Funding is continuous, not project-based
- Decisions are made close to value creation, not escalated through governance layers
The implication is profound. Innovation is no longer a discrete activity. It becomes an emergent property of the system.
Continuous improvement is not a method
Many organisations interpret continuous improvement as a practice. Something to be implemented through methodologies, rituals, or frameworks. But that assumption is flawed. Continuous improvement is not a practice. It is a structural condition.
It is not something teams decide to do. It is something the organisation either allows or prevents. When ownership is fragmented, improvement slows or stops altogether. When funding is episodic, every learning cycle resets. When governance is centralised, adaptation becomes dependent on approval rather than driven by insight.
In that context, adding agile practices or launching innovation programs changes very little. It may create the appearance of progress, but the underlying system — the part that actually determines how value is created — remains untouched.
Start delegating value creation
As long as projects remain the default mechanism to drive change, innovation will stay episodic and, in many cases, largely performative.
The answer is not to run better projects. It is to remove the organisational dependency on projects altogether. That shift starts with a different question. Not who delivers the initiative, but who owns the value.
Delegating value creation means moving away from temporary responsibility and towards structural ownership. It requires organisations to assign clear and enduring ownership to value streams, allocate capital directly to those streams instead of to predefined initiatives, and enable teams to continuously prioritise, adapt, and improve based on what they learn.
At the same time, accountability shifts as well from delivering output to being responsible for outcomes. This is not a change in delivery approach. It is a change in governance.
Projects are blocking innovation
Projects create movement, but not necessarily progress. They provide structure, yet often strip away ownership. They introduce urgency, but rarely bring clarity. They deliver outputs, but seldom improve the system that produces them.
More importantly, they postpone a more fundamental question: how value is actually created within the organisation.
As long as change is organised through projects, it remains something external to the core organisation. And as a result, that core remains largely unchanged.
Towards a projectless organisation
A projectless organisation is not an organisation without change. It is one where change is continuous, owned, and embedded in how the organisation operates.
In such an organisation, value streams become the primary organising principle. Capital allocation is used to enable adaptation rather than constrain it. Decision rights are placed close to where value is created, and learning is allowed to accumulate over time instead of being reset with every new initiative.
That is what enables real innovation. Not more initiatives. Not better planning. But a structure that allows the organisation to continuously evolve.