How to Keep Yourself Productive While Managing a Team

Most engineering managers came from individual-contributor roles, were promoted because they were excellent at making things, and then discovered, painfully, that the skills that made them great ICs actively work against them as managers. Productivity, in particular, becomes a problem they had never thought about until it stopped working.

The first thing to accept

You are no longer measured by what you ship. You are measured by what your team ships. Your calendar will fill with one-to-ones, design reviews, hiring loops and incident retros. The instinct to "just code a little bit each day" will quietly cost you weeks per quarter, because every coding session takes you off the critical path of unblocking your team.

A workable model

I have stolen this from three managers I worked under, all of whom shipped a lot:

1. Protect mornings ruthlessly

The first two hours of your day are when your team is mostly online but their meeting load hasn't started. That is the window for your deep work: writing the document, doing the planning, drafting the difficult email. Block it on the calendar and defend it like your job depends on it (because it does).

2. Batch the management interrupts

One-to-ones, syncs and reviews all go in the afternoon. Even a 15-minute "quick chat" in the morning destroys an hour of deep work. Push back politely on AM scheduling.

3. Have a weekly "no-meeting" day

Pick one. Defend it. Use it for the work that takes four uninterrupted hours — performance reviews, technical strategy, hiring decisions. Without this day, those documents stretch out for weeks.

4. Write more, decide more

Your team's productivity is bottlenecked on your decisions, not on your code. The single highest-leverage thing you can do is make the next ten decisions faster — even if some of them are wrong. A reversible bad decision today beats a perfect decision in two weeks.

The traps

• Becoming the most-helpful debugger. Easy in the short term, fatal in the long term. Your team has to learn to debug without you or they will never grow.
• Saying yes to every meeting. The default invite is not a binding contract. "Skip — please share notes" is a complete sentence.
• Skipping one-to-ones. The most common shortcut. Also the one that costs the most retention.
• Working evenings. Your team copies your habits, not your words.

A small habit that matters

End every Friday with three things: who on the team is blocked, what decision is overdue, and one thing you will personally do differently next week. Write it down. Re-read it on Monday. The compounding effect is enormous.

The honest truth

Engineering management is the only role I know of where the productivity gains come from doing less. The instinct is to fill the calendar to prove you are working hard. The reality is the opposite: protect the white space, defend the deep work, write more, decide more, and let the team ship. That is the productive manager.