Opening: The Day You Worked All Day and Built Nothing
Friday, six in the evening. As you close your laptop, you might have a thought like this: "I clearly worked nonstop today, so what on earth did I actually make?"
You answered Slack threads, sat in three meetings, processed five code reviews, and emptied your inbox. You were definitely busy. And yet the thing that was supposed to be this week's goal — "refactoring the payment module" — has not advanced a single line. It slips to next week again.
This experience is not a problem of laziness. If anything, the more diligent you are, the more often it happens. The problem is that we spend our days in finely shattered fragments. Each fragment looks meaningful on its own, but gathered together they build nothing.
This piece is not a sermon to "work harder." I want to treat focus not as a problem of willpower but as a problem of design. Starting from Cal Newport's concept of deep work, I will go through, concretely, how expensive context switching actually is, how to secure focus blocks, and how to protect focus not alone but at the level of the whole team.
Let me say one thing up front. This piece is wary of exaggerations like "do a digital detox and your life will change." Focus is not a cure-all, and not every task needs to be deep work. But if we lose the ability to protect deep work, we slowly become more and more replaceable. Let us talk about how to get that ability back into our hands.
1. Deep Work and Shallow Work
Start With a Clear Definition
Cal Newport divides work into two kinds.
- **Deep Work**: activities performed in a state of high cognitive demand, through distraction-free concentration. It creates new value, improves your skill, and is hard to replicate. Examples: designing a complex algorithm, writing, root-cause analysis of a difficult bug, learning a new domain.
- **Shallow Work**: logistical-style tasks that are low in cognitive demand and can be done even in a distracted state. They are easily replicated and create little new value. Examples: replying to email, Slack chatter, scheduling, perfunctory meetings.
There is one thing not to misunderstand here. Shallow work is not bad. For a team to function, someone has to coordinate schedules and answer questions. The problem is the **ratio at which shallow work crowds out deep work**. If a day is filled only with shallow work, we are busy but do not grow.
Measure Your Own Ratio First
Instead of an abstract resolution, I recommend logging just one week. One line every hour: note only whether the thing you just did was deep or shallow.
[Focus Log — Tuesday]
09:00 deep payment refactor design (2 interruptions)
10:00 shallow Slack, email, standup
11:00 shallow hiring interview
13:00 deep refactor implementation (5 interruptions -> effectively shallow)
14:00 shallow meeting: quarterly OKR alignment
15:00 shallow meeting: design review
16:00 deep bug tracking (3 interruptions)
17:00 shallow PR review + Slack
Deep time (few interruptions): about 1.5 hours / 8 hours
Most people are shocked the first time they do this log. Out of an eight-hour day, the truly deep time is often only one or two hours. If you do not measure, you are left only with the feeling that "I was busy today," and you cannot tell what to change.
2. Context Switching: The Real Cost Is Hidden
The Price of "Let Me Just Check Real Quick"
The biggest enemy of focus is not the long interruption. It is the "quick" one. A single Slack notification, a "just one question" tap over your shoulder, an email preview alert.
The problem is not the length of the interruption itself but **the time it takes to return to the original task**. Gloria Mark and her team at the University of California, Irvine have repeatedly reported that once you are interrupted, it takes more than twenty minutes on average to fully return to the original task. A thirty-second Slack reply therefore becomes, in reality, a twenty-minute loss.
Context-switching cost diagram
Deep flow state
|
| ############ (flow curve fills slowly, takes about 15-20 min)
| ##
|##
+---------------------------------------------> time
^ Slack notification (30-second interruption)
|
v flow collapses
Start over from scratch:
|
| ############ (15-20 min to re-accumulate)
| ##
| ##
+---------------------------------------------> time
Real loss = not 30 seconds, but broken flow + re-accumulation time
Multitasking Is an Illusion
Synthesizing many studies, the American Psychological Association (APA) concludes that people do not truly process tasks "simultaneously"; they merely switch rapidly. And every switch incurs a "switching cost." The more often you move between tasks, the longer the total time and the higher the error rate.
In other words, "I'm good at multitasking" usually means "I'm used to switching often," and that familiarity is not efficiency but cost.
3. How to Secure Focus Blocks
The Core Principle: Time You Do Not Block Off Disappears
Empty time on your calendar is not "free time"; it is "time not yet taken from you." The moment someone books a meeting, it vanishes. So focus time must be **explicitly reserved on the calendar**, just like a meeting.
[Focus Block Calendar Example — Maker Mode]
09:00 - 11:30 [LOCKED] focus block (payment refactor)
. Slack quit, notifications blocked
. phone in another room
11:30 - 12:00 shallow work batch (Slack/email all at once)
12:00 - 13:00 lunch + walk (recovery)
13:00 - 15:00 [LOCKED] focus block (bug root cause)
15:00 - 16:00 meeting batch (design review, 1:1)
16:00 - 16:30 shallow work batch
16:30 - 17:30 [LOCKED] focus block (light implementation / docs)
17:30 - 18:00 prep for tomorrow + shutdown ritual
Three things are key in this schedule. First, focus blocks are made long enough — roughly 90 minutes to 2 hours. A 30-minute one ends just as you finish warming up. Second, shallow work is batched rather than scattered. Third, recovery time is deliberately included. Focus is not a resource you can draw on without limit.
Start With a Small Commitment
If you try to block four hours of focus per day from the start, you will almost certainly fail. Realistically, it is better to start with one 90-minute block per day. Once that holds for two weeks, grow it to two. Focus is like a muscle: if you suddenly overload it, you get hurt.
Start Ritual and Shutdown Ritual
Short routines for opening and closing a focus block are surprisingly effective.
[Start Ritual — 2 minutes]
1. Write the single goal of this block in one sentence
e.g., "Handle all boundary conditions of the payment retry logic"
2. Close all unrelated tabs
3. Put your phone out of sight, quit Slack
4. Start a 90-minute timer
[Shutdown Ritual — 3 minutes]
1. Record in one line where you stopped (to return quickly next time)
2. If you hit a wall, write it down as a question
3. Pre-write the first action of the next block
In particular, the shutdown ritual's "one line on where you stopped" greatly reduces the restart cost of the next focus block. When you sit back down, you will not spend five minutes wandering, asking "what was I doing again?"
4. Managing Notifications and Meetings
Notifications: Invert the Default
Most apps default to "notify everything immediately." Leaving that default as-is is like handing control of your attention over to the app's developers. You have to invert the default.
[Notification Audit Checklist]
[ ] Slack: turn off desktop notifications, allow only mentions/DMs
[ ] Slack: "Do Not Disturb" mode during focus blocks
[ ] Email: disable push entirely, check only 2-3 times a day
[ ] Phone: focus mode during work hours (only calls/urgent pass)
[ ] Phone: turn off all red badge numbers on the home screen
[ ] Calendar: keep only the 10-minutes-before meeting alert
[ ] Browser: block all web push notifications
The key is to face the fear of "what if I really miss an urgent message?" In reality, truly urgent things come by phone. Ninety-nine percent of Slack notifications are things that would be perfectly fine to answer two hours later.
Meetings: Make Your Default Stance "Decline"
Meetings not only eat time, they also chop your calendar into pieces and destroy the focus blocks in between. A single 11 a.m. meeting can render the entire four hours from 9 to 1 useless.
When you receive a meeting request, build the habit of asking the following.
[Questions Before Accepting a Meeting]
- What is this meeting's decision? (If there is no decision, a doc is enough)
- Do I have to be there, or do I just need to know the outcome?
- Can it be replaced asynchronously (doc/comments)?
- Can it be cut to 30 minutes? (Most 1-hour meetings can be)
If declining is hard, it helps to prepare a polite but clear phrasing in advance.
[Dialogue Example — Politely Declining a Meeting]
Colleague: "Are you free for a roadmap-alignment meeting at 11 tomorrow?"
Me: "That's my focus block, so after 1 p.m. would be better if possible.
If you write up just the items to be decided in a doc, I'll leave
my thoughts as comments first. If we still need a synchronous
discussion, let's grab 30 minutes at 1:30."
The key in this phrasing is not the refusal but the **alternative offered**. When you say "here's a better way" rather than "no," you can protect your focus without harming the relationship.
5. Designing the Physical and Digital Environment
Change the Environment Rather Than Willpower
Trying to protect focus through willpower usually fails. Human willpower is a finite resource, and if you fight temptation every moment, you have no energy left for the work itself. The better strategy is **designing an environment that keeps temptation away in the first place**.
[Physical Environment Checklist]
[ ] Phone in another room/bag, not on the desk
[ ] Clear the desk of anything unrelated to the current task
[ ] Block out noise (noise-canceling or steady white noise)
[ ] If possible, separate a "focus seat" from a "meeting/errand seat"
[ ] Pour a glass of water in advance (fewer excuses to leave your seat)
[Digital Environment Checklist]
[ ] Close tabs/apps unrelated to the task
[ ] Separate a focus browser profile (minimal bookmarks/extensions)
[ ] Time-block distracting sites (only during focus hours)
[ ] Tidy the desktop wallpaper (remove visual noise)
[ ] Empty the notification center (turn off badges/popups)
Build a Signal
The brain is sensitive to contextual cues. If you repeat a signal that says "now it is time to focus" — the same music, the same cup of tea, the same seat — then over time that signal alone helps you enter focus mode faster. This is not superstition but conditioning. It need not be grand; it just needs to be consistent.
6. Maker's Schedule and Manager's Schedule
Two Kinds of Time Collide
In his essay "Maker's Schedule, Manager's Schedule," Paul Graham offers a decisive insight. There are two ways of handling time in the world.
- **The Manager's Schedule**: the day is chopped into one-hour units. Meetings are the work. If an hour opens up, you just fill it with a meeting. For a manager, this is natural.
- **The Maker's Schedule**: making work — like writing and programming — requires solid blocks of at least half a day. An hour-long sliver can effectively build nothing.
The problem arises when these two collide within one organization. A 30-minute meeting that a manager casually drops into the middle of the afternoon destroys half a day for a maker. To the manager it is a one-eighth cost; to the maker it is the cost of everything they could have built that day.
| Aspect | Manager's Schedule | Maker's Schedule |
| --- | --- | --- |
| Time unit | 1 hour | Half a day or more |
| Meaning of a meeting | The work itself | An interruption to making |
| A meeting mid-day | Small cost | Destroys a solid block |
| The ideal day | Densely packed with meetings | Long focus + batched meetings |
| Typical roles | Managers, executives | Developers, writers, designers |
How to Let the Two Schedules Coexist
The key is not to blame one side as wrong, but for the organization to acknowledge that the two schedules are different.
[Coexistence Strategy]
- Cluster meetings at the two ends of the day (early morning or late afternoon)
- Designate a "no-meeting day" or "no-meeting morning"
- Makers block their morning as a focus block on the calendar in advance
- Managers respect the other person's focus block before booking a meeting
- Async-first: if only a decision is needed, use a doc + comments
Paul Graham's insight, reduced to one sentence: never forget that asking a maker for a single meeting may be asking not for an hour, but for the entire afternoon.
7. Digital Minimalism
Subtraction, Not Addition
In his follow-up, Digital Minimalism, Cal Newport says the problem is not technology itself but **the lack of intention in the relationship we form with it**. When we install a new app, we do not ask "what value does this provide"; we install it for the weak reason "this might be useful someday." Those weak reasons accumulate and finely gnaw away at our attention.
Digital minimalism is not an asceticism that tells you to cut off all technology. Rather, it is **intentionally choosing a few tools and using them deeply**.
[Digital Tool Audit — Once a Quarter]
For each app/service, ask:
1. Does this directly support a value I genuinely care about?
2. Is it the best way to serve that value, or am I just used to it?
3. How should I use it so the value survives and the cost shrinks?
(e.g., do not quit social media; limit it to twice a week on desktop)
-> If the answer to #1 is "no," delete it boldly
Practicing Tolerance for Boredom
The enemy of focus is not only distraction. It is **the habit of not tolerating boredom for even a second**. The 30 seconds waiting for an elevator, the 2 minutes in line, the moment waiting for a light — we fill every one of those gaps with the phone instantly. Once the brain learns "gap equals instant stimulation," the ability that deep work demands — "to endure boredom and stay with a single problem" — weakens.
The solution is simple. Practice not pulling out your phone in small gaps. The muscle that endures that brief boredom is the same muscle that does not flee in front of a hard problem.
8. Measuring Focus
By Data, Not by Feeling
The feeling that "I focused well today" cannot be trusted. We often confuse a busy day with a productive one. So light measurement is needed. No grand tools are required.
[Weekly Focus Scorecard]
Focus blocks planned this week : 10
Focus blocks actually kept : 6 (60%)
Avg interruptions per block : 2.3
Main sources of interruption : Slack(5), over-shoulder questions(4), meetings(3)
"Deep outputs" this week : payment refactor done, 1 design doc
One improvement for next week:
-> Experiment: quit Slack entirely during the morning focus block
The value of this scorecard is not the score itself but the "one improvement for next week." If you change just one variable each week, you can tell what works. If you change ten things at once, you will never know which one worked.
Know the Trap of Measurement Too
It is a problem when measurement itself becomes a compulsion. Some people fail to focus precisely because they are busy tracking their focus time by the minute. Keep measurement light — a once-a-week retrospective is enough. Numbers are a compass that tells you direction, not a whip.
9. Team-Level Agreement
There Is a Limit to Focus Alone
No matter how diligently an individual turns off notifications and books blocks, if the team culture is "ignore anyone who doesn't reply within five minutes," it eventually collapses. Focus is an individual skill and at the same time a **team protocol**. The most effective change happens at the team level.
[Team Focus Protocol Example]
1. Make response expectations explicit
- Slack is async. Instant replies are not the default.
- Truly urgent matters go only via phone/separate channel.
- For normal messages, "reply within the day" is the standard.
2. Protect no-meeting time
- Every day from 9 to 12 is jointly protected as "focus time."
- Meetings in this window only for genuine emergencies.
3. Meeting hygiene
- Every meeting states an agenda and purpose. No agenda, no meeting.
- Default 30 minutes. One hour requires justification.
4. Async-first
- Decisions are recorded in docs.
- Notes and decisions are written so anyone can catch up later.
The Conversation to Introduce a Protocol
Such protocols provoke pushback if forced from above and fizzle out if left alone. It is better to propose them as small experiments.
[Dialogue Example — Proposing Focus Time to the Team]
Me: "Lately there are so many meetings in the morning that deep,
dig-in work keeps slipping to the afternoon. As a two-week
experiment, what if we don't book meetings from 9 to 11 a.m.?"
Lead: "What if something urgent comes up?"
Me: "Urgent things can go by phone. When we look back in two weeks,
if it's not working we'll just revert. It's a low-downside experiment."
The key is to propose it not as a "permanent rule" but as a "reversible two-week experiment." People resist permanent change but agree to experiments relatively easily.
10. A Concrete Practice Plan (4 Weeks)
So this does not end as mere words, here is a gradual one-month plan. Do not try to change everything at once. It collapses.
[Week 1 — Measurement and Awareness]
- Write a focus log daily (one line per hour: deep/shallow)
- Apply the notification audit checklist, first pass (start by turning off Slack desktop alerts)
- Goal: understand how your day actually flows
[Week 2 — Your First Focus Block]
- Reserve one 90-minute morning focus block on the calendar daily
- Introduce the start ritual / shutdown ritual
- Put the phone in another room
- Goal: the habit of keeping one block a day
[Week 3 — Meetings and Environment]
- Apply the 4 questions before accepting a meeting
- Politely decline meetings / try async replacement
- Apply the digital and physical environment checklists
- Goal: reduce sliver-time on the calendar
[Week 4 — Team and Measurement]
- Propose a "2-week no-meeting morning" experiment to the team
- Write a weekly focus scorecard
- Decide one improvement variable for next month
- Goal: extend an individual habit into a team protocol
Each week has exactly one goal. One variable per week. This pace may feel frustratingly slow, but the attempt to change everything fast is ultimately the slowest. Because it repeats the cycle of collapsing and starting over.
Common Traps
Let me flag in advance the traps people often fall into when trying to design focus.
First, **the greed to turn every task into deep work**. Shallow work is needed too. If you treat answering a colleague's question or coordinating a schedule as a sin, collaboration breaks. The goal is not the eradication of shallow work but an appropriate ratio.
Second, **tool-collecting addiction**. People keep switching focus apps, timer apps, time-tracking apps, hunting for the "perfect system" and failing to actually focus. The simpler the tool, the better. A single sheet of paper and a timer are enough.
Third, **the vicious cycle of guilt**. The pattern of breaking a focus block once and then giving up entirely, muttering "see, I just can't." There will always be days you break it. What matters is starting again the next day, not a flawless unbroken streak.
Fourth, **mistaking burnout for focus**. Working deeply without rest does not last. Recovery is not the opposite of focus but a part of it. Walks, enough sleep, and time spent blankly are the fuel for the next bout of focus.
Closing: Focus Is a Disappearing Ability, and One You Can Reclaim
The ability to focus deeply is becoming ever rarer. In an age when everyone is distracted, simply being able to stay with one thing for a long time becomes a major differentiator. This is not merely a matter of productivity but of what work we can build, and of who we become in the process.
At the same time, there is no need to become overly grave. Focus is not a badge of moral superiority. Some days are full of shallow work; on some days recovery matters more. Balance is the key.
But one thing is clear. The ability to protect deep work is not maintained on its own. Notifications grow ever cleverer, and calendars try to chop themselves into ever finer pieces. Standing against that current — deliberately blocking off time, designing the environment, and agreeing with the team — that is focus design for people who make things.
Choose one thing you can do today. Block off 90 minutes tomorrow morning on your calendar. That single block is the first step back toward being someone who makes things again.
References
- Cal Newport, "Deep Work" (author page and resources): https://www.calnewport.com/books/deep-work/
- Cal Newport, "Digital Minimalism": https://www.calnewport.com/books/digital-minimalism/
- Cal Newport blog (many essays on focus and productivity): https://www.calnewport.com/blog/
- Paul Graham, "Maker's Schedule, Manager's Schedule": https://www.paulgraham.com/makersschedule.html
- American Psychological Association, the cognitive cost of multitasking: https://www.apa.org/topics/research/multitasking
- Gloria Mark, "Attention Span" (author page): https://gloriamark.com/
- Harvard Business Review, collected pieces on attention and focus: https://hbr.org/topic/subject/attention
- Will Larson (lethain), engineering time management and focus: https://lethain.com/
현재 단락 (1/210)
Friday, six in the evening. As you close your laptop, you might have a thought like this: "I clearly...