Argumenting Design Decisions

That gap between understood and agreed with is where most design work is lost. Clarity gets your idea across the table intact. It doesn't get you the budget, the two sprints, or the engineer.

Closing the gap means moving people who don't think the way you do. They weigh your design in revenue, risk, headcount and roadmap space, and they aren't being difficult by doing that, since it's what their own job is measured on. Persuasion breaks into parts you can name and assemble, the same way a layout does.

Anatomy of an Argument

You say the checkout button should be bigger. The stakeholder asks why. You say it's only 32px. They say "and?" and the room goes quiet.

Nothing you said was wrong. The number is right, the recommendation is right, and the argument still stalled, because you gave two of its parts and left out the one that connects them. The stakeholder heard a fact and a demand with nothing joining them, so they had no way to agree.

The philosopher Stephen Toulmin worked out why arguments do that in The Uses of Argument in 1958. He broke any argument into six parts and showed that the persuasive ones make a specific part explicit.

The Six Parts

Here they are with a single design argument running through all of them.

• Claim: what you want accepted. "The primary checkout button should be at least 44pt tall."
• Grounds: the facts you're standing on. "It's 32px today, and mobile checkout completes 6 points below desktop."
• Warrant: the principle that turns those grounds into that claim. "Targets under the platform minimum get mis-tapped more often, and a mis-tap on the last step is an abandoned order."
• Backing: support for the warrant itself, when somebody questions it. "Fitts's Law predicts it, and Apple asks for 44pt while Material asks for 48dp."
• Qualifier: how strongly the claim holds. "For the primary action on mobile."
• Rebuttal: the conditions where the claim doesn't hold. "Unless the button stands alone with nothing adjacent to mis-tap."

Read those six in order and the argument is hard to refuse. Read the claim and grounds alone and you get the exchange the stakeholder walked away from.

The Warrant Is the Part Designers Skip

The warrant is the sentence you never say because you already believe it. You've internalized that small targets get missed, so "it's 32px" feels like it obviously implies "make it bigger". To somebody who has never read a usability study, 32px is just a number.

That's why the missing warrant is more damaging than a missing figure. A stakeholder without your warrant doesn't experience your grounds as evidence at all, so adding more grounds makes it worse. You end up quoting three more numbers into a silence.

So say the warrant out loud, every time, in one sentence. It's the cheapest fix in this entire module, and it converts a fact into a reason.

Qualifier and Rebuttal, the Two That Build Trust

The last two parts feel like weakening your case and do the opposite. A claim with no qualifier invites somebody to find the edge case where it breaks, and once they do, the whole argument goes with it.

Naming the qualifier yourself keeps the argument inside the ground you can defend. "For the primary action on mobile" means nobody can beat you with a desktop tooltip. Naming the rebuttal shows you already looked for the counter-case, which is what separates a recommendation from a preference.

Watch what happens in the room when you supply both. The stakeholder who was going to test your claim finds it already tested, and the conversation moves to the decision rather than to whether you did your homework.

Where Each Part Goes in a Real Review

You rarely get to lay out all six in order. The parts still have natural homes.

• The claim opens, in the first sentence, before any setup.
• The warrant follows immediately, because it's what makes the next part land.
• The grounds come third, and they're now heard as evidence rather than trivia.
• The backing waits until somebody challenges the warrant. Leading with Fitts's Law makes you sound like you're quoting scripture.
• The qualifier attaches to the claim as a clause, not a separate sentence.
• The rebuttal comes last, offered rather than extracted.

Because the backing sits in reserve, you can hold a two-sentence version for a Slack thread and a full version for the meeting. "The checkout button needs to hit 44pt, because targets under the platform minimum get mis-tapped and a mis-tap there is a lost order. It's at 32px now."

Pro tip: Before your next review, write your argument out as all six parts on one line each. It takes four minutes. The part you struggle to write is the part the room was going to attack.