Interaction model brief
Define how product objects, actions, states, and navigation behave as one coherent system.
Product features · 45 min · Advanced · 21 questions
Objects and relationships
What things can users create?
What things do users need to view?
What things do users need to manage?
What does the user call each object?
How does each item connect to the others?
Who owns each object?
What event creates each object?
What event ends its lifecycle?
Actions and state
Which action can a user take on one object?
Which action can apply to a selection?
Which states can each object enter?
Which event triggers each state change?
When must a state change be blocked?
How will users know a state change succeeded?
What should users see when the same item changes somewhere else?
Navigation and control
How do users move between related objects?
Which context must navigation preserve?
Which action can be undone?
Which deleted object can be recovered?
How will keyboard users perform the core actions?
Which state change should a screen reader announce?
How to use this brief
Use this brief as a bank of questions for the conversation. Choose what is relevant, mark covered questions as you go, and skip anything that has already been answered.
Use this brief when...
Use when you need to define how product objects, actions, states, and navigation behave as one coherent system.
Best used as: Workshop
- Category
- Product features
- Discussion time
- 45 minutes
- Depth
- Advanced
- Last updated
- Jul 21, 2026
- Scope
- Design briefs
- Best used as
- Workshop
- Design roles
- Product designer
- Audience
- Product designersUX and UI designersDesign leadsFreelancers and consultants
- Platforms
- Cross-platform
- Company type
- StartupB2BB2CEnterprise
- Product stage
- Early-stageGrowthMature product
- Tags
- product-featuresinteraction-modelproduct-and-experienceinteraction-modelcomplex-productbehavior-architecture