Where a held-back concern becomes a finding.
Safety-critical and regulated work on plant floors, on job sites and in control rooms. The list is closed on purpose. A consultancy that serves everyone has no particular claim to know where your information stops moving.

Aerospace manufacturing
What it costs
By the time a concern held back for six weeks reaches a customer source inspection, it is a nonconformance with a paper trail.
Where it shows up
Long qualification cycles, zero tolerance for undocumented change, and quality data that travels up more slowly than it travels sideways.
Pharmaceutical manufacturing
What it costs
In a validated environment, "everyone understood the change" is not a defence. The defence is what was recorded, when, and by whom.
Where it shows up
Deviations and batch records that depend on early disclosure, new systems landing on top of existing habits, and audit exposure that rewards the team that escalates fastest.
Engineering and construction
What it costs
Rework is the cost of a handoff that did not land. It shows up in the schedule, and the schedule is where the margin was.
Where it shows up
Distributed sites, subcontractor interfaces, decisions made live in one long weekly meeting, and a site crew whose first language is often not the language of the drawing set.
Transit
What it costs
Service decisions are made under time pressure, with public consequences. A queue behind one controller is an operational risk.
Where it shows up
Shift handovers, control-room load concentrating on whoever has been there longest, and post-merger depots still running separate systems and separate habits.
General manufacturing
What it costs
Scrap, rework and downtime are usually the visible end of an information gap that started two shifts earlier.
Where it shows up
Shift-to-shift continuity, expansion adding a new language group to the floor, and corporate functions communicating in a register the floor does not use.
Communication systems rarely fail slowly. Something changed.
These events usually come right before the friction. They are also when a diagnosis is cheapest, before the new pattern has had a year to become how things are done.
- A new VP or plant leader arrived in the last year
- Two sites, agencies or companies have been combined
- Several people were promoted quickly into roles they have not held before
- A new system or tool went live on top of existing habits
- The meeting cadence changed, and decisions now happen somewhere else
- An expansion added a shift or a site that works in another language
- Something else
The same symptom, resolving four different ways.
Each of these starts with a leadership team confident they knew the cause. The last column shows what the evidence found.
Illustrative scenarios built on synthetic data, using invented teams to test the method. None of them are clients, and no real client engagement is described anywhere on this site.
Aerospace manufacturing (synthetic)
Communication has gone quiet.
Trigger
A new VP of Operations, five months in.
Mechanism
Safety
Where the evidence pointed
The team performed in front of the VP and behaved differently once they left the room. A tooling dispute went unraised for around six weeks and surfaced at a customer inspection. Several leaders described checking the VP's mood before deciding whether to raise anything at all.
Engineering and construction (synthetic)
Information is sent, and it doesn't land.
Trigger
A new weekly scheduling cadence, and a French-first site superintendent joining.
Mechanism
Protocol mismatch
Where the evidence pointed
Decisions were being made live in one long weekly meeting, in a second language, with no written follow-up. Nobody was withholding anything or underperforming. The format did not fit half the people in the room.
Pharmaceutical manufacturing (synthetic)
Looks fine until execution.
Trigger
Two sites merged eight months earlier; leadership believed alignment existed.
Mechanism
Assumption gap
Where the evidence pointed
Agreement was being assumed rather than confirmed, and the coordination trail was so thin that the two sites could hold different understandings of the same decision for weeks without either noticing.
Transit (synthetic)
Volume builds around one person.
Trigger
Two recent promotions, a new scheduling tool, and one senior controller absorbing both.
Mechanism
Competence gap
Where the evidence pointed
Decisions queued behind the person who had been there longest. The new tool had been rolled out without reinforcement, so instead of learning it, the team routed around it and through that one controller.
General manufacturing (synthetic)
Quiet across the language line, and not landing when it is not.
Trigger
An expansion added French-first shift leads alongside English-first corporate engineers.
Mechanism
Safety and protocol mismatch together
Where the evidence pointed
Meetings and safety documentation ran in English only. Two mechanisms compounded each other: people who could not raise a concern in the language of the room eventually stopped trying. A combination like this gets a sequence of fixes rather than a list of problems.
