Marcus Andrey Study
Ler em português Library

Framework · Influence & change · 3 min read

Articulating design decisions

A four-step way to answer stakeholder feedback (listen, restate, respond, agree) that frames each design decision in the stakeholder's terms instead of yours.

  1. 1Listen

    Hear the whole concern. Ask "why" to find the need behind it.

    "What problem would that solve?"
  2. 2Restate

    Say the concern back in your words and wait for a yes.

    "So the worry is that…?"
  3. 3Respond

    Goal, then decision, then reasoning, then evidence. In their terms.

    "We both want… so we chose…"
  4. 4Agree

    Close with a decision, an owner, or a quick test.

    "Can we test both this week?"
Tom Greever's approach: understand and restate the concern before you answer it.

Use it when

  • A product manager asks in a review for "a bigger, red button", and you sense the real worry is something else.
  • A senior stakeholder pushes back on a design you believe is right, and you need to keep the decision without a fight.
  • Two people in the room want different things, and you need to turn the debate into a choice between clear options.

How to use it

  1. Listen to the whole concern. Let them finish. Ask "why" until you reach the underlying need: "Can you help me understand what problem that solves?" Don't explain your design yet. Output: the real concern, which is often different from the first request.
  2. Restate it in your own words. "So the worry is that users won't find the export?" Wait for a yes. If they correct you, restate again. Output: a concern you both agree on.
  3. Respond with goal, decision, reasoning, evidence. Start with the goal you share, then say what you decided, why, and what supports it (usability data, analytics, a test, an NN/g guideline). Keep it short. Output: a short answer framed in their terms.
  4. Offer options with explicit trade-offs. If there is a real alternative, name it: "We have two options with different trade-offs. Here's what we gain and lose with each. I recommend A because… If we choose B, we should be aware that…" Output: a choice, not a debate.
  5. Agree next steps or a test. Close with a decision and an owner. When you are stuck, propose a quick test: "Can we test both with five users this week and decide with data?" Output: an agreed next step, sent in writing after the meeting.

Worked example

A shipment-booking screen on an internal operations platform. In a review, the head of operations says: "Put the export button at the top, and make it big. People can't find it."

Step What the UX lead says
Listen "Can you tell me more? Who is missing it, and when?" (Answer: shift supervisors, at the end of the day, when they send a report.)
Restate "So the worry is that supervisors can't get the daily report out quickly?" ("Yes, exactly.")
Respond "We both want supervisors to finish their day fast. We kept export in the table toolbar because it exports the filtered rows. In last week's test, 4 of 5 users found it, but the one who didn't was a supervisor."
Options "Two options. A: keep it in the toolbar and add a 'Daily report' shortcut on the dashboard. B: move export to the page header, which makes it easy to export the wrong rows. I recommend A."
Agree "Let's ship A and check it with three supervisors next week. I'll send a short note today."

The lead never argued "the button is fine". They found the real need (a daily report) and solved that.

Watch out for

  • Defending before you understand. If you answer the first comment, you often fix the wrong problem. Restate first.
  • Arguing on UX's terms. "It's more consistent" rarely wins. Translate it into what they care about: time, errors, support load, risk.
  • Too many options. Two or three options with clear trade-offs help a decision. More than that sounds like you have no view. Always say which one you recommend.
  • No written follow-up. Agreements made out loud get reopened. Send the decision and the next step after the meeting.

Template

Fill this in before a review for the decisions most likely to be challenged.

Decision:
Shared goal (in their terms):

Likely concern:
  Restate as: "So the worry is that ..."

Response:
  Goal ->
  Decision ->
  Reasoning ->
  Evidence ->

Options:
  A (recommended):   We gain:          We lose:
  B:                 We gain:          We lose:

If stuck, test:     With whom:        By when:
Next step / owner:
Source
Tom Greever

"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close