esc
  • WorkflowsPages
  • Case studiesPages
  • Machine Learning FoundationsLearn
  • AI EngineeringLearn
  • AI Guardrails & Red TeamingLearn
  • UI/UXLearn
  • Design SystemsLearn
  • Production System DesignLearn
  • Book a callContact
  • Download ResumeContact
Let’s talk

I’ll build the agent for it.

Design Principles: Short Statements That Settle Design Trade-Offs

A design principle is a short, shared statement that helps a team choose between good options when no rule applies. Learn how to write, test, and use one.

In short

A design principle is a short, shared statement that helps a team choose between good options when no rule applies.

11 min readFree

What You Will Learn

Every design team makes choices that no rulebook covers. Should a page show every option at once, or one step at a time? Should an error message be short, or should it explain more? A design principle is a short, shared statement that helps a team make these calls the same way each time. In this lesson you will learn what a principle is, how it differs from a rule, what makes one strong, how to write one, and how to use it in critiques and handoffs.

Key words

Design principle
A short, shared statement of what matters most for a product. Teams use it to make design decisions.
Rule
A fixed instruction that says exactly what to do in one kind of case.
Guideline
Written advice on how to use a part or pattern well. It often explains the reasons behind it.
Visual style
The look of a product, such as its colours, spacing, and type.
Trade-off
A choice where getting more of one good thing means getting less of another.
Critique
A team meeting where designers show work and others give feedback on it.
Handoff
The moment a designer passes finished work to the people who will build the product.
User need
Something a person must get done, or wants to get done, when they use the product.

What Is a Design Principle?

A design principle is a small set of firm opinions about what a product should do for its users. <cite index="17-2">Such statements are usually four to eight in number, and a team agrees on them so that they can guide every design decision.</cite> When a hard choice comes up, a principle tells the team which value to favour. It is a tie-breaker, not a checklist.

Principles sit above the individual parts of a design system. Rather than living inside one button or one colour, a principle works across all of them, shaping how each part is chosen and used. <cite index="17-4">They inform all of the parts they sit above.</cite>

  • Principle

    States which value wins when goals clash. It does not give the exact size, colour, or wording to use. Atlassian describes principles as guides to behaviour and aids for tradeoffs.

  • Rule

    A fixed instruction for one case, such as 'the main action uses the strongest colour'. Rules are useful, but they run out. When a new case appears that no rule covers, a principle still gives the team a direction.

  • Guideline

    Advice on how to use a part well, often with examples and reasons. A guideline says how to do something. A principle says what matters most when the guideline does not reach.

  • Visual style

    The look of the product: colour, spacing, type, and shape. <cite index="21-6,21-7"></cite> A style answers 'what does it look like?', while a principle answers 'which goal wins?'

Tip

Ask one question about a draft sentence: does it help me pick between two good options? If it only describes how something looks, it is a style. If it tells you exactly what to build in one place, it is a rule.

What Makes a Principle Good?

Not every short, catchy line is a useful principle. Many teams write phrases that sound nice but never change a decision. A good principle has four qualities. It is specific, memorable, actionable, and able to settle a real trade-off.

  • Specific to your product

    <cite index="10-3,10-4">Universal sayings that could apply anywhere do little work. A principle should apply uniquely to the product that is being built.</cite> 'Less is more' could describe almost any product, so it cannot guide your team alone.

  • Short and memorable

    A principle is not an essay. <cite index="13-5">It should be concise, because design principles are not meant to be long.</cite> Keep the title short enough that a team member can repeat it in a meeting. The NN/g guidance also warns that a long list gets forgotten, so keep the set small.

  • Actionable

    A principle earns its place when it helps someone choose. <cite index="10-6">The main purpose of design principles is to help the team make decisions.</cite> If nobody uses it in a real choice, it is decoration.

  • Settles a real trade-off

    The best principles name a winner when two good things clash. <cite index="22-15">Atlassian frames its principles as one important thing over an equally important thing, so the team stays aware of what it gives up.</cite>

A simple test catches weak principles. This lesson's own check, which none of the cited sources establishes as a standard method, is to imagine that nobody on the team would argue against the statement. 'Be user-friendly' passes that test, which means it fails. Everyone agrees with it, so it cannot end a debate about a checkout page.

Tip

Run the disagreement test. Picture two sensible teammates who pick opposite options for the same screen. If your principle helps you decide between them, keep it. If both of them could claim it, rewrite it.

How Do You Write Principles?

Writing principles is a process, not a single brainstorm. Most teams work through a few clear steps, often in a workshop with designers, product staff, and content writers. <cite index="11-4"></cite>

  1. 1

    List the values the product needs

    Start with the few values the product cannot succeed without. Look at vision notes, project briefs, and what sets your product apart from competitors. If you have many values, keep the most important ones.

  2. 2

    Ask why each value matters to users

    For each value, ask what it helps the user achieve, and what would happen to users if the team ignored it. <cite index="13-11">To keep principles user-centred, ask why these values are important.</cite> Write the answers down.

  3. 3

    Look for arguments that keep coming back

    <cite index="11-6">Look for areas of recurring disagreement or inconsistency.</cite> A debate that repeats across projects often marks a trade-off that a principle should settle.

  4. 4

    Draft a short title and a one-line reason

    Give each principle a short title, such as 'Clarity over decoration'. Then add one sentence that explains the value and why it helps the user. <cite index="14-8">Some teams keep a principle to one sentence, while others write several paragraphs.</cite> For a team that is new to this, one sentence is a good start.

  5. 5

    Compare and refine

    Check that no two principles fight each other. <cite index="13-7,13-8">If two principles are both important but apply in different contexts, say which one wins in which context.</cite> Then test the wording on real past decisions and tighten it until it is clear.

Tip

Use your own history as the source of examples. <cite index="10-15"></cite> Past screens, old arguments, and past user complaints show where principles are needed.

Keep the set small. <cite index="10-13,10-14">Having too many principles weakens how well they support decisions, and three is a number that one writer has found works well for a product or feature.</cite> NN/g warns that with 10 or more principles, many are forgotten. More than that and they stop being used.

How Do You Use Principles in Critiques and Handoffs?

A principle does nothing sitting in a document. It has to be used in the moments when a team makes a decision. <cite index="23-7">Before starting any design, the team needs guiding principles to make sound decisions.</cite>

  1. 1

    Name the principle first in a critique

    When you show an option in a critique, say which principle it serves before you walk through the screen. The group can then judge the option against a shared standard, not just personal taste.

  2. 2

    Say which value wins and which one you give up

    Every trade-off has a cost. Say it out loud. <cite index="13-13">Use the principles to explain and justify design decisions, rather than saying a choice is best or was made because someone said so.</cite>

  3. 3

    Carry the reason into the handoff

    When you pass work to the people who will build it, include the principle and a one-line reason in the notes. This stops the build team from quietly changing a choice that was made for a reason.

  4. 4

    Revisit the principle when results disappoint

    If a principle keeps leading to poor results, the wording or the scope may be wrong. Rewrite it, test it on the next decision, and record what changed. Principles should be treated as drafts that improve over time.

Worked Example: GOV.UK's Question Pages

GOV.UK is the UK government's website, and its design team publishes a set of government design principles. Two of them are <cite index="4-7">'Start with user needs'</cite> and <cite index="4-10">'Do the hard work to make it simple'</cite>. Below is how a team could use those two principles to settle a real choice. The team is building a form that asks a person for several facts. It must choose between one long page with every question, or a step-by-step flow with one question per page.

  1. 1

    Name the trade-off

    The long page is quick to build and keeps everything in one view. The step-by-step flow takes more design and build work, but each screen asks less of the person. The team needs a reason to pick one.

  2. 2

    Test the options against user needs

    The first principle asks what the person filling in the form needs. The team asks whether the long page serves the person, or only the team that built it. This moves the choice from habit to evidence.

  3. 3

    Apply 'do the hard work to make it simple'

    This principle asks the team to take on the extra effort so the user has less to do. GOV.UK's own service guidance supports this reading: <cite index="8-11,8-12">a series of simple questions can be easier to answer than one complex question, especially when parts of the complex question do not apply to every user.</cite> One question per page moves the effort from the person to the team.

  4. 4

    Check the question style

    <cite index="8-7">Closed questions are easier to answer than open questions, especially in services where users are often afraid of getting it wrong.</cite> So each page should ask a question that has a clear answer, not a long essay to write.

  5. 5

    Cut questions that do not earn their place

    <cite index="8-5">Before starting, make sure you know why you are asking every question.</cite> Any question without a clear purpose is removed, which makes the flow shorter for everyone.

  6. 6

    Record the decision

    The team writes a short note: we chose one question per page because it starts from user need and makes the task simple. The long page would have pushed the hard work onto the person filling in the form. Anyone who revisits the form later can see the reason.

Tip

<cite index="8-13,8-14">GOV.UK's guidance gives a warning sign. If a team has to use help text to explain the interface, the service is too complicated.</cite>

Practice: Choose With a Principle

Try these two short scenarios. Each one needs the ideas from this lesson to answer.

Quick check

Your team is debating whether to add a decorative animation to the Pay button at checkout. Your product's principles are 'Clarity over decoration' and 'Respect the user's time'. Which choice is best, and why?

Quick check

A team building a tax filing product proposes four principles. Which statement is the strongest principle to keep?

Where This Lesson Stops

This lesson covers the decision tool itself: what a principle is, how to judge it, how to write it, and how to use it. Other lessons cover the topics that principles support. Vision, the long-term goal of the product, is one such topic. Principles help a team reach a vision, but they do not define it. Tone of voice, design language, accessibility and readability, naming and spacing, and individual components each have their own lessons, where principles are applied to specific work.

Sources

How is this lesson?

Last updated on 17 November 2026

Learn with me

Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.