Protecting focus time

Hard engineering — design, debugging, nontrivial implementation — needs uninterrupted stretches. Context switching is not free. A "quick" Slack reply can cost 15–20 minutes of re-immersion on a gnarly bug.

Busy calendars and always-on Slack feel productive while quietly destroying the conditions for hard technical judgment.

Walking through a maker day

Defaults that work in most teams:

• Block 2–3 focus hours on most weekdays. Treat them like meetings with a critical stakeholder (you).
• Batch communication: check Slack and email on a cadence — mid-morning, after lunch, end of day — unless you are on-call.
• Cluster meetings on fewer days when you have influence over scheduling. Two meeting-heavy days and three maker days beats five fragmented ones.
• For reviews: a daily or twice-daily window so authors get predictable turnaround without you living in the inbox.

You will not get a perfect calendar at a meeting-driven company. You can still reclaim islands. If your calendar is fully owned by others, that is a career problem — raise it in 1:1s with data ("I had three uninterrupted hours last week").

Put the hardest cognitive work in your personal peak. Do not spend peak hours on Slack triage. Use low-energy windows for reviews, scheduling, and admin.

You have a design review at 3 p.m. and a half-written design. Wrong plan: clear Slack until 2:40, then panic-write. Better plan: 90-minute morning focus to finish the risky sections (failure modes, migration), lunch, one Slack batch, then light polish. Review quality tracks the morning block, not the heroic pre-meeting scramble.

Treat meetings like a spending account. A default full-time IC budget might be about 10 hours per week of meetings before focus collapses; adjust for role. Decline or convert to async anything without a decision or unblock. Ask for an agenda; leave if there is none and you are not required. If your title is IC and your calendar is managerial, renegotiate scope or title honestly.

Common mistakes

• Protecting zero blocks and calling the leftover fragments "focus."
• Spending peak hours on Slack and saving design for when you are tired.
• Treating every meeting as required. No agenda and no decision is optional for most ICs.

Check yourself

A "quick" Slack reply during a debugging session. What does it cost?

Often 15–20 minutes of re-immersion, not the 30 seconds of typing.

Your IC calendar is 20 hours of meetings. First move?

Decline or convert anything without a decision; raise the pattern in a 1:1 with a week of data.

Key takeaways

• Protect 2–3 focus hours on most weekdays. Batch communication.
• Maker work needs chunks. Manager calendars fragment them on purpose.
• Spend peak energy on the hardest thinking.
• Budget meetings; about 10 hours a week is a useful IC default.

Further learning

Next: tooling and automation.