Projects are one of the primary mechanisms through which organisations organise and deliver change, but they are not where enterprise change begins. Every project ultimately responds to an enterprise need that already exists.
When new priorities emerge, organisations naturally move towards delivery. A project may be defined, accountability established, resources allocated and governance put in place. This approach has served organisations well for decades, providing structure and a recognised means of executing change. Yet the project itself is not the reason change exists.
Before a project is proposed, there is already a need for the enterprise to respond. Strategic direction may require action, regulatory obligations may demand compliance, ageing technology may require renewal, operational performance may need to improve, or changing market conditions may create new opportunities and risks. These enterprise needs exist independently of whether a project has been proposed, approved or established.
Modern portfolio and demand management practices have significantly strengthened how organisations evaluate proposed work, allocate resources and align investment with strategic priorities. Enterprise Portfolio Architecture builds upon these established practices by distinguishing the enduring enterprise need from the temporary Delivery Response established to address it.
Within Enterprise Portfolio Architecture, Enterprise Demand represents that enduring need and is established through Enterprise Demand Objects. An Enterprise Demand Object becomes an enduring enterprise planning object that remains connected to Enterprise Intent, Enterprise Context, Enterprise Investment, Enterprise Value and Enterprise Evolution. As enterprise conditions and understanding evolve, the Enterprise Demand Object evolves with them while preserving continuity with the enterprise need it represents.
Projects, programmes and other forms of enterprise change can then be understood as Delivery Responses established around Enterprise Demand. They remain essential mechanisms for delivering change, but they can be established, adapted or concluded without replacing the enduring planning object itself. This distinction becomes particularly important in complex enterprises, where one Enterprise Demand Object may require several Delivery Responses over time, or where delivery structures change while the underlying enterprise need continues.
When the enterprise need and its Delivery Response become indistinguishable, attention can progressively shift towards schedules, budgets, milestones and delivery performance while the original reason for the investment becomes less visible. Maintaining Enterprise Demand independently provides a more enduring point of reference, preserving the connection between why the enterprise needs to act, the investment made in response and the Enterprise Value that investment is intended to realise.
This perspective does not diminish the importance of projects. It places them within their appropriate enterprise context. Projects are not the starting point of enterprise planning; they are one of the mechanisms through which the enterprise responds to Enterprise Demand.
For executive leaders, this creates an important shift in the planning conversation. Before asking “What projects should we start?”, the enterprise can first ask “What Enterprise Demand are we responding to?” That question places the enduring enterprise need at the centre of planning and allows the appropriate Delivery Response to be determined from a clearer understanding of what the enterprise is seeking to protect, enhance or realise.