Pattern Diagnosis Workshop¶
Facilitated workshop — instantiates System Archetype Diagnosis
Convenes the people who each see one arc of a recurring problem to build a shared loop map and narrow to a provisional archetype together.
Pattern Diagnosis Workshop is the mechanism for the case where no single person can see the whole loop. It gathers the stakeholders who each experience a different segment of a recurring problem, surfaces their conflicting symptom stories, reconciles them into one shared causal map, negotiates the boundary of what belongs inside the frame, and narrows to a small set of candidate archetypes the group can own. Its distinguishing feature is that the diagnosis is produced socially: the reconciliation of divergent stakeholder accounts is the core activity, not a byproduct. Where a lone analyst's map encodes one mental model, the workshop's map is contested into shape by the people who hold the pieces — which is both its power and the source of its characteristic risk.
Example¶
A manufacturing plant keeps shipping the occasional defective unit despite years of fixes. Line operators blame rushed changeovers; QA blames operators skipping checks; design blames a tolerance that procurement blames on a cheaper supplier the design team chose. Each is right about its own segment and blind to the others. A Pattern Diagnosis Workshop brings all four into a room. The facilitator has each group tell its symptom story, then draws the accounts onto a single wall map, insisting that arrows connect across the functional silos — the cheaper part raises rework, rework compresses the changeover window, the compressed window pushes operators to skip a check, the skipped check lets the defect through. The group negotiates the boundary (procurement's supplier choice is in; the customer's handling is out), and reconciles the four blame stories into one loop nobody could see alone. The workshop's output is deliberately provisional: a shared map, an agreed boundary, and two or three candidate patterns to test — not a verdict.
How it works¶
- Convene the segment-holders. Assemble the people who each see a different part of the loop; the workshop's value is proportional to how much of the structure the room collectively touches.
- Elicit each symptom story separately. Capture every group's account before merging, so minority views survive contact with dominant ones.
- Reconcile into one map. Draw the accounts onto a shared causal map, forcing cross-silo links that expose the loop hidden between functions.
- Negotiate the boundary and narrow. Agree what is inside the frame, then converge to a short list of candidate archetypes — held explicitly as hypotheses for later testing.
Tuning parameters¶
- Participant breadth — how many segments are in the room. Wider coverage catches more of the loop; too wide and the session loses focus.
- Convergence pressure — how hard the facilitator pushes toward a single answer. High pressure produces a crisp result and risks premature consensus; low pressure preserves alternatives at the cost of closure.
- Story-separation discipline — whether accounts are captured independently before merging. Skipping this lets the loudest voice write the map.
- Alternatives preserved — how many candidate patterns leave the room alive. Carrying two or three guards against locking in a memorable-but-wrong label.
When it helps, and when it misleads¶
Its strength is that it assembles a loop no individual can see and, in the same motion, builds the shared understanding and buy-in that any later intervention will need. It is the right mechanism precisely when the problem's segments are owned by different people who currently blame each other.
Its failure mode is groupthink: a facilitated room under time pressure can converge on a memorable label and mistake agreement for evidence, especially when a senior or louder voice anchors the map.[1] The classic misuse is running the workshop to ratify a conclusion leadership has already chosen — theater dressed as diagnosis. The guarding discipline is to separate mapping from deciding, to capture dissenting stories before merging, and to send the narrowed candidates onward for disciplined naming and validation rather than treating the room's agreement as proof.
How it implements the components¶
symptom_pattern— aggregates the recurring signs from every segment-holder, assembling a fuller pattern than any single vantage supplies.causal_loop_map— co-builds one shared map by forcing the separate accounts to connect across silos.feedback_loop_boundary— negotiates, with the people affected, what belongs inside the diagnostic frame and what is out of scope.stakeholder_story_check— reconciles the divergent, often conflicting accounts into a single coherent structure, the workshop's signature move.
It narrows to candidate patterns but does not perform the disciplined naming — archetype_match belongs to the named diagnoses and System Archetype Template — nor the falsification testing (pattern_fit_evidence, counterexample_check) that is Archetype Fit Checklist's. Unlike the solo modeling artifact Causal Loop Diagram, its map is produced by many stakeholders rather than one analyst.
Related¶
- Instantiates: System Archetype Diagnosis — supplies the shared, multi-stakeholder map and boundary the naming mechanisms then work from.
- Consumes: System Archetype Template supplies the template cards used as prompts during the session.
- Sibling mechanisms: System Archetype Template · Archetype Fit Checklist · Escalation Archetype Mapping · Fixes That Fail Diagnosis · Limits to Growth Diagnosis · Shifting the Burden Diagnosis · Tragedy of the Commons Diagnosis · Leverage Point Matrix · Causal Loop Diagram
Editorial Notes¶
Form Classification¶
Form family: Communication, Facilitation & Learning
Rationale: The workshop convenes complementary segment-holders, preserves their accounts, and builds a negotiated shared loop map and provisional archetype.
Nearest alternative: Assessment, Review & Assurance — Diagnostic findings result, but facilitated cross-silo participation and shared understanding are the load-bearing form.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Systems Thinking & Cybernetics
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Pattern Diagnosis Workshop is rooted in systems thinking and cybernetics: System dynamics established group model building to construct and diagnose shared feedback-loop models.
Related originating lineages:
- Organizational & Management Science — Organizational and management science materially shaped Pattern Diagnosis Workshop through coordination, organizational learning, performance, and change practice. Group facilitation and organizational learning materially shaped collaborative diagnosis workshops.
Review resolution: Both blind reviewers agree that systems thinking and cybernetics is the primary origin. Reconciliation resolves origin_mode_disagreement, encyclopedia_synthesis_disagreement. Formative alternate lineages are retained as organizational_management; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
References¶
[1] Group model building is the established practice, developed in the system dynamics field (notably by Jac Vennix, Group Model Building, 1996), of facilitating stakeholders to construct a shared system model together. Its documented benefits are shared understanding and commitment; its documented risks include convergence on a socially preferred rather than evidence-preferred model. registry ↩