When to use this chapter
Use before any planning meeting, site visit, or deployment decision. Required whenever plans feel complete but fragile, or responsibilities are understood but not written.
Core failure this chapter prevents
Treating visible activity as the system. Most failures originate not from what was done poorly, but from what was never seen or named.
Illustrated Reference Table
| Domain | Visible Activity | Invisible Driver | Owner |
|---|---|---|---|
| Authority | Daily coordination meetings | Final decisions taken offline | Event Director |
| Time | Published schedules | Unofficial political windows | Protocol Lead |
| Information | WhatsApp groups | Selective forwarding, filtering | Control Room |
| Fear | No reported issues | Staff avoiding escalation | Ops Head |
| Reputation | Media calm on surface | One pending incident | Media Lead |
Working Worksheet - Fill In
| Domain / Area | What is Visibly Happening? | What is Actually Driving Outcomes? | Owner |
|---|---|---|---|
Complete this worksheet before the event, not during it.
Practice Drill
A major issue appears 'unexpected.' Ask: What failed visibly? What was invisible before it failed? Who could have noticed earlier? Why didn't they? (15 minutes)
Common Failure Pattern
Plans appear complete → invisible forces ignored → warning signals dismissed → failure appears 'out of nowhere.'
Post-Use Audit
Answer honestly: “The most dangerous invisible factor in our event right now is _________.”
Confidence Check (0-10)
| Area | Score /10 | Notes |
|---|---|---|
Any area below 6 is a live risk. Address it before operations begin.
System Scorecard - Chapter 1
Score each parameter from 1 to 5. Circle the weakest score before leaving the room.
| Parameter | Score | Red Flag (1-2) | Green Flag (4-5) |
|---|---|---|---|
| Invisible Driver Naming | ___ / 5 | Visible activity is listed; hidden drivers are unnamed. | Hidden drivers are named, owned and reviewed. |
| Assumption Exposure | ___ / 5 | Plans rely on assumptions no one has tested. | Assumptions are written, tested and assigned. |
| Dependency Visibility | ___ / 5 | Critical dependencies sit outside the planning map. | Every dependency has an owner and warning signal. |
| Failure Signal Capture | ___ / 5 | Signals are noticed only after visible failure. | Early signals are actively collected and escalated. |
| Decision Owner Mapping | ___ / 5 | Problems have no named decision owner. | Each risk has a named decision owner and route. |
Total Score
_____ / 25
System Status
- 22-25: Optimised. Systems are visible before they fail.
- 17-21: Functional. Strengthen the weakest invisible dependency.
- 11-16: Fragile. Blind spots remain inside the plan.
- Below 11: Critical. A hidden driver will become a visible failure.
One Action This Week
Name one invisible driver and assign a decision owner before the next review.
