The Complete Guide to UX Laws: 33 Principles, Their Real History, and How to Use Them

Every app you love, every website that just feels easy, did you ever think about why? It feels simple, it feels smooth, you just move through it. That is not luck. That is not even the designer’s taste. It is the way your brain works, and a set of rules that quietly follow it.

We call them UX laws.

Now here is the funny part. Most people who talk about UX laws have no idea where they came from. They copy a one line definition from another blog, paste a random example, and move on. No story. No history. Nothing real to understand. So the reader learns the name, but not the meaning. And a name without meaning is useless in a real project.

I wanted to fix that.

So this is the full guide. 33 UX laws, and for each one, the real story. Who found it. When. How they found it. Some of these are almost 100 years old. Some came from a lab, some from a jam shop, some from a guy watching waiters in a cafe. The innovation is the oldest, but the usage is future friendly. That is the beauty of it.

A quick heads up: this is a 34-part series

Quick heads up before we start. This post is Part 1 of a 34 part series. Think of this one as the full map. After this, every single law gets its own deep dive, one blog each, 33 more coming. That is 34 in total. Full origin story, usability, pros and cons, real examples, all of it.

So you don’t miss them, subscribe below and I will send you each new law the day it goes live.

What is a UX law, really?

Let’s be clear first. A UX law is not a law like a traffic law. Nobody will fine you for breaking one. It is a pattern. A pattern of human behavior that keeps showing up, again and again, no matter the product, the country, or the year.

And here is the part most designers don’t know. Most of these did not start in design at all. They came from psychology, from economics, from the early days of computers. Smart designers just noticed something. The way a person’s mind works while reading a menu is the same way it works while reading your website. Same brain. So they borrowed the science and pointed it at the screen.

That is the honest truth about our field. We did not invent most of this. We adopted it. And to be fair, that is our strength, not our shame.

Do UX laws kill your creativity?

This is the biggest myth, and I want to kill it early.

A lot of designers think laws make your work boring. Follow the rules, lose your style, right? Wrong. It is the opposite.

Think about driving. The road rules don’t decide where you go, and they don’t pick your car. You still choose the destination, you still choose the ride. The rules just stop you from crashing. Same thing here. UX laws handle the boring, predictable part of how people behave, so your creative energy is free for the part that actually needs you. The story, the visual, the feeling, the moment of delight.

It is like I always say about design systems, same road, but different vehicles. The law is the road. Your creativity is still the vehicle.

“Good design is actually a lot harder to notice than poor design, in part because good designs fit our needs so well that the design is invisible.” – Don Norman, The Design of Everyday Things

That invisible fit? That is these laws, working quietly in the background. So nobody claps for them, but everybody feels them. Now let’s meet all of them.

How this guide is organized

33 laws is a lot, I know. So I grouped them by what part of the human mind they touch. Five groups. Read them top to bottom, or jump to the one you need right now.

1. Memory and attention
2. Decision making
3. Perception and Gestalt
4. Interaction and motor
5. Experience and psychology

---

Part 1: Memory and attention

Here is a hard truth. Your user has a small memory and a short attention, and they are not going to fix that for you. So these laws are about respecting it, not fighting it.

Miller’s Law

Definition: People can only hold a small number of items in their working memory at once.

The story: In 1956, a Harvard psychologist named George A. Miller published a paper with a fun title, “The Magical Number Seven, Plus or Minus Two.” He noticed that across many different tests, people could juggle around seven things in their head before they started dropping them. The paper became one of the most famous in all of psychology.

But here is the part almost every design blog gets wrong. Miller was half joking about the number seven. He never said “put seven items in a menu.” Later research by Nelson Cowan in 2001 showed the real limit is closer to four chunks, not seven. So if someone tells you a navigation bar must have seven links because of Miller’s Law, they are using it wrong.

In UX: Think about how a phone number is written, 0171 avoids one long string, it breaks into small groups. Your brain handles the small groups easily.

How to apply: Don’t dump everything at once. Group content into small, meaningful chunks. And please, never use “the magic number 7” as an excuse for a lazy layout.

Working Memory

Definition: The short term mental workspace where we hold and use information for the task right in front of us.

The story: For a long time, people thought short term memory was just one small box. Then in 1974, two British psychologists, Alan Baddeley and Graham Hitch, showed it was more like a workshop with different stations, one for sound, one for images, and a manager keeping it all in order. This is a different idea from Miller’s number. Miller counted the items. Baddeley and Hitch explained the room they sit in.

In UX: A good checkout keeps your cart total visible on every step. Why? Because you should not have to remember the number in your head while you type your card details.

How to apply: Never make a user carry information from one screen to the next in their memory. Show it. A summary, a running total, a filled in field. Take the load off their brain and put it on the screen.

Cognitive Load

Definition: The total amount of mental effort a person is using at one moment.

The story: This one comes from a classroom, not a design studio. In 1988, an Australian educational psychologist named John Sweller built Cognitive Load Theory while studying how students learn. He split the effort into three types. The load from the task itself, the load from bad presentation, and the good load of actually learning. Designers mostly fight the middle one, the wasted effort from clutter and confusion.

In UX: Look at the Google homepage. One logo, one search box. Now think of a busy news portal with a hundred links fighting for your eye. Same job, opening a page. Very different mental cost.

How to apply: Cut the extra. Every needless button, every bit of jargon, every busy background is stealing brain power your user needed for the real task.

Chunking

Definition: Breaking a big block of information into smaller, meaningful groups.

The story: The word “chunk” in this sense came from that same 1956 Miller paper. He noticed the brain does not store raw data, it packs things into units. The letters F B I are three items. But as “FBI” they become one chunk. Same information, less load.

In UX: A card number field split into four groups of four. A long form broken into three short steps. That is chunking in action.

How to apply: Wherever you have a long string, a long form, or a wall of text, break it into groups. Small groups feel easy. Big blocks feel like homework.

Selective Attention

Definition: We consciously notice only a small slice of everything around us, and filter out the rest.

The story: This is not one person’s discovery, it grew over time. In 1953, Colin Cherry studied the “cocktail party effect,” how you can focus on one voice in a noisy room. Then in 1999, Daniel Simons and Christopher Chabris ran the famous “invisible gorilla” test, where people counting basketball passes completely missed a person in a gorilla suit walking through the scene. Your attention is a spotlight. Whatever it is not pointing at, you basically don’t see.

In UX: This explains “banner blindness.” Users have learned to ignore anything that looks like an ad. So if you style your important message like a banner ad, people will scroll right past it.

How to apply: Don’t make your key information look like the stuff people are trained to ignore. And don’t crowd the screen with fake urgency, because the spotlight can only be in one place.

Serial Position Effect

Definition: People remember the first and last items in a list best, and forget the middle.

The story: The credit here goes to Hermann Ebbinghaus, a German psychologist who, in the 1880s, ran memory experiments on himself using lists of nonsense syllables. He found two effects, primacy for the start and recency for the end. The middle just fades. Note the date, this is one of the oldest laws on the list, and it still runs your navigation bar today.

In UX: Look at almost any nav bar. “Home” sits first. The cart or profile sits last. The most important actions land where memory is strongest.

How to apply: Put your most important items at the start and the end of any list or menu. Treat the middle as the weak spot.

Von Restorff Effect

Definition: When many things are similar, the one that stands out is the one people remember. Also called the Isolation Effect.

The story: Named after Hedwig von Restorff, a German psychiatrist and pediatrician who published the finding in 1933. She showed that in a list of similar items, an odd one out gets remembered far more. A woman scientist, in 1933, gave us the reason your “Most Popular” pricing box works.

In UX: A pricing page with three plans, and one of them highlighted with a colored border and a “Recommended” tag. Your eye goes straight to it. That is her effect at work.

How to apply: Make your single most important element visually different. But only one. If you highlight five things, nothing stands out, and the effect dies.

---

Part 2: Decision making

Every screen you design is asking the user to decide something. Click this, pick that, buy now or leave. So these laws are about how people actually make those choices, not how we wish they did.

Hick’s Law

Definition: The more choices you give someone, the longer they take to decide.

The story: In 1952, two psychologists, William Edmund Hick and Ray Hyman, measured this precisely. They found decision time grows in a logarithmic way as options increase, and they even wrote it as a formula. It became one of the most quoted laws in interface design.

But be careful. The law was measured with simple, random choices. It does not mean “always fewer options.” A well organized menu with clear categories can beat a short messy one. So the real lesson is not “cut everything,” it is “organize.”

In UX: A TV remote with 40 buttons freezes you for a second. A remote with five clear buttons does not. Same for a checkout with too many payment options.

How to apply: Reduce and group choices, especially at decision points like sign up and checkout. But structure beats brute cutting.

Choice Overload

Definition: Too many options can cause anxiety and make people choose nothing at all. Also known as the Paradox of Choice.

The story: In 2000, researchers Sheena Iyengar and Mark Lepper ran a now famous study in a grocery store. One day they offered 24 kinds of jam to taste, another day just six. The big display drew more people, but far more people actually bought from the small one. In 2004, psychologist Barry Schwartz turned this into a popular book, The Paradox of Choice.

Honest note. The jam study is famous, but later studies got mixed results. So treat this as a strong tendency, not an iron rule.

In UX: The endless scroll of a streaming app, where you spend 20 minutes picking and watch nothing. That is choice overload.

How to apply: Curate. Offer smart defaults and “recommended” picks. Help the user not have to weigh everything.

Pareto Principle

Definition: Roughly 80 percent of results come from about 20 percent of causes. The 80/20 rule.

The story: This started with an Italian economist, Vilfredo Pareto, around 1896. He noticed 80 percent of the land in Italy was owned by 20 percent of the people. Later, a quality expert named Joseph Juran named it after him and showed the pattern was everywhere.

In UX: In most products, a small set of features drives most of the usage. A few pages get most of the traffic. Find that small 20 percent that carries the weight.

How to apply: Put your best effort into the small part that carries the most weight. Don’t polish a feature nobody uses while the main flow stays broken.

Parkinson’s Law

Definition: Work expands to fill the time available for it.

The story: In 1955, a British naval historian named Cyril Northcote Parkinson wrote a half joking essay in The Economist. His line, work expands so as to fill the time available for its completion, was about office bureaucracy. But it turned out to be deeply true about human behavior.

In UX: Give a user a long, slow form and they will treat the task as big and heavy. Give them a fast autofill and a short checkout, and the same task feels small. Time shapes effort.

How to apply: Set tight constraints. Use autofill, smart defaults, and short steps so tasks finish faster than the user expected. Fast feels good.

Occam’s Razor

Definition: When you have many solutions, the simplest one, with the fewest assumptions, is usually best.

The story: This is the oldest idea on the whole list. It comes from a 14th century English friar and philosopher, William of Ockham. His principle was about logic and reasoning, cut away the unneeded assumptions. Seven hundred years later, we point it at interfaces.

In UX: Apple’s design is a long lesson in Occam’s Razor. Remove a step, remove a button, remove a screen, until you can’t remove any more without breaking the job.

How to apply: For every element, ask “does the design break if I remove this?” If not, remove it. But do not confuse simple with too little. The goal is fewest parts that still work.

Cognitive Bias

Definition: The mind takes mental shortcuts, and those shortcuts cause predictable errors in judgment.

The story: This whole field was built by two psychologists, Amos Tversky and Daniel Kahneman, starting around 1972. They showed that human decisions are not cold and rational, they bend in patterns. Anchoring, loss aversion, and dozens more. Kahneman later won a Nobel Prize for this work.

In UX: A crossed out “original” price next to a lower one. Your mind anchors on the high number, so the low one feels like a deal. That is anchoring bias.

How to apply: Understand biases so you design with honesty, not tricks. Use them to reduce friction, not to fool people. Dark patterns win once and lose the customer forever.

---

Part 3: Perception and Gestalt

How does the eye decide what belongs together? A group of German psychologists answered this a hundred years ago. Their school was called Gestalt, a German word meaning “shape” or “whole.” Max Wertheimer, Kurt Koffka, and Wolfgang Kohler founded it in the 1910s and 1920s. These next laws all come from that work.

Law of Proximity

Definition: Things placed close together are seen as a group.

The story: A core Gestalt principle from the 1920s. The brain reads distance as relationship. Close means related, far means separate. No lines needed, just space.

In UX: A form label sitting right above its input feels connected. Push it far away and users get confused about which label belongs to which field.

How to apply: Use spacing to group related things. White space is not empty, it is doing real work.

Law of Similarity

Definition: Elements that look alike are seen as related, even when they are far apart.

The story: Another founding Gestalt law. Same color, same shape, same size, the brain files them together automatically.

In UX: Every link on your page in the same blue with the same underline. The user learns “this look means clickable” and trusts it everywhere.

How to apply: Keep the same function looking the same. Consistency is not just tidy, it teaches the user your language.

Law of Common Region

Definition: Elements inside the same boundary are seen as one group.

The story: Rooted in Gestalt, and formalized later by psychologist Stephen Palmer in 1992. Draw a border or a shared background around some items, and instantly they feel like a set.

In UX: A card. That simple box that holds a title, an image, and a button. The border tells your eye “these belong together.”

How to apply: Use cards, containers, and background blocks to bundle related content. It is the cleanest way to organize without adding clutter.

Law of Pragnanz

Definition: The eye prefers the simplest, cleanest interpretation of what it sees. Also called the Law of Good Figure.

The story: This is the central Gestalt law, and its name is German for “conciseness.” The idea, the mind will always resolve a messy image into the simplest possible shape, because simple takes less effort.

In UX: The FedEx logo. Most people never notice the arrow hiding between the E and the x, but their brain reads the clean shapes instantly. Simple forms just click.

How to apply: Favor clean, simple shapes and icons. If the eye has to work to decode it, you are spending your user’s energy for nothing.

Law of Uniform Connectedness

Definition: Elements connected by a line, a color, or a frame feel more related than elements that are just near each other.

The story: From the Gestalt tradition, sharpened by Stephen Palmer and Irvin Rock in 1994. They showed connection is the strongest grouping cue of all, even stronger than proximity or similarity.

In UX: A progress stepper where the steps are joined by a line. The line says “these are one journey, in this order.”

How to apply: When things truly belong to one flow, connect them visually. It is the most powerful way to say “these go together.”

Law of Closure

Definition: When a shape is incomplete, the mind fills the gaps to see a whole.

The story: A classic Gestalt principle. The brain hates loose ends, so it completes the picture on its own. You see a full circle even when only part of the line is drawn.

In UX: The WWF panda. The IBM logo made of stripes. Both are incomplete, and your brain finishes them. That gap is what makes them feel clever and memorable.

How to apply: You don’t have to draw every outline. Trust the user’s mind to complete simple shapes. It makes design lighter and more elegant.

Figure/Ground

Definition: The eye separates a scene into a main object, the figure, and everything behind it, the ground.

The story: This came from a Danish psychologist, Edgar Rubin, in 1915, with his famous “Rubin’s vase,” the image you can see as either a vase or two faces. It showed the brain is always deciding what is in front and what is behind.

In UX: A modal dialog with a dimmed, blurred background. The dim tells your eye “this box is the figure, ignore the rest for now.”

How to apply: Use contrast, depth, blur, and shadow to make clear what is active and what is background. Never leave the eye unsure where to look.

---

Part 4: Interaction and motor

Now we move from the mind to the body. How the hand moves, how the thumb reaches, how fast the machine answers back. Design is not just what people think, it is what they physically do. So these laws live in the muscle, not just the head.

Fitts’s Law

Definition: The time to reach a target depends on how far away it is and how big it is. Bigger and closer is faster.

The story: In 1954, an American psychologist named Paul Fitts published this while studying the human motor system. He was not thinking about screens, computers barely existed. He was measuring how people move toward targets. Decades later it became one of the most important laws in interface design. Small detail people get wrong, it is “Fitts’s Law,” with two s’s, and the year is 1954.

In UX: The Mac menu bar sits at the very top edge of the screen. Why is that smart? Because your mouse can’t overshoot the edge, so the target is basically infinite in size, and easy to hit. Same reason mobile buttons need to be big enough for a thumb.

How to apply: Make important buttons large, and place them close to where the user already is. Use screen edges and corners, they are the easiest targets of all.

Doherty Threshold

Definition: When a system responds in under about 400 milliseconds, people work faster and stay engaged, because the machine keeps pace with the mind.

The story: This one comes from IBM. In 1982, Walter Doherty and Arvind Thadani found that when computer response time dropped below 400 milliseconds, productivity did not just improve a little, it jumped. The person and the machine fell into a rhythm together. Note the real names, not Nielsen, a common mix up.

In UX: Search that shows results as you type. An app that responds to your tap instantly instead of freezing. That speed keeps you in flow.

How to apply: Aim for responses under 400ms. When you can’t be that fast, use skeleton screens and progress feedback so the wait feels shorter than it is.

Steering Law

Definition: The time to move through a narrow path depends on how long and how narrow the path is. Long and thin is hard.

The story: In 1997, two HCI researchers, Johnny Accot and Shumin Zhai, published a paper called “Beyond Fitts’ Law.” Fitts’s Law was about hitting a target. Steering Law is about moving through a tunnel to get there, like dragging your cursor down a thin submenu without slipping out.

In UX: Those old cascading menus, where you had to keep your mouse inside a thin strip while sliding across to the submenu, and one wrong move closed the whole thing. Pure Steering Law pain.

How to apply: Avoid long, thin paths. Widen your menus, use click to open instead of hover tunnels, or switch to a mega menu.

Flow

Definition: The state of full focus and enjoyment where you lose track of time, when challenge and skill are balanced.

The story: A Hungarian American psychologist, Mihaly Csikszentmihalyi, named this in 1975 after studying artists and athletes who got completely lost in their work. He found flow happens in the sweet spot, hard enough to hold attention, easy enough not to frustrate.

In UX: A game tutorial that grows in difficulty just as your skill grows. Duolingo streaks that keep you in a steady rhythm. Good pacing creates flow.

How to apply: Match difficulty to the user’s skill. Remove interruptions and friction so people can stay in the zone.

Goal-Gradient Effect

Definition: The closer people get to a goal, the harder they push to reach it.

The story: This began in 1932 with an American psychologist, Clark Hull, who watched rats run faster as they neared food. Much later, in 2006, researchers Ran Kivetz and colleagues proved the same thing in humans with loyalty cards. People buy more, faster, as the reward gets close.

In UX: A loyalty card that starts with two stamps already filled, so you feel closer to the reward. An onboarding bar that says “80 percent complete.” That nearness pulls you forward.

How to apply: Show progress clearly, and when you can, give a head start. People finish what feels almost done.

---

Part 5: Experience and psychology

Last group, and to me the most human one. This is about feeling and memory. Not what your product does, but how it feels to use, and what people remember after they close the tab. Because that memory is what brings them back, or not.

Aesthetic-Usability Effect

Definition: People believe attractive designs are easier to use, even when they are not.

The story: This is one many blogs get wrong, so listen close. It was not Don Norman. In 1995, two researchers at Hitachi in Japan, Masaaki Kurosu and Kaori Kashimura, tested 26 versions of an ATM screen with 252 people. They found that how pretty a screen looked shaped how easy people thought it was to use, more than how easy it actually was. Don Norman later made the idea popular in his book Emotional Design, but the discovery was theirs.

In UX: A beautiful finance app can feel simpler than a plain one, even if they do the exact same thing. Beauty buys trust.

How to apply: Invest in visual polish, it is not just decoration, it earns goodwill. But be careful in user testing, because good looks can hide real usability problems.

Peak-End Rule

Definition: People judge an experience mostly by two moments, its most intense point and its ending, not the average of the whole thing.

The story: This comes from Daniel Kahneman and his colleagues in the early 1990s, through some intense studies on how people remember pain. They found memory is not an average, it is dominated by the peak and the end. Kahneman put it beautifully.

“We do not choose between experiences, we choose between memories of experiences.” – Daniel Kahneman

In UX: The little celebration screen after you finish a task. Mailchimp’s famous high five after you hit send. That strong ending is what you carry away.

How to apply: Design a clear high point and a satisfying ending into your key flows. A great finish covers a lot of small bumps in the middle.

Zeigarnik Effect

Definition: People remember unfinished tasks better than finished ones.

The story: This has one of the best origin stories. In the 1920s, a Soviet psychologist named Bluma Zeigarnik was sitting in a busy Vienna cafe. She noticed the waiters could remember complex unpaid orders perfectly, but forgot them the moment the bill was paid. She took it to the lab and proved it in 1927. An open task stays alive in the mind. A closed one is released.

In UX: The “your profile is 70 percent complete” bar on LinkedIn. That open loop nags at you until you finish it.

How to apply: Use progress bars and checklists to create small open loops. People come back to close them.

Paradox of the Active User

Definition: Users never read the manual. They start clicking right away, so they often never learn the faster way.

The story: Two IBM researchers, John Carroll and Mary Beth Rosson, described this in 1987. People are so eager to get started that they skip all the instructions, even when reading would save them time later. It is not laziness, it is human nature.

In UX: Nobody reads your onboarding tooltips. They tap “skip” and dive in. So your help has to live inside the interface, right where the action is.

How to apply: Make the interface teach itself as people use it. Don’t hide the important stuff in a manual nobody opens.

Jakob’s Law

Definition: Users spend most of their time on other websites. So they expect yours to work like the ones they already know.

The story: This one is named after Jakob Nielsen, co founder of the Nielsen Norman Group and one of the biggest names in usability. He stated it around 2000. His point was simple and a little humbling for designers. Your users built their habits on thousands of other sites, not yours.

“Users spend most of their time on other sites. This means that users prefer your site to work the same way as all the other sites they already know.” – Jakob Nielsen

In UX: The shopping cart icon lives at the top right. The logo takes you home. You did not invent these, and you should not fight them.

How to apply: Meet the convention first. Be familiar where it counts, and save your creativity for the parts that actually make you different.

Tesler’s Law

Definition: Every process has a certain amount of complexity that cannot be removed, only moved. Also called the Conservation of Complexity.

The story: Named after Larry Tesler, a computer scientist who worked at Xerox PARC and Apple in the 1980s. He argued that complexity never truly disappears. The only question is who deals with it, the user or the product. Good design takes that weight onto itself.

In UX: An email field that quietly accepts names, spaces, and messy formats, and cleans them up for you. The product ate the complexity so you did not have to.

How to apply: Find the complexity that cannot be removed, and make sure your product carries it, not your user.

Postel’s Law

Definition: Be generous in what you accept, and careful in what you send. Also called the Robustness Principle.

The story: This came from the world of computer networks. In 1980, an American computer scientist named Jon Postel wrote it while defining how the early internet should talk to itself. It shaped how machines communicate, and it turns out to be great advice for forms too.

In UX: A phone number field that accepts spaces, dashes, brackets, any way you type it, and quietly formats it correctly. The user should never be punished for small formatting choices.

How to apply: Accept messy, human input without complaint. Do the cleanup behind the scenes. Forgiving forms feel kind.

Weber’s Law

Definition: The smallest change a person can notice is proportional to how big the thing already is.

The story: This is old, and it comes from science, not design. Around 1834, a German doctor named Ernst Weber studied how people sense differences in weight and light. He found we don’t notice fixed amounts, we notice ratios. Gustav Fechner later built it into the field of psychophysics.

In UX: Small, gradual changes to a layout or a price often go unnoticed, while a big sudden jump feels jarring. This is why smart redesigns roll out in small steps.

How to apply: Make changes proportional. Small tweaks can ship quietly. Big leaps need warning and care, or users feel the shock.

---

Why this matters for your business

If you run a product or a company, this is not just design theory. This is money.

Here is the simple version. Every one of these laws is really about one thing, reducing friction and matching how people already think. Why does that matter so much? Because less friction means more people finish what they started. And more finishing means more sign ups, more sales, more people who stay. That is the whole game.

I have seen this with my own eyes. On the website revamps I have worked on, respecting how users actually behave, backed by real behavior data from tools like Microsoft Clarity, has driven around a 35 percent average lift in conversion. Not from a magic trick. Just from removing the small pains these laws warn you about, one by one. These issues look very minor, but they take a massive effect on your numbers.

Where you are losing people

So think about where you are losing people. A checkout with too many choices, that is Hick’s Law and Choice Overload leaking money. A slow, laggy interface, that is the Doherty Threshold. Or a form that rejects a phone number because of a space, that is Postel’s Law being ignored. A beautiful competitor who feels easier than you, that is the Aesthetic-Usability Effect. Each of these is a real leak, and each one has a fix that is almost 100 years old.

Good design is not decoration. It sticks to your business like glue. When you design with these laws, you are not following rules for fun. You are removing the reasons people leave.

“Good design is as little design as possible.” – Dieter Rams

Frequently asked questions

What are the laws of UX?

The laws of UX are a set of principles, mostly borrowed from psychology, economics, and early computer science, that describe how people think and behave when they use an interface. They are not strict rules with penalties. They are reliable patterns, like Hick’s Law on choices or Fitts’s Law on targets, that help designers make products that feel natural.

How many UX laws are there?

There is no official number. The popular collection at lawsofux.com lists around 30. In this guide I cover 33, including a few that most lists leave out, like Working Memory, Steering Law, Figure/Ground, and Weber’s Law. The point is not the count, it is understanding the human behavior behind each one.

Who created the laws of UX?

No single person created them. They come from many fields and many decades, from George Miller in 1956 to the Gestalt psychologists in the 1920s to Paul Fitts in 1954. The designer Jon Yablonski is the one who gathered many of them into the well known “Laws of UX” collection and book, but he compiled them, he did not invent them.

What is the difference between UX laws and design principles?

UX laws describe how the human mind works, they come from research on behavior. Design principles are guidelines a team chooses for how they want to design, like “clarity first” or “consistency.” Laws are about people. Principles are about your own choices. Good design uses both.

Get every law as it drops

That was the map. Now the real journey starts.

This is Part 1 of 34. Next up, each law gets its own full post, the complete origin story, where it works, where it breaks, and real examples you can copy into your own product. Fitts’s Law is first.

If you build products or you design them, this series is the shortcut to understanding how people actually think. So don’t chase down each post later. Let them come to you.

One last thing

Learn the story behind each law, not just the name. Because when you understand why a rule exists, you know exactly when to follow it, and when to break it on purpose.

That is the difference between a designer who copies patterns and a real world designer who knows what the user actually needs.

Now go build something people find easy.