Hey Reader,

I keep hearing the same thing in my mentoring calls lately: it's never really the design that gets pushback — it's the thinking behind it, and most designers don't have language for that conversation. This issue gives you the exact phrases, plus a few resources worth keeping in your back pocket.
​
​In today's email:

• AI as a teammate, not just a tool: what it looks like when coding agents share the workspace with humans.
• Craft worth studying: the year it took to design Cursor's 600+ icons, by hand.
• A resource worth bookmarking: a growing library of design tools, inspiration, and studios in one place.

Live next week Our next Level Up Club workshop, with Dan Cariño (OpenAI, ex-Meta). It's all about what actually moves the needle in hiring right now, and how AI has shifted the signal companies look for from senior designers. Save your spot Level Up Club member? Join the Event Calendar using the email tied to your membership for free access.

Design gems of the week

• ​How to turn your AI into a world-class designer: Reading this could either make you sweat about the future of design jobs, or get you super pumped about what's possible.
  ​
• ​hilos: A shared chat space where people and coding agents work in the same room. Agents can post progress, open pull requests, and hand back context for review. A glimpse at what collaboration looks like when agents become teammates, not just tools.
  ​
• ​The making of Cursor's icons: A year of drawing, testing, and shipping a complete 600+ icon system for Cursor, with every exploration and final variant drawn by hand.
  ​
• ​catalog.design: A well-organized library of design resources, from apps and foundries to inspiration, tools, and mockups. One to bookmark for whenever you need a spark or a better place to start.
  ​
• ​Job hunting and Europe relocation in the AI era: One designer's honest account of quitting a job, moving to Amsterdam, and using Claude to prototype through the job search. Proof AI can speed up the work, but understanding the tradeoffs is still what gets you hired.
  ​
• ​5 ways to use HTML docs in your design process: A look at using HTML docs for rapid prototyping and exploration.
  ​
• ​The Senior Designer's career toolkit: A career resource for designers past the beginner stage: senior resumes, case studies, interviews, career paths, and translating design work into outcomes executives understand.

Open design roles worth a look

• ​Senior Product Designer, Design Systems @ Anduril Industries, Costa Mesa, California
• ​Lead Product Designer​ @ DNA.inc, Europe - Fully remote or hybrid in Amsterdam, Madrid, or Valencia
• ​Product Designer @ WorkOS, Remote in United States & Canada
• ​Designer @ Primitive Labs, Remote

The exact phrases to use when you next experience stakeholder pushback

There are two very different conversations hiding inside "they didn't like it" — whether "they" is a client, your VP, or the PM sitting next to you.

One is about pixels — the wrong blue, a button that feels too big, a headline that doesn't land. That conversation is easy. You've had it a thousand times, and you know how to have it.

The other is about reasoning. They're not questioning what's on the screen — they're questioning why you think it's the right move at all. That's the conversation most designers still don't have language for. So they either fold, or they get defensive, and either way the stakeholder walks away trusting the work a little less next time.

Why this is showing up everywhere right now

It's not a coincidence this feels sharper this month. AI has made producing options nearly free — more variations, more prototypes, more directions than any team can evaluate. NN/g's been calling this the "custodial era of UX": teams can generate faster than anyone can judge what's actually good. The scarce skill isn't generating anymore. It's judgment.

I'm seeing the same thing from the other side. In the last 2 weeks I chatted to fourteen designers, each in different company environments — and almost everyone named the same goal.

The reframe

It's easy to treat pushback as personal. Our defences get raised and our first reaction is often to double down.

But rather than treating pushback as a threat to defend against, what if we flipped it and treated it as a request for more reasoning? Almost every "pushback on thinking" moment is really the stakeholder saying I don't have enough of your logic.

Phrases for four common moments

When they challenge the direction itself

• "That's a fair challenge — can I walk you through what led us here, then we can decide together if it still holds?"
• "Is the concern the direction, or how we got to it?" (Those are different conversations).

When they want to skip straight to a different answer

• "I can explore that — I want to flag what we'd be trading off first, so we're choosing it with purpose."
• "What outcome are you hoping that gets us closer to? Let's make sure we're solving the same problem."

When you need to hold the line

• "That makes me feel a little uncomfortable – here's why."
• "Here's my honest read, and what I'd need to see to change it."

When you want to stay collaborative without losing the thread

• "What would it take for you to feel confident in this direction?"
• "I'm open to being wrong — what are you seeing that I might not be?"

The phrases help in the moment. What changes the pattern long-term is narrating your reasoning before anyone pushes — in the file, in the deck, in the walkthrough.

Most designers only show their thinking once it's under attack. By then it reads as defense. Show it earlier and it reads as leadership.

Have a topic you'd like me to write about? Reply to this email and let me know! I read every reply.