Two things on my calendar this week. Last month was our best.

Two things on my calendar this week. A client call on Tuesday and the gym on Thursday.

I sent a screenshot of it to a founder friend and he asked if things had gone quiet. They hadn't. Last month was the best month the business has had. The empty calendar is not the absence of work, it is what the work looks like once you stop being the mechanism.

That took about a year, and almost none of it was interesting.

Why your calendar fills up

Nobody schedules meetings because they enjoy meetings. Meetings exist because information is trapped in one person's head and the only retrieval method anyone has ever invented is to book thirty minutes and ask them.

So the real question is never "can we cancel this meeting." It is "why is this the only way to get that answer."

Once you ask it that way, most of a calendar falls apart on its own. A status meeting exists because nobody wrote the status down. A check-in exists because nobody knows who is allowed to decide. A kickoff exists because the brief is vague and everyone is hoping the vagueness resolves itself if enough people are in the room.

None of those are meeting problems. They are writing problems wearing a meeting costume.

[IMAGE-1: a real Google Calendar week view, almost entirely empty, two small events all week]

The three things that actually emptied mine

None of them were a productivity system. I have tried the productivity systems. They reorganise the symptoms.

The first was written updates that arrive whether or not anyone asks. Not a status meeting. A document that updates itself from the systems that already know the answer, and gets read by whoever needs it, whenever they need it. The moment the update exists in writing, the meeting about the update has nothing to do.

The second was naming a decider for every recurring decision. Half of all standing meetings are a group of adults waiting to find out who is allowed to say yes. Write the name down once and the meeting dies quietly, without ceremony, and nobody misses it.

The third was a default of no. Every meeting request gets one question back: what decision are we making here. If there is no decision, there is no meeting. About a third of requests never come back after that question, which tells you what they were.

What i wrote down, exactly

This is the part people skip, so here is the concrete version.

I opened a document and listed every question anyone had asked me in the previous month. Not tasks. Questions. Things like "can we refund this", "should we pause this campaign", "is this client worth keeping", "can I approve this invoice".

Then I wrote a rule for each one. Not a process, a rule. A process describes steps. A rule describes a decision and its boundary.

"Refund anything under $80 without asking me" is a rule. "Handle refunds" is a wish.

"Pause any campaign that spends 3x its daily budget with zero conversions, and tell me after" is a rule. "Keep an eye on spend" is a wish.

The list came to about forty items. Some of those rules now run inside software. Some of them are a paragraph a human reads. The mechanism genuinely does not matter. Getting the decision out of my head and into a sentence somebody else can execute is the entire exercise.

[IMAGE-2: a hyper-real document of written rules, plain and unglamorous]

The part nobody warns you about

When the calendar clears, you find out whether you actually know what to work on.

This is the uncomfortable bit and it is why most people quietly refill it. Being busy is a complete identity. It answers the question "am I doing enough" without you having to think about it. An empty week asks you what the business actually needs next, and that question has no comforting answer.

I refilled mine twice before it stuck. Both times I invented work that felt important and wasn't.

The forty rules, by category

People ask what forty rules actually looks like, so here is the real shape of the list. It sorts into five buckets and the proportions surprised me.

Money decisions came to eleven. Refunds under a threshold, discount approvals, when a client goes on hold for non-payment, what invoice size needs a second pair of eyes, which recurring costs auto-renew and which get re-approved. Every one of these had been coming to me, and every one of them had a boundary I could name in a sentence once I sat down to write it.

Client decisions came to nine. When to escalate, when to fire, what counts as scope creep, what we do when a client goes quiet for two weeks, who is allowed to promise a deadline.

Account and delivery decisions came to fourteen, which is the bucket everyone expects to be biggest and is. Budget change limits, what triggers a pause, what triggers a call, which checks run nightly and which run weekly, what an alert has to contain before it is allowed to wake anyone.

Hiring and people decisions came to four. Small, but they were the ones I had been avoiding hardest, which is its own signal.

Everything else was two. Genuinely two. The long tail I had been imagining did not exist.

The boundary is the entire rule

The single most common mistake I see when someone tries this is writing rules with no number in them.

"Escalate if the client seems unhappy" is not a rule. Seems unhappy according to whom, and at what point. "Escalate if a client sends two messages in a week that we have not resolved within 24 hours" is a rule. It is checkable by someone who has never met the client.

Every rule needs three parts: the trigger, the action, and the edge where it stops and comes back to a human. Drop the third part and you have built something that will confidently do the wrong thing at the worst possible moment, because you never told it where its authority ended.

I write mine in exactly this shape, and I keep them in one plain document rather than scattered across tools:

WHEN spend on any single campaign exceeds 3x its daily budget with zero conversions in 48 hours THEN flag it in the channel with the campaign name, the spend, and the last conversion date NEVER pause it, never change the budget, always wait for a reply

That third line is the one that took me longest to learn to write, and it is the one that lets me sleep.

How to test whether it worked

There is only one honest test and it is uncomfortable.

Go away for a week without telling anyone you are testing anything. No heads up, no "I'll be reachable". Then look at what broke.

The first time I did this, three things broke and all three were the same category: decisions nobody had been given permission to make. Not skill gaps. Permission gaps. That distinction changed how I wrote every rule afterwards.

The second time, one thing broke. The third time, nothing broke and I found that genuinely unsettling for about two days, which is the part of this nobody writes about.

Where this goes wrong

Two failure modes, both of which I hit.

The first is automating a decision you have not actually made. If you are inconsistent about something, writing it down does not make you consistent, it makes your inconsistency permanent and fast. Sit with the decision until you can defend the boundary before you hand it to anything.

The second is deleting the human check too early because the system has been right for a month. A month is not evidence. The failures you care about are the rare ones, and rare things need quarters, not weeks, before you trust them unsupervised.

One last thing about delegation

Every article about this says "delegate more" and stops there, which is useless advice, because delegating a task you have not thought about just moves the confusion to someone else and adds a status meeting to track it.

What actually transfers is a decision with a boundary. Tasks transfer badly because a task is the visible tip of a judgement you made without noticing. Write the judgement down and the task follows on its own.

That is why the forty rules took a year and the tooling took a fortnight. Everyone wants the fortnight.

Three things to do this week

Open your calendar for the last month and mark every recurring meeting with the decision it produced. Anything with no decision goes.

Write down the five questions you were asked most often. Turn each one into a rule with a number in it. A rule without a boundary is not a rule.

Pick one meeting and replace it with a written update this week. One. See if anybody notices.

An empty calendar is not a sign the work stopped. It is a sign it stopped needing you in the room.