domain
/layers:domain
Assumes /layers:intro has been loaded for framework context.
The domain layer maps what exists in the real world independently of any product: the concepts, terminology, processes, relationships, and mental models users bring with them. This is observation, not design.
Critical distinction: Do not resolve contradictions at this layer. Contradictory, messy, inconsistent domain language is data — it signals where different user communities have diverged, and where the product will need to make deliberate choices. Resolution happens at the conceptual model layer.
Decisions this layer needs to make:
- What are the key concepts in this domain, and how do they relate?
- What language do people use — and where does that language conflict or diverge?
- Where are the natural seams where different communities use the same words differently?
- What events and processes structure the domain's activity over time?
Methods:
| Method | When |
|---|---|
| Concept maps / bubble diagrams | Domain is complex and poorly understood. Informal nodes-and-lines show how concepts relate without forcing premature structure. |
More from jamiemill/layers-skills
layers-conceptual-model
Defines the product's objects, relationships, states, and vocabulary independently of any interface — the most load-bearing layer
160layers-domain
Maps domain concepts, terminology conflicts, and bounded contexts — produces a noun harvest for the conceptual model layer
158layers-orient
Diagnostic audit across all seven layers — identifies the bottleneck layer and recommends where to focus
157layers-intro
Framework orientation for Layers of Product Design — load this first; provides the context all other skills depend on
157layers-product-strategy
Connects user opportunities to business outcomes and solution bets — produces a strategy tree and prioritised experiments
157layers-interaction-flow
Maps interaction structure and flow — produces breadboard notation with edge cases, failure paths, and open decisions
157