Workshop Index
Action Situation Mapping
Maps the concrete decision field where participants, rules, information, actions, and outcomes meet.
Full Practice · Knowledge · Reading What's Operating
Mechanism
Action Situation Mapping reads the place where the system becomes a choice.
Many institutional failures are described at the wrong level. "The organization rewards silence." "The school punishes curiosity." "The lab is too close to release pressure." These statements may be true, but they are still too broad to repair. You need to know where the action happens: who is in the situation, what positions they occupy, what choices are available, what information they have, what outcomes they can affect, and what costs or benefits follow.
Action Situation Mapping turns a system diagnosis into a decision field you can inspect.The action situation is not the whole institution. It is the focal site where participants interact under rules and conditions that shape what they can do. A hiring panel, a safety-review meeting, a budget allocation, a classroom discipline decision, a release gate, a moderation appeal, a board vote, a crisis call. Each is small enough to map and large enough to matter.
Action Situation Mapping differs from Rules-in-Use. Rules-in-Use asks which rule actually governs behavior under pressure. Action Situation Mapping asks what situation the participants are inside at all. It also differs from Mechanism Design. Mechanism Design asks what game would produce a desired outcome. Action Situation Mapping first asks what game is already being played at the focal site.
The tool sits close to Acting on What You See, which is why its placement needs care. Mapping the action situation often reveals what to change. But the reading is still separate from the intervention. If you skip the map, action becomes theater: a reform aimed at "the system" that never touches the situation where choices are actually made.
Control misreads Action Situation Mapping by turning the map into administrative capture: every participant reduced to a role, every action enumerated, every local judgment flattened into process. Decay misreads it by refusing the map because the system feels too complex, too relational, or too alive for analysis. The Range reading maps enough to act responsibly without pretending the map exhausts the situation.
Practice
The diagnostic question is: "Where, exactly, does the relevant action happen?"
Use this when a broad institutional diagnosis needs to become concrete enough to inspect, audit, or repair.
Choose the focal situation. Name the meeting, transaction, decision, review, exchange, appeal, vote, allocation, or conflict where the pattern becomes action.
Map participants and positions. Who is present or represented? What role does each participant occupy? Who is affected but absent? Who has standing to speak, decide, block, appeal, or leave?
Define possible actions. What can each participant actually do inside the situation: approve, object, conceal, report, delay, exit, escalate, comply, reinterpret, sanction, or ignore?
Locate information and control. Who knows what before action is taken? Who can see consequences after the fact? Who controls which outcome follows which action?
Trace outcomes and payoffs. What happens after each action? Who gains, who pays, who is recorded, who is blamed, who benefits from ambiguity, and who carries delayed cost?
Check adjacent situations. The focal situation may be shaped by another one: budget rules, promotion incentives, legal exposure, release deadlines, public metrics, or informal hierarchy.
The map can be simple. It does not need a dissertation. A useful first pass is often one page: focal situation, participants, choices, information, control, outcomes, costs. If you cannot fill those fields, you probably do not yet know what you are trying to change.
In the Wild
An AI lab says safety review has authority. The action situation is not "the lab." It is the release meeting where evaluation results, product pressure, executive authority, and documentation meet. Who sits in the room? Who can block release? Who sees raw eval failures? What happens if the safety lead objects? Does the objection enter durable record? Without that map, "safety review" is only a phrase.
A school says students should learn rather than merely test well. The action situation may be the teacher evaluation process. Who judges the teacher? What information counts? What can the teacher do with a struggling student? What outcome follows lower test scores but deeper learning? The problem may not live in the classroom alone. It may live in the action situation where teaching is translated into evaluation.
A community group says every member has voice. The action situation is the meeting where agenda, speaking order, facilitation, time, and authority shape whose voice changes the outcome. A norm of openness may exist. The map asks whether that norm has an action situation where it can operate.
Before you fix a system, find the situation where the system becomes choice. The first honest map is often less dramatic than the diagnosis, and far more useful.
Lineage
The Codex did not invent Action Situation Mapping. It inherits the tool from Elinor Ostrom's Institutional Analysis and Development framework and the Bloomington School's institutional-analysis tradition.
The IAD framework studies action arenas, which include participants and action situations. An action situation is the analytical unit where participants in positions choose actions under information, control, costs, benefits, and rules that generate outcomes. That sentence can sound technical. The practical point is plain: institutions are not only documents or organizations. They are repeated situations in which people make choices under constraints.
Kiser and Ostrom's work on institutional analysis helped define the action arena. Ostrom's Understanding Institutional Diversity developed the framework in depth. McGinnis's guides to the language of the Ostrom Workshop make the vocabulary more accessible for readers who need the map without becoming specialists.
The Codex's translation is a practical map for Reading What's Operating. The tool lets you move from a broad claim about a system to the concrete situation that can be tested. It does not replace the full IAD framework, and it does not pretend an institution can be reduced to one meeting or decision. It carries the part a practitioner most often needs first: the focal situation where the pattern becomes observable action.
The tool has limits. Over-mapping can become delay. A bad map can create false precision. The focal situation can also be chosen too narrowly, hiding the adjacent situation that actually drives the outcome. Use the map to sharpen observation, not to pretend the system is smaller than it is.
Cross-references
Within the category. Rules-in-Use asks which rule actually governs the mapped situation. Mechanism Design asks what game the mapped situation creates or could create. Tragedy of the Commons often needs an action-situation map before resource governance can be understood.
Across the Workshop. Acting on What You See is the natural next category when the map becomes an intervention question. Polycentric Governance becomes relevant when multiple action situations are linked across levels and centers of authority.
Limitation. The action situation is not the whole system. It is the piece of the system you can inspect closely enough to stop speaking in generalities.