Meetings, “productivity,” and burnout: I stopped optimizing the wrong hours

I used to treat burnout like a personal efficiency problem. I bought the lamp. I blocked “deep work” on a calendar nobody respected. I read the books that told me to wake up earlier so I could earn my own hours before the company took them. I got a little more done at 6:30 a.m. I also got worse. The workday was still a chopped-up mess, and I had spent the only quiet time I had on a second shift I invented.

The story I told myself was that I was not disciplined enough. The story that was true was that I was optimizing the wrong hours. I was squeezing nights and mornings because the middle of the day had been sold to meetings, and I was calling that sale “collaboration.”

I manage engineers. I have also been the engineer who accepted every invite because declining felt political. This is what I changed when I stopped pretending a better morning routine could fix a calendar I had refused to fight.

The hours I was actually optimizing

I optimized the edges. Sleep later, then sleep earlier. Inbox at 10 p.m. so tomorrow would be “clear.” A Friday evening to “just finish the review.” A productivity system for the scraps between calls. Those scraps are not a system. They are residue.

What I did not optimize, for years, was the 10 a.m. to 4 p.m. block that decides whether an engineer has a profession or a talk show. I treated that block as weather. You do not negotiate with weather. You buy a better coat and work at night.

Night work feels like virtue when you are the one doing it. It looks like coverage when you are the manager watching the Slack timestamps. It is neither. It is a transfer: the company bought your evenings because it would not spend political capital on the calendar. I was the one making the transfer easy.

Meetings are not the villain. Unowned meetings are.

I do not want a company with no meetings. I have worked in that fantasy. Decisions rot. People duplicate work. The loudest Slack message wins. A meeting with a decision, a name on the decision, and a note afterward is cheaper than a week of threads.

What burned us was the other kind: the standing invite that survived its purpose, the “sync” with no question, the status meeting that existed because a director liked hearing voices, the optional meeting that was not optional if you wanted to know the plan. Those hours do not show up as “meeting cost” in a nice chart. They show up as people who cannot hold a problem in their head for two hours.

Context switching is not a metaphor. After the third 25-minute block I cannot remember the bug I was holding. I can remember the agenda I just performed. Then I open the laptop at 8 p.m. to recover the bug. That evening is not extra productivity. It is a refund for a theft I signed off on.

The productivity theater I retired

Pomodoro on a day with six calls is a joke you play on yourself. Time-blocking a calendar you do not control is journaling. Inbox zero at midnight is a way to import tomorrow’s anxiety into today so you can call it complete.

I also retired the story that tools would save it. A better notes app does not return an hour. A standup bot does not return an hour if the standup is still a twelve-person tour. AI summaries of meetings I should not have attended are a tax on the original tax. I use summaries. I do not pretend they make the meeting free.

What I measure now, for myself and for the team, is not tasks closed per evening. It is whether anyone got a two-hour block that survived. If the answer is no for a week, we do not have a motivation problem. We have a staffing or a meeting problem. Those are my problems. They are not a reason to buy another course on focus.

What I cut first — not the useful hour

I did not start by canceling the design review that actually unblocked a release. I started with the meetings that existed to make someone feel informed. Information can be a document. Feeling informed is a habit. I offered the document. I made the meeting optional and meant it. The first week people still came. The third week they read the note. The ones who needed a decision booked a smaller room.

I stopped stacking 30-minute holds with no gap. Back-to-back is how you guarantee the last five minutes of every call are a performance of wrapping up. Ten minutes between is not luxury. It is how the notes get written and the bathroom happens. I used to skip that and then lose twenty minutes after the last call “recovering.” I had optimized the wrong minutes.

I stopped using my own deep-work block as the overflow parking for other people’s urgency. If something is urgent, it gets a named trade: what slips. If nothing slips, it is not urgent. It is just louder. I say this as someone who used to treat every Slack ping as a fire because I liked being the person who answered.

Burnout was not a badge. It was a scheduling error I kept making.

The symptoms were ordinary: Sunday dread, short patience in reviews, the feeling that a simple ticket was heavy. I slept less to “catch up.” Catching up never completed. The pile was not a pile of tasks. It was a pile of fragments.

I have watched engineers blame themselves for this and then leave. The exit interview says “growth.” The calendar said they had not owned a problem from start to finish in months. People do not burn out only from hours. They burn out from hours that do not add up to a finished thing. Meetings can be hours. They often do not add up.

The fix that helped me was not a sabbatical speech. It was putting two mornings a week outside the default booking rules, defending them like a production window, and going home on the days I had used those mornings well. Going home felt like slacking the first month. It was the point. The wrong-hours version of me had already worked a second day. The right-hours version owed the evening nothing.

What I ask my team now

I ask how many two-hour blocks they actually got, not how they feel about “workload.” Feelings lie in both directions. Heroes under-report. Exhausted people over-apologize. Blocks are countable.

I ask which meetings they would delete if they could not be blamed. Then I delete some of those myself so they do not have to spend political capital. That is the job. “Empowered to decline” is a poster if the manager still books over the decline.

I ask whether the remaining meetings produce a decision or a broadcast. Broadcasts become writing. Decisions keep a room. If a meeting is both, it is two meetings wearing one invite, and one of them can go.

I do not ask people to be more productive in the leftovers. That question is how I trained myself to steal evenings. I ask what we will stop so the middle of the day works. If we cannot name a stop, we are planning to pay in nights. I would rather have the argument about the stop.

A week I still use as a template

Two mornings with no default booking, published on the team calendar so they are not a secret. One midweek hour that is only for decisions that have a doc already. A Friday 25-minute “what did we actually ship” that replaces a longer status tour. Everything else has to argue its way in. The template is ugly and specific on purpose. Vague “focus time” dies in the first product emergency. A named template can be restored after the emergency.

I review the template monthly the way I review on-call. If the protected mornings died three weeks in a row, I do not add a wellness webinar. I look at who is booking over them and I take that conversation. Sometimes the answer is that we are understaffed for the meeting load we accepted. That is a hiring or a scope conversation. It is not a mindfulness conversation.

The hours that are worth optimizing

Sleep. I was wrong when I treated it as optional infrastructure. I was not wrong because a book told me. I was wrong because my reviews got mean and my estimates got cute. That is a quality problem with a bedtime.

The first real block of the day, if you can defend it, for the hardest problem you owe. Not email. Not the meeting prep for a meeting that should have been a paragraph. The problem.

The last thirty minutes, for a note that future-you can open. Not a heroic push to “almost done.” Almost done is how nights start.

I do not optimize lunch into a walking one-on-one every day. Sometimes a walk is the one-on-one. Sometimes lunch is food. I had collapsed those and called it leverage. It was just another meeting with a sandwich.

What I will not pretend

Some roles are meeting-heavy. Staff-plus and managers live there more. The answer is not “no meetings.” The answer is fewer unowned ones, and no second job at night to fake a maker schedule you no longer have. If the role is meetings, say so. Hire for it. Stop telling people they would be fine if they just used the morning better.

Some weeks blow up. Incidents do not respect focus blocks. A blown week is a reason to protect the next one, not a reason to invent a lifestyle around 10 p.m. deploys. I still fail this. I still catch myself opening the laptop to feel in control. The test I use now: is this the only window, or is this the window I prefer because I will not move a meeting tomorrow. If it is the second, I close the lid.

Productivity, as sold, is a story about individuals outrunning a system. I ran that race. I got faster at the edges and emptier in the middle. Burnout was the bill. The refund was not a new system. It was putting the argument back where it belonged: the hours everyone can see, on a Tuesday, in a calendar I am paid to edit.