Skip to content

Institutional Mapping Workshop

Diagnostic mapping method — instantiates Institutional Rule–Role Stabilization

A facilitated session that surfaces and maps an institution's actual rules, roles, authority lines, and interfaces as they really operate — so drift, gaps, and overlaps become visible and fixable.

An Institutional Mapping Workshop is a structured, facilitated session that brings role-holders together to map an institution as it actually operates — its real purpose and boundary, who holds which authority, and how its parts hand off to one another and to outside bodies — and to spot where the arrangement has drifted, fragmented, or grown redundant. Its defining feature is that it is a diagnostic snapshot of an already-formal but drifted institution: it takes stock of what is on the books and how it really runs, and reconciles the two. It is not the founding document that declares the rules, and — crucially — it is not the business of turning informal habit into first-time structure; its job is to find and undo drift in structure that already exists.

Example

A sixty-year-old engineering society has forty committees accreted over decades; nobody can quite say which owns what, and two separately claim authority over standards approval. The workshop gathers the committee chairs and staff for two days. On the wall they map each committee's stated charge against what it actually does, the handoffs between committees, and the interfaces with the parent accreditor and the member chapters. It surfaces three overlapping mandates, two orphaned functions no one owns, and a purpose statement no living member recognizes. The output is a shared as-is map and a shortlist of drift to fix — the raw material the revision path and the role matrix then act on. The workshop rewrites nothing; it shows where the existing arrangement has come unstuck.

How it works

What distinguishes it: as-is before to-be (map reality, not the org chart's fiction), all role-holders in the room (so tacit knowledge and real practice surface), focus on interfaces and boundaries (where drift and fragmentation hide), and explicit reconciliation of the formal arrangement against the actual one. It diagnoses; it does not decide or ratify, and it stops short of formalizing practices that are working fine unwritten.

Tuning parameters

  • Scope — the whole institution or one fault line. Broad reveals systemic drift but risks boiling the ocean.
  • Participant mix — leaders only, or down to the people doing the work. Wider surfaces real practice but is harder to run.
  • As-is vs. to-be balance — pure diagnosis, or tipping into redesign in the room.
  • Facilitation neutrality — an insider or an external facilitator. External usually gets more candour.
  • Output formality — a wall of sticky notes, or a documented interface register handed onward.

When it helps, and when it misleads

Its strength is making invisible drift and fragmentation visible and shared, which is the precondition for fixing them — it is often the first move when a long-running institution has become person-dependent and illegible. Its failure modes: mistaking the map for the territory, since the map is not the territory and a tidy diagram can omit the real power lines[1]; analysis-paralysis, mapping forever and changing nothing; and the temptation to over-formalize, freezing living informal practice into brittle procedure. The classic misuse is running it to manufacture consensus for a reorganization already decided. The discipline is to keep it diagnostic, validate the map against people who were not in the room, and hand the findings to the mechanisms that actually revise.

How it implements the components

  • institutional_interface_contract — its core output: a map of how roles, committees, and outside bodies actually hand off to one another — the interfaces that drift and fragment.
  • institutional_purpose_and_boundary — it re-surfaces the institution's real operating purpose and boundary and reconciles them against the nominal ones on the books.

It does not declare or codify the rules and purpose — that's the charter; it does not detail each role's rights and duties — that's role_rights_and_duties_matrix; and it does not enact the changes it reveals — that's sunset_and_revision_clause.

Notes

The neighbouring pattern of turning informal practice into new explicit structure is a different job. This workshop assumes the rules and roles are already formal; its value is diagnosing where that formal structure has fragmented or drifted from its purpose — a re-stabilization move, not a first formalization. Keeping the two separate stops the workshop from over-writing habits that work better left unwritten.

References

[1] "The map is not the territory" — Alfred Korzybski's dictum that a model is never identical to the thing it represents. A mapping workshop's output is a useful abstraction of the institution, not the institution itself, and it can quietly leave out what it did not think to draw. ↩