An Engineering Leader's Sustainable Weekly Rhythm

For my first six months as an engineering manager, I had no rhythm. Every week felt like a different emergency. My calendar was a mosaic of context-switching: one-on-ones crammed between architecture reviews, strategy documents half-written at midnight, incident responses interrupting everything. By Friday, I'd feel exhausted and unable to point to anything I'd accomplished.

I remember one Thursday evening, sitting in my home office at 9 PM, finally getting to the "strategic thinking" I'd promised myself all week. The thing that was supposed to be my most important work — setting direction, removing long-term blockers, thinking about where the team needed to go — was getting my worst hours. My most depleted, most unfocused, most resentful hours.

That's when I realized: if I don't design my week intentionally, other people's urgency will design it for me. And their priorities will always outshout mine, because their priorities come with notifications and my priorities come with silence.

The Myth of the "Typical Week"

Let me be honest upfront: no two weeks in engineering leadership are the same. There's no perfect template that works every time. Incidents happen. Reorgs happen. A team member has a crisis. The VP needs something by end of day.

What I'm going to share isn't a rigid schedule. It's a rhythm — a default pattern that provides structure when things are normal, and a home base to return to when chaos subsides. Think of it less like a train schedule and more like a heartbeat: regular enough to sustain life, flexible enough to respond to what the body needs.

My Current Weekly Rhythm

Here's how I structure a typical week. This has evolved over years of experimentation, failure, and refinement.

Monday: Orientation and Connection

Time Block	Activity	Purpose
9:00 - 9:30	Weekly review + planning	Orient myself to the week ahead
9:30 - 10:00	Team standup	Pulse check on blockers and morale
10:00 - 12:00	One-on-ones (batch 1)	People first when I'm fresh
12:00 - 13:00	Lunch (actually away from desk)	Recharge
13:00 - 14:30	Cross-functional sync	Alignment with product/design/stakeholders
14:30 - 16:00	Admin + async responses	Catch up on Slack, PRs, docs

Why Monday for one-on-ones: I used to scatter them throughout the week. Now I batch them on Monday and Tuesday mornings when my empathy and patience are highest. One-on-ones deserve my best self, not my Wednesday-afternoon-depleted self.

Tuesday: People and Problems

Time Block	Activity	Purpose
9:00 - 12:00	One-on-ones (batch 2)	Remaining direct reports
12:00 - 13:00	Lunch with someone	Informal relationship building
13:00 - 15:00	Problem-solving block	Active engagement with technical blockers
15:00 - 16:00	Hiring/pipeline work	Interviews, sourcing, candidate discussions

Wednesday: Deep Work (Protected)

Time Block	Activity	Purpose
9:00 - 12:00	NO MEETINGS	Strategy, writing, thinking
12:00 - 13:00	Lunch	—
13:00 - 14:00	Architecture/design review	Technical contribution
14:00 - 15:00	Team rituals (demo day, etc.)	Culture maintenance
15:00 - 16:00	Buffer	Overflow from the week

The sacred morning: Wednesday morning has no meetings. None. I protect this with my life. This is when I write strategy documents, think about team structure, plan career development paths, draft difficult communications, and do the work that requires sustained attention. If someone tries to book this time, they get a polite "I have a conflict." The conflict is with myself, and that's valid.

Thursday: Execution and Alignment

Time Block	Activity	Purpose
9:00 - 10:00	Leadership team meeting	Alignment with peers
10:00 - 12:00	Project oversight	Unblocking, decision-making, progress checks
12:00 - 13:00	Lunch	—
13:00 - 15:00	Technical contribution	Code review, architecture feedback, docs
15:00 - 16:00	Hiring/pipeline	Interviews, candidate debrief

Friday: Reflection and Closure

Time Block	Activity	Purpose
9:00 - 10:00	Week-in-review	What happened? What did I learn?
10:00 - 11:00	Team retro/planning (biweekly)	Collective reflection
11:00 - 12:00	Mentoring/coaching	Investment in others' growth
12:00 - 13:00	Lunch	—
13:00 - 14:30	Loose ends	Close out anything hanging
14:30 - 15:00	Next-week prep	Set intentions for Monday
15:00 onward	Low-stakes, optional	Or just... stop.

Friday afternoons: I try to end early on Fridays. Not officially — just personally. My brain is cooked by Friday afternoon, and anything I produce will be low quality. Better to rest and come back sharp on Monday than to grind out mediocre work at 4 PM on a Friday.

The Principles Behind the Rhythm

1. People Get Your Best Hours

One-on-ones, coaching conversations, and difficult discussions happen in the morning, early in the week. These require empathy, patience, and presence. I cannot offer those at 4 PM on a Thursday.

2. Deep Work Gets Protected Time

Strategy and thinking work doesn't happen in 25-minute gaps between meetings. It requires 2-3 hour blocks of uninterrupted time. If you don't protect this explicitly, it will never happen — and your team's long-term direction will suffer.

3. Admin Fills the Cracks

Slack messages, email, PR reviews, and small admin tasks expand to fill whatever time you give them. I give them specific blocks rather than letting them consume the whole day.

4. Friday Is for Reflection

Without reflection, you repeat mistakes. The Friday review takes 30 minutes and pays for itself a hundred times over. What went well? What didn't? What am I avoiding? What needs my attention next week?

5. Buffer Exists By Design

I leave 2-3 hours per week deliberately unscheduled. Not as slack time — as incident buffer, overflow space, and margin for the unexpected. Because something unexpected will happen every week.

What Breaks the Rhythm (And How to Recover)

This rhythm breaks constantly. Incidents, escalations, urgent hiring needs, emotional crises on the team. The key isn't preventing disruption — it's recovery speed.

When my week gets blown apart, I ask: "What's the one thing I absolutely cannot skip this week?" Usually it's either a one-on-one with someone who's struggling or my protected deep-work block. Everything else can flex.

And when I lose a week entirely to chaos, I don't try to "catch up" the following week by cramming two weeks of work into one. I just restart the rhythm. Fresh. No guilt.

The Things I Had to Stop Doing

Building this rhythm required saying no to things I used to think were mandatory:

• Attending every meeting I'm invited to. If I'm not needed for a decision and the information can reach me async, I decline. Politely, but firmly.
• Responding to Slack immediately. I check Slack in batches, not continuously. The team knows: if it's urgent, escalate explicitly. Otherwise, I'll see it in my next batch.
• Being available to everyone all the time. Open-door policies sound generous. In practice, they mean you never get strategic work done. I'm available at predictable times. That's sufficient.
• Working evenings as a default. Early in leadership, I'd work 7 AM to 9 PM because the work expanded infinitely. Now I have boundaries. The work will still be there tomorrow.

The Energy Management Layer

Time management is necessary but insufficient. You also need to manage energy. Some activities fill your tank; others drain it. I've learned:

Fills my tank: One-on-ones where someone has a breakthrough. Solving a hard problem collaboratively. Writing strategy that crystallizes my thinking. Mentoring.

Drains my tank: Back-to-back meetings with no breaks. Political conversations where I'm navigating ego. Context-switching between unrelated problems. Conflict without resolution.

I try to alternate: draining activity → filling activity → draining activity. Or at minimum, I don't stack five draining activities in a row. The rhythm of the week reflects this.

A Word on Guilt

If you're an engineering leader feeling guilty about protecting your time, I want to name that feeling and gently challenge it.

The guilt says: "If I'm not in that meeting, I'm not adding value." But the truth is: if you're in every meeting, you're adding no strategic value. Your team doesn't need you in every discussion. They need you to be thinking ahead, removing obstacles before they appear, building a team that can function independently.

The highest-leverage work you do as a leader is almost always invisible: a well-timed conversation, a structural decision, a hire that transforms the team. That work requires protected time and a rested mind. Defending your rhythm isn't selfish. It's responsible.

Building Your Own Rhythm

Don't copy my schedule exactly. Build your own based on:

1. When are you sharpest? Schedule people-work and deep-work in those hours.
2. What drains you most? Don't stack those activities together.
3. What gets skipped when you're busy? That thing needs a protected block.
4. Where does your team need you most? Optimize for their needs, not just yours.
5. What time do you want to stop working? Build backwards from there.

Then try it for a month. Adjust what doesn't work. Keep what does. Iterate quarterly as your role evolves.

Your rhythm will never be perfect. But having a deliberate rhythm — even an imperfect one — is transformatively better than having no rhythm at all. It's the difference between feeling like you're driving and feeling like you're being dragged.

You deserve to feel like you're driving. Build the rhythm that lets you steer.