Uwarp

Real-world design principles for product teams

Tool powered by principles.design on principles.design.

Browse digital product design principles, product principles, and org design examples from Airbnb, HubSpot, Mercedes-Benz, and more on principles.design in the browser.

What is principles.design?

principles.design is a free, curated library of design principles from real organizations—plus articles and a field guide by Ben Brignell. Teams searching for digital product design principles, product principles, or organisation design principles use the /examples/ index to compare how companies like Airbnb, HubSpot, and public-sector design systems phrase trade-offs. This site does not author or edit upstream examples.

What principles.design offers

Narrative guidance plus a searchable example index.

  1. Indexed real-world examples: Each organization gets a dedicated route—product, brand, org, or system-level principles with context.
  2. Articles on craft and adoption: Posts cover when principles help, how many to keep, and how they differ from rigid rules.
  3. Field guide for teams: Practical steps to move from slogans to repeatable decisions in critiques and roadmaps.
  4. Submission path for new sets: The site invites public principles you respect when they fit the collection’s scope.
  5. Works beside the design-system tools: After research, continue to /design-systems-repo or /component-gallery for systems and pattern references.

How to use principles.design

Turn browsing into a decision your squad can ship.

  1. Name the trade-off first: Principles resolve tension—speed versus clarity, consistency versus local needs—not generic inspiration.
  2. Open two or three comparable examples: Pick teams in a similar domain or maturity stage from the /examples/ index on principles.design.
  3. Draft a small testable set: Prefer a handful of memorable lines over a long catalog nobody uses in review.
  4. Attach behavior to each line: Add what the team will do or stop doing when a principle applies in a real ticket.
  5. Open principles.design in a new tab if needed: Long articles or blocked iframes are easier to read on the publisher site directly.

Tips for working with design principles

Principles should reduce debate, not add posters.

  1. Do not duplicate your values doc: If a sentence repeats the company mission, merge or cut it so each line does distinct work.
  2. Test in real reviews: Apply principles to upcoming launches and tickets—not only workshop slides.
  3. Revisit on a schedule: Products shift; a yearly pass keeps language aligned with roadmap pain points.
  4. Borrow structure, not copy: Public examples inform phrasing; your principles should reflect your users and constraints.

Who this is for

Anyone who needs shared language before pixels or code take over.

  1. Design system and brand leads: Ground tokens, components, and content rules in principles the whole org can reference.
  2. Product managers and strategists: Frame roadmap choices so UX quality does not get negotiated away by default.
  3. Research and content designers: Align synthesis and voice with what the team agrees to optimize for in tough calls.
  4. New product squads: Build a first charter faster with public product design principles examples.

Why open principles.design

Directory placement without replacing the official library.

  1. Stable directory path: Link `/design-principles` in specs; Hero attribution points to principles.design.
  2. Near other design-system routes: Continue to /component-gallery or /designsystems-com without losing research context.
  3. does not curate examples: Articles and entries update on principles.design; we link to and document honest use.

Frequently Asked Questions

Have questions? We have answers.

Related tools

More tools from Learn & References.

View all Learn & References