What it is
A methodology (Sophia Prater) that identifies the core objects in a domain, their content, metadata, and relationships, before designing actions and interfaces, so structure reflects users’ mental models.
When to use it
During Synthesize into Prototype, for content- and data-rich products where structure is complex.
Why (value)
Aligns the system with how users think about the domain, reduces rework, and produces more coherent, scalable IA.
How to run it
- Identify the domain’s core objects (nouns).
- Define each object’s content and metadata.
- Map relationships between objects.
- Attach calls-to-action to objects.
- Derive screens and IA from the object model.
Inputs and outputs
- Inputs: Domain understanding and research.
- Outputs: An object model driving IA and interface design.
Time and effort
Medium. A structured analysis effort.
Evidence and limitations
A structuring framework; the object model should reflect validated user mental models, not just internal data schemas. See Evidence and limitations.
Tips and pitfalls
- Start from objects (nouns), not screens or actions.
- Ground objects in user mental models, not the database.
- Map relationships explicitly.
Variations
ORCA process, object mapping workshops.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Content modeling — Define the structure, types, and relationships of content so it can scale and reuse.
- Taxonomy design — Design the categories and labels that organize content so people can find things.
- Sitemapping — Map the hierarchy and structure of a site or app's pages and sections.
