The Hierarchy Problem: Why Most Designers Optimize for the Wrong Thing First

Visual hierarchy gets a lot of attention. Designers learn it early: the most important thing gets the most size, the most weight, the most contrast. Your eye goes there first. Clear, organized, done.

But that’s not the hard problem.

The hard problem is deciding what’s actually important before any of that work begins. And most designers skip it — or mistake the symptoms for the disease.

The real hierarchy problem

Here’s what I see happen most often: a design review where the feedback is “the CTA isn’t prominent enough” or “users aren’t noticing the key feature.” The instinct is to fix this visually — make the button bigger, change the color, add a badge.

Sometimes that’s right. More often, the visual hierarchy problem is a symptom of a conceptual hierarchy problem. The real question is: has anyone decided what the page is actually trying to do? Because if the underlying priorities are wrong, you can’t save them with typography.

A button that’s too small is usually not a visual problem. It’s a sign that nobody agreed on what should happen on this page.

What “optimizing for the wrong thing first” looks like

Designers who jump straight to visual hierarchy are solving a known problem with a known toolkit. That’s comfortable.

The messier work is sitting with a blank page — or an existing design — and asking: if a user had to leave with one thing, what is it? Not “what did we want them to do.” What will they actually leave with, given everything competing for their attention?

That question forces a decision that a lot of teams never make. They design by accretion — every stakeholder adds their thing, and the page becomes a negotiated settlement between competing priorities. The designer’s job then becomes trying to visually rank things that were never actually ranked.

You can’t design a clear hierarchy out of unclear priorities.

The fix, which isn’t visual

Before touching weights or sizes or contrast, I want three things answered:

What’s the primary action or message? One thing. If there are two, you have a strategy problem, not a design problem.
What does the user need to understand first in order to take that action?
What’s genuinely optional versus what just feels essential to someone who built it?

Running that exercise usually reveals the real problem isn’t “the button isn’t prominent enough.” It’s that the page is trying to do three things and nobody wanted to choose.

Making the button 20% bigger doesn’t fix that. It just decorates the problem.

Visual hierarchy is craft. Information hierarchy is judgment. Most designers are better at the first than the second — the craft is teachable, the judgment is harder to develop.

But the judgment has to come first. Otherwise you’re applying a skilled technique to a problem that hasn’t been defined yet.

The result looks polished and doesn’t work. That’s the hierarchy problem.