Informal Structure Mapping¶
Reveal the unofficial relationships, workarounds, and influence paths that determine how work actually gets done.
The Diagnostic Story¶
Symptom: The org chart says decisions flow one way but everyone knows they actually flow through two people not on the chart. New hires struggle despite complete documentation because what the documentation describes does not match what actually happens. Managers keep being surprised by bottlenecks and resistance because the informal approval path bypasses them entirely. Compliance looks high on paper but exceptions are handled off-record through channels the official process never mentions.
Pivot: Compare official structure with actual practice, identify the informal roles, workarounds, influence paths, and hidden coordination networks that carry real work, and then decide — explicitly and with evidence — whether each informal element should be formalized, supported, repaired, constrained, or retired.
Resolution: Operating reality becomes visible enough to design against rather than around, and formal structure improves because it is revised to match what actually works. Hidden fragility decreases as informal dependencies are acknowledged and supported or deliberately replaced. Change efforts become more reliable because they are planned with knowledge of the actual decision paths.
Reach for this when you hear…¶
[organizational design] “Everyone routes procurement approvals through Marcus because the official system is broken — the question is whether we fix the system or just give Marcus a formal role.”
[merger integration] “The acquired company's knowledge lives in five people's heads and one shared drive that was never in the data room — map that before anyone quits.”
[regulatory compliance] “The policy says exceptions go to the risk committee, but in practice the desk head approves them verbally on Friday afternoons — that is the real approval process.”
Mechanisms / Implementations¶
- Actual-vs-Documented Process Map
- Communication Pattern Review: Reads the collective's real communication network — who actually coordinates with whom — from its meetings, messages, and handoffs, so the social topology can be compared against the architecture it will imprint.
- Informal Leader Mapping
- Organizational Network Analysis
- Process Mining Review
- Shadow Process Audit
- Workaround Review
- Workflow Ethnography
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (3)
- Formal vs. Informal Structures: Official vs actual systems.
- Network: Models interactions between components.
- Observability: Infer internal state externally.
Also references 8 related abstractions
- Accountability: Responsibility for actions.
- Boundary: Defines system limits.
- Emergent Formalization (Language): Informal to formal evolution.
- Feedback: Outputs influence inputs.
- Hidden Path and Barrier Crossing: Non-obvious transitions.
- Implicit Knowledge: Unconscious understanding.
- Organizational Culture: Shared norms and values.
- Transparency: Open processes.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Shadow Process Mapping · implementation variant · recognized
Maps the undocumented process that people actually follow when the official process does not describe operational reality.
Informal Network Mapping · subtype · recognized
Maps unofficial relationship networks through which advice, trust, information, help, and escalation actually flow.
Informal Power Path Mapping · governance variant · recognized
Reveals unofficial vetoes, approvals, persuasion routes, and legitimacy channels that shape decisions outside formal authority.
Workaround Triage · risk or failure variant · recognized
Classifies repeated deviations from official process as adaptive repairs, necessary exceptions, unsafe shortcuts, or obsolete habits.
Actual Operating Model Mapping · scale variant · likely subtype
Maps how roles, routines, systems, information, decisions, and exceptions actually combine into the working operating model.