Programs at scale fail less often because the technical work was wrong than because the partnership underneath it was assembled on a deadline that did not survive its first political cycle.
We see this pattern at three points: at the procurement stage, when the consortium is bid as if it were already a partnership; at financial close, when capital is aligned in the contract but not in the operating cadence; and at handover, when the SDG outcomes were a downstream concern rather than an embedded one.
The corrective is that partnership is not the late artifact of a program. It is the first one. Before scope is locked, before the design package is fixed, before the build schedule is committed — the partnership has to be structured. Specifically: the parties contracted; the capital aligned in cadence not just amount; the governance forum defined and convened; and the SDG outcome framework embedded in the operating reports the program will run on, not in a separate disclosure document.
This is unfashionable. It costs the program calendar time at the front. It requires accepting the discomfort of disagreement among partners while the deal is still wet. It is also, from our portfolio, the single highest-leverage thing a program lead can do.
The diagnostic discipline we run starts with a partnership map for exactly this reason. Until the map is on the table, we are not in a position to recommend a delivery structure — and our clients should not let any other firm recommend one either.