Dive Club
Posts
🤿 elevating craft

🤿 elevating craft

+ best advice I've been given this year

Ridd
March 07, 2025

In this week’s episode Christophe Tauziet shares a piece of advice that I'll take with me the rest of my design career.

That’s not hyperbolic... it literally changed how I work in Figma the very next day.

He describes iteration as “shooting darts” — the more shots you have the better your odds of hitting the target 🎯

Here’s the problem though… most people (myself included) iterate by duplicating the previous screen and making tweaks:

Iteration through duplication anchors you to your first idea.

Just this week I was exploring concepts for Inflight and cranked out ~20 artboards. Except… if I zoom out there were really only two separate ideas (read: darts 🎯).

Christophe recommends designers do this instead:

Before you start slinging pixels draw {n} empty artboards and force yourself to start from scratch on each concept.

“Every time I've given that advice to someone and they've tried it, they came back to me being like, wow, I'm a different designer now.”

Christophe Tauziet

This week’s episode is top tier juice per minute 🧃 so there’s a lot more advice where that came from.

Here are some other ways you can elevate craft in your org 👇

🤝 WITH INFLIGHT

I don’t know about you… but I’ve never been happy with the way I get async feedback on my designs.

Whether it’s Figma comments, Loom videos, Slack threads… It’s a mess.

So behind the scenes I’m working on the product that I’ve always wanted to exist.

It’s called Inflight. And I’d love to show it to you before it goes live 🤫

Get a little sneak peek of what’s coming next 👇

🎓 KEY TAKEAWAYS

Ways to elevate craft at your org

“Sweating the details” is literally a company value at Plaid.

So I asked Christophe to pull back the curtain and show us exactly what that looks like in practice. Here are a few snippets that I saved in my notes 👇

1 — “Design Jams”

There’s an unspoken social cost to asking for help. We know people are willing but it’s still hard to say “I’m stuck can you help?” especially early in a project.

That’s why Plaid has branded the idea of “Design Jams”.

At any moment a designer can drop a note in Slack and say “hey I’d love to have a design jam on _____”.

Giving it a name strips away the social cost and creates an expectation that designers collaborate very early in the process.

2 — Lots of Loom videos

Christophe talks a lot about the value of “exposing the process” and one core way that happens is through async Loom videos in Slack.

There are a lot of benefits that I’ve talked about before but one thing really stood out to me from our convo:

Exposing more of thinking through Loom increases the surface area for engineers to contribute. And the bigger role they play early in the process, the more pride they take in their work and the more likely they are to go above and beyond when implementing your design.

“We’re in the video generation now”

Christophe Tauziet

3 — Keeping CRIT fresh

Christophe shares a ton of advice for CRIT and giving feedback but one thing that really stood out to me was how he intentionally mixes up the format to keep the practice from growing stale.

Plaid uses three types of CRIT interchangeably:

Presentation with Q&A at the end
Silent CRIT live with Figma comments
No context CRIT (just show the work and people immediately start critiquing)

4 — “Polish reviews”

Plaid has a panel of ~4 super senior ICs who have a great eye for visual details and deeply understand the design system.

As a final step before production code is written, they have 24-48 hours to take a fine comb through the Figma file and nit-pick the sh*t out of the UI.

I would’ve paid to have this as a service at Maven 😅

There are another 5+ takeaways in my notes but this email is long and I’m about to go fill those blank artboards in Figma :)

I’m super pleased that this episode is the 100th ever because it’s as good as it gets.

Listen on YouTube, Spotify, Apple, or wherever you get your podcasts 👇