The power of routine is the leverage you get from making repeated behaviours automatic, predictable, and aligned with your goals. Routine reduces decision cost — you don't re-debate what to do each morning or how to run a meeting — and it creates capacity for the work that actually requires judgment. When building and scaling, most of the load is execution: the same types of decisions and actions recur. Routine turns those into defaults so that attention and willpower are reserved for the exceptions.
Routine is not rigidity. It's a default script that you can override when the situation demands. The best operators have strong routines for the repeatable parts (how they start the day, how they run 1:1s, how they review metrics) and stay flexible for the non-routine (crises, strategy pivots, key hires). The mistake is either no routine — everything is ad hoc, and decision fatigue burns you out — or total routine — you can't adapt when the world doesn't match the script.
Research on habits and implementation intentions supports the idea: behaviour is more likely when it's cued by context and when the "if X then Y" is pre-decided. Routine is the structural expression of that — you design the context (time, place, sequence) so that the right behaviour is the path of least resistance. In building and scaling, routine scales you: the same 24 hours produce more when the high-value actions are baked into the day and the week.
Section 2
How to See It
Routine shows up when someone has a fixed sequence for recurring situations — same order of operations, same triggers, same outputs — and when that sequence clearly serves capacity or quality rather than ritual for its own sake. Look for "I always…" or "we always…" applied to repeatable work.
Personal
You're seeing Power of Routine when a founder starts every day with the same block — e.g. 90 minutes of deep work before email — and protects it. The routine isn't negotiable; it's the default. The result is predictable output and less morning decision drain.
Team
You're seeing Power of Routine when a team runs stand-ups, reviews, and retros on fixed days and formats. The content varies; the structure doesn't. New members onboard to the rhythm quickly, and the team doesn't waste time deciding how to meet.
Scaling
You're seeing Power of Routine when a company has standard playbooks for onboarding, support escalation, and launch — so that growth doesn't require reinventing process every time. Routine is what makes scaling repeatable.
Judgment
You're seeing Power of Routine when a leader reserves certain decisions for certain times (e.g. "we only change roadmap on Mondays") so that the rest of the week isn't consumed by re-opening settled questions. The routine protects focus and reduces churn.
Section 3
How to Use It
Decision filter
"For any activity that recurs, ask: have I made it routine? If not, you're paying decision cost every time. Design a default — time, trigger, sequence — and protect it. Override only when the situation clearly warrants it."
As a founder
Routine is a force multiplier when building and scaling. Put your highest-leverage activities into fixed slots: deep work, customer contact, strategy review. Make meetings and communication follow a predictable pattern so the team can plan. The mistake: treating every day as a blank slate and re-deciding everything. The second mistake: never revisiting routines when they stop serving. Review routines quarterly — what should be default now that wasn't before? What should be flexible again?
As an investor
Routine supports consistency in how you source, evaluate, and support. Fixed cadences for pipeline review, due diligence, and portfolio monitoring reduce the chance that things slip or that you're swayed by mood. The content of each deal is unique; the process can be routine. That frees attention for the judgment calls that can't be routinised.
As a decision-maker
Identify the decisions and actions that repeat. Turn them into routines — same time, same format, same criteria — so you're not re-litigating them. Reserve creative energy for the decisions that are genuinely one-off or strategic. Use routine to create slack for the exceptions.
Common misapplication: Routinising what should stay flexible. Some decisions need to be re-opened when context changes. If you lock everything into routine, you become brittle. Routine the repeatable; keep the strategic and the novel open for judgment.
Second misapplication: Confusing routine with busywork. A routine should serve an outcome — better focus, faster execution, clearer communication. If the routine exists because "we've always done it," question it. Measure or at least name the benefit.
Jobs was known for a consistent uniform and for ritualised product reviews and design critiques. The routine wasn't arbitrary — it removed variability from everything except the work that mattered. Same context, same bar, so that attention went to the product and the detail. The power of routine at Apple showed up in how often the same high standards were applied because the process was predictable.
Bill GatesCo-founder, Microsoft; Co-chair, Gates Foundation
Gates has long used "think weeks" — blocked time away from the office to read and reflect — as a routine for strategic input. The routine ensures that reading and deep thinking happen regardless of operational pressure. It's a structural solution to the problem of protecting high-leverage, non-urgent work.
Section 6
Visual Explanation
Routine turns repeated actions into defaults. Without routine: every occurrence costs a decision. With routine: context cues behaviour, decision cost drops, capacity is freed for non-routine work.
Section 7
Connected Models
The power of routine sits alongside other models of behaviour, focus, and scaling. The connections below show what reinforces it, what tensions exist, and what it enables.
Reinforces
Habits
Habits are automatic behaviours cued by context. Routine is the deliberate design of those cues and sequences. The two reinforce each other: routines create the conditions for habits to form; habits make routines stick with less effort.
Reinforces
Systems vs Goals
Systems vs goals emphasises designing processes that produce outcomes rather than fixating on targets. Routine is a system — a recurring process that, if well designed, yields consistent results. Focus on the routine (system) and the outcomes follow.
Tension
Flexibility
Flexibility is the ability to adapt when the situation demands. Routine can reduce flexibility if it's applied too broadly. The tension: routine the repeatable; keep the exceptional and the strategic open to judgment and change.
Tension
Deep Work
Deep work requires long, uninterrupted blocks. Routine can protect those blocks (e.g. "every morning 8–10 is deep work"). It can also conflict if the routine is meeting-heavy and fragments the day. Design routine to protect deep work, not to crowd it out.
Leads-to
Section 8
One Key Quote
"Could the young but realize how soon they will become mere walking bundles of habits, they would give more heed to their conduct while in the plastic state."
— William James, psychologist
Routine is how you shape that "plastic state" into a structure that serves you. The habits you form — and the routines you design — become the default. The practitioner's job is to choose those defaults deliberately and to revisit them when goals or context change.
Section 9
Analyst's Take
Faster Than Normal — Editorial View
Routine is a scaling lever. When building and scaling, the bottleneck is often execution consistency — doing the right things repeatedly. Routine makes the right thing the default. Design routines for the activities that recur and that matter: deep work, communication, review, learning.
Protect the high-leverage routine first. Identify the one or two routines that most affect output (e.g. morning deep work, weekly strategy slot). Make them non-negotiable. Other routines can be more flexible, but the core ones should be defended.
Reduce decision cost, not just activity. A routine that adds busywork doesn't help. A routine that turns "what do I do now?" into "I do this now" frees attention. Audit routines: does this reduce cost or add it? If it doesn't reduce cost or improve quality, drop it or change it.
Revisit routines periodically. What was right at 10 people may be wrong at 100. Quarterly or twice-yearly review: which routines still serve? Which should be added? Which should be relaxed? Routine is a tool, not a religion.
Don't routinise strategy. The big bets — what to build, where to compete, whom to hire for critical roles — should stay judgment-based. Routine the execution; keep the strategic decisions in the space where you're willing to re-open and re-decide.
Section 10
Test Yourself
Is this mental model at work here?
Scenario 1
A founder reserves 8–10 a.m. every day for deep work and treats it as non-negotiable. The rest of the day is meetings and communication.
Scenario 2
A company has always run Monday all-hands at 9. Growth has made it unwieldy, but no one has questioned it.
Section 11
Summary & Further Reading
Summary: The power of routine is the leverage from making repeated behaviours automatic and aligned with goals. Routine cuts decision cost and frees capacity for the work that requires judgment. Use it for recurring activities: fix time, trigger, and sequence so that the right behaviour is the default. Override when the situation clearly warrants. Revisit routines when goals or context change. Pair routine with flexibility — routine the repeatable; keep the strategic and the novel open.
Newport argues for blocking time for focused work. Routine is how you protect those blocks — same time, same rules, so deep work becomes the default.
Keystone Habits
Keystone habits are habits that trigger or support other positive behaviours. A strong routine for one high-leverage activity (e.g. morning block, weekly review) can act as a keystone — it structures the day and makes other good behaviours more likely.
Leads-to
Implementation Intentions
Implementation intentions are "if X then Y" plans that link a cue to a behaviour. Routine is the repeated application of such intentions — same cue (time, context), same behaviour. Building routine is building implementation intentions at scale.
