| name | lamina-leverage-points |
| description | High-impact intervention points in product design — rules, information flows, and goals over UI tweaks. Use when local fixes fail to change behavior. |
| metadata | {"lamina":{"id":"leverage-points","problems":["UI tweaks that don't change outcomes","where to intervene in product rules","high vs low impact design changes"],"related":["lamina-system-traps","lamina-invariants","lamina-tradeoffs"],"tags":["design-default"]}} |
Leverage Points
Small shifts in the right place outperform large UI changes in the wrong place. Intervene on rules, information flows, and goals before rearranging screens.
Decision frameworks
- Low leverage: Parameters and numbers (button color, timeout value, copy tweak) — easy to change, limited structural effect.
- Medium leverage: Information flows — who sees what, when (student sees venue before payment vs after).
- High leverage: Rules and constraints — what is allowed, when, by whom (ticket available only after payment confirmed).
- Highest leverage: Goals and purpose — what the product optimizes for (throughput vs fairness vs compliance).
Checklists
- Before a UI redesign, ask: is this a leverage problem or a presentation problem?
- List current rules governing the failing behavior.
- Identify who lacks information that would change decisions.
- Propose rule changes before screen changes when traps persist.
- Document leverage rationale in
run.json domain or scenarios.
Heuristics
- Parameters are weak levers: Changing a timeout rarely fixes a broken workflow.
- Information beats persuasion: Showing "3 seats left" changes behavior more than motivational copy.
- Rules beat reminders: Disable illegal actions rather than warn after the fact.
Anti-patterns
- UI churn without rule change: Redesigning the download screen when availability rules are wrong.
- Hiding high-leverage decisions: Deferring permission model "until later."
Examples
- Ticket download window: Low leverage — bigger download button. High leverage — rule: download enabled only 48h before exam AND payment confirmed. Information flow — student sees countdown to availability.
Related capabilities
