Marcus Andrey Study
Ler em português Library

Framework · Strategy & vision · 2 min read

Design principles

A few opinionated rules that help a team choose between two good options. Use the opposite test to check that each one actually says something.

  1. 1Generate

    Collect candidate rules from the team's real choices between good options.

    "What did we choose, and why?"
  2. 2Opposite test

    Write the opposite. Would a reasonable team choose it? If not, drop it.

    "Could anyone disagree?"
  3. 3Try on past

    Check them against three or four recent decisions. Keep the ones that decide.

    "Would this have helped us choose?"
  4. 4Use them

    Name the principle in critiques and reviews when you make a call.

    "Which principle does this follow?"

Repeat when your context changes, or when a principle stops being quoted.

Good design principles are built from real decisions and survive the opposite test.

Use it when

  • Design reviews keep ending in taste arguments, and nobody can say which option fits "our" way.
  • Your team has principles on a poster, but nobody uses them to make a decision.
  • You are writing a UX strategy and vision and need the "how we decide" part that sits under it.

How to use it

  1. Generate candidates with the team. Ask designers and a few product partners: "When we had to choose between two good options, what did we choose and why?" Write each answer as a rule of the form "X over Y". Output: 10 to 15 candidate principles.
  2. Apply the opposite test. For each candidate, write the opposite and ask whether a reasonable team somewhere would choose it. Drop or sharpen any candidate whose opposite is absurd. Output: candidates with a valid opposite.
  3. Try them on real past decisions. Take three or four decisions from recent projects and check whether the principles would have helped choose. Keep the ones that actually decide something. Output: 3 to 5 principles that passed.
  4. Add a short explanation and an example. Under each principle, write one sentence on what it means in practice and one example from your tools. Output: a one-page principles sheet.
  5. Use them in critique and reviews. Name the principle when you make or challenge a decision, and revisit the list when your context changes. Output: principles quoted in real review notes.

Worked example

Example principles for internal operational apps, from the module. Each one has an opposite that is valid elsewhere.

Principle Opposite (also valid elsewhere)
Speed for experts over guidance for novices. Keyboard, density, bulk actions. Guided onboarding first
Show the exception, not the rule. Surface what needs attention. Show everything, let the user filter
Consistent across tools, specific within domains Each domain optimises locally
Prevent errors before reporting them Validate on submit
Measure what we change Ship and move on

In a review, a designer proposed a step-by-step wizard for a booking form. The team pointed to "Speed for experts over guidance for novices" and kept the single dense form, with a short help link for new staff.

Watch out for

  • Principles nobody could disagree with. "User-centred" and "simple" sound good and decide nothing. Use the opposite test.
  • Too many. Ten principles can't be remembered or used in a meeting. Keep three to five.
  • Written alone. Principles the lead writes alone get compliance, not use. Build them from the team's real decisions.
  • Never used. If nobody quotes a principle in a review for months, rewrite it or retire it.

Template

Copy this to draft and test your principles.

Candidate principle:   ___ over ___
Opposite:              ___ over ___
Would a reasonable team choose the opposite?  Yes / No
Past decision it would have helped:
What it means in practice (one sentence):
Example from our tools:
Keep / Sharpen / Drop

"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close