Part VIII · The Execution Path — Chapter 50
Your weekly operating system
A useful week begins with the capacity you actually possess, protects the promises already made, and ends with evidence strong enough to change the next week.
The copied founder schedule fails because it assumes somebody else’s job, health, family, commute, energy, team, and cash position. A salaried professional building beside work should not imitate a full-time operator. A founder in a launch week should not pretend the same pace is sustainable every week. Build a cadence from constraints, then hold it firmly enough to produce trust.
Calculate honest capacity first
Use a representative time audit. Mark each block:
- • Build: creates future capability, customer value, distribution, or a stronger system;
- • Run: keeps current promises, operations, and administration functioning;
- • Restore: protects sleep, health, relationships, and the quality of later judgment;
- • Waste: consumes time without changing an outcome worth keeping.
Begin with non-negotiable employment, care, health, and recovery commitments. Add customer and legal obligations. Keep buffer for uncertainty. The remaining usable blocks are planning capacity. Do not schedule an ideal self who appears only on Sunday evening.
Every new commitment must replace, delay, delegate, or cancel another commitment. A calendar is a capacity ledger. A long task list can conceal insolvency in time.
Choose the week’s operating mode
Use one of three modes based on current facts. Name the mode before choosing targets.
| Mode | When it applies | Required outcome |
|---|---|---|
| Protect | Illness, family demand, cash shock, employment peak, or recovery deficit | Keep essential promises, surface risk early, preserve health, and prevent avoidable damage |
| Standard | Normal capacity and ordinary uncertainty | Deliver the must-win, move the market, improve one constraint, and close the review loop |
| Expansion | Temporary opportunity with explicit extra capacity and protected downside borrowing from sleep, quality, family, or | Pursue the opportunity without silently future promises |
Expansion needs a start condition, an end date, and a recovery plan. If “temporary” intensity keeps renewing, the system is under-capacity, underpriced, overscoped, or badly governed.
Build the week around outcome blocks
The order depends on role and energy, but every active business week needs homes for these functions:
Promise block. Delivery, acceptance, support, collections, and any work whose delay harms a customer or colleague. Put threatened promises on the calendar before optional creation.
Market block. Discovery, qualification, outreach, proposals, decisions, follow-up, and asking for payment. A builder can remain busy for months while avoiding the moment the market can say no.
Build block. The hardest work on the current constraint: capability, offer, product, process, or proof. Place it where your real attention is strongest, not where a productivity author says mornings belong.
Control block. Cash, receivables, runway, quality, security, compliance, risk, and commitments. Look first at the number you would prefer to postpone.
System block. Remove one repeated cause of delay, error, or founder dependency. Documentation without adoption is not a system; test the changed path in actual work.
People block. Feedback, decisions, thanks, difficult conversations, and context that another person needs. Bad news should travel early with facts, impact, action, and the next update time.
Restore block. Recovery and meaningful presence are capacity maintenance. Protect them before the week fills. A business that requires chronic impairment has a design problem, even when the revenue line is rising.
Batch low-context communication where practical. Cluster meetings. Keep margin for customer incidents, travel, care, and opportunity. Limit work in progress so the week finishes important outcomes instead of opening many.
Use a stage-specific scorecard
Metrics should answer the current gate from Chapter 49. Choose a small set that links input, outcome, and decision.
| Current gate | Useful evidence | Decision it supports |
|---|---|---|
| Capability | Artifact shipped, test passed, explanation defended | Continue, deepen, or change the skill bet |
| Problem access | Workflow observed, consequence verified, buyer process clarified | Test an offer or return to discovery |
| Paid proof | Scope accepted, result delivered, cash collected, lesson recorded | Repeat, reprice, redesign, or stop |
| Repetition | Contribution, conversion, quality, cycle time, repeat use | Fund another cycle or narrow the engine sys |
| Transferability | Hand-off success, exceptions, founder interventions, control failures | Delegate further or strengthen the tem |
| Stewardship | Cash, customer risk, people capacity, compliance, concentration | Allocate, protect, or slow growth |
Set the target from capacity, baseline, customer need, and the current experiment. Record why it is credible. A universal outreach count, deep-work duration, or sleep score creates false discipline when the underlying job differs.
Track leading action and lagging result together. Outreach without qualified movement may be poorly targeted. Revenue without collection may increase risk. Hours worked without acceptance evidence may be rework in disguise. A metric earns its place only if its movement can change a decision.
Close the loop before planning again
At the weekly review, answer in writing:
1. What changed for a customer, the company, or my capability? 2. Which promise was kept, broken, or placed at risk? 3. What cash moved, what is overdue, and what assumption changed?
4. Where did planned capacity differ from actual capacity? 5. What did I avoid, and what is the operational reason beneath the emotion? 6. Which experiment closed, and what decision did its evidence earn? 7. Who needs truth, feedback, thanks, help, or an apology? 8. What repeated work should be removed, standardised, delegated, or priced? 9. What could cause irreversible harm if ignored next week?
10. What is the one must-win outcome now?
Then choose only the few outcomes the honest calendar can carry. Put them into timed blocks, name owners and acceptance evidence, and reserve buffer. Close the review. Do not let planning consume the recovery it claims to protect.
Define the minimum viable week
When life contracts, preserve the spine:
- • protect health and people;
- • tell affected customers or colleagues early;
- • check cash and irreversible risk;
- • complete or renegotiate the most consequential promise;
- • keep one small market or capability action alive where safe;
- • record what must restart when capacity returns.
This prevents one difficult week from becoming concealed debt. Recovery is a mode with explicit priorities, not a moral failure.
· ASC pp. 132–134 · LG pp. 22–25, 90–93 · GE ch. 43. Time-audit, calendar, review, and scorecard mechanisms paraphrased; schedules and targets are capacity-specific rather than fixed by role mythology.