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.