Your calendar is your strategy

core5-2020-5050-150150+

Whatever you actually spend hours on is your real strategy. Everything else is an aspiration you've written down, and the calendar is the only honest record of which is which.

Also available as a standalone Playbook →

Export last month's calendar and add up the hours by category.

That total is your strategy. Whatever the strategy document says.

Uncomfortable exercise. Also the only honest one available, because intentions are cheap and hours aren't.

A leader who says the priority is engineering quality and then spent four hours on it in a month has communicated their real priorities very clearly to everyone around them, whatever they said at the all-hands.

The organisation reads that calendar, incidentally.

Not literally. But they know what you show up to, what you cancel, and what you ask about.

That's the actual signal, and it's far louder than anything you say out loud.

The audit

Take four weeks. Not one. One week is unrepresentative in whichever direction happens to be convenient for you.

Sort every hour into four buckets.

Reactive. Meetings you were invited to, escalations, unblocking, anything at all you didn't initiate yourself.

Operating. Running the machine. One-to-ones, the weekly leadership session, reviews, decisions.

Building. Work that makes the org better next quarter than it is right now. Hiring, developing people, systems and process work, the thing you keep meaning to fix and never do.

Thinking. Strategy, writing, learning what's actually happening in the organisation, unstructured time to notice things.

TypicalAimReactiveOperatingBuildingThinking
The bucket that disappears first is the one nothing else can replace.

Most leaders doing this for the first time find 60 to 70 percent sitting in reactive, almost nothing in thinking, and are surprised.

The surprise is itself informative. It means the drift happened without anybody deciding anything, which is how it always happens.

What mine looks like

Roughly half my week is protected. Deep work, strategy, writing, thinking. In real blocks, not in the gaps.

Saying it plainly, because it's the sort of claim that sounds aspirational, and if it were aspirational this lesson would be dishonest.

It holds most weeks. It doesn't hold during a crisis, or a raise, or the fortnight after something breaks. I don't pretend otherwise.

What makes it hold isn't discipline. Discipline fails. It's a small number of structural things.

The blocks sit in the calendar as immovable events, made months ahead, treated the same as any other commitment.

Default answer to a meeting request landing on one is no. And the only person who can move it is me.

I run one standing cadence, weekly. Nothing else recurring.

Most calendars fill up with monthly and quarterly ceremonies, each one individually reasonable, and together they eat the week. Refusing to have them at all is the largest single lever on this whole problem.

Decisions get pushed to whoever holds the context, which is usually not me.

Every decision routed through you costs an hour of somebody's time and a slot in your week. Most of them never needed you at all.

And I don't hold recurring one-to-ones with people who don't report to me.

Those are the most common source of calendar creep at scale. They feel productive. They're a slow substitute for having managers you trust.

Protecting thinking time so it survives

Three failure modes. All predictable.

Thinking time gets scheduled and then colonised, one exception at a time, each of them individually justified.

Counter: treat it as an appointment with an actual person. You'd never cancel that four weeks running.

Or it survives on the calendar and gets spent on email, because thinking is uncomfortable and there's always something nearby that feels more productive.

Counter: give the block a subject in advance, in writing. Not "thinking time." Something like "the decision about the second platform hire," or "why the deploy numbers stopped improving."

Or it happens, produces nothing, and quietly gets deprioritised.

Counter: make it produce something written, every time. Not for anybody else.

Writing is what makes thinking finish. An unwritten thought reliably turns up again next month in exactly the same unresolved form.

The ratio worth aiming at

Not a rule, and the balance moves with the stage of the company. Roughly a quarter reactive, a quarter operating, a quarter building, a quarter thinking.

Reactive can't be zero, and shouldn't be.

A leader unreachable in the moment isn't helping anybody, and being available for the genuinely urgent is part of the job. What it can't be is 60 percent, because at that level you're operating entirely inside other people's frames and nothing you do originates with you.

If building and thinking are both under 15 percent, you're running the company you have rather than the one you're supposed to be building.

Survivable for a quarter. Corrosive over a year.

And it shows up as an organisation that's fine right now and has no answer at all for what's coming.

What to stop this week

The audit produces a list of candidates. The same three things turn up on most people's.

Meetings you attend to stay informed.

That's what a written update is for, and the meeting costs you an hour to receive information you could have read in four minutes. Leave. Ask for the note.

Meetings where you're a decision backstop nobody has needed in months.

Tell the team you're stepping out and to escalate if they need you. Most won't. Finding that out is worth more than the attendance was.

And the recurring thing set up for a situation that has since resolved itself. Every calendar has at least one.

Cancel it for three weeks as an experiment rather than killing it in an argument, and see whether anybody misses it.

Usually five to eight hours a week, recovered. Much better place to find thinking time than getting up earlier.