Module 2 Lesson 2: When to defer to legal

Course 1 › Module 2: The designer's lane › Lesson 2.2

When to defer to legal

Five deferral triggers, how to escalate well, and how to push back — 34 min · 6 sections

Section 1 of 617% complete

Section 1 · 2 min

Audio ready

OpeningDeferring well — what it means and why it matters~2 min

There's a version of "defer to legal" that looks like this: you get stuck, you forward it to legal, you wait.

That's not deferral. That's abdication. And it's one of the most common ways designers lose credibility in fintech organisations — not by making wrong calls, but by making no calls and creating bottlenecks.

Deferring to legal well is a different skill. It means knowing precisely which decisions require a legal determination, framing the question clearly enough that legal can answer it quickly, providing the options rather than asking legal to generate them, and being able to push back constructively when a legal requirement creates a genuine UX problem.

The designers that legal teams trust most are not the ones who never push back — they're the ones who push back well. They understand the regulatory goal, they propose compliant alternatives, and they ask specific answerable questions. That's what this lesson teaches.

We'll cover the five situations that always require deferral, how to escalate in a way that gets fast and useful responses, how to push back on legal decisions that create UX problems, and you'll practise both in a live simulator before building your personal escalation card.

Let's start with the situations where the answer is always: stop and get legal in the room.

Section 1 of 6