Conversation Is a Design Tool Too

A single 20-minute conversation that redefined the success metric for the whole project had the highest impact last year, not the redesign itself.

I was deep into building a new component for an internal platform. The brief was clear. The design was solid. But something felt off, like I was solving the wrong version of the problem. So instead of opening Figma, I started a conversation with my stakeholders about what adoption would look like for the teams using this thing.

That single conversation shifted everything: the metric changed, the priority changed, and the work was sharper because of it. This experience led to a larger realization.

Here’s what I learned: designers are trained in tools and craft. We know how to prototype, test, and iterate. But we’re rarely trained in the conversations that shape the work before a single pixel gets pushed.

And those conversations?

They’re where the real design happens—and, too often, where we miss out because we’re focused on the tools, not the dialogue.

Conversation is discovery.

Your strongest design insight this quarter likely won't arise from a tool, but from a conversation you might overlook.

Growth design lives in that gap between what’s in the brief and what’s actually driving the business. Conversation is how you close it.

Ask better questions in everyday conversations — not just in formal research settings. You surface the business context that actually moves the work forward. Hidden priorities. Unspoken tradeoffs. The real “why” behind the ask.

Just like prototyping, conversation is a practice you can design.

As a growth design architect, I obsess over user flows. Every screen, every interaction, every decision point is mapped and intentional. But the conversations that shape those flows — the ones where scope gets defined, metrics get chosen, and trade-offs get made — are often completely undesigned. (Sigh) We just show up and react.

Back to the project I mentioned in the beginning. In that moment, I thought of ways to apply that same rigor.

A well-designed conversation has the same bones as a well-designed flow: a clear entry point (what's the one question we're here to answer?), a deliberate structure (what context does the room need before we get to the decision?), and a defined outcome (what are we walking away with?).

This is especially high-leverage in growth design, where the wrong metric can send an entire team optimizing in the wrong direction. The conversation where you align on what "success" actually means — before anyone opens a dashboard — is often worth more than the next three design iterations combined.

Treat conversation as a feedback loop: input a good question, output team alignment on design direction.

Conversation also becomes critical as you shift to new paradigms, such as an AI design system.

This one's for my fellow systems thinkers.

I’m transitioning to an AI design system, and I've already discovered my biggest adoption blocker isn't a missing component — it's the missing conversations about aligning AI-driven processes with real team needs.

I build components and modules for internal platforms. And I've watched beautifully documented systems sit unused because no one had the conversation about naming conventions with the people actually using them.

Adoption rates, feedback loops, shared language — these are shaped more by conversation than by documentation. The rituals and processes around how teams communicate ARE part of the system. They're just the part we forget to design.

So I leave you with this. The next time you feel stuck on a project, try closing the application and opening a conversation instead.

Conversation could be your most valuable—and underused—design tool.