Protect Your Team's Time — Engineering Leadership, Part 10
Engineers need long stretches of focus. Meetings, requests, and interrupts kill them. Your job: build the firewall.
Step 1: Audit Where Time Goes (15 min)
For two weeks:
Track meeting time per engineer
Track interrupt frequency (Slack DMs, "quick questions")
Track context switches per day
If a senior engineer has >15 hours of meetings/week: something's wrong.
If they're DMed 30 times/day: same.
Measure before fixing.
Step 2: Make Focus Time a Default (10 min)
Block "deep work" time on the team calendar:
Tue/Thu mornings: no meetings, no Slack expectations
Engineers know: nobody schedules during these. Slack messages can wait.
Hard to enforce 100%. Defending it 80% is huge.
Step 3: Push Back on Meetings (10 min)
For each meeting on the calendar:
Why are you specifically there?
Could async do it?
Could a smaller group do it?
Decline or delegate when you can. Encourage your team to do the same.
"Can this be a written update instead of a sync?"
"Do you need just me or the whole team?"
Step 4: Run Better Meetings When You Must (15 min)
If you must meet:
Clear agenda, sent in advance
Right people only
Time-boxed
Decision documented at the end
End early when done
A 30-minute meeting that finishes in 15 = give 15 minutes back. Don't fill it.
Step 5: Designate an Oncall Person (10 min)
Interrupts often go to whoever is most known.
Rotate "interrupt duty":
Designated person fields questions for the week
Others have heads-down time
Without this, the same 2 people get hit constantly.
For engineering questions from other teams: a Slack channel + designated responder.
Step 6: Async First (10 min)
Default to async:
Standups in Slack
Status updates in writing
Design reviews on docs
Sync when:
Urgent
Genuinely interactive
Building relationships
For 80% of work: async wins. Less interrupt; more focus.
Step 7: Batch Communication (5 min)
"I check Slack at 10am, 1pm, 4pm. Urgent? Phone."
Tell the team your pattern. Encourage them to publish theirs.
People stop expecting instant replies. Stress drops.
For genuinely urgent: clear escalation path (PagerDuty, phone).
Step 8: Say No to "Quick Favors" (10 min)
Other teams ask for help. Saying yes feels good. Hurts your team.
Default no:
"We're committed for the quarter. I can't pull capacity. Let me
know if it's a Q4 priority and we'll discuss."
Some yeses are right (true emergencies, strategic partnerships). Most are not.
You're the team's shield. Use the shield.
Step 9: Cut Recurring Meetings (10 min)
Every 6 months: review all recurring meetings.
Is this still useful?
Could it be shorter / less frequent?
Who can be removed?
Meetings accumulate. Killing dead ones reclaims hours.
The "weekly sync that nobody knows why" — kill it. If it matters, it'll come back.
Step 10: Model Boundaries (5 min)
You set the example:
Don't reply to Slack at 11pm
Take vacation; truly disconnect
Block your own focus time
Say no publicly when warranted
If you violate boundaries, the team will too. Burn out together.
Healthy boundaries = team norm.
What You Just Did
Protect team time: audit, focus time, meeting pushback, better meetings, oncall, async, batch comm, say no, cut recurring, model boundaries. The firewall.
Common Failure Modes
Yes to every meeting / request. Team has no focus time.
Open Slack expectations. Constant interrupt.
Burn out trying to do everything. Worst leadership state.
Personal availability 24/7. Sets a bad expectation.
Recurring meetings never reviewed. Hours wasted weekly.
You're Done With Path 42
Engineering leadership: transition, delegation, 1:1s, decisions, direction, underperformance, manage up, culture, disagreement, time protection. From senior IC to leader.
Recommend Mentoring Engineers — the other side of leading: growing people.
