How operational execution works
Prepare. Coordinate. Monitor. Decide. Learn.
Five moves, in the order an operator lives them. Step four, relating a change to what it affects, is the one general-purpose tools leave to a person with a phone.
-
STEP 01
Prepare
Your procedures become templates that already know the roles, the sequence, the timing and who gets told what. Vendors, sites, vehicles and people are described once.
What it removes
The hour of assembly at the start of every operation. Do this well and activation is a single selection.
-
STEP 02
Coordinate
The template supplies the structure; this operation supplies the facts. Every task lands with an owner, a due time and what has to happen first.
What it removes
The scramble to work out who is doing what. It was decided before the clock started.
-
STEP 03
Monitor
One picture: status against the clock, people and locations, alerts, the map. Field confirmations arrive without a phone call.
What it removes
The status round. Nobody is watching everything — they are managing the exceptions the picture makes visible.
-
STEP 04
Decide
Because the mission knows what depends on what, a change arrives with its consequences attached instead of as an alert. The operator approves, adjusts or rejects; the rules already in the procedure carry the update to the people it concerns.
What it removes
The person with a phone working out what an alert actually means.
-
STEP 05
Learn
Actions, timings, decisions and messages stay with the mission. Review it, fold the lesson into the template, and the next run starts better prepared.
What it removes
The write-up. Nothing is reconstructed, because nothing was lost. Experience becomes preparation.
A worked example
One mission, two changes.
An inbound arrival and escort to headquarters — an unremarkable operation, until two ordinary things go wrong. The same five moments, run both ways.
- When Without LiveSOP With LiveSOP
- Day −2 Mission built Emailed round. Everyone reads a different version. Eleven tasks and four rules, assigned from the template.
- 13:48 Inbound delayed 95 min The duty officer starts calling, working from memory. Four tasks, two owners, an expiring hold and the briefing — together.
- 13:51 New timings approved Forty minutes of calls. Someone still has the old time. One approval. Six people notified. Three minutes.
- 15:26 Badge outage at HQ Found on arrival. Three people at a door nobody can open. Arrival moves to the north gate. A check is added, with an owner.
- 16:12 Mission closed A write-up promised for next week, assembled from memory. Every task has an owner, a timestamp and a status.
Two changes, three minutes each. No round of phone calls, and the record existed the moment the mission closed.
Built for changing conditions
Built for operations that may not go exactly as planned.
Pick a change and watch it move through the mission — on the map, in the tasks, and in what the operator is asked to approve.
Machine-speed awareness. Human judgment and control.
Bring the procedure you think will break it.
The messy one, with the exceptions and the step only one person knows. That is the useful test, and it is the one we would rather run.