Oct 20, 2026
3 min read
Design Principles Should Settle Arguments, Not Decorate Walls
A principle nobody could disagree with can’t decide anything. How I write design principles a team can actually use in the room.

Introduction
Most design principles I have read could belong to any company.
“Simple.” “Human.” “Delightful.”
Nobody disagrees with them, and that is the problem. A principle nobody could disagree with cannot decide anything. It goes on a slide, the slide goes in a deck, and the next design review is settled by whoever argues longest.
I use one test. A principle earns its place when it settles an argument the team actually had. Here is how I write principles that pass it.
1. Write them as trade-offs
Real decisions are rarely good against bad. They are good against good. Speed against accuracy. Showing everything against showing what matters.
So I write principles as “this over that”, where both sides are worth wanting. “Clarity over density.” “Consequences before confirmations.” If I cannot name what the principle gives up, it is a slogan, not a principle.
2. Mine them from real disagreements
Good principles are not invented in a workshop. They are found in the arguments a team keeps having.
I go back through recent design reviews and write down every debate that took more than one meeting. Then I ask what the winning argument was, in one line. Those lines are the first draft. A principle is a decision the team has already made, written down so it does not have to be made again.
3. Keep fewer than five
A principle only works if someone can recall it mid-review without opening a document. Most people can hold three or four. Past that, the list becomes something people look up, and things people look up do not shape decisions in the room.
If there are more than five, some of them are guidelines. Guidelines are useful too. They just live somewhere else.
4. Give each one a question
A principle should be something you can check a screen against.
On Distributor Packages, one change could reach many clients at once, so every screen followed one rule: show the consequence before the click. As a question, it becomes: “Before they confirm, can the user see what will change, and for whom?” Anyone can ask that of any screen, including people who were not in the room when the rule was written.
That is the real job of a principle. It lets the team make the decision you would have made, when you are not there to make it.
5. Let them lose, and write down why
Principles are defaults, not laws. Sometimes the right call breaks one.
When that happens, I note it next to the decision: which principle we broke, and what was more important this time. Over a few months, those notes tell you something. A principle that is broken once is doing its job. A principle that is broken every week is wrong, and should be rewritten.
6. Retire the ones nobody uses
Once a year, I check which principles were actually quoted in reviews, specs and decisions. A principle nobody cited all year is decoration. It goes.
Retiring one is not a failure. It usually means the product, or the team, has moved on, and the list should move with it.
Why this matters more as you get more senior
Early on, my influence was the screens I drew. Later, most of the decisions that mattered happened in rooms I was not in, made by people working faster than any review cycle.
Principles are how judgement travels to those rooms. Not as rules to obey, but as decisions already made, with the reasons attached. Written well, they are the most scalable design work there is.
Key Takeaway
Write principles as trade-offs, take them from real arguments, keep fewer than five and give each one a question. A good principle lets the team make your decision when you are not in the room.
Be the first to know about every new letter.
Stay ahead in the world of web design with expert insights, industry trends, and practical tips.
No spam, unsubscribe anytime.


