HOME / INSIGHTS / PERSONAL SYSTEMS · INSIGHT

A reading system for busy operators

A reading system for busy operators is a small pipeline: rules for what enters your queue, when you read, and what happens to the ideas afterwards. It replaces the pile of unread books with a flow that feeds your decisions. You do not need more hours; you need fewer inputs, a fixed slot, and a mechanism for applying what you keep.

Why do most operators stop reading?

Not for lack of interest. Reading competes every day against tasks with deadlines, and reading has none, so it loses by default. The result is a familiar stock-and-flow problem: books arrive faster than they are read, the pile grows, and the pile itself becomes a reason not to start — every glance at it is a small reproach.

The failure is structural, not moral. Wanting to read more is an intention, and intentions lose to calendars. In a personal operating system, anything that matters gets the same treatment: a decision made once, encoded as a rule, executed on schedule. Reading is no different.

What should a reading system actually produce?

Not finished books. Changed decisions. The honest measure of a reading system is ideas applied per quarter, not books completed per year. That reframing changes behaviour immediately: abandoning a mediocre book halfway is a win, because it frees the slot; re-reading one chapter of Goldratt's The Goal before a capacity decision is a win, because it changes the decision. A book you finished but cannot act on scored zero.

Once reading is treated as an input to operations rather than a leisure metric, the rest of the system follows from that purpose.

How does the pipeline work?

The mechanism has five stages, each with a when-then rule.

  1. Capture. When anyone recommends a book or article, then it goes onto a single capture list — it does not get bought. Buying at the moment of enthusiasm is how piles form.
  2. Select. When the monthly review comes round — the same review I use for self-governance — then I pick at most two items from the list, chosen against a current problem, and buy only those.
  3. Read. When a book is active, then it gets a fixed daily slot of twenty to thirty minutes, attached to something that already happens: the first coffee, the commute, the half hour before bed. The slot does the work; motivation is not consulted.
  4. Note. When an idea is worth keeping, then it becomes a short note in my own words, tagged with the decision it might affect. Highlights are not notes; they are deferred reading.
  5. Apply. When the weekly review runs, then open notes get scanned against the week's decisions. A note that never surfaces at a review may as well not exist.

There is one exit rule: when a book has not been picked up for fourteen days, then it is abandoned without ceremony. The queue is a tool, not a curriculum.

How do you choose what to read?

Just-in-time beats just-in-case. Read against your current constraint: if the pipeline is empty, read about sales systems; if you are drowning in operational noise, read Donella Meadows's Thinking in Systems rather than another marketing book. Ideas land when there is a problem for them to attach to. The same book read a year too early typically leaves nothing behind.

Two supporting rules help. First, keep at most two books active — one for work, one for pleasure. The pleasure book protects the habit on days when work reading feels like more work, and it is a small act of boundary design in its own right: a slot the business does not own. Second, weight the queue towards older books. A book that has survived thirty years of readers has survived scrutiny; this year's business bestseller commonly has one idea and 240 pages.

Is this not just more admin?

The whole system costs the daily slot plus perhaps fifteen minutes a month of selection. At twenty-five minutes a day it typically works through a dozen or more books a year — more than most operators manage, with far less of it wasted.

The notes are the part people skip and the part that pays. A shelf of read books is inventory; retrieval is the product. It is the same logic as reporting: a number nobody looks at manages nothing, which is why six numbers you actually see daily beat a forty-tab spreadsheet you never open. A note that resurfaces at the moment of a decision is the entire return on the reading. Build the small pipe, keep it flowing, and stop measuring yourself by the height of the pile.


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

Total Format builds the systems UK B2B service firms grow on — AI-powered outbound, automation, and reporting — so growth stops depending on the founder's time.

The Format — a fortnightly letter on business and personal systems. One idea per issue.

SUBSCRIBE BY EMAIL