Self-governance: running yourself like a system

Self-governance means running yourself the way you would run a well-designed firm: with written decision rules instead of in-the-moment willpower, a few honestly measured numbers instead of feelings about progress, and a scheduled review loop instead of occasional resolutions. The premise is blunt — you are the most important process in your business, and you are almost certainly the least documented one.

Why govern yourself like a system at all?

Because the alternative is governing yourself by mood, and mood is a terrible executive. Every founder already runs on rules; most are just unwritten, inconsistent and re-litigated daily. Should I take this call? Work Saturday? Discount this deal? Answering each case fresh burns decision energy and produces different answers on Tuesday than on Friday afternoon.

A firm that ran this way — no policies, every choice escalated to a tired owner — would be an obvious redesign candidate. The founder who runs this way personally is the same case. This is the governing idea behind The Personal Operating System: the founder is a component of the business, and components perform to their design, not to their intentions. Willpower is real but it is a stock that depletes; rules are a flow that keeps working when the stock is empty.

What is a personal decision rule?

A pre-made decision in "when X, then Y" form, written down while calm and applied while busy. Working examples:

• When a meeting has no agenda, then I decline it and ask for one.
• When a proposal's win rate runs above 60%, then the next proposal goes out 15% higher.
• When it is before 10:00, then the inbox stays shut and the Now list item gets worked first.
• When I have worked two consecutive weekends, then the third is off, regardless of what is on fire.

Note what these do: they convert recurring dilemmas into policy. The single-priority rule, for instance, is just one decision rule installed deeply — which is why the Now list is the natural first module for anyone starting this.

How do you install the rules?

The mechanism runs in five steps:

1. Log the repeat decisions for two weeks. Every time you notice yourself deliberating about something you have deliberated about before, write it down. When a decision recurs, then it is a candidate for a rule; one-off decisions stay judgement calls.
2. Draft rules for the top five. Strict "when X, then Y" form, one line each. If a rule needs a paragraph, the trigger is too vague to fire in real life.
3. Write them where you will collide with them. The top of your task list, a card by the desk — not a document you will never reopen. An unread rule governs nothing.
4. Run them for a quarter without renegotiation. The rule decides; you observe. When a rule feels wrong in the moment, then that gets noted for review rather than acted on — in-the-moment exceptions are exactly what the rule exists to prevent.
5. Review and revise quarterly. Keep what held, rewrite what didn't, delete what you ignored. Rules are policy, and policy gets amended by process, not abandoned by impulse.

Five rules, honestly run, will outperform fifty aspirations.

What do you measure?

Three or four numbers that describe the operator rather than the business: hours actually worked per week, first-block sessions hit (out of a possible five), finished projects per quarter, weeks of real holiday taken. Counted plainly, reviewed quarterly, no narrative attached. The measures exist to catch drift early — a creeping 55-hour week announces burnout long before you feel entitled to call it that.

What happens when the system lapses?

It will, and this is where most people quit — they treat a broken streak as evidence of a broken character and abandon the whole apparatus. A systems operator treats a lapse as an incident: expected occasionally, diagnosed, recovered from by protocol.

The business equivalent is instructive. A neglected CRM full of stale records looks unrecoverable, yet a dead pipeline responds to a resurrection protocol — a defined sequence, not a burst of motivation. Lapsed personal systems respond the same way. The recovery protocol is three steps: when a rule has lapsed for a week, then restart the smallest unit (one first-block, not a perfect week); diagnose the trigger in one sentence at the next review; and revise the rule if the trigger will recur. No back-payments, no self-audit of your worth — re-entry, then redesign.

Where does judgement fit?

Everywhere the rules don't reach — which is the point. Governance is not the removal of judgement; it is the reservation of judgement for questions that deserve it. The rules handle the recurring 80% so that attention is available for the novel 20%. Inputs deserve the same design as decisions, incidentally — a deliberate reading system governs what enters your head the way decision rules govern what leaves it. Run yourself like a system and you will make fewer decisions, and better ones.

---

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