Uwarp

Design principles for clearer team decisions

Browse principles.design: a free library of real-world design principles, articles, a field guide, and indexed examples to support product and design system decisions.

What is principles.design?

principles.design is a curated, free library focused on design principles: short statements that help teams agree on what matters and how to make trade-offs when building products and services. The site publishes articles, a growing index of real-world examples from many organizations, and a field guide for teams who want principles that hold up in practice. The project is created and maintained by Ben Brignell. This Uwarp page embeds the public site at https://principles.design/ so you can read and compare examples next to your other Uwarp resources.

What you can explore on the site

The library connects narrative guidance with searchable examples you can learn from, not copy blindly.

  1. Read principles in real contexts: Review how different teams name, scope, and explain principles so you can calibrate language for your org.
  2. Use articles for craft and process: Follow posts on when principles help, how many to keep, and how they differ from hard rules.
  3. Follow the field guide for adoption: Use practical guidance to turn principles from slogans into decisions your team can repeat.
  4. Submit examples you respect: The site invites submissions when you know a public set of principles that fits the collection.

How to use this embedded library

Keep research tied to a decision you are trying to ship.

  1. Name the trade-off you face: Principles work when they resolve tension, for example speed versus clarity, or consistency versus local needs.
  2. Find two or three reference sets: Compare how teams in related domains state priorities before you write your first draft list.
  3. Draft a small, testable set: Prefer a handful of memorable principles to a long catalog nobody reads in critique.
  4. Tie each principle to behavior: Add one line on what the team will do or stop doing when a principle applies.

Tips for working principles with your team

Principles should reduce debate, not add posters.

  1. Avoid duplicates with your values doc: If a sentence repeats the company mission, merge or cut it so each line does distinct work.
  2. Review in real reviews: Test principles against upcoming launches and tickets, not only in a workshop slide deck.
  3. Revisit on a schedule: Products shift; a yearly pass keeps language aligned with the roadmap and the real pain points users feel.
  4. Pair with accessible outcomes: State how inclusive and legible experiences show up in decisions the principle is meant to protect.

Who this resource is great 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 a short list 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 research synthesis and voice with what the team agrees to optimize for in tough calls.
  4. Newly formed product squads: Build a first charter faster when you can point to public examples and plain-language models.

Benefits of using this library in your workflow

Embedding the site in Uwarp keeps principles research next to tools you already use.

  1. Faster pattern matching: Scan many teams’ phrasing in one sitting instead of opening dozens of PDFs in separate tabs.
  2. Clearer buy-in for leadership: Show that serious orgs document principles, not that your proposal came from a single opinion.
  3. Support for long-term memory: When someone joins mid-quarter, a stable internal plus this public index shorten onboarding time.
  4. Connection to active writing: Articles on the same domain stay updated; check there when your internal list feels stale.

Technical notes

This page embeds https://principles.design/ and adds workflow context in Uwarp.

  1. Embed source: The iframe loads the public principles.design home experience, including navigation to articles and the example index, subject to that site’s availability.
  2. Third-party frame rules: If the frame is blank, the host may block embedding; open https://principles.design/ in a new tab to continue reading.
  3. Content ownership: Examples, articles, and the field guide are published on principles.design; Uwarp does not edit upstream copy.

Frequently Asked Questions

Have questions? We have answers.