Why I Started Joining Dev Team Meetings — and Why You Should Too

I've been making a point of sitting in on developer meetings — especially the ones where the dev team lead and engineers review roadmap items and work items with the PM, but without a designer in the room. It started as an experiment. It became a non-negotiable part of how I work.

Here's what I've learned.

It builds real relationships with your dev team

Showing up to their space signals that you care about their work and their constraints. You start to understand how they think, what slows them down, what they're proud of. You stop being the person who shows up at the end with a Figma file and starts being someone who actually understands the shape of what's being built. That trust pays off in every design handoff that follows.

You catch the moments that matter most — before it's too late

When a designer isn't in the room, the team will still move forward. Technical limitations come up. Trade-offs get weighed. Decisions get made. Without a designer present, UX is often the thing that gets cut first — not out of malice, but because there's no one advocating for it in that moment.

A real example that changed a shipped feature

During a dev sync, the team flagged a technical limitation and proposed removing reply connectors for the comment section in Community. From a pure implementation lens, it seemed like a reasonable trade-off. Reply connectors are the visual lines that connect nested replies to their parent comment in a thread.

But reply connectors are a foundational UX pattern — Reddit, YouTube, every major community platform uses them because they make threaded conversation legible at a glance. Without them, nested discussions collapse into visual noise.

You understand what everyone is actually working on

Our joint product meetings move fast. There's rarely enough time to get a real picture of each person's workload. Attending dev syncs gives you that context — you start to see who's heads-down, who has bandwidth, what's coming up next.

That lets you time your UX work more strategically:

• Tackle design debt when devs have a quieter period
• Flag your priority work before they're committed elsewhere
• Identify where you can take a ticket yourself to unblock something important

How to start

You don't need permission. You don't need to speak up every time. Start by attending a single dev sync as a quiet observer. Don't bring a Figma file. Don't set an agenda item. Just listen for how decisions are made when design isn't in the room — and notice how your presence, over time, starts to shift those decisions.

If you're not already in dev syncs (even as an occasional lurker), try it. The habit is low-cost and the return is surprisingly high.