In 2019, Basecamp had a problem that hits most growing tech companies. Their product team went from a few people to dozens. Quick talks in the hallway became endless Slack messages. Simple features that used to take days now took months.
Ryan Singer, their Head of Product Strategy, saw something scary: their best developers spent more time dealing with interruptions than writing code. One lead developer tracked his day and found he switched tasks 47 times before lunch.
Basecamp's fix became a method called Shape Up. They completely changed how teams work. They moved to six-week cycles with zero interruptions. No daily standups. No status updates during work time. Just focused work.
Here's what most people missed about Basecamp's change: they didn't just fix their interruption problem. They found something that became their edge. While other companies burned out senior talent with constant task-switching, Basecamp made a place where experienced engineers could do what they do best—think deeply about hard problems.
You have the same chance today. Not to change your whole company, but to become the tech lead who ships stuff while everyone else sits in meetings.
The Focus Problem We're All Stuck In
Recent studies show knowledge workers get interrupted every 2-4 minutes. Microsoft found people face 275 interruptions per day—one every two minutes. We never actually get your focus back. We're always partly distracted, like a computer trying to run too many programs at once.
But here's the insight everyone misses: in an environment where nobody can focus, the person who can protect even two hours of deep work has an almost unfair advantage. You don't need to be smarter or work harder. You just need to work differently while everyone else deals with constant interruptions.
The question isn't whether switching between tasks is killing your productivity—it obviously is. The question is whether you'll be one of the few who does something about it.
Why We Let Ourselves Get Interrupted
Let's be honest about something uncomfortable: part of us allows this pattern. Being the person everyone comes to for answers feels good. When someone says "you're the only one who knows this," it gives you a rush. We become the tech expert everyone needs, and experts are always wanted.
But there's a hidden cost: while you're answering the same questions over and over, someone else is learning the next technology. While you're in your fifth meeting today, someone else is shipping the feature that gets them promoted. While you're proud of being "helpful," someone else is building systems that make them impossible to replace.
This pattern isn't totally our fault—modern workplaces are built to break up your attention. Research shows that when people get constantly interrupted, they do work faster but feel much more stressed, frustrated, and tired. We try to make up for broken focus by rushing, but we pay the price in health and quality work.
The System Is Broken (That's Your Chance)
Modern software development is built to prevent deep work:
The Agile system makes sure you get interrupted every two hours (standup, grooming, retro, planning). The collaboration theater makes interrupting easier than looking things up yourself. The hero culture rewards people who fight fires instead of preventing them. The flat organization means everyone can interrupt everyone.
This isn't a mistake—it's on purpose. Companies have optimized for feeling productive instead of being productive. They've mixed up being busy with making progress, working together with creating things.
But here's the thing about broken systems: they create chances for people who can work around them smartly. While your coworkers fight daily fires, you can slowly build systems that don't catch fire. While they go to every meeting, you can find ways to contribute meaningfully while protecting some focus time.
The game has rules that don't help deep work. Once you accept that, you can start playing more smartly.
The Daily Setup That Actually Works
Forget complex productivity systems. Here's what actually works in real workplaces:
The Night-Before Setup (5 minutes before leaving)
Tomorrow's first two hours are decided today. Before you close your laptop, write three specific things:
The ONE thing that, if you finish it, makes tomorrow a win
The first line of code you'll write (or the first paragraph, or the first design choice)
How you'll protect this work
This stops morning decision tiredness. You wake up knowing exactly what to do.
The Morning Block (First 90-120 minutes, when possible)
Phone in another room (or airplane mode)
Slack closed (not just minimized—closed)
Calendar blocked as "Deep Work: [Specific Thing You're Making]"
ONE browser tab open (docs only)
ONE problem to solve
Start before checking any messages when you can. This isn't about willpower—it's about setting up your space when you can control it.
The Message Batches (30 minutes, twice daily)
11:30 AM: Handle all morning messages
3:30 PM: Handle all afternoon messages
People slowly learn your schedule. The urgent stuff finds another way. The non-urgent stuff often fixes itself.
The Three-Task Reality
Each day has three big tasks maximum. Not ten. Not five. Three. Everything else is either a two-minute task (do it now) or tomorrow's problem (add to tomorrow's three). This isn't limiting—it's accepting what's actually possible when you get interrupted every few minutes.
The Scripts That Actually Protect You
These aren't just polite ways to say no. They're smart responses that make you look more professional, not less available:
For the Slack "Quick Question": "Great question. I'm deep in [specific thing] until [specific time]. I'll give you a detailed answer then, or if it's blocking you right now, try [documentation/person/channel]."
You've acknowledged, set expectations, and provided alternatives. Nobody can fault this.
For the Meeting Without Agenda: "I want to make sure I'm prepared to contribute. Could you share what decisions we need to make? If it's mainly updates, I can share mine async and join for the decision part."
You're not declining—you're optimizing everyone's time.
For the Drive-By Interruption: "Perfect timing—I have something to sync with you about too. Let me finish this thought [gesture at screen] and I'll find you at [specific time] so we can cover everything properly."
You've turned their interruption into a scheduled sync that you control.
The Physical Signs That Matter
Your workspace teaches people how to treat your attention:
The Headphone System
No headphones: Available
One ear: Only for important things
Both ears: Emergency only
Big over-ear headphones: Don't interrupt unless the building is on fire
The Status System
🔴 Deep Work until [time] - Will respond then
🟡 In meetings - Text preferred
🟢 Available for questions
The Interrupt Log
Keep a visible notebook. When interrupted, clearly write down the time and topic before responding. Don't be aggressive—just make it visible. After a week, share the data: "I tracked my interruptions to understand how to be more helpful. I'm getting interrupted every 3 minutes on average. How can we make this work better?"
Data changes conversations that complaints never could.
When This Makes You More Valuable (Not Less Available)
Here's what people get wrong about boundaries: they think being less available makes you less valuable. The opposite can be true, but only if you use the protected time well.
For every hour of protected time, try to make something visible:
Documentation that prevents future interruptions
Systems that work without you
Features that actually ship
Decisions that unblock others
The formula is: Protected Time + Visible Output = More Respect. Protected time alone can make people mad if you don't handle it thoughtfully.
When you ship that critical feature during your focused time while others are in their third meeting, people notice. When your code reviews are thoughtful because you had time to think, people notice. When you're calm in the afternoon because you got something meaningful done in the morning, people notice.
The Step-by-Step Plan
Don't announce a productivity makeover. Start small:
Week 1-2: Wait 15 minutes before responding to Slack. Write better answers.
Week 3-4: Block one morning for "Project Work." Deliver something visible.
Week 5-6: Add a second focus block when your schedule allows. Share what you built.
Week 7-8: Start your message batches when possible. Document the time saved.
Week 9-10: Add informal office hours. Watch non-urgent questions go down.
Week 11-12: You're now protecting some focused time weekly and shipping more than before.
The key: Make every boundary earn its keep through visible output, and adjust based on what you can actually control.
When Not to Do This (The Reality Check)
Don't do this if:
You're on a performance plan or probation (survive first)
You're in your first 90 days (show up first)
Your manager clearly values being present over getting things done (document everything, think about options)
You're at a real early startup where everyone does multiple jobs
You're already burned out (recover first, optimize later)
Be careful if:
You don't have much political power in your organization
You have a new manager (test the waters slowly)
Your company is in crisis mode (be visibly helpful first)
Your job requires real real-time availability (adjust your approach)
Your ability to set boundaries often matches how hard you are to replace and your relationship with your manager. This reality isn't fair, but ignoring it isn't helpful. Build leverage and trust while putting in place sustainable practices.
The Bigger Game You're Actually Playing
Here's what's really happening: this isn't just about productivity. It's about sustainability and skill growth.
Every time you choose deep work over another meeting, you're betting on creating over coordinating. Every protected morning is practice at the kind of thinking that becomes rarer as organizations grow. Every thoughtful boundary is a small step toward work that energizes instead of drains you.
The tech leads drowning in constant interruptions often burn out within a few years. Many leave for management or leave tech completely. Meanwhile, those who find ways to keep focused work time often stay engaged with technology longer, continuing to build, learn, and create.
You're not just protecting your time. You're protecting your long-term relationship with the work itself.
Small Changes, Big Results
Remember that developer with constant task switches before lunch? Today, Basecamp attracts senior talent partly because of their sustainable work practices. They ship sophisticated products with small teams, and their developers often create influential work beyond their day jobs.
Many of their competitors are still burning through talent, still mixing up busy for productive, still wondering why experienced engineers keep leaving.
You face similar choices, just on a smaller scale. You can keep accepting every interruption, slowly watching your technical skills shift toward coordination and away from creation. Or you can start small—maybe just 15-minute response delays—and slowly reclaim some ability to do focused work.
Not because you'll transform your company overnight. Not because you'll eliminate all interruptions. But because in six months, you might find yourself shipping better work while feeling less stressed. While others burn out from constant task-switching, you might remember what drew you to engineering in the first place.
The interruptions won't stop themselves. The meetings won't automatically decrease. The Slack messages will keep coming.
But tomorrow morning, for even 90 minutes, you could close a few apps and tackle something meaningful. You could experiment with being the tech lead who occasionally goes deep while others stay surface-level.
The system has structural problems. But your small corner of it is still yours to influence, within the limits you face.
Your next interruption is probably coming soon. But your next focused session is one small decision away.
Read next: How To Multiply Your Time
(The 5-Second Filter That Saves You Hours)
I always struggled and still struggle with context switching.
I call it: The octopus syndrome 🐙, where I multitask thinking: I will get more things done ✔️
The truth I realized, inspired by your Substack is that: Context switching is useless.
Very relatable. Will try these tips