Most executives don’t approve projects because they want more activity. They approve them because they want more value such as higher sales, lower leakage, reduced risk or better service delivery.
Yet in many organisations, success is still defined as “on time, on budget, in scope”. The project file closes, the steering committee disbands and the numbers barely move. The CRM is live, but sales haven’t shifted. The plant is commissioned, but throughput is flat. The hospital opens, but outcomes don’t improve.
At Dwalalam, we think that is the wrong definition of success. We are not project‑complete until you are value‑complete.
Why “on time, on budget” is not enough
In African infrastructure and corporate environments, projects operate in high‑risk, highly visible conditions. Capital is scarce, scrutiny is intense and failure can be politically and reputationally expensive.
When the only definition of success is “we delivered what we said we would deliver”, three things tend to happen:
- Business cases are quietly forgotten once implementation starts.
- The PMO becomes an operational reporting function, a checklist and not a governance instrument.
- Executives and boards are left with activity, not outcomes and with risk, not assurance.
In that world, it is entirely possible to have a “successful” project that has failed the organisation.
A different starting point: name the value
Our starting point is simple: every project is a capital investment decision. If there is no value case, there is no strategic reason to proceed.
So before we talk about plans, resources or tools, we insist on naming value in business terms:
- Revenue: higher sales, better conversion, improved pricing or lower churn.
- Cost: reduced leakage, lower unit cost, more efficient use of assets.
- Risk: fewer impairments, better audit outcomes, lower exposure.
Once the value is named, governance needs to be built around it. It is here where we design PMO as a governance and assurance asset for the C‑suite.
A PMO built this way does not live only in operations. It becomes a strategic instrument that helps executives make better, faster decisions about where to double down, where to intervene and where to stop.
Staying until value lands
Projects may be technically “complete”, but the organisation is likely still climbing the change curve. Users are learning new processes. Data is still being cleaned. Old workarounds are still in place.
Value doesn’t arrive the day the system switches on or the ribbon is cut.
Our approach is to stay through that gap, by tracking the specific business metrics agreed at inception – not generic KPIs and fixing the practical issues that block value.
This means that CFOs, CEOs and other value stewards will have clear, auditable lines of sight of capital from inception to realised outcomes. It gives them governance that simplifies execution and removes bureaucracy. It provides security in capital investment and support through value delivery.
We are not project‑complete until you are value‑complete
This is why our work is designed around a simple idea:
We start by naming the value, we govern to protect it and we stay until it shows up in your numbers and in the lives of the people you serve.
In a market where capital is constrained and trust is fragile, we believe this is the only definition of success that matters.