The founder problem is usually not a shortage of plans
Founders can generate options faster than most systems can absorb them. The cost is fragmentation: the strategic objective lives in one document, the urgent work lives in messages and the uncomfortable move is repeatedly displaced by activity that feels productive.
A daily accountability system creates a line from strategy to evidence. Every layer should answer one question: did today’s action materially advance the defined mission?
Step 1: define one mission with a hard edge
Choose an outcome that can be assessed at a deadline. “Grow the business” is too soft. “Reach £50,000 in collected monthly revenue from a repeatable offer by 30 November” gives the system a target, a commercial measure and a clock.
Add only the few checkpoints that prove the mission is moving. A 90-day window is long enough for meaningful work and short enough to expose drift before it becomes a year of explanation.
Outcome
What observable state must be true at the deadline?
Current position
What is true today, using the same measure?
Checkpoints
Which three or four results would prove the path is working?
Constraints
Which limits—cash, health, family, legal or operational—must the plan respect?
Step 2: issue one daily order
The daily order is not the entire to-do list. It is the move that deserves protection before reactive work expands. A good order has a deliverable, a decision or a verifiable action and can be resolved by the end of the day.
“Work on launch” leaves room to hide. “Send the final decision pack and secure a signed commercial decision by 16:00” defines what completion means. Specificity makes the check-in useful.
Step 3: capture proof, including the miss
At the end of the day, mark the order completed, missed or consciously declined. Add the minimum evidence needed to make the record credible. The point is not punishment; it is to prevent narrative from replacing execution data.
A truthful miss can be strategically valuable. It may expose that the order was poorly scoped, that the mission is not actually prioritised or that a recurring blocker needs an owner. Editing the past destroys that signal.
Step 4: run a weekly correction, not a weekly diary
Review resolved orders, check-ins and checkpoints together. Separate effort from outcome: an exhausting week can still produce weak mission progress, while one decisive conversation can produce a high-value result.
What moved?
Name the concrete change in the mission’s position.
What repeated?
Identify the blocker, avoidance pattern or scope error that appeared more than once.
What stops?
Remove activity that consumed time without changing the outcome.
What is next?
Set the next week’s focus before Monday’s reactive work arrives.
A workable daily cadence
Review the mission and commit to the order before the day fragments. Protect a block for the order. Resolve it before shutdown, then use the weekly review to correct the system rather than renegotiate every morning.
The War Room turns this cadence into a private iPhone workflow: Battle Plan, Today’s Order, check-in, order proof and Weekly War Report. The AI coach is optional and operates only after explicit consent.
