Design Principles

Why Most Design Principles Fail

Fri, 10 Apr 2026 13:55:39 +0000

Many organisations publish design principles. They appear in slide decks, design systems and internal documentation. They are sometimes printed on posters and hung on office walls. Yet they are rarely used.

Meetings still go on and on. Teams argue over the same questions. Decisions often depend on opinion or whoever speaks the loudest.

The problem is usually not that teams lack design principles. The problem is that most design principles don’t work.

They are written like slogans

Many design principles sound impressive, they’re idealistic and make everyone feel positive. They come from great motives.

Be user-centric.
Keep things simple.
Delight the customer.

But these are not really principles. They are aspirations. They describe how a team would like their work to feel.

A design principle should do something more practical. It should help a team make a decision when there are several possible options.

A slogan describes intent. A principle guides a choice.

For example:

“Keep things simple.”

What does that mean in practice?

“Simple” is subjective.

Simple for whom?
Simple compared to what?
Simple in which situation?

“Simple” sounds sensible, but it’s also very vague. Different people will interpret simple in completely different ways.

One designer might think simple means removing options. Another might think it means reducing visual clutter. Someone else might think it means hiding complex features behind a menu so the initial view is clean.

All of those interpretations could be defended as “keeping things simple”.

There is another problem here. Simplicity is not always the right goal.

Imagine applying the same idea of keeping things simple when designing an aircraft cockpit. A cockpit would certainly be simpler if it contained only a steering wheel and a start button. But that level of simplicity would make it completely unusable for its purpose.

A cockpit contains many instruments and controls because the pilot needs them. Removing them might make the interface look simpler, but it would make the aircraft much harder — and far more dangerous — to operate.

So the instruction “keep things simple” does not really guide a decision. It only describes a general preference.

A principle needs to go a step further. It needs to explain what should happen when things become complicated.

A more useful principle might be something like:

“Prefer what matters.”

Now a team has something they can use. If a design includes too much information, the principle guides them towards what to prioritise. The discussion becomes about prioritisation rather than personal preference. The discussion becomes about what truly matters.

They avoid trade-offs

Real principles reveal priorities. Many sets of principles list ideas that sound sensible but never conflict with one another.

A typical list might look like this:

Be consistent
Be flexible
Be simple
Be powerful

All of these sound reasonable. But none of them help when a decision becomes difficult. Real design work involves trade-offs.

Sometimes consistency conflicts with clarity. Sometimes simplicity conflicts with flexibility.

A useful principle helps resolve those moments. If everything is equally important, nothing actually guides the decision.

There are too many of them

Some organisations publish ten or fifteen design principles. Long lists are difficult to remember and difficult to recall in conversations when discussing a decision. When principles become long lists, they turn into documentation instead of tools. A small number of principles is easier to remember and easier to use in conversation.

Good principles should appear naturally in discussions:

“Does this follow our clarity principle?”

“This might conflict with our accessibility requirement.”

“Does this feature really matter here?”

If nobody can remember them, they will never influence decisions. The most effective examples use 3-5 principles.

They are never used

The real test of a design principle is very simple. Does anyone actually refer to it?

If principles only exist on a website or inside documentation, they are unlikely to matter.

When principles work well they become part of everyday language. Teams refer to them during discussions and use them to justify decisions. They help people explain and understand why one option is better than another. Without that practical use, they remain decorative.

They are often confused with values

Many design principles are actually organisational values. Design principles aren’t mission statements.

Values describe what a company believes.

Principles guide how teams make decisions.

Both are important, but they serve different purposes.

A value might say:

We value transparency.

A principle might say:

Help the user understand what is happening and why.

Values shape culture.

Principles shape decisions.

When the two are mixed together, principles become vague and difficult to apply.

What principles are really for

Design principles are not statements of intent. They are tools. They help teams make decisions when things are unclear. They reduce debate. They give people a shared way to reason about choices.

When written well, they quietly shape how work gets done. When written poorly, they become slogans that nobody uses.

The difference is not whether a team has principles. It is whether those principles actually guide decisions.

Often design principles are confused with rules. It’s important to understand the difference between principles and rules. This distinction is explained in the free sample chapter of the field guide Design Principles in Practice.

I write occasionally about how principles function in real organisations, where they succeed, where they fail, and how they evolve over time.

If that’s useful to you, you can subscribe below.

No spam. Unsubscribe any time.
See our Privacy Policy.

Principles for Knowing When to Stop Designing

Fri, 10 Apr 2026 13:55:39 +0000

At the moment the design world is obsessed with how fast things can be built. The conversations are about “I shipped a whole product in 2 hours” or “I built a startup in a weekend.”

New tools are creating faster workflows, quicker iterations, and the ability to produce more than ever before. In many ways, our new tools deliver and extend our capabilities as designers. But as always when the focus of conversation shifts to being about tools rather than outcomes, something has been lost in the process.

In music, knowing when to stop is just as important as knowing what to play. The pause gives structure to the sound. Without it, everything becomes noise.

As Mile Davis said “It’s not the notes you play, it’s the notes you don’t play.”

Tools will continuously improve and develop but they’re focused on delivery, shipping, iterations, not pausing or reflection.

These principles for knowing when to stop are not about slowing down for the sake of it. They’re about recognising when a decision has already been made, and when further work stops serving the user and starts serving the designer.

And ultimately understanding why we are building something rather than how quickly we are building something.

1. Stop when the next change is for you, not the user

Not every improvement is meaningful.

When changes are driven by taste, preference, or the desire to explore, are they solving a design problem? At this point, design becomes self-expression rather than problem solving. It’s art, not design.

This is often the quiet moment where good design work starts to drift.

2. Stop when the problem isn’t proven

Design without evidence is speculation.

Is the problem even real? If you can’t clearly point to a problem through research, behaviour, or observable friction you’re no longer solving something real. You’re designing in anticipation of a need that may not exist.

This doesn’t mean certainty is required, but it does mean intent should be grounded.

3. Stop when the question shifts from “why?” to “how?”

The moment the conversation becomes about execution, the decision is already behind you.

“How should this work?”, is not a design question. It’s a delivery question. The risk is that designers continue to iterate as if the core problem is still open, when in reality it has already been resolved.

Continuing to design at this point often leads to unnecessary variation rather than better outcomes.

4. Stop when you’re redesigning not refining

Refinement reduces uncertainty. Redesign introduces it.

Often we’re asked to help with a “redesign” but often we’re just building the same thing but different.

If each iteration creates new questions instead of resolving existing ones, the work is no longer converging. It’s diverging again, often without intention.

This is one of the clearest signals that we’ve crossed from improvement into reinvention.

5. Stop when the design can’t be tested in its current form

Test a design as early and in as fit a state as possible for who you’re testing it with. If it can’t be shown, used, or experienced by someone else, further iteration is disconnected from reality. The only meaningful next step is getting some feedback, not additional polish. The polish can go on forever.

Design only improves through contact with use.

6. Stop when you’re designing for edge cases

Edge cases are important but they shouldn’t lead. Discussions around edge cases can dominate meetings.

When rare scenarios begin to dictate core decisions, it’s often a sign that the central use case hasn’t been fully resolved. Designing for the margins before stabilising the centre creates fragile solutions and is often a very slow and painful journey.

Solve the common case well first. The edges can follow.

7. Stop to allow time to learn

Design doesn’t end when you stop working on it.

The most valuable insights come after pausing for feedback, testing or release, when real behaviour replaces assumptions. Without this pause, there’s no opportunity to understand whether you were close to getting things right.

Stopping isn’t the end of design. It’s a pause that makes learning possible.

You don’t need to stop for long. Stopping doesn’t slow things down. But knowing when to stop is what turns design from activity into decision-making.

I write occasionally about how principles function in real organisations, where they succeed, where they fail, and how they evolve over time.

If that’s useful to you, you can subscribe below.

No spam. Unsubscribe any time.
See our Privacy Policy.

How Many Design Principles Should a Team Have?

Fri, 10 Apr 2026 13:55:39 +0000

There is no universal rule. But looking across many organisations, effective sets of principles tend to remain relatively small.

How many principles are too many?

Some organisations publish ten or even fifteen design principles.

While these lists are usually well intentioned, long lists are difficult to remember and are unlikely to appear in everyday discussions.

Design principles are primarily a decision-making tool, but they can also play a broader role within an organisation. They can support cultural change, reinforce new ways of thinking, or help explain why a shift in approach is needed.

This was the case with the GOV.UK Digital Service Standard. The list of principles is long, eighteen in total. But at the same time, the digital transformation work carried out by the GDS team affected every part of government. Principles were embedded into processes, clearly communicated and publicly visible.

In an environment shaped by risk, compliance and policy, questions about why change is necessary inevitably arise. In this context, principles helped explain the reasoning behind the transformation.

Was eighteen principles too many?

It depends on the context. The team understood how the principles guided decisions and the scale of the work they were supporting. For most organisations, however, a list of this size would be difficult to use in practice.

When the list becomes long, principles become harder to remember and less likely to influence everyday decisions.

Long lists often become documentation rather than tools. As the list grows, principles also tend to drift closer towards being rules rather than guidance.

Why small sets work better

Design principles are most useful when they can be remembered easily. Three, four or five principles are much easier to remember and use than eight, nine or ten.

A short set allows people to recall them quickly during discussions and apply them when evaluating different options.

When a principle can be referenced naturally in conversation, it becomes part of how a team reasons about design decisions.

For example, someone might ask:

“Are we over thinking this? Our principle is pragmatism…?”

Or someone else might say:

“This seems too rigid, it might conflict with our flexibility principle.”

In these moments, the principle is actively shaping the decision.

This is much harder to achieve when a team has a long list of principles that nobody can recall without looking them up.

A common pattern

Looking across many organisations, effective sets of design principles often contain between three and five principles.

This number is not a strict rule, but it appears frequently.

A small set creates focus. It forces teams to identify the ideas that matter most when making decisions.

When too many principles exist, it becomes unclear which ones should take priority.

The longer the list gets the more diluted they can become.

Principles are not meant to cover everything

One reason organisations sometimes produce long lists of principles is the desire to include every important idea. There is a natural tendency to lean towards rule-making in order to feel safe, to feel like everything is covered, documented and in control.

But design principles are not intended to describe everything a team values. Gaps are healthy.

They are meant to guide decisions when there are multiple reasonable options.

Because of this, a small number of principles is often more useful than a comprehensive and well-documented list.

The goal is not completeness. The goal is clarity.

In practice

Effective design principles are usually few in number and easy to recall.

They appear naturally in conversations and help teams explain why one option is better than another.

When a set of principles becomes too large to remember, its influence tends to fade.

In practice, the most useful sets are often the simplest: a small number of ideas that consistently guide how a team approaches design decisions.

If you’re interested in how design principles help teams make better decisions, I occasionally share new articles and ideas by email.

You can sign up below.

No spam. Unsubscribe any time.
See our Privacy Policy.

The Difference Between Rules and Principles

Fri, 10 Apr 2026 13:55:39 +0000

Understanding how principles help with decision making starts with understanding how they differ from rules. The distinction matters. Rules and principles serve very different purposes. Yet many “design principles” are written more like rules.

What rules do

Rules remove ambiguity. Rules are rigid. They tell people exactly what must happen. Rules usually lead to a consequence, either:

the rule is broken, or
something happens when the rule isn’t followed.

For example:

Our logo must always appear on a white background.

This rule guarantees consistency. Everyone knows exactly what to do.

A rule like this prevents designers from using the logo on:

coloured backgrounds
photography
illustrations
gradients

Even if those options might work perfectly well.

Rules assume there is one correct answer or only one solution has been considered.

In many situations, especially technical or legal ones where a level of compliance has to be reached, rules are appropriate.

What principles do

Principles work differently.

Instead of prescribing a single outcome, they describe what a good outcome should achieve.

Consider the same example written as a principle:

The logo should be clearly legible.

The goal is the same: protecting the visibility of the logo. But now designers have room to explore solutions.

They can place the logo on different backgrounds, colours or images, as long as the logo remains easy to see.

The principle does not dictate the design.

It guides judgement.

Why this matters

Design decisions are rarely as simple as deciding how to display a logo. Design rarely involves a single correct answer. Most design work involves balancing competing priorities between different people and different goals, navigating budgets, timelines, and politics.

For example:

clarity vs completeness
consistency vs flexibility
simplicity vs capability

Rules struggle in these situations because they assume the answer is fixed.

Principles acknowledge that design decisions often involve tension between competing forces.

They help teams navigate those trade-offs.

Visualising how principles work

One way to think about this is to imagine a design decision being shaped by different priorities pulling in different directions. Principles help teams balance those forces and arrive at a thoughtful outcome.

This idea is illustrated in the sample chapter of Design Principles in Practice, where the relationship between design decisions and principles is explored in more detail.

→ View the sample chapter

Rules and principles both have their place

Most organisations need both. Rules are useful when consistency or compliance is essential. Principles are useful when teams need guidance to make thoughtful decisions.

Rules define the answer.

Principles help teams find the best answer.

Or more simply:

Rules remove choice. Principles guide choice.

If you’re interested in how design principles help teams make better decisions, I occasionally share new articles and ideas by email.

You can sign up below.

No spam. Unsubscribe any time.
See our Privacy Policy.

Design Principles vs. The Principles of Design

Fri, 10 Apr 2026 13:55:39 +0000

Despite the title sounding like a battle that’s about to commence on a whiteboard, there is an important distinction to be made.

The terms “the principles of design” and “design principles” are often used interchangeably or blurred into one. Often I see people refer to examples on this website and say “Great example, I’m going to use those in my design (or for my organisation).”

But who design principles are for and what they refer to are two different things. They operate at different levels, serve different purposes, and guide different kinds of decisions.

Principles of design focus on the how. How a design is executed, composition, arrangement, layout.

Design principles are strategic and focus on the why? They are used to aid decision-making about a project’s goals.

Understanding the distinction matters, especially when teams use the language loosely and assume everyone means the same thing.

The Principles of Design

When people refer to the principles of design, they are usually talking about foundational visual principles that are taught in art and graphic design.

These include ideas such as:

Contrast: The use of difference to create emphasis.
Balance: The distribution of visual weight.
Hierarchy: The organisation of importance.
Alignment: The deliberate positioning of elements.
Proportion: The relative sizing of parts.
Repetition: The reuse of elements to create cohesion.
Unity: The sense that a composition belongs together.
Rhythm: The visual pacing of elements.
White space: The intentional use of empty space.

These principles describe how visual elements relate to one another in a composition or layout. They help designers organise form, create clarity, and shape perception.

They are concerned with:

How something looks
How elements are arranged
How visual relationships are structured

They are craft-level principles. They guide execution.

They are also universal and relatively stable. The principles of visual design have been taught for decades because they describe perceptual and compositional fundamentals.

They serve a common purpose for all designers.

Design Principles

Design principles, in a broader organisational or product context, are different.

They are not about composition or how something looks.

They are about decision-making.

A design principle, in this sense, is a guiding statement that helps a team make trade-offs when the right answer is not obvious.

Unlike rules, which prescribe a specific outcome, principles guide judgement.

They operate at a strategic level rather than a purely visual one.

Let’s take a look at the following design principles, example (taken from Fisher-Price’s Toy Making Principles ):

“Intrinsic play value”
“Ingenuity”
“Strong construction”
“Good value for the money”
“Action”

These are not instructions about alignment or contrast. They are lenses through which decisions are evaluated.

They help answer questions such as:

We’ve had a great idea for a new product but it will be expensive to make, can we justify the cost? (Principle to consider: “Good value for the money”)
We need to cut production costs, what compromises can we make? (Principle to consider: “Strong construction”)

Design principles act as constraints. They shape direction. They reduce ambiguity. They establish a common goal but allow team members to have ownership, flexibility and empowers them to make decisions.

Strategic decisions are about what an end goal is but they need consider the decisions we need make now in order to get there. There are always compromises and trade-offs along the way.

Where the principles of design guide universal composition, design principles guide choices. Design principles are unique to an organisation, team or project.

Do they overlap?

The two are not mutually exclusive.

Visual design principles can inform decision-making principles.

For example:

A team principle such as “Prioritise clarity” may be expressed visually through hierarchy, contrast, and spacing.

In that case, the principles of design become tools used in service of a broader design principle.

The overlap happens in application.
The distinction exists in intent.
One describes how elements relate.
The other describes how teams decide.

Why the distinction matters

Confusion often arises when teams say “we need design principles” but mean different things.

If one person is thinking about visual hierarchy and another is thinking about product strategy, alignment becomes difficult.

Being explicit about which kind of principle you are referring to avoids unnecessary debate.

It also clarifies responsibility:

The principles of design belong to craft and execution.
Design principles belong to direction and judgement.

Both are valuable.

They simply operate at different layers of practice.

Applying principles in practice

The distinction between visual principles and decision-making principles is subtle, but words are important, they shape how we think and how teams work.

I write occasionally about how principles function in real organisations, where they succeed, where they fail, and how they evolve over time.

If that’s useful to you, you can subscribe below.

No spam. Unsubscribe any time.
See our Privacy Policy.