The Tech Lead's Guide to Meeting Minimalism

For the Senior Engineer or Tech Lead, the primary currency is Focus. Yet, as your career progresses, the organization attempts to pay you in a different currency: Meetings.

This transition often leads to the 'Maker vs Manager' schedule conflict first described by Paul Graham. To thrive as an executive-level engineer, you must master the art of tactical absence.

The Rule of Three

High-performing engineering leaders should aim for no more than three hours of synchronous meetings per day. Anything beyond that creates a 'fragmented focus' state where deep work becomes impossible.

Strategies for Protecting Maker Time

• Asynchronous-First: If a decision can be made in a Slack thread or a Google Doc comment, cancel the meeting. Force stakeholders to write down their thoughts. Writing is thinking; talking is often just rehearsing.
• The 25-Minute Block: Standardize on 25-minute meetings instead of 60. It forces a faster transition to the core issue and leaves time for the mental context-switching required to get back to code or architecture.
• Delegate the Presence: You don't need to be in every stakeholder sync. Empower your senior developers to represent the team. It builds their 'Agency' while preserving yours.

The Narrative of Value

When you decline a meeting, don't just say 'no.' Frame it as a trade-off: "I am skipping this sync to ensure the Q3 architecture audit is completed by Friday. Please tag me in the notes if a technical decision requires my input."

Protect your time, not because you are busy, but because your output depends on it.