Against the 5am club: routines that survive contact

You do not need to wake at 5am. You need a morning that still works on five hours' sleep, with a child off school, in a week when a client project is on fire. The measure of a routine is not how it performs on its best day — it is whether it survives contact with an ordinary one.

Why do most morning routines fail?

Because they are designed for ideal conditions and borrowed from someone else's life.

The typical version is a chain: wake at 5, gym, cold shower, journal, meditate, read, then work. Chains fail at their weakest link. Miss the 5am start once and the whole sequence collapses, and because the routine was framed as an identity — "I am the kind of person who gets up at 5" — the miss reads as a character verdict rather than a scheduling event. Two misses become a lapse, a lapse becomes abandonment, and by February the routine exists only in the notes app.

There is also a sampling problem. The people selling dawn routines are usually people whose calendars they control completely. A founder running a 15-person firm, doing a school run, taking client calls across time zones, does not have that life. Copying the routine without copying the conditions is how you end up tired and demoralised rather than productive. In The Personal Operating System I make the broader argument: personal systems should be designed like business systems — for the operator you are, under the load you actually carry.

What should a routine be designed for?

The worst plausible morning, not the best one.

A routine that only runs under perfect conditions is not a system; it is a performance. A system has to specify what happens when inputs are degraded — when sleep was short, when the first meeting moved to 8am, when you are travelling. If the routine has no answer for those mornings, the answer becomes "nothing", and nothing repeated is how routines die.

So invert the design question. Do not ask "what would my ideal morning contain?" Ask "what is the minimum I am unwilling to skip even on a bad day, and what can be layered on top when conditions allow?"

How do you build a routine that survives contact?

Build it in three tiers and attach a rule to each. The mechanism runs like this: when I wake rested with no early commitments, then the full version runs — perhaps 60 to 90 minutes of exercise, planning, and reading before the first call. When sleep was short or the diary starts early, then the reduced version runs — 20 minutes, usually a walk and a written plan for the day. When the morning is already gone before it starts, then the floor version runs — five minutes to write down the day's single most important task before opening email.

Three properties make this durable:

• The floor is trivially small. Five minutes cannot be argued with, so the streak never technically breaks and the identity damage never happens.
• The decision is pre-made. You are not negotiating with yourself at 6:45am; the tier is determined by conditions, not willpower. This matters because willpower is exactly the resource a bad morning has already spent — the theme of Decision fatigue: budget it like money.
• Every tier ends the same way. Whatever else happens, the day starts with a written intention, which is the part that actually moves work forward.

The daily plan has somewhere to come from, too. Mine comes out of a notes system reviewed weekly — the kind I describe in A second brain that actually gets queried — so the morning is retrieval, not invention.

Does the hour itself matter?

Less than the consistency of the first block. There is reasonable evidence that people differ in chronotype, and no evidence I am aware of that virtue accrues specifically before sunrise. If your best thinking happens at 9pm, a 5am start amputates it. What matters is that the first working block of the day is protected and pointed at something you chose in advance — whether that block starts at 6 or at 9:30.

What does this have to do with running a firm?

Everything, because it is the same engineering. I build client systems on the identical assumption that conditions will degrade: a prospect database is built expecting records to decay and get re-verified, not assuming the list stays clean — the discipline laid out in The B2B Database Building Guide. Systems that only work when everything goes right are not systems.

Routines are the personal version. Design for the bad morning, give yourself a floor you cannot fail, and let the impressive version be a bonus rather than the standard. The 5am club optimises for the photograph. You are optimising for the decade.

---

Keep the thinking coming: The Format — a fortnightly letter on business and personal systems. Subscribe by email.