What it is
Defining the types of content a product has, their attributes, and relationships, independent of layout, so content can be structured, reused, and managed at scale.
When to use it
During Synthesize into Prototype, for content-heavy or multi-channel products.
Why (value)
Enables structured, reusable, channel-agnostic content and prevents ad hoc page-by-page content decisions.
How to run it
- Identify the content types in the domain.
- Define attributes/fields for each type.
- Map relationships between types.
- Validate against real content and use cases.
- Feed the model into CMS and design.
Inputs and outputs
- Inputs: Content inventory and domain understanding.
- Outputs: A content model of types, fields, and relationships.
Time and effort
Medium. Analysis effort.
Evidence and limitations
A structural framework; should be validated against real content and user needs, not just editorial convenience. See Evidence and limitations.
Tips and pitfalls
- Model content, not pages.
- Ground it in real content examples.
- Coordinate with OOUX and taxonomy work.
Variations
Structured content models, CMS content types.
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
- Object-oriented UX — Design around the real-world objects users care about before designing actions and screens.
- Taxonomy design — Design the categories and labels that organize content so people can find things.
- Content-first design — Design around real content instead of filling a layout with lorem ipsum.
