| name | extreme-attribute-prototyping |
| description | A framework for discovering non-obvious product solutions by rapidly building and testing radical, opposing versions of a feature's core attributes. Use this when stuck between mediocre design options, when a feature involves a fundamental trade-off (like speed vs. safety), or when designing a V1 from scratch. |
Extreme Attribute Prototyping
This framework avoids the "trap of the middle ground" by forcing teams to explore the radical ends of a design spectrum. By building "extreme" versions of a feature, you reveal hidden requirements and emotional hooks that lead to an "obvious in hindsight" solution.
The 10% Velocity Rule
Before applying the framework, set the pace. Speed is a proxy for competence, not sloppiness.
- Set a Time Budget: Determine how long the total feature should take to build (e.g., 4 weeks).
- The 10% Milestone: By the time 10% of the budget has passed (e.g., 2-3 days), you must have a workable, internal version that tests a key hypothesis.
- Avoid Perfection: Do not wait for pixel-perfect designs. Use the first 10% to "feel" the software and validate or invalidate major assumptions.
The Prototyping Process
1. Identify the Core Tension
Define the two competing values or attributes for the feature.
- Example: Speed vs. Safety, Customization vs. Simplicity, Predictability vs. Availability.
2. Design the "Extreme Archetypes"
Instead of looking for a compromise, design two radical versions that ignore the other side of the tension entirely.
- Version A (The Radical Max): If "Speed" is the goal, build the version that requires zero clicks, even if it feels "unsafe" or risks data loss.
- Version B (The Radical Safe): If "Safety" is the goal, build the version that auto-saves every character and interrupts the user constantly to prevent mistakes.
