Description
Translate research themes into a few concise, product-specific imperative principles, then use them to generate concepts and to judge which concepts to keep.
Design principles are short imperative statements that turn what research found into what the product should do. The framework runs from patterns in the data, to themes that explain why each matters and why it occurs, to a prescriptive principle, to concepts generated by asking how might we honour it, to tests asking whether a concept should go ahead. Opower's theme that people forget simple ways to save energy became 'Always lead to action', which generated a door-tag reminder and is still used in critiques. Good principles are clear, open about form, agreed and authoritative. Spool-style tests check quality: a principle should help the team say no, distinguish the product, have a plausible opposite, and be specific to this product rather than a truism such as 'be usable'.
Attributes
- Discipline
- Design & Product Practice
- Loss type
- Active
- Stage
- Definition, Design
- Data
- Analytical / expert
- Effort
- Days
Steps
- Identify patterns or themes in the research data.
- For each theme, write why it matters, why it occurs and its usual consequences.
- Write a prescriptive principle stating what the product should do in response; keep the set to roughly three to seven.
- Test each principle: does it help say no, differentiate the product, have a plausible opposite, and apply specifically here?
- Generate concepts by asking 'How might we ...' against each principle.
- Evaluate concepts against every principle and drop those that fail.
- Agree the principles across the organisation, use them in critiques, and revise them when new research arrives.
Sources
- Designing Connected Products (Rowland et al., 2015)
- Chatbot Research and Design: CONVERSATIONS 2022 (Følstad et al., 2023)
Also known as
- Design principles framework
- Themes to principles to concepts to tests
- Design principles
Categories
- Design
- Design & Product Practice