Part 5 · 1 chapters · ~10 min

Design Pushback Drill

The four kinds of design the JD asks you to challenge, each with a worked example from trading and payments: the risk in user terms, an alternative that keeps the design's intent, a measure and an owner, then the way to say it and a practice drill of four more cases.

8

Unsafe, misleading, inaccessible, unnecessarily complex

challenge for a better design, not a won argument
  1. Unsafe: show the amount as held, never the balance before confirmation.
  2. Misleading: honest time ranges, and the fee shown up front.
  3. Inaccessible: never colour alone, labelled controls, no auto-confirm.
  4. Unnecessarily complex: one review screen, with step-up only where the risk justifies it.
  5. How to say it: the goal, the risk, an alternative, a measure, and who owns the decision.
  6. A real example of your own, told honestly.
code
drill: for each, say the challenge out loud in under 60 seconds
1. "After a successful deposit, auto-redirect to the trading screen after 3 seconds."
   → risk: the user cannot read the receipt; screen readers lose context; WCAG timing.
     alternative: a receipt with a clear "Start trading" button. measure: receipt views, deposit-related contacts.
2. "Pre-tick 'Save this card' and 'Enable instant withdrawals to this card'."
   → risk: consent not given; surprise later. alternative: unticked, explained. owner: compliance on consent wording.
3. "Hide the spread and show only 'zero commission'."
   → risk: misleading on cost. alternative: show the spread in the ticket. owner: compliance; product on wording.
4. "Shake the whole screen red when an order fails."
   → risk: motion sensitivity, panic, no information. alternative: an inline error saying what happened and what to do; respect reduced motion.
THE DESIGN PUSHBACK DRILL
four kinds of design to challenge (unsafe, misleading, inaccessible, unnecessarily complex) and the shape of a good challenge
swipe the figure sideways, or tap expand for full screen
1/6
unsafe
Unsafe: a design shows the new balance immediately after the user taps Withdraw, before the server confirms. Risk: the withdrawal may fail or be pending, and the user acts on money they do not have. Alternative that keeps the intent (instant feedback): show the amount as held, with the available balance reduced and a pending state, resolving when the server confirms. Measure: support contacts about "missing" money.