💡 Core idea
A manager’s real scarce resource is attention. The calendar is a strategy document, whether you meant it to be or not.
You can declare priorities in a slide and then spend the week in rooms that have nothing to do with them. The team will believe the calendar. Seth Godin treats attention as something to protect, not spend by default. That is the right instinct. Your week already has a theory of the job. The work of this chapter is to make that theory intentional.
Audit before you overhaul
Do not redesign your week from a feeling of busyness. For two weeks, tag hours as they actually go: coaching, direction-setting, firefighting, status, individual work, admin. Count them. The usual surprise is how little time lands in coaching and direction, and how much lands in status and interruption.
Spencer Tom is useful here: treat energy, time, and tasks as one system, not only a sequence of meetings. A week that is fully booked and fully depleted is not a well-run week.
Then apply a simple filter to anything that wants a slot: impact, reversibility, and whether only you can do it. High impact, hard to reverse, and only you: that stays. The rest is a candidate to shorten, delegate, write down, or refuse.
Maker time and manager time on the same team
Your team does not live on your schedule. People who need unbroken hours to think, build, or write cannot also be available to you all day. Protect their focus time as a team rule, not as a personal favor. Your own deep work matters too, but their deep work is how the team produces anything worth managing.
Fragmented attention is expensive. In a field observation of information workers, González and Mark (CHI 2004) found that people averaged about three minutes on a continuous task (“event”) and about 11 minutes 28 seconds in a thematically connected “working sphere” before switching. A later simulation of interruption and recovery is a useful way to see how those switches compound; it is a model, not a measured law. The practical point does not depend on a formula: a day of shallow switches will not produce careful work, no matter how full it looks.
Available is not the same as interruptible
Office hours, a written channel for non-urgent questions, and a few focus blocks will do more than an open door that is never actually closed. Being reachable in a crisis is part of the job. Being reachable every five minutes is how you teach the organization that your attention has no price.
Aviv Ben-Yosef argues that chronic overload is often a habit you have trained the company to expect. Saying no belongs in the operating system, not in a once-a-year complaint. Stay SaaSy makes the team-level version of the same point: if everything is urgent, the calendar will never show strategy.
levels.io offers a strong personal case for being deliberately unreachable. Use it as a prompt, not as a rule. Your job includes some availability that a solo founder can decline. The usable idea is narrower: default-on interruption is a design choice, and you can change it.
A weekly cadence, not a heroic week
A sustainable operating rhythm is short and visible:
- Standing 1:1s (their agenda first — see Chapter 9).
- One team meeting with a stated purpose, or none.
- A written priorities memo of at most three items.
- A personal review: where time went, what you will cut, what decisions are still ownerless.
Trade-offs should be explicit. “We are not doing X so that Y can finish” is management. Silent accumulation is how weeks fill with other people’s urgency.
Autonomy still needs a visible trace of the work. Oussama Ammar wants people to have “a lot of freedom,” but also to “understand what is happening without asking six people and becoming a private investigator in my own company.” “Freedom gets fragile when the work is invisible.” His answer is a useful trace — what they tried, what changed, what failed — and a matching duty: if you punish unfinished thought, people will “show me a beautiful fiction.” The weekly memo and the written channel exist for that visibility, not for surveillance.
Tools
- Two-week time audit. Tag hours. Share the pattern with your manager if the shape of the week is imposed from above; some load is not yours alone to fix.
- Priority filter. Impact × reversibility × “only I can do this.”
- Weekly operating cadence. 1:1s, one purposeful team meeting, a short priorities memo, a personal review.
- Focus blocks and office hours. Named, recurring, and actually defended.
🤖 AI-era tip: A weekly leverage report
Once a week, use an approved tool to turn your calendar and meeting notes into a short report: time spent coaching versus firefighting versus status, plus open decisions that still have no owner. You still choose what to cut. Skim the source notes. Summaries soften disagreement and drop commitments. Do not let a tidy report replace your memory of what you actually promised.
Takeaways
- Audit the week before you redesign it; the calendar is already a strategy.
- Protect thinking time for the team, not only for yourself.
- Availability without a design becomes interruption; you may have taught the company to overload you.
- A short weekly cadence beats a heroic, unrepeatable week.
- Saying no is a managerial act, not a personality flaw.
Evidence
- González, V. M., and Mark, G. (2004). “Constant, constant, multi-tasking craziness”: Managing multiple working spheres. CHI 2004. Field observation of 14 information workers: about three minutes on a continuous event, and about 11 minutes 28 seconds in a working-sphere segment, before a switch (about 12 minutes after excluding brief disruptions). People interrupted themselves about as often as they were interrupted.
- Off by One (2025). The math of why you can’t focus at work. A simulation of interruption rate, recovery time, and minimum useful block length — useful as a model, not as an empirical measurement of your team.
- Ammar, O. (@daedalium) (2026). Freedom and the private investigator. Founder post on autonomy with a visible trace of the work; anecdotal.