A Project Delivers. An Organisation Learns.
Strategy only creates value when the organisation becomes capable of delivering it.
Strategic ambitions can often be described clearly. New products, digitalisation, AI, sustainability and new markets all sound compelling on a strategy slide.
The real challenge begins when those ambitions have to be translated into priorities, decisions, responsibilities and practical delivery.
This is where projects become important. They bring together the people, disciplines and decisions needed to turn strategic direction into real work.
From strategic direction to practical delivery
Most organisations are reasonably good at describing where they want to go. The challenge is working out what must actually happen to get there.
Which products, technologies or capabilities need to be developed? Which functions need to work together? Which decisions must be made now, and which can wait? Where are the critical dependencies? Who has the authority to resolve them?
These are practical questions, but they are often left unanswered when a strategic initiative is launched.
Instead, organisations establish programmes and projects to make the strategy executable.
That is one reason projects have become so important. They bring together engineering, software, manufacturing, procurement, quality, supply chain, operations and commercial teams around a common objective.
In many technology companies, no single function can deliver strategic change on its own.
Projects have become central to strategy execution
In a recent Harvard Business Review article, Antonio Nieto-Rodriguez argues that organisations are becoming increasingly project-driven. Projects are no longer simply vehicles for implementing predefined solutions. They are increasingly expected to explore new technologies, develop new products, establish new business models and build capabilities that the organisation does not yet possess.
This reflects a pattern I have seen across technology and product development projects.
The Ansoff Matrix offers a useful way of understanding why this becomes difficult. As organisations move towards new products or new markets, uncertainty increases. Pursuing both simultaneously increases it further.
However, I do not believe the conclusion is that organisations simply need more projects.
The more important question is whether the organisation becomes stronger because those projects happened.
The formal delivery is only part of the result
Projects are normally measured against scope, schedule, budget and quality. Those measures remain important. A project that does not deliver its agreed result has clearly fallen short.
But they do not capture everything a project creates.
A development project may establish new engineering knowledge, stronger supplier relationships, improved decision-making, better collaboration across functions or a deeper understanding of customer needs.
An AI initiative may create new ways of analysing data and making decisions. A manufacturing programme may establish capabilities that become essential for the next generation of products.
These outcomes are often less visible than the formal delivery, but they may prove even more valuable over time.
The question therefore is not only:
Did the project deliver?
It should also be:
What can the organisation now do that it could not do before?
This is where value is often lost
I have seen successful projects deliver exactly what they were asked to do. The product is launched, the system goes live, production starts and the project closes.
The project team is dissolved, people move on to new assignments and external specialists leave.
A few months later, another project begins.
Some of the same discussions reappear. Lessons have been forgotten, and knowledge that existed within the project has disappeared with the team.
The project delivered its result.
The organisation retained less than it should have.
This is rarely the responsibility of the project manager alone. In many organisations, no one has explicitly decided who owns the new capability once the project has finished.
Projects are temporary.
Organisations are permanent.
Someone has to connect the two.
Governance should protect more than delivery
In an earlier article, I argued that the Project Board is not a status meeting. Its role is to improve decisions and help the project succeed.
I believe that responsibility also extends beyond project delivery.
Sponsors and Project Boards should understand which capabilities a project is creating, how those capabilities will become part of the organisation and who will take ownership once the project has closed.
That means asking questions such as:
Who owns the new capability?
Which knowledge must remain within the organisation?
What responsibilities move into the line organisation?
Which processes need to change?
How will the next project benefit from what has been learned?
These questions should be discussed throughout the project, not only during project closure.
The answer is not more project organisation
There is sometimes a temptation to conclude that organisations should simply become more project-driven.
I do not believe that is the answer.
Projects and line organisations exist for different reasons.
Projects are designed to create change. Line organisations provide continuity, ownership and operational stability.
The challenge is not choosing one over the other.
It is ensuring that the capabilities developed within projects become embedded in the permanent organisation.
Otherwise, valuable knowledge, relationships and ways of working gradually disappear when the project ends.
Beyond the Agile discussion
In another recent article, I argued that organisations need to move beyond the traditional Agile-versus-Waterfall discussion.
This is one of the reasons why.
Choosing the right delivery approach remains important. Agile, Stage-Gate and hybrid approaches all have their place depending on the level of uncertainty and the nature of the work.
However, no methodology can solve the question of organisational ownership.
An Agile project can still lose critical knowledge.
A Stage-Gate project can successfully pass every gate while failing to establish lasting organisational capability.
Hybrid approaches may improve execution, but leadership and governance determine whether the organisation actually benefits after project completion.
Methodologies help projects deliver.
Leadership helps organisations retain the value.
Five questions before closing a project
Before a project is considered complete, I believe every sponsor and Project Board should be able to answer five simple questions:
What can the organisation do now that it could not do before?
Who owns that capability going forward?
Which people, processes and tools must remain in place?
What knowledge is still dependent on individual project members?
How will this project make the next one easier?
If those questions cannot be answered, the project may not be as complete as the final status report suggests.
My Perspective
Much of my work has taken place where strategic ambitions meet practical delivery. This is where people, technologies, governance and execution have to come together around a common objective.
Projects create products, systems and change.
But their longer-term value is measured by what the organisation is capable of doing afterwards.
A good project delivers the agreed result.
A great project also leaves the organisation stronger than before.
A project delivers.
An organisation learns.
