Programme design documents rarely predict where coordination will actually break down. In practice, the same handful of warning signs tend to appear across health programmes well before a formal review flags a problem.
1. Field teams report the same operational blocker in different words
When staff independently describe the same underlying constraint — a supply delay, a referral bottleneck, an approval that takes too long — using different language, it usually means the issue has never been named or owned at a coordination level.
2. Meetings produce decisions that don’t change anything the following week
A coordination structure that generates minutes but not visible operational change is a symptom, not a fix. It typically means the people in the room cannot act on what is decided, or the decisions are not reaching the people who can.
3. Quality-of-care indicators and operational indicators tell different stories
When clinical quality data looks stable but frontline staff describe rising strain, the disconnect is almost always operational — staffing gaps, supply interruptions or referral delays that have not yet shown up in the clinical numbers, but will.
4. Escalation depends on who happens to be available
If resolving a cross-team problem depends on reaching a specific individual rather than following a defined path, coordination is running on relationships rather than structure — durable until that person is unavailable, then not.
5. New staff take months to understand how decisions actually get made
A coordination structure that cannot be explained clearly to a new team member in their first week is usually informal in ways that create risk during handovers, surge periods, or staff turnover.
Why this matters before a crisis, not during one
Every one of these signs is visible well before an epidemic response, a funding cut or a security incident tests whether coordination actually works. Strengthening it is far cheaper — in time, money and patient outcomes — as a deliberate exercise than as an emergency one.