Skip to content

Shared Situation Model

Shared artifact — instantiates Constraint-Guided Improvisation

Gives everyone acting in the moment one continuously-updated picture of the situation, risks, and who's doing what, so improvised moves are fitted to what is actually happening rather than to stale or private assumptions.

Competent improvisation depends on reading the situation right — but in a fast, distributed effort each actor sees only a slice, and those slices go stale at different rates. Shared Situation Model is the single, continuously-updated representation everyone acts against: the current state, the live risks, the resources in play, who holds which role, and what all of that implies for the next move. It is not a decision and not a rule — it is the common picture that makes decisions and rules apply to the same reality. Its defining feature is that it is shared and live: one authoritative view that every improviser reads from and writes back into, so that two people acting a corridor apart are fitting their moves to the same facts instead of to two diverging private guesses.

Example

A wildfire incident command post runs on a common operating picture. On one board — physical map, digital overlay, and status columns — sit the fire's current perimeter, wind and its forecast shift, which crews are where, which roads are cut, and where the safety zones are. A hotshot crew boss keys in that the head has jumped a ridge; within minutes that update is on the board, and a division supervisor two valleys over reroutes an engine before it drives into the new run. The board didn't make the decision — the supervisor did, improvising against fresh facts — but without it she'd have been improvising against a perimeter that was already an hour wrong.

The model earns its keep precisely when the plan runs out. The moment the fire does something the plan didn't anticipate, the shared picture is what lets a dozen semi-independent crews keep making locally competent, mutually consistent moves instead of a dozen private, colliding ones — and every observation any crew feeds back sharpens it for the rest.

How it works

  • Hold one authoritative view. Maintain a single representation of state, risks, resources, and roles that is designated the picture — so "the situation" means one thing, not one per person.
  • Ingest feedback continuously. Give every actor a fast path to write observations back in; the model's value is proportional to how quickly reality reaches it.
  • Timestamp and attribute. Mark how fresh each element is and where it came from, so readers can weigh a five-second update against a five-hour-old one.
  • Render for action, not archive. Surface what the current state implies for the next move, so a reader converts the picture into a fitted decision at a glance.

Tuning parameters

  • Update latency — how fast observations reach the shared view. Low latency keeps everyone fitted to reality but demands attention and bandwidth to maintain; high latency is cheap and quietly dangerous.
  • Fidelity vs. legibility — how much detail the model carries. Rich detail supports subtle moves but can bury the signal; a spare picture is scannable under pressure but drops nuance.
  • Authority of the view — strictly single-source versus several reconciled feeds. Single-source prevents contradictory pictures; multiple feeds capture more but risk the "which board is right?" problem.
  • Freshness signaling — how visibly staleness is flagged. Strong timestamping stops readers trusting old data; none invites confident action on a picture that has already moved.
  • Write breadth — who may update it. Broad write catches more reality faster; narrow write keeps it clean but slows the very feedback that gives it worth.

When it helps, and when it misleads

Its strength is coherence without central control: a shared picture lets distributed improvisers stay mutually consistent and fitted to reality at once, and it turns every actor's observation into shared awareness through the feedback path. It is most valuable exactly when the situation outruns the plan and there is no time to convene.

Its danger is that people come to trust the model over the world — and the map is not the territory.[n1] A picture that is stale, partial, or subtly wrong becomes a shared false belief, which is worse than scattered private errors because it is coordinated: everyone confidently makes the same mistake. The classic misuse is updating the board to match the plan rather than the ground — grooming it into a comforting fiction. The discipline is aggressive freshness signaling, a designated authoritative source, and a habit of reconciling the model against direct observation, especially at the moments it matters most.

How it implements the components

Shared Situation Model fills the awareness-and-feedback components — the ones a live shared artifact can hold:

  • live_situation_model — it is the continuously-updated representation of state, risks, resources, and roles that improvisers read to fit their moves to reality.
  • feedback_channel — it is also the sink and distributor for feedback: the fast path by which any actor's observation updates the picture for everyone.

It does not sequence who acts when (coordination_signal — that's Facilitated Turn-Taking), assign authority over decisions (local_action_envelope — Decision-Rights Matrix), or set the standing limits (constraint_backbone — Constraint-Backbone Brief). It supplies the shared facts those mechanisms act on; it does not itself act.

Editorial Notes

Form Classification

Form family: Monitoring, Sensing & Alerting

Rationale: Shared Situation Model operates as ongoing observation, sensing, or alerting that detects and surfaces state without itself executing the response because it gives everyone acting in the moment one continuously-updated picture of the situation, risks, and who's doing what, so improvised moves are fitted to what is actually happening rather than to stale or private assumptions.

Independent corroboration: The frozen evidence defines Shared Situation Model as 'Gives everyone acting in the moment one continuously-updated picture of the situation, risks, and who's doing what, so improvised moves are fitted to what is actually happening rather than to stale or private assumptions', so its operative form is Monitoring, Sensing & Alerting.

Nearest alternative: Representation, Specification & Plan — Shared Situation Model includes features of a static representation, map, specification, schema, or prospective plan that externalizes information, but its defining operation is ongoing observation, sensing, or alerting that detects and surfaces state without itself executing the response.

Review outcome: Independent reviewer agreement; medium confidence.

Origin Attribution

Primary origin: Disaster Management & Risk Reduction

Origin pattern: Convergent development

Present-day reach: Universal

Rationale: A continuously updated shared picture of risks, actions, and actors is the common operating picture of incident management. FEMA's operational doctrine explicitly uses it to coordinate agencies from current rather than private or stale information.

Related originating lineages:

  • Engineering & Design — Engineering design, reliability, and systems-safety practice supplies a parallel or contributing lineage for the mechanism's defining operation: gives everyone acting in the moment one continuously-updated picture of the situation, risks, and who's doing what, so improvised moves are fitted to what is actually happening….
  • Military & Strategic Studies — Command-and-control doctrine depends on shared situational awareness across units.
  • Organizational & Management Science — Cross-functional response teams need synchronized assumptions and ownership.
  • Systems Thinking & Cybernetics — A common state estimate coordinates distributed control under changing feedback.

Review resolution: The blind reviewers disagree on primary lineage (disaster_management versus systems_cybernetics). Authoritative or primary research supports disaster_management as the best historical origin: A continuously updated shared picture of risks, actions, and actors is the common operating picture of incident management. FEMA's operational doctrine explicitly uses it to coordinate agencies from current rather than private or stale information. The cited FEMA, Response and Recovery Federal Interagency Operational Plan: Common Operating Picture; NIST, Situational Awareness Glossary directly supports the mechanism's defining operation. All independently supported contributing domains are retained without an arbitrary cap. origin_mode=convergent records lineage, while domain_reach=universal records later applicability separately from provenance.

Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.

Review outcome: Researched adjudication after independent review; high confidence.

Sources consulted:

Notes

The Shared Situation Model is a hub other mechanisms lean on — turn-taking references it, stabilization reads it to know what "safe" means now, rollback watches it for the signals that trip its thresholds, and After-Action Review mines it to reconstruct what happened. That centrality is its risk as much as its value: when the picture is wrong, every mechanism drawing on it is wrong in the same direction at once.

[n1] "The map is not the territory" — Alfred Korzybski's reminder that a representation is never the reality it stands for. It is the standing caution for any shared operating picture: the more people trust the board, the more it must be kept honest against the ground.