Personal operating system examples

Four shapes, for four kinds of work. They differ in what they keep and almost not at all in how they are built, which is the useful finding: the structure varies far less than people expect, and the thing that decides whether it survives is not structural at all.

The consultant, running six clients at once

The organising unit is the engagement, and the hard part is not the work, it is the context switch. Coming back to a client after two weeks means reconstructing where things stood, what was promised, and what the last conversation actually decided. So the project file leads with status and the open questions, the decision log carries the reasoning rather than just the outcome, and every meeting transcript gets summarised into the engagement the same day rather than sitting in a folder.

What this shape needs most is the follow-up sweep: across six clients, the thing that damages a reputation is not doing poor work, it is the commitment made in passing on a Thursday that nobody wrote down. More on this shape at the consultant's version.

The founder, where everything is half-finished

Nothing is ever done and the number of live threads exceeds what anyone can hold. The system's job is less about memory and more about triage: what changed since yesterday, what is blocked and on whom, and what is quietly rotting because nobody has looked at it. The status rollup matters more here than anywhere else, and it must be derived from the project files rather than maintained beside them, or it becomes another thing to update.

The people layer earns its place here too. Investors, candidates, and prospects all need a relationship record separate from the deal, because you will talk to them again in six months about something unrelated. See the founder's version.

The researcher, drowning in what they have read

Here the reference layer dominates. The failure mode is a folder of a thousand saved papers with no idea which ones were relevant to what, and no memory of why any of them were saved. The fix is filing by purpose rather than by subject: what question was I chasing when I kept this. That single change makes the archive searchable in the way you will actually search it two years later, which is by the problem, not by the topic.

Reading intake is its own workflow, covered at saving articles so an assistant can use them, and the researcher's fuller shape is at the researcher's version.

The executive, whose work is other people

The projects are largely other people's, and what the system holds is commitments, context on people, and the state of things you are accountable for without doing. Prep is the recurring need: walking into a meeting knowing the history without having asked anyone to brief you. This shape leans hardest on the people files and on the morning brief, and least on the reference layer. See the executive's version.

What all four share

That is the honest lesson from looking at examples: copying someone else's structure is nearly free and nearly useless. The structure was never the hard part. If you want a starting layout anyway, take the template, and then spend your actual effort on the layer that fills it.