The Driftify Checklist: 5 Foundational Design Laws for Instant Usability Wins

Every product team has that moment: a feature ships, users struggle, and the feedback thread fills with confusion. The fix often isn't a new feature—it's a forgotten design law. We wrote this checklist for busy product managers, designers, and developers who need practical, repeatable usability wins without a full redesign. These five foundational laws work across web, mobile, and desktop interfaces. Apply them, and you'll catch the most common friction points before they reach users.

1. Why These Five Laws Matter Right Now

User expectations have never been higher. A single confusing interaction can push someone to a competitor. Yet most usability problems trace back to a handful of psychological principles that designers have understood for decades. The five laws we cover here—Fitts's Law, Jakob's Law, the Von Restorff Effect, Miller's Law, and Hick's Law—are not theoretical curiosities. They are practical tools that predict how people perceive, decide, and move through an interface.

Consider a typical dashboard redesign. The team spends weeks on colors and typography, but the primary action button is buried in a dropdown. Users miss it. That's Fitts's Law in action: the time to acquire a target depends on its size and distance. A quick fix—making the button larger and placing it closer to the user's natural cursor position—could have saved days of complaints.

Or take onboarding flows. Many products bombard new users with seven to ten options on the first screen. Overwhelmed, people either click nothing or make a random choice. Hick's Law tells us that decision time increases logarithmically with the number of choices. Reduce visible options to three or four, and users make faster, more confident decisions.

These laws are not just for designers. Product managers can use them to prioritize backlog items: a feature that violates a foundational law is likely to cause disproportionate friction. Developers can spot issues during implementation: if a button is tiny and far from the action area, flag it. QA testers can build a usability checklist around these laws to catch problems before release.

The business case is straightforward. Lower friction means higher task completion rates, fewer support tickets, and better retention. According to multiple industry surveys, improving usability can increase conversion rates by 50% or more. You don't need a massive budget—you need a systematic way to apply these laws.

This checklist gives you that system. Each law comes with a specific check, a common failure mode, and a quick test you can run in minutes. By the end, you'll have a repeatable process to audit any screen, catch the biggest usability leaks, and fix them without waiting for a sprint.

2. Core Ideas in Plain Language

Let's define each law before we talk about implementation. We'll keep it concrete.

Fitts's Law

Fitts's Law states that the time to acquire a target (like a button or link) is a function of the target's size and its distance from the user's starting point. Bigger targets that are closer are faster to click. This is why the most important actions—like "Submit" or "Add to Cart"—should be large and placed near where the user's cursor or thumb naturally rests. On mobile, that means bottom of the screen. On desktop, it means near the center of the active area.

Jakob's Law

Jakob's Law says that users spend most of their time on other websites. So they expect your site to work the same way. If your checkout flow deviates from the norm—like putting the "Pay" button on the left instead of the right—users will hesitate or make errors. This law argues for convention over innovation in core interactions. You can be creative with branding, but the basic navigation and form patterns should match user expectations.

The Von Restorff Effect (Isolation Effect)

Also called the isolation effect, this law states that an item that stands out visually is more likely to be remembered. If you want users to notice a key piece of information—a warning, a discount, a primary action—make it visually distinct. But use this power carefully. If everything is highlighted, nothing stands out. The effect works best when one element differs from its surroundings in color, size, shape, or motion.

Miller's Law

Miller's Law is often summarized as "the magic number seven, plus or minus two." It refers to the average number of items a person can hold in working memory. For interface design, this means you should chunk information into groups of five to nine items. Navigation menus, list items, and options in a dropdown all benefit from this limit. Exceeding it overwhelms users and increases errors.

Hick's Law

Hick's Law states that the time it takes to make a decision increases with the number and complexity of choices. This is why a simple interface with few options feels faster. For critical decisions—like selecting a plan or confirming an action—limit the number of choices to three or four. If you must offer many options, use progressive disclosure: show a few first, then reveal more if needed.

3. How These Laws Work Under the Hood

Understanding the mechanism behind each law helps you apply them correctly, not just follow a checklist blindly.

The Motor and Visual System Behind Fitts's Law

Fitts's Law is rooted in human motor control. When you move a cursor or finger toward a target, your brain plans a ballistic movement and then makes corrective micro-adjustments as you get close. Larger targets require fewer corrections, and closer targets reduce the initial movement distance. This is why corner buttons on screens are so effective: the cursor stops at the edge automatically, effectively giving you an infinite target size. Designers can exploit this by placing critical actions at screen edges or corners.

A common pitfall is making a button large but placing it far from the action area. For example, a "Save" button at the top of a long form forces the user to move the cursor a long distance. A better approach is to put the button at the bottom of the form, near where the user finishes typing. On mobile, thumb zones matter: the bottom third of the screen is easiest to reach one-handed.

Why Jakob's Law Reduces Cognitive Load

Jakob's Law works because of mental models. When users encounter a familiar pattern—like a shopping cart icon in the top right—they don't have to learn a new interaction. Their existing mental model transfers, reducing cognitive load. Violating this law forces users to form a new model, which takes time and often leads to frustration.

The catch is that conventions evolve. What was standard five years ago may now feel dated. The trick is to distinguish between core conventions (like left-to-right form flow in Western cultures) and surface trends (like flat vs. skeuomorphic design). Stick to the core conventions; innovate on the surface.

The Neuroscience of the Von Restorff Effect

The Von Restorff Effect is tied to how our brains process novelty. The reticular activating system (RAS) filters out familiar stimuli and flags unusual ones for attention. A red button among gray buttons triggers a stronger neural response than a gray button among gray buttons. This is why error messages are often red—they need to be noticed quickly.

But overuse leads to habituation. If every other element is highlighted, the brain stops treating any of them as special. Use isolation sparingly. Reserve it for one primary call-to-action per screen, a critical warning, or a key data point.

Miller's Law and Chunking in Working Memory

Miller's Law is about the limits of working memory. When you present more than nine items, users start to forget earlier items as they process later ones. Chunking—grouping related items—helps. A phone number is easier to remember as three chunks (555-123-4567) than as ten individual digits. In UI design, chunk navigation menus into groups of five to seven items, and use submenus for overflow.

Hick's Law and Decision Fatigue

Hick's Law is a function of both the number of choices and their complexity. Each additional choice adds a small amount of decision time. Over many decisions, this accumulates into decision fatigue. For high-stakes choices, reduce options to the minimum necessary. For low-stakes browsing, you can offer more variety, but still keep the total under nine to avoid overwhelming users.

4. Worked Example: Auditing a Checkout Flow

Let's walk through a concrete scenario. Imagine you're auditing a checkout screen for an e-commerce site. The current design has a small "Place Order" button in the top right corner, four payment options displayed as radio buttons, a promo code field, and a summary of items. Users are abandoning at high rates.

Apply the checklist step by step.

Step 1: Check Fitts's Law

The "Place Order" button is small (40x20 pixels) and located in the top right corner, far from where the user's cursor is after filling in the form (at the bottom). Fix: enlarge the button to at least 60x40 pixels and move it to the bottom center of the form, directly below the last input field. Also consider making the button sticky as the user scrolls.

Step 2: Check Jakob's Law

Most checkout flows place the "Place Order" button on the right side of the form, with the total on the left. This design has it on the left. Fix: move the button to the right to match convention. Also, the promo code field is hidden behind a link labeled "Have a coupon?"—a common convention that works. Keep that.

Step 3: Check the Von Restorff Effect

The "Place Order" button is the same color as the background (light gray). It blends in. Fix: make the button a distinct color—typically green or blue—that contrasts with the background. Ensure the button is the most visually prominent element on the screen. The total price should also stand out, but less so than the button.

Step 4: Check Miller's Law

The payment options are four radio buttons—well within the seven-plus-or-minus-two limit. But the summary section lists eight items (product name, quantity, price, subtotal, shipping, tax, discount, total). That's borderline. Fix: group the summary into two chunks: "Items" (product, quantity, price) and "Totals" (subtotal, shipping, tax, discount, total). Use visual grouping (lines or background color) to separate them.

Step 5: Check Hick's Law

The user has to choose among four payment methods and decide whether to enter a promo code. That's five decisions. For a checkout flow, that's acceptable, but we can reduce friction. Fix: pre-select the most common payment method (e.g., credit card) and move the promo code to a secondary step (after order placement). This reduces the visible choices to one primary action (Place Order) and one optional action (change payment).

After applying these fixes, the team sees a 15% increase in checkout completion in A/B testing. The changes took one developer a day to implement.

5. Edge Cases and Exceptions

No design law applies universally. Here are common situations where these rules bend or break.

When Fitts's Law Backfires

Making a button too large can look clumsy or dominate the screen, especially on mobile. Oversized buttons may also trigger accidental clicks. The fix is to balance size with context: use generous padding but keep the button proportional to nearby elements. Also, for touch targets, the minimum recommended size is 44x44 points (Apple HIG) or 48x48 pixels (Material Design). Going larger than 60x60 may cause problems.

When Jakob's Law Leads to Stagnation

If every product follows the same pattern, innovation stalls. Some of the most successful interfaces (like the original iPhone) broke conventions deliberately. The key is to know which conventions to break. Break interaction patterns at your own risk; break visual trends more freely. For example, you can use a non-standard color scheme, but keep the navigation standard.

When the Von Restorff Effect Causes Confusion

If you highlight too many elements, users become overwhelmed and miss the truly important one. A common mistake is to highlight both the primary call-to-action and a promotional banner on the same page. The user's attention splits. The rule: one standout element per screen. If you need multiple highlights, use different methods (e.g., color for the main action, size for a secondary one) and ensure they don't compete.

When Miller's Law Is Misapplied

The "seven plus or minus two" number is often misinterpreted. It applies to working memory for simple items (like digits or words). For complex items (like menu categories), the limit may be lower—around four or five. Also, chunking works best when the chunks are meaningful. Grouping unrelated items into a chunk doesn't help. Test with real users to find the right chunk size for your content.

When Hick's Law Reduces Satisfaction

Reducing choices too aggressively can frustrate users who want variety. For example, a streaming service that shows only three movies may annoy users looking for niche content. The solution is progressive disclosure: show a limited set of curated options first, with an obvious "Show more" link. This respects Hick's Law while preserving depth.

6. Limits of the Checklist Approach

This checklist is a starting point, not a substitute for user testing. Design laws are heuristics—they work most of the time, but they can't predict every user's behavior. For example, Fitts's Law assumes a mouse or finger input; it doesn't account for voice or eye-tracking interfaces. Jakob's Law assumes a homogeneous user base; if your audience is from a different culture (e.g., right-to-left reading), conventions differ.

Another limit: these laws focus on efficiency and learnability, not on emotional design or brand differentiation. A usable interface can still feel cold or generic. Use these laws to remove friction, then layer on personality through copy, imagery, and micro-interactions.

Finally, the checklist is only as good as your implementation. A button that is large but poorly labeled still fails. A navigation that follows conventions but has confusing labels still frustrates. Always combine heuristic checks with usability testing with real users.

To get the most out of this approach, integrate the checklist into your regular workflow. Add it to your design review checklist, your QA test plan, and your product launch criteria. Over time, applying these laws will become second nature, and you'll spot violations without thinking.

Start small: pick one screen this week, run the five checks, and fix the biggest issue. Measure the impact. Then move to the next screen. Over a quarter, these incremental wins compound into a noticeably better user experience—and fewer support tickets.