Here’s a number that keeps bugging me: the average engineer at a large tech company spends only 30-40% of their workweek on actual engineering work. The remaining hours vanish into meetings, Slack, email, context switching, and whatever passes for “alignment” this quarter.

That means in a 40-hour week, you’re getting maybe 16 hours of real output. Two full days, gone.

After years managing engineering teams — at TaskRabbit, at Google — the pattern holds consistent across companies, team sizes, and seniority levels. Smart people sit down to write code, get interrupted, attend a meeting that should have stayed a doc, get interrupted again; by 4pm the day has accomplished roughly nothing.

The “6th day” concept works like this: reclaim 8 of those lost hours through deliberate habits, and the week gains a full extra workday. Not by working longer. By working differently.

The Context Switching Tax #

Paul Graham wrote about the maker’s schedule versus the manager’s schedule back in 2009. Thirteen years later, most engineering organizations still operate as if every engineer is on a manager’s schedule.

A single meeting in the middle of a 4-hour block doesn’t cost you one hour. It costs you the entire block. The context switch penalty before the meeting — deep work stops 20 minutes early because why start something complex — plus the ramp-up time after (another 15-20 minutes to reach flow state again) means a 30-minute meeting actually consumes over an hour of productive time.

Last year, after tracking meeting patterns across the team for a full quarter, the numbers confirmed the hunch. Engineers with 3+ meetings scattered across their day produced roughly 40% less code output than engineers with the same number of meetings batched into a single half-day. Same total meeting time. Radically different output.

Protect Your Mornings (Or Whatever Your Peak Hours Are) #

Mornings work best for me. My best thinking happens between 8am and noon. So I block those hours aggressively — no meetings, no Slack, notifications off. The team knows the deal. The calendar enforces the boundary.

But most people get the wrong thing about time blocking: the block itself barely matters. The edges matter.

The 15 minutes before your deep work block starts — that narrow window most people squander on email — exist for one reason: deciding exactly what to work on. Not vaguely, the way you’d say “I’ll work on the auth service” while the morning slips away. Specifically: “I’m going to implement the token refresh logic in the middleware layer, starting with the test cases.” Specificity eliminates the worst productivity killer of all, sitting down and burning 30 minutes just figuring out what to do.

Cal Newport covers the concept in “Deep Work” and gets the core right; he undersells how much the preparation phase matters, though. Blocking time takes five minutes. The on-ramp kills people.

The Meeting Audit #

Every quarter, the engineers on the team face an uncomfortable exercise: list every recurring meeting on the calendar and justify each one. Not “this meeting exists because it’s always existed.” An actual justification for attending.

Last time we did this, we cut 4.5 hours per week per engineer. Four and a half hours. More than half a workday, recovered by one question: “does attending this meeting change anything?”

Some rules that help:

• If you’re not speaking or making a decision, you don’t need to attend. Read the notes after.
• Status updates belong in async documents, not synchronous meetings. We use a shared doc that everyone updates by 10am Monday. The “standup” is reading the doc.
• Any meeting without an agenda gets declined. No exceptions. If the organizer fails to articulate the ask in advance, the meeting lacks a reason to exist.
• 25-minute meetings instead of 30. 50 instead of 60. The Parkinson’s Law thing is real; meetings expand to fill their allotted time.

Does this make me unpopular with some people? Probably. But the team ships faster than most teams twice the size; engineers go home at reasonable hours. Worth the trade.

Batch Your Communication #

Slack is engineered to make you responsive. Every ping, every red badge, every “someone typing…” animation yanks an engineer out of whatever occupied the last 45 minutes of focus. It’s a brilliant product for collaboration and a terrible product for concentration.

My approach — which took about three weeks to feel anything close to normal — I check Slack three times a day. Morning (when I start), after lunch, and end of day. Three windows. Done. A Slack status explains the schedule. The world has not ended.

Email gets the same treatment. Twice a day — morning and afternoon. If something is truly urgent, people call. In three years of doing this, I’ve received maybe four genuinely urgent calls. Four.

The anxiety about missing something important is almost entirely imagined. I say “almost” because once, I did miss a time-sensitive message from a VP. I responded two hours late. Nothing bad happened. Artificial urgency, as usual.

The “Default No” Policy #

The single biggest productivity shift came from defaulting to “no” for anything that fails to advance the week’s priorities.

New Slack channel invitation? No. Optional brown bag session? Usually no. “Quick sync” with someone three levels removed from the actual project? No.

Sounds harsh, right? The opposite, actually. Saying no respects everyone’s time — including the person who asked. Every “yes” to something low-priority steals a “no” from something that actually matters. Cal Newport calls the phenomenon “attention residue”; once the pattern clicks, the old way of working looks insane.

A running list of the week’s top 3 priorities lives on a sticky note next to the monitor. When a request comes in, the list gets checked. If the request fails to connect to one of those three priorities, the default answer stays no — unless a genuinely compelling reason surfaces.

Finding Your 8 Hours #

Here, broken down by what I’ve actually tracked working across multiple teams, is where those 8 hours come from:

• Meeting audit: 3-5 hours recovered per week—often the single biggest gain
• Communication batching: 1-2 hours (conservative estimate)
• Eliminating decision paralysis through pre-planned deep work blocks: 1-2 hours
• Default “no” policy: 1-2 hours of avoided low-value commitments

That’s 6-11 hours per week. Call it 8 on average. A full workday.

Simple math. The discipline? Brutal. Every one of these habits requires saying no to things that feel productive in the moment but aren’t. Meetings feel productive. Slack conversations feel productive. Constant “availability” feels responsible.

Actual output doesn’t care how busy you felt. Output cares about uninterrupted hours spent on the thing that mattered most.

Go find that 6th day. The hours already sit in the calendar — buried under meetings nobody needs.