Dev Velocity Lab
← Back to blog
tools-and-systems

The Meeting Attention Audit: When to Tune Out and Get Actual Work Done

Not all meetings deserve your full attention. Here's how I figured out which ones do—and why staying present during the ones that matter is what actually looks professional.

Watch on YouTube
ShareX / TwitterLinkedIn

I'm in a new SRE team. Every week we have a story review that's supposed to be an hour but usually stretches to ninety minutes. Twelve people, each walking through their completed work.

Here's what I realized after three months of slowly dying inside: I was treating every single story review like it required my full attention, and it was killing my ability to actually ship.

The trap is that junior engineers are trained to always be present, always be engaged, always look busy. But I was learning nothing from watching senior engineers demo work on systems I didn't understand yet, and I was losing ninety minutes where I could've actually made progress on my own stories.

So I stopped.

The Rule I Use Now

When it's my story being reviewed: completely present. No laptop, no Slack, nothing. That's non-negotiable.

When it directly relates to me: present. If someone's finishing a resiliency automation pattern and I'm going to own something similar next sprint, I listen in. That's context I need.

When it's a deep dive on someone else's work: I stay reachable, but I work. I'm not zoned out—I'm available if my name comes up, and if someone asks me a question I can actually answer it because I was there.

The real skill nobody teaches you is deciding which meetings actually need you.

What Changed

The guilt died first. I realized I wasn't being disrespectful—I was being strategic. The senior engineers aren't building their careers by having me stare at their screen for ninety minutes. They're building it by shipping.

Then I started shipping faster. Finishing my own work in parallel meant I wasn't scrambling Friday afternoon. I had time to actually understand the patterns instead of just cramming them.

The weird part? I got better context by being selective. When I tuned in for stories that mattered to my roadmap, I actually absorbed something instead of enduring.

The Caveat

This only works if you're genuinely intentional. I'm not half-present, doom-scrolling Slack, getting distracted. I'm actively working on something specific, and I know exactly when to stop.

The moment my name comes up, I'm there. The moment someone asks me a direct question, I have an actual answer. I'm not checking out—I'm being honest about where my attention is most valuable.

What Actually Got Me Here

I was frustrated for weeks because I thought something was wrong with me. Turns out, the system was wrong. Not every meeting is equally important. Some meetings provide context AI can't. Others are just status broadcasts you can work through.

Learning the difference is what separates people who "look busy" from people who actually move things forward.