Description
A team lists the words it wants and never wants used about its product, defines each with a measure and method, and re-evaluates the product against both lists every release.
Specifications state goals yet teams still diverge. With personas in hand, the team brainstorms on sticky notes the words it would like users, marketing or reviewers to use about the product, using product reaction cards as a prompt, groups them and keeps no more than about ten guiding principles. Each is defined so it can be measured and given a method: 'easy to use' as 100% booking success without help in usability studies, 'fast' as results under 30 seconds in log analysis. The same is done for antiprinciples, things the team never wants said, such as 'ad-filled' (ads over 10% of the screen) or 'untrustworthy'. Antiprinciples are a strong check on feature creep. The rigour is the measurement: evaluation checkpoints are scheduled before and after launch and the lists are revisited each version.
Attributes
- Discipline
- Design & Product Practice
- Loss type
- Vestigial
- Stage
- Strategy, Definition, Post-launch
- Data
- Mixed
- Effort
- Days
Steps
- With personas visible, brainstorm desired descriptors on sticky notes, using reaction cards to start, and group them.
- Keep up to about ten guiding principles.
- Write a measurable definition and name the measuring method for each (for example task success in usability testing, response time in logs).
- Repeat the process for antiprinciples, again with definitions and measures.
- Schedule evaluations against both lists before and after launch.
- Revisit and revise both lists at each version or market change.
Sources
- Understanding Your Users (Baxter et al., 2015)
- The Staff Engineer's Path (Reilly, 2022)
Also known as
- Product principles and anti-principles
- GPs and APs
- Experience principles
- Design principles
- Even over statements
Categories
- Design
- Design & Product Practice