A staff engineer at a fintech company came in convinced he had a meeting problem. He was spending six to eight hours per week in meetings — not unusual for someone at his level — and feeling like he never had time to write code. His instinct was to get some of those meetings off his calendar.
What the Data Actually Showed
After setting up four layers — Deep Coding, Meetings, Code Review, Admin — and tracking for two weeks, the meeting total confirmed his estimate: about 30% of his work hours, roughly seven hours per week. By most benchmarks, that is a manageable meeting load for a staff engineer.
The problem was not the total. It was the distribution. His meetings were scattered throughout every day — a standup at 9:30, a planning call at 11, a 1:1 at 2, a review at 4. Across the full two weeks, he had four contiguous coding windows of 90 minutes or longer. Four. In two weeks.
The research benchmark for meaningful engineering work is three hours of uninterrupted time. He was getting that twice a week at best. Everything else was coding in fragments — and coding in fragments is largely an illusion of productivity.
The Real Constraint
He was not blocked from deep work by total meeting load. He was blocked by distribution. Each individual meeting was defensible. Together, they created a calendar where no day had a usable chunk of focused time. The six hours of meetings per week were effectively costing him the ability to do engineering work at all — not because of the time they took, but because of what they did to the time around them.
The Changes
He worked with his manager to consolidate. All standup and planning meetings moved to morning blocks: standup at 9:30, planning on Tuesday and Thursday at 10. The 1:1s and reviews moved to the early afternoon — 1pm and 2pm slots. The goal was not to reduce meetings. It was to create three uninterrupted afternoon coding blocks of three hours or more per week.
The Result
Within a month, his contiguous coding windows had gone from four per two weeks to twelve. Total meetings per week: approximately the same as before. Total effective engineering hours: dramatically higher. He calculated roughly 12 additional hours of useful work per month — not from working more, but from changing when the interruptions happened.
This is the meeting drag problem. It is not usually about too many meetings. It is about meetings distributed in a way that makes focused work structurally impossible. The fix is not fewer meetings — it is better placement.