Message hierarchy: choosing what leads

Say one thing first and mean it — the rest is support, not a second headline.

The idea

A product has many benefits. A message has one lead. If you try to say five things at once, the reader remembers none of them — attention drops off a cliff after the first line. So you rank the benefits, promote one to the headline, and demote the rest to support copy that earns its place under the lead.

The lead is not the feature the product team is proudest of. It’s the benefit that answers the dominant need of the audience you’re talking to, in this channel, right now. Same product, different reader — different lead.

One product, two audiences · drag to rank

Vaultly · team password manager

—

Start free trial

Where the reader’s attention goes

Message fit for this audience 0%

Pick an audience and rank the benefits. The top card becomes the headline; the rest become support.

How it works

Treat reader attention as a budget that mostly gets spent on the first line. A rough attention curve down a message looks like this — and “message fit” is just how well your ranking spends that attention on the benefits this audience actually cares about.

attention by position:   lead  1.00
                         2nd   0.50
                         3rd   0.30
                         4th   0.15
                         5th   0.05

fit = sum( benefit_value(audience) x attention(position) )
      -------------------------------------------------- x 100
              best possible arrangement

IT buyer values:  Encryption+SSO 9 · Admin+audit 8 · Fewer tickets 7 · Any device 5 · Autofill 4
End user values:  Autofill 9 · Any device 8 · Fewer tickets 5 · Encryption+SSO 3 · Admin+audit 2

Lead with Autofill for the IT buyer and you spend 1.00 attention
on a benefit worth 4 to them.  Lead with Encryption+SSO instead
and you spend it on a 9.  Same product, different lead.

When to use it

Match the lead to…	…and the trade-off to hold
The audience’s dominant need (IT buyer: control & risk; end user: ease).	You may bury a benefit the org loves — that’s the point; it becomes support.
The channel moment (a search ad has one line; a landing page has room to support).	Narrow channels force a harder single choice than a long page does.
The stage (cold ad leads on the hook; a comparison page leads on the differentiator).	The right lead shifts as the reader moves down the funnel.

Watch out for

Two headlines. If your “support” line is as loud as the lead, you have two leads and therefore none. Demote it in size and weight, not just position.
Leading with the team’s favorite feature. Internal pride is not audience need. The thing engineering is proudest of is often the reader’s fourth priority.
One message for every audience. The IT buyer and the end user buy the same product for different reasons. A single lead under-serves at least one of them.
Ranking by feature magnitude, not benefit value. “256-bit encryption” is a big feature; “you’ll never type a password again” is the benefit that leads for a user.
A lead that’s a category, not a claim. “Security” is a topic; “bank-grade encryption and SSO, built in” is a lead. Make the headline say something.

Worked example

An interviewer says: “Here’s our password manager and its five benefits. Write the search ad for IT admins, then the one for employees.” A strong answer ranks before it writes. For the IT admin, the dominant need is control and risk, so the lead is “Bank-grade encryption and SSO, built in”, supported by admin controls and the drop in reset tickets; autofill is a footnote. For the employee, the dominant need is friction, so the same product leads with “Your passwords, filled in with one click — everywhere”, supported by “works on every device.” You’d point out that you didn’t change the product or invent benefits — you re-ranked the same five to the reader in front of you, and let the channel (a one-line search ad) force a single, honest lead.

Check yourself

You’re writing a one-line search ad aimed at IT admins for this password manager. Which benefit should lead?

Engineering insists the ad lead with the feature they spent a year building, even though it’s the audience’s fourth priority. What’s the message-hierarchy answer?