form-follows-function-success-criteria

Define and prioritize design success criteria to evaluate candidate form options.

6|3|Updated May 3, 2026
One-click install
npx skills add https://github.com/HDeibler/universal-design-principles --skill form-follows-function-success-criteria
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: form-follows-function-success-criteria
Source: https://github.com/HDeibler/universal-design-principles/tree/main/plugins/aesthetics-and-emotion-principles/skills/form-follows-function-success-criteria
Command: npx skills add https://github.com/HDeibler/universal-design-principles --skill form-follows-function-success-criteria

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It resolves form-vs-function design disputes by making the team’s success criteria explicit, so decisions are evaluated against agreed outcomes rather than implicit preferences.

Core Features & Use Cases

  • Success-criteria reframing: shift the question from “what should we omit?” to “what must be critical to succeed?” for this specific surface.
  • Criteria identification and ranking: list candidate criteria (user performance, satisfaction, business outcomes, brand differentiation, accessibility, cost, maintainability, emotional response) and prioritize the dominant ones.
  • Trade-off decision support: evaluate candidate design choices against the top 2–3 criteria, then accept deliberate trade-offs on lower-priority criteria, including worked examples for disputed designs.

Quick Start

Ask an AI assistant to help you list and rank the success criteria for your disputed UI or product surface, then evaluate which design option best satisfies the top criteria.

Frequently Asked Questions about form-follows-function-success-criteria

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve form versus function debates during a UI review?

Resolve form versus function debates by shifting focus from subjective preferences to explicitly naming and ranking success criteria for the specific UI surface. This operationalizes outcomes like user performance, brand differentiation, and accessibility, allowing the team to evaluate candidate designs against agreed priorities.

What is the best way to define success criteria for a disputed UX design?

Defining UX success criteria involves listing candidate outcomes such as user satisfaction, business goals, and maintainability, then prioritizing the dominant two or three. This reframes unclear briefs and establishes a defensible baseline for evaluating which design choice should win.

How do I handle trade-offs between competing UI design options?

Handle UI design trade-offs by evaluating candidate options against your top prioritized success criteria, then deliberately accepting compromises on lower-priority criteria. This explicit trade-off analysis ensures stakeholder alignment and reaches defensible design decisions.

Can I use success criteria prioritization for stakeholder alignment on unclear briefs?

Yes, success criteria prioritization clarifies unclear briefs by forcing stakeholders to explicitly agree on what outcomes matter most for the surface. This shared ranking shifts debate from implicit preferences to criteria-weighted evaluation, resolving disagreement.

When do I need to operationalize design success criteria for a product surface?

Operationalize design success criteria when a team cannot articulate why a concept feels wrong or struggles to choose between competing design directions. It is specifically needed during stakeholder disagreement, unclear briefs, and design reviews to reach defensible decisions.