Entity Definition Workshop¶
Ritual — instantiates Entity Individuation Criteria Design
A facilitated session that surfaces the tacit, conflicting assumptions about what counts as one entity before any system is built on them.
Most identity disasters are baked in before a single record is written, at the moment when everyone in the room assumed they meant the same thing by "device" or "customer" or "site" and no one checked. Entity Definition Workshop is the deliberately front-loaded session that forces those assumptions into the open. It gathers the people who hold incompatible mental models — the operator who thinks in physical boxes, the finance owner who thinks in billing accounts, the engineer who thinks in serial numbers — and makes them argue about the boundary of one entity until the disagreements are explicit and the scope is fixed. Its defining move is that it is generative and pre-implementation: it does not verify an existing model (that comes later) or govern it (that is the charter's job). It exists to discover the questions, name the entity kinds in play, and settle where parts compose one whole — before code, schemas, or counts calcify a hidden guess.
Example¶
A facilities team is rolling out sensors across a corporate campus and needs to define what "one asset" means before the maintenance platform is built. The workshop puts a rooftop HVAC unit on the screen and asks a deceptively simple question: is it one asset? The mechanical engineer says yes — one unit, one maintenance contract. The energy analyst says no — the compressor, the fan array, and the controller are three separately metered components. The finance lead says it depends on the depreciation schedule, which splits it yet another way. Facilities says the unit and its ductwork are one system because they fail together.
The facilitator does not resolve this by fiat. She draws the four proposed boundaries on the wall, and the group discovers that "asset" has been silently meaning four different things — a discovery that would otherwise have surfaced two years later as irreconcilable work-order counts. By the end they have fixed the scope (the maintenance platform, not the finance ledger), listed the candidate kinds (unit, component, system), and agreed a unity rule: components that share a single failure-and-repair envelope compose one maintainable asset. That agreement, reached out loud, is the deliverable.
How it works¶
- Assemble the incompatible viewpoints. Success depends on getting the people whose mental models conflict into the same room, not the ones who already agree.
- Fix the scope first. Pin down where the criteria apply — which process, which system — before arguing about entities, so the group is not silently negotiating several scopes at once.
- Probe with boundary cases. Put concrete, contested examples on the wall and ask "one or many?" until the tacit rule people are using becomes speakable.
- Draft, don't ratify. Capture the emerging kind catalog and unity rule as a proposal to be tested and governed downstream — the workshop opens the questions; it does not close them with authority.
Tuning parameters¶
- Participant breadth — how many stakeholder perspectives are in the room. Wider surfaces more hidden conflict but slows convergence and risks design-by-committee.
- Case provocation — how deliberately adversarial the example cases are. Sharper edge cases expose deeper disagreement but can stall the group in the exotic before the common case is settled.
- Facilitation firmness — how hard the facilitator pushes toward a decision versus keeping divergence open. Too firm buries dissent; too loose yields no draft.
- Time-box — a single half-day versus an iterated series. Iteration deepens the model but delays every downstream commitment.
When it helps, and when it misleads¶
Its strength is timing: it is the cheapest possible moment to discover that stakeholders individuate the world differently, because nothing has been built yet. It converts the archetype's most expensive failure — a tacit rule discovered only after systems depend on it — into a two-hour argument.
Its failure mode is that workshops surface only the assumptions people can articulate, and the most dangerous ones are tacit — genuinely known-but-unspoken, the kind Michael Polanyi meant by "we know more than we can tell."[1] A confident, articulate participant can also anchor the room on their model and suppress the quieter viewpoint that was actually right. And a workshop that mistakes its draft for a ruling ships an ungoverned guess. The guarding discipline is to provoke with concrete boundary cases (tacit rules surface as reactions to examples, not to abstract questions), rotate whose framing leads, and hand the output downstream to be verified and governed rather than treating consensus in the room as authority.
How it implements the components¶
individuation_scope_boundary— its first act is to fix where the criteria apply, so the group argues one entity within one scope rather than talking past each other.entity_kind_catalog— the session enumerates the candidate kinds and separates identity-providing kinds from mere roles and states.unity_criterion— its core product is a drafted part-whole rule: what composes one whole, reached by working contested cases aloud.
It does not set the identity_criterion (same-as) or hold the authority_and_revision_protocol — same-as is operationalized by the Entity Resolution Policy and governance is vested in the Individuation Criteria Charter; the workshop only surfaces and drafts.
Related¶
- Instantiates: Entity Individuation Criteria Design — the discovery ritual that seeds the criteria before anything is built.
- Sibling mechanisms: Individuation Criteria Charter · Identity and Unity Test Checklist · Entity Resolution Policy · Count Impact Assessment · Split/Merge Decision Tree · Master Entity Registry · Edge-Case Adjudication Panel · Versioned Identity Rulebook
Editorial Notes¶
Form Classification¶
Form family: Communication, Facilitation & Learning
Rationale: Entity Definition Workshop operates as a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding because it a facilitated session that surfaces the tacit, conflicting assumptions about what counts as one entity before any system is built on them.
Independent corroboration: The frozen evidence defines Entity Definition Workshop as 'A facilitated session that surfaces the tacit, conflicting assumptions about what counts as one entity before any system is built on them', so its operative form is Communication, Facilitation & Learning.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Facilitated requirements practice established stakeholder workshops that expose conflicting definitions through concrete cases before implementation.
Related originating lineages:
- Computer Science & Software Engineering — Conceptual data modeling supplied entities, identity boundaries, and schema consequences.
Review resolution: GSA documents facilitated requirements-development workshops, whereas OMG documents the entity-modeling content; the mechanism's distinguishing intervention is the facilitated workshop, making organizational management primary.
Attribution caveat: The workshop form is organizational requirements practice applied to a data-modeling problem.
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:
References¶
[1] Polanyi, M. The Tacit Dimension. Doubleday (1966). Defines tacit knowing as knowledge that exceeds what a person can explicitly tell. registry ↩