If you track your time honestly for one week, the number you find is usually embarrassing. Email. Slack. A quick check-in here, a status update there. A 15-minute call that could have been a two-sentence message. By 2pm, you’ve been “working” for six hours and haven’t produced anything that directly moves a client project forward.
This is the shallow work trap, and it’s not a discipline problem. It’s a structural one. When your calendar has no explicit protection for deep work, shallow work fills every gap, because shallow work is always knocking on the door and deep work is not.
The 60/40 ratio isn’t aspirational. It’s the minimum threshold at which a solo service business actually functions well. Below 60% deep work, your output suffers, your prices feel hard to justify, and you’re always behind. The fix is architectural, not motivational.
What the 60/40 Ratio Looks Like in a Real Workday
For an 8-hour day, 60/40 means:
- Deep work: 4.8 hours (round to 4.5–5 hours)
- Shallow work: 3.2 hours (round to 3–3.5 hours)
Here is the sample daily schedule that achieves this:
| Time | Activity | Type |
|---|---|---|
| 8:45–9:00 | Setup: review today’s single top priority | Transition |
| 9:00–9:30 | First email block (inbox triage only) | Shallow |
| 9:30–11:30 | Deep work block 1 | Deep |
| 11:30–11:45 | Break (no phone, walk or stretch) | , |
| 11:45–1:15 | Deep work block 2 | Deep |
| 1:15–2:00 | Lunch + actual break | , |
| 2:00–2:45 | Calls, client check-ins, admin | Shallow |
| 2:45–3:00 | Second email block | Shallow |
| 3:00–4:30 | Deep work block 3 | Deep |
| 4:30–5:00 | Admin, invoicing, close-of-day ritual | Shallow |
That gives you 5 hours of deep work (62%) and 3 hours of shallow (38%). The key structural move: deep work starts at 9:30, after a contained 30-minute email window, not after “checking in” until 11am.
The Three Most Common Inversion Patterns
Most solos don’t fail at deep work through laziness. They fail through three specific patterns:
Pattern 1: Morning inbox death spiral. You open email at 8am to “just check.” One question requires a quick reply, which opens a browser tab, which surfaces a Slack message, which leads to a 20-minute thread. It’s 10am and the deep work block never started.
Fix: No email before 9:30am. Period. Set your first deep work block before you open the inbox. Even 60 minutes of early deep work before email shifts the day significantly.
Pattern 2: Availability signaling. You respond to messages within minutes because you’re afraid clients will perceive you as unresponsive. This keeps you in shallow mode because every notification is a potential priority.
Fix: Response-time expectation setting. Tell clients explicitly: “I respond to messages twice daily, mid-morning and mid-afternoon. For genuine urgency, [phone/text].” Most clients accept this immediately. None of them actually needed you to respond in 4 minutes.
Pattern 3: Undifferentiated calendar. Your calendar shows meetings and calls but no deep work blocks. Without a scheduled block, deep work doesn’t happen, it gets crowded out.
Fix: Calendar blocks for deep work, treated as meetings with yourself. Mark them as “Busy” in your shared calendar. If someone asks, “I have a client deliverable block” is a complete answer.
The Three Friction Removes That Make It Sustainable
Getting to 60/40 for one week is easy. The difficulty is sustaining it when clients push, projects spike, and your inbox hits 80 unread. These three friction removes address the structural causes of backslide.
Friction Remove 1: Auto-reply that handles urgency without you.
Set an email auto-responder during deep work blocks:
“I’m in a focused work block until [time]. I’ll respond to your message by [time]. If this is urgent, [phone number or signal] reaches me directly.”
This does two things: it resets response-time expectations, and it filters actual urgency (someone picks up the phone) from false urgency (someone can wait but hasn’t said so). In practice, the phone almost never rings.
Friction Remove 2: Pre-made decisions for common shallow work.
Every time you spend 5 minutes deciding whether to do a task now or later, you’ve already lost 5 minutes of cognitive energy. Solve this once:
- Billing: every invoice goes out same-day the project milestone is hit, no exceptions
- File organization: every deliverable goes in [Client] > [Project] > [Date] immediately
- Proposals: template first, customize second, never build from scratch during a shallow window
- Recurring reports: fixed template, fixed send day, fixed format
When shallow work has a pre-made decision, it takes 50% less time to execute.
Friction Remove 3: Async by default, calls by exception.
Every time you agree to a call that could have been a three-paragraph message, you’re spending 30–60 minutes (including prep and re-entry) instead of 10.
The rule: before scheduling any call, ask “Can this be answered in writing in under 10 minutes?” If yes, write it. If no, schedule the call and keep it to 20 minutes with an agenda. Apply this to inbound requests too, when someone asks to “hop on a quick call,” respond: “Sure, what’s the main question? I might be able to handle it in a message and save us both the call.”
Shallow work expands to fill available time because it’s reactive, visible, and socially reinforced, responding fast feels professional. Deep work only happens when you protect it explicitly. The calendar is the policy, not the discipline.
What the Reversal Produces
When solos actually reach 60/40 for 30 consecutive days, the outputs are consistent:
More deliverables per week. Deep work blocks produce 2–3x more output than the same clock-hours scattered across shallow windows. A 4-hour uninterrupted writing session produces more than 8 hours of interrupted writing.
Higher quality work. Shallow-mode work is reactive and surface-level. Deep-mode work allows you to hold a complex problem in working memory long enough to reach non-obvious solutions. Clients notice the difference even when they can’t name it.
Lower end-of-day exhaustion. This is counterintuitive but consistent: a day of deep work feels more satisfying and less draining than a day of shallow work, even though deep work is harder. Decision fatigue from constant shallow context-switching is more depleting than focused cognitive effort.
Easier pricing. When you’re producing visibly higher-quality work in half the clock time, raising rates becomes straightforward. You’re not “charging more”, you’re charging for the concentrated expertise that shows in the output.
The 30-Day Implementation Path
Don’t try to go from 30% deep to 60% deep in one week. The failure mode is attempting a complete restructure, running into one client emergency that blows up the schedule, and abandoning the whole system.
Instead:
Week 1: Add one protected deep work block per day (9:30–11:30am). Don’t change anything else.
Week 2: Add the second email block protocol (9am and 3pm only). Set the auto-responder.
Week 3: Extend the morning deep work block to 9:30–1pm (3.5 hours). This is your core deep work investment.
Week 4: Add a third deep work block (3–4:30pm) after the afternoon email check. This gets you to the full 60/40 target.
Track your deep work hours in a simple spreadsheet, just the start and end time of each block, daily. After 30 days, look at the trend line. The number you see will be more motivating than any framework.
You cannot reach 60% deep work by trying harder in the existing structure. The structure has to change. Protect the blocks first. The motivation follows the results, not the other way around.
The One Metric That Tells You If It’s Working
After 30 days, answer this: how many significant client deliverables did you complete in the last week? Count only work that directly advanced a client project, not emails about it, not calls about it, not admin around it. The actual work.
If you’re at 60/40, that number should be noticeably higher than it was at 30/70. If it’s not, you have a prioritization problem inside your deep work blocks (doing the wrong things in the right blocks), which is the next problem to solve.
But most solos who do this honestly find the number is dramatically higher, and the deliverables are better. That’s the case for the restructure. Not productivity as a virtue, but output as a business result.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
