TECH LEAD NOTES

How I organise a Tech Lead day.

Leadership practice9:00 AM–9:00 PM IST

A calendar is not a measure of impact. It is a promise about where people can find clarity, feedback, and support—while preserving enough quiet time to make good decisions.

A deliberate operating rhythm

Time	Focus	Activities
9:00–11:00	Focus hours	Individual contribution, email and Slack triage, follow-ups, documentation, and work that needs uninterrupted thought.
11:00–12:00	Team internal	15 minutes: run a focused scrum for the eight-engineer MRO, GEN1, and DEX team—review operational signals, defects, priorities, and ownership. 45 minutes: connect individually with engineers to align on approach, remove blockers, and make sure the day’s most important work is clear.
12:00–1:00	Leadership alignment	Manager syncs, roadmap planning, and updates that keep delivery connected to leadership context.
1:00–2:00	PR & design reviews	The first review block: help decisions land early, without making quality a late-stage surprise.
2:00–4:00	Cross-team support	IST collaboration, queries, hiring, and Bar Raiser conversations—time intentionally available for the wider organisation.
4:00–6:00	Protected thinking time	A walk, a reset, room for thought, and the highest-leverage leftover priority of the day.
6:00–6:30	PR & design reviews	A second review block, so teams know when they can expect careful feedback.
6:30–9:00	Cross-time-zone work	US-facing support, meetings, preparation, and decisions that need a wider room.

WORKING AGREEMENTS

Predictable access, better decisions.

PR requests have known review windows; quick approvals can become a short call when discussion is more useful.
IST meetings and recruiting coordination belong in the 2:00–4:00 PM window.
US and cross-time-zone meetings use 6:00–9:00 PM, with a buffer before and after.
Offline questions get an expected response time. Same-day meetings need prior discussion.

FRIDAY FOCUS

Make room for the work around the work.

Friday avoids routine connection meetings. It is for documentation, team learning, personal learning, sprint planning and retrospection, 1:1s, selected cross-team catch-ups, exploration, and POCs that can create organisation-level impact.

Answers generated by AI

Questions this article answers.

Hover or focus a question to reveal a short answer drawn only from the article’s published content.

Why does a Tech Lead need protected focus time?

It preserves space for sound decisions, reviews, mentoring, and strategic work instead of letting meetings consume the day.

When does the article place cross-time-zone meetings?

US and cross-time-zone meetings sit in the 6:00–9:00 PM window, with buffer time around them.

What is Friday reserved for?

Friday makes room for documentation, team learning, planning, retrospection, 1:1s, exploration, and useful POCs.