Every design team I've seen try to build culture inside a larger organization has made the same mistake.

They've treated it like a communications problem. They launch a design COP ... they run workshops ... they present at all-hands meetings about design thinking. Or my favorite, they schedule brown bags / lunch and learns that twelve people attend, eight of whom are already on the design team.

Six months later, they're exhausted.

The conclusion they reach: if they just had more authority, a seat at the table, a mandate from leadership, a VP who "gets it," things would be so much easier and different.

That diagnosis is wrong.

The authority framing is easy to lean into because it puts the problem outside your control. If the obstacle is organizational structure or executive buy-in, your job becomes waiting or campaigning, not rethinking the approach. But organizations with strong design cultures got there because a few people behaved as if design mattered, and made it hard for others not to notice. They weren't loud, they were impactful.

The evangelism model mistakes awareness for change. You can run every workshop on your calendar, share every article about user-centered thinking, build a wiki page no one opens, and leave the organization exactly where you found it. Culture is behavior that's become expected. Awareness alone doesn't get you there.

Two things change behavior in organizations: proximity and stakes. People change how they work when the new way makes their job easier, or when the cost of the old way starts showing up somewhere leadership can see.

The designers who shift culture rarely do it by talking about design. They attach themselves to the work that already matters: the product that's behind schedule, the customer complaint the exec team keeps mentioning, the initiative with a real deadline and real visibility. Those individuals show up, do the work, and translate their contribution into terms the organization already tracks and can understand.

Done right, design becomes harder to cut and becomes a part of the business conversation.

The takeaway for practitioners here: Change what people experience when design is involved. The beliefs, and habit change will follow.

Translating your work into an organization's language can feel like code-switching, like you're conceding something. But you're not. If design improves outcomes, making those outcomes legible in the terms the organization already values is part of the work. Insisting that people learn to value design on your terms is a luxury the results can't afford. Now that being said, over time as design takes hold in the org you can start to move to a language that makes sense for both, it's all a game you need to navigate.

People also imitate more than they absorb instruction. When a designer pushes back on an assumption with real evidence, when a design manager runs a critique that's rigorous and specific rather than vague and affirming, or when someone names the design debt in a room that would rather not discuss it, those moments accumulate. People start expecting them. Eventually they start doing them ... not because anyone mandated it, but because they saw it done enough times that it became normal, it's now a habit.

This is slow, and I haven't seen a shortcut that holds. Let's be honest, rarely shortcuts are worth it in the long run.

Most design culture efforts stall from impatience, not lack of authority. Teams invest in the artifacts of culture, the COP, the toolkit, the shared Figma library. All of this rather than the conditions that sustain it: trust, demonstrated value, a track record that makes design harder to ignore.

The question worth asking: what's the smallest thing you can do, on something that matters to this organization, that makes design's contribution undeniable? Start there and then repeat it in bigger rooms and bigger conversations.

The organizations where design culture takes hold aren't the ones with the most evangelists. They're the ones where a few designers showed up, did rigorous work on things that mattered, and made it expensive to cut corners on the work they touched.

That's the playbook, at least in my mind. The hard part is running it long enough for it to matter.

Until the next volume, thanks for joining me. 
- Andrew Preble