Gumshoe · Method reference

Design principles

A short set of shared values that guide decisions and resolve trade-offs consistently.

Conceptual illustration of design principles.
Effort
Medium
Participants
Not required
Remote friendly
Yes
Evidence / output
Inference

What it is

A concise, memorable set of statements expressing what a team values in its design, used to guide decisions and adjudicate trade-offs when there is no obvious right answer.

When to use it

During Initiate and Synthesize, once the team understands the problem and audience well enough to commit to priorities.

Why (value)

Creates consistency across people and time, speeds decisions, and gives critique an objective reference beyond personal taste.

How to run it

  1. Draw on user needs, brand, and constraints to draft candidate principles.
  2. Make each principle specific and opinionated enough to guide trade-offs.
  3. Test them against real decisions, would they change anything?
  4. Refine to a short, memorable set.
  5. Socialize and apply them in reviews.

Inputs and outputs

  • Inputs: User and business understanding, existing values, real design decisions to test against.
  • Outputs: A small set of actionable, prioritized design principles.

Time and effort

Medium. Drafting is quick; earning adoption takes iteration.

Evidence and limitations

Principles express intent and values, not empirical findings. They guide decisions but do not validate them. See Evidence and limitations.

Tips and pitfalls

  • Avoid generic platitudes (“be simple”) that guide nothing.
  • Make them prioritized so they resolve conflicts.
  • If a principle never rules anything out, it is not useful.

Variations

Prioritized trade-off principles, brand pillars, editorial principles.

Need help choosing and applying a method?

Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.

Discuss your project with Gumshoe Explore Gumshoe services

Sources and further reading

Explore related methods

  • Design briefs — A one-page contract that aligns everyone on goals, scope, constraints, and success before design starts.
  • Design critique — Gather peers to give structured, goal-focused feedback on work in progress.
  • Design system work — Build and maintain the shared components, tokens, and guidelines a product is made from.

A general practice reference. This page does not establish that a method was used on a particular client project or that an outcome was measured.