Fitts's Law
/fɪtsɪz lɔː/ · noun
A predictive model stating that the time to reach a target is a function of the target's size and distance from the starting point.
Fitts’s Law is one of the few genuinely predictive models in interaction design. Formulated by psychologist Paul Fitts in 1954, it states that the time required to move to a target area is a logarithmic function of the distance to the target divided by the width of the target. In plain language: bigger, closer targets are faster and easier to hit. Smaller, farther targets take longer and invite more errors. The relationship is mathematically precise, which is rare in a discipline that often relies on heuristics and intuition.
The law originally described physical pointing tasks — reaching for a light switch or pressing a button on a control panel — but it maps remarkably well to digital interfaces. Every time a user moves a cursor toward a button, taps a link on a phone screen, or reaches for a navigation element, Fitts’s Law is quietly governing the effort involved. It explains why edge-anchored menus (like the macOS menu bar) are faster to access than floating menus: the screen edge acts as an infinitely wide target, effectively reducing the precision required to zero in one dimension.
Understanding Fitts’s Law helps designers make informed trade-offs about layout, sizing, and spacing. It does not replace usability testing or good judgement, but it gives you a reliable framework for predicting whether a given arrangement of interactive elements will feel effortless or frustrating. When you pair it with an understanding of cognitive load and visual hierarchy, you start making decisions that are grounded in how human motor and perceptual systems actually work rather than how you assume they work.
Why it matters
Fitts’s Law matters because it turns subjective complaints like “that button feels hard to click” into measurable, defensible design decisions. When a stakeholder asks why you made a call-to-action button larger or moved a destructive action away from a save button, you can point to a well-established model of human motor behaviour rather than relying on personal preference. This is especially valuable in organisations where design decisions are frequently challenged and designers need to justify their choices with evidence.
On a practical level, ignoring Fitts’s Law leads to interfaces that punish users with unnecessary effort. Tiny tap targets on mobile, critical actions tucked into far corners, or closely packed buttons for opposing actions (delete next to save) all create friction that accumulates over time. Respecting the law does not mean making everything enormous — it means being deliberate about where you invest screen real estate and ensuring that the most important or frequent actions are the easiest to reach.
In practice
-
Sizing primary actions on mobile. A team noticed that their mobile app’s main call-to-action had a tap target of just 32 pixels — well below recommended minimums. Fitts’s Law predicted what analytics confirmed: the button had a high miss rate. Increasing the target to 48 pixels and adding generous padding reduced erroneous taps by 40%, improving both task completion rates and user satisfaction.
-
Positioning destructive actions deliberately. In a file management interface, the “Delete” button sat directly beside “Rename,” both at the same size and proximity. Applying Fitts’s Law thinking, the team moved “Delete” into a secondary menu and made “Rename” the more prominent affordance. Accidental deletions dropped sharply without adding meaningful friction to intentional ones.
-
Optimising toolbar layouts. A design tools company analysed click heatmaps and found that the most-used tools were scattered across a wide toolbar. By clustering frequently used tools closer together and increasing their hit areas — while pushing rarely used options to overflow menus — they reduced average tool-switch time measurably, a microinteraction improvement that compounded across thousands of daily actions.
Related Terms
Affordance
A property of an object or interface that suggests how it should be used.
Cognitive Load
The total amount of mental effort required to use an interface or process information.
Microinteraction
A small, contained moment of interaction — like a toggle, a swipe, or a loading animation — that serves a single task.
Hierarchy
The arrangement of elements to signal their relative importance and guide the viewer's attention.