Domain Patterns for Product Designs
Domain patterns are the design conventions that differ by product context. B2B SaaS and dashboards favour dense data and complex permissions, mobile consumer apps favour speed, gestures and short sessions, and fintech or health products must add clarity, consent and compliance. Knowing the context decides which rules apply.
Stage: Specialised Product Areas · Part of the Product Design roadmap · Last reviewed 19 November 2026
What to learn in Domain Patterns
- Design a data table with sorting, filtering and bulk actions for a B2B tool
- Plan a mobile flow around thumb reach and short sessions
- Show money amounts, fees and confirmations clearly in a fintech flow
- Handle consent, privacy and error recovery in a health product
- Adapt a pattern when regulation or audit trails limit the options
Domain Patterns interview questions
How does designing a B2B dashboard differ from a consumer app?
B2B dashboards serve expert, repeated use, so they favour dense information, filters, saved views, roles and keyboard efficiency. Consumer apps prioritise quick onboarding, delight and simple flows, because users have less training and more alternatives.
What extra care does design in a regulated domain need?
Regulated domains such as finance and health require clear disclosures, explicit consent, accurate error messages, audit trails and security-aware flows. Designers work with legal and compliance teams early so that usability changes do not break required wording or steps.
Where Domain Patterns fits in the Product Design roadmap
Domain Patterns belongs to the Specialised Product Areas stage (intermediate level), which takes about 5 hours. Different contexts, different rules.
Back to the full Product Design roadmap