Use Fitts’s Law for targets, and use Steering Law for the path users must travel to reach them. That single distinction can save menus, drawing tools, sliders, maps, dashboards, and complex web apps from feeling slow, fussy, or weirdly hard to control.
TLDR: Fitts’s Law predicts how long it takes to point at a target, while Steering Law predicts how long it takes to move through a constrained path, such as a submenu, tunnel, slider track, or drag route. For example, if analytics show that 38% of users abandon a multilevel menu after opening the first submenu, the problem may not be the menu label at all; the path may be too narrow or too easy to exit by mistake. Wider paths, forgiving hover zones, and shorter pointer travel can cut hesitation by several hundred milliseconds per interaction.
What Steering Law means in UX
Steering Law describes the time needed to move a pointer through a path without touching the sides. Think of guiding your cursor through a narrow corridor. The longer and narrower the corridor, the slower and harder the movement becomes.
In interface design, that “corridor” can be many things:
- A cursor path from a menu item to its submenu.
- A slider track with a small thumb.
- A drag path in a design tool.
- A route through a map or canvas.
- A radial menu slice.
- A scrollable region inside another scrollable region.
Honestly, it feels like some interfaces were designed by people who never had to use a trackpad on a train. A submenu that collapses because the pointer drifted three pixels outside its invisible lane is not “clean.” It is annoying.
What Fitts’s Law means in UX
Fitts’s Law predicts how quickly a person can move to a target. It says that movement time depends on two main factors: distance and target size.
A button that is close and large is easy to hit. A tiny icon tucked in a far corner is slower. This is why strong interface design often uses large tap targets, roomy buttons, and predictable placement.
Classic examples include:
- Primary buttons made large enough to click with confidence.
- Mobile tap targets sized around a finger, not a mouse pointer.
- Screen corners used for frequent actions because the pointer cannot overshoot them.
- Floating action buttons placed near expected thumb zones.
Fitts’s Law is about getting to a target. Steering Law is about staying inside a route. That difference matters more than many teams think.
Steering Law vs Fitts’s Law: the real difference
The simplest comparison is this: Fitts’s Law is about pointing. Steering Law is about guiding.
| UX question | Best law to use | Design focus |
|---|---|---|
| Can users hit this button quickly? | Fitts’s Law | Make the target larger or closer. |
| Can users move through this menu without losing it? | Steering Law | Make the path wider, shorter, or more forgiving. |
| Can users drag an object along a route? | Steering Law | Reduce path constraints and accidental exits. |
| Can users tap the close icon? | Fitts’s Law | Increase the touch area. |
Both laws deal with movement time. Both help reduce friction. But they solve different errors. Fitts’s Law helps prevent missed targets. Steering Law helps prevent broken movement paths.
Why Steering Law is often ignored
Fitts’s Law gets more attention because buttons are visible. You can point to a button and say, “This is too small.” Steering problems are sneakier. They live in the space between objects.
That empty space can ruin an interface.
Picture a desktop ecommerce site. A user hovers over “Products,” then tries to reach “Laptops” in a flyout submenu. If the submenu opens to the right but the cursor path is diagonal, the pointer may pass outside the hover zone. The menu closes. The user tries again. It takes two extra seconds. Small? Maybe. But across 50,000 sessions, that is a lot of wasted time and irritation.
The catch is that users rarely report this clearly. They do not say, “Your steering path violates a motor control model.” They say, “The menu is buggy.” Or worse, they leave.
How Steering Law affects common interface patterns
Dropdown and mega menus are the obvious case. If a submenu requires a tight diagonal movement, users may slip out of bounds. Good menus add buffer zones, delayed closing, or triangular safe areas that match the expected pointer path.
Sliders also rely on steering. A thin slider track may look elegant, but it can be painful for exact input. This is even worse when the handle is small. Users slow down because they are trying not to lose grip.
Drag and drop tools depend on path design too. If users must drag a file across the screen into a small drop zone, Fitts’s Law explains the final target difficulty. Steering Law explains the effort during the trip, especially if the route passes over panels, scroll zones, or auto-opening folders.
Image not found in postmeta
Drawing and editing software may suffer from narrow control paths. Think of resizing a shape by grabbing a tiny handle, then dragging along a precise line. The target is small, yes. But the path is also constrained. That means both laws apply.
Design rules based on Steering Law
Use Steering Law when the user must maintain control across movement. The goal is simple: make the route easier to complete without slips.
- Make paths wider. Larger hover zones and drag regions reduce accidental exits.
- Shorten paths. Place related controls closer together when a user must move between them.
- Add tolerance. Do not close a menu the instant the pointer leaves by one pixel.
- Use delay wisely. A 300 millisecond close delay can save a submenu without making it feel sticky.
- Support diagonal movement. Users rarely move in perfect right angles.
- Avoid fragile hover chains. If three hover states must stay active in sequence, expect errors.
- Make drop zones generous. A large landing area helps users finish long drags.
These choices sound small. They are not. They affect rhythm. A user who can move with confidence feels faster, even if the measured time improves only slightly.
Design rules based on Fitts’s Law
Use Fitts’s Law when the main task is reaching a specific target. The goal is to reduce pointing effort.
- Increase target size. This helps both mouse and touch users.
- Reduce distance. Keep frequent actions near the user’s current focus.
- Use edges and corners. They act like large targets because the pointer stops there.
- Group related actions. Users should not travel across the screen for the next obvious step.
- Respect touch input. Fingers need more room than cursors.
Fitts’s Law is especially useful for buttons, icons, tabs, controls, and toolbar items. If users misclick often, start here.
When both laws apply at the same time
Many interface issues need both models. A small menu item is a Fitts’s Law problem. A narrow route to its submenu is a Steering Law problem. Fix only one and the design may still feel clumsy.
Consider a calendar app. A user drags an event from 9:00 to 11:30. The event block must be easy to grab. That is Fitts’s Law. The vertical drag path must feel stable and forgiving. That is Steering Law. If the grid snaps too aggressively or scrolls too soon, the user loses control.
Image not found in postmeta
This is why usability testing should measure more than clicks. Watch pointer paths. Count abandoned drags. Record submenu closures. Track hover retries. These behaviors show friction that basic click analytics can miss.
A practical way to choose the right law
Ask one question first: Is the user aiming at a target or moving through a route?
If the task is “click Save,” use Fitts’s Law. Make Save visible, close, and large enough. If the task is “move through a menu to pick Export as PDF,” use Steering Law. Make the path stable and forgiving.
For product teams, a quick audit can help:
- List high-frequency actions. Buttons, icons, tabs, menu items, and drag tasks.
- Mark target problems. Tiny controls, distant actions, cramped tap areas.
- Mark path problems. Narrow hover routes, fragile submenus, long drags, tight sliders.
- Fix the worst friction first. Target size and path width often beat visual polish.
- Retest with real input devices. Mouse, trackpad, stylus, and touch can expose different failures.
Good interface design is not only about what users see. It is also about how their hands move. Fitts’s Law gets users to the thing. Steering Law helps them complete the motion without fighting the interface. Use both, and your product will feel calmer, faster, and less brittle.