Complex programmes rarely fail because nobody knows how to build a schedule. They fail when objectives, responsibilities, information and decisions stop moving together. The larger the consortium, the more regulated the environment and the more external funding is involved, the more visible this becomes.
That is why I do not see governance as an administrative layer placed on top of delivery. Done well, governance is the operating system that allows delivery to remain coherent when circumstances change.
1. Complexity usually lives between systems
A technically strong team can still struggle when its work depends on several organisations with different incentives, approval processes and interpretations of success. One partner may optimise for technical quality, another for budget absorption, another for contractual compliance and another for political visibility. None of those objectives is illegitimate. The problem appears when nobody makes the interfaces explicit.
Good governance starts by defining who decides what, what evidence is required, where dependencies sit and how disagreement is escalated. This sounds simple. In practice, it is one of the main differences between a consortium that collaborates and a consortium that merely exchanges documents.
2. More reporting does not automatically mean more control
Many organisations respond to uncertainty by requesting more information. The result can be impressive reporting packs that consume time without improving a single decision. Control is not the volume of information available. Control is the ability to detect meaningful deviation early enough to act.
For senior leadership, useful reporting should answer a small number of difficult questions: Are we still pursuing the right outcome? What has changed? Which dependencies threaten delivery? Where is a decision required? What happens if we do nothing?
3. Compliance should be designed into delivery
In EU-funded, quality-managed or otherwise regulated programmes, compliance cannot be an exercise performed at the end. If evidence, eligibility, approvals and quality criteria are considered only when a report or audit is due, the programme has already created avoidable risk.
The better approach is to translate external requirements into practical controls that live inside normal delivery: clear ownership, proportionate evidence, defined review points and traceable decisions. This is where project management and quality management reinforce one another. The first creates a path to the outcome; the second asks whether the path is controlled, repeatable and supported by evidence.
4. Agility needs structure
Agile thinking is sometimes presented as the opposite of governance. I see the opposite. Adaptation is only safe when the organisation knows what can change, who can authorise the change and which constraints cannot be ignored.
A programme that cannot change is fragile. A programme that changes without traceability is uncontrolled. The objective is disciplined adaptability: short feedback loops, visible priorities and rapid decisions inside a governance framework that protects the outcome rather than the original plan.
5. What good governance should feel like
When governance works, teams spend less time discovering who owns a problem. Senior stakeholders receive fewer surprises. Compliance evidence is produced as a by-product of good work rather than reconstructed afterwards. Risks become explicit earlier. Decisions move faster because the right people receive the right information at the right time.
Most importantly, governance creates trust. Partners know the rules of engagement. Funders can see how resources are controlled. Teams understand what success means. Leadership can distinguish noise from genuine risk.
For me, that is the standard: not more process, but better alignment; not more reports, but better decisions; not rigidity, but controlled delivery.