form-follows-function-success-criteria

Resolve form-versus-function debates by making success criteria explicit: list the criteria the design should serve, rank them for the specific surface, and evaluate each option against the top two or three. The dominant criterion usually resolves the disagreement.

Common criteria include user performance, user satisfaction, business outcomes like conversion and retention, brand differentiation, accessibility, implementation simplicity, maintainability, and aesthetic response. Most designs serve several; the key question is which dominate when they conflict.

Debates stall when team members assume different implicit criteria: designers assume visual elegance, engineers assume simplicity, marketers assume differentiation. Without explicit shared criteria, every decision is contentious because each side argues from a different definition of success.

Read the parent form-follows-function skill first for the core principle and its interpretations. This sub-aspect skill applies specifically when the team is already in a form-versus-function dispute and needs to step back to define what success means.

Legitimate trade-offs include visual polish versus load time, brand differentiation versus convention adherence, aesthetic minimalism versus feature discoverability, and custom versus native components. Each should be made deliberately with explicit success criteria informing the choice.