A Personal Operating System

A personal operating system is a repeatable cadence, capture, orient, decide, review, for turning a head full of half-formed obligations into an honest next move. As of August 2026, after 15 years building products for people who have to decide under real stakes, and a 36-hour mountain effort at 29029 Snowbasin that stripped my own habits down to what actually holds up, I keep landing on the same four steps. Capture gets the noise out of your head and onto something you trust. Orient tells you the truth about what actually matters this week, not what feels loudest. Decide picks the smallest next move, not the whole plan. Review is the step almost everyone skips, and it's the one that keeps the other three honest.

What is a personal operating system?

A personal operating system is four repeatable steps, capture, orient, decide, review, run on a fixed cadence, that turn scattered obligations into a trustworthy next move. It isn't a single app or planner. It's the rhythm you run those tools through, whether the week is calm or on fire.

The homepage of this site names a framework I use professionally: land, orient, act. It's built for the moment someone hits a product under pressure and needs to know what to do next, fast. The personal version runs slower and adds a step, because ordinary life doesn't hand you one crisis at a time. It hands you forty of them, all at once, most of them small.

Capture, orient, decide, review is that four-step version. I wrote about the orient-decide-act loop in Decision-Making Under Pressure for the moments when the clock is the enemy. This is the version for the week you're not on a mountain, when the obligations arrive quietly instead of all at once, and the risk isn't panic. It's letting things pile up until nothing gets your best attention.

Why does capture have to come before anything else?

Capture comes first because an obligation you're only holding in your head costs attention whether or not you're working on it. David Allen's Getting Things Done calls this an open loop, an unresolved commitment your mind keeps rechecking. Writing it down somewhere you trust closes the loop, even before you've decided what to do about it.

I learned this the expensive way running product teams through eight acquisitions. Every reorg produced its own flood of half-finished threads: decisions waiting on someone, promises made in a hallway that never made it into a system anywhere. The ones that got dropped weren't the big ones.

Nobody forgets a launch date.

It was the small hallway promise that quietly turned into a broken one, because it only ever lived in someone's head.

At home it looks smaller and just as real. A shoe nobody can find, a permission slip due Friday, a repair I keep meaning to get to on a boombox that's been sitting on the bench for three weeks. None of that is urgent enough to remember on its own. Capture means it goes into one place I actually check, the moment it shows up, before I've decided what, if anything, to do about it.

How do you turn a captured list into an honest orientation?

Orientation means sorting what you captured against what's actually true this week: your real energy, your real deadlines, and what's reversible if you're wrong. It's the same honest self-check I describe in decision-making under pressure, run at a slower pace and a longer interval, against a to-do list instead of a heart rate.

Pressure isn't the only thing that distorts a read on yourself. So does a full inbox. The email that arrived ten minutes ago always feels more urgent than the deadline three weeks out, even when the deadline matters more and the email doesn't. Orientation is the step where you catch that, on purpose, instead of working whatever showed up last.

The habit is the same one I rehearsed on a mountain and wrote about in Decision-Making Under Pressure: an honest read of your actual state before you touch a decision. At a desk, the read is different. It's not a heart rate number. It's asking which of these ten open items would actually matter if I only got to one, and admitting the honest answer is usually a smaller item than the one making the most noise.

What does the decide step need to produce?

The decide step needs to produce one concrete next action, not a category or a vague intention. Handle onboarding isn't a decision. Draft the onboarding email, twenty minutes, before three o'clock is. If the item leaving orientation can't fit that shape, it hasn't been decided. It's been renamed.

This is where most systems quietly fail, and I've watched it happen in product reviews as much as on a Tuesday morning at home. A backlog full of items like improve onboarding or deal with the garage isn't a decided list. It's a list of categories wearing a to-do list's clothes.

Nobody can act on a category. Somebody can act on draft the onboarding email, twenty minutes, before three.

Here's the version of the cadence I actually run, written the way I'd hand it to someone else:

How often should you review the system, and why do most people skip it?

Review on a fixed weekly slot, not whenever you remember to. Its only job is to catch what capture and orient missed that week. Skip it and the system doesn't fail loudly. It quietly stops being trusted, which is worse than never building one, because now you've also lost the habit of using it.

Mine happens Sunday evening, after the kids are down, fifteen minutes with the captured list from the week. I'm not doing the work in that slot. I'm checking whether the system told me the truth: did the important thing actually get the decide step, or did it get buried under six loud small ones again.

Some weeks the honest answer is no. That's fine. The review is what tells you, instead of finding out three weeks later when something you cared about quietly missed its window.

The metric I care about professionally is time-to-confidence: how long before someone under pressure knows what to do next. The personal version of that question doesn't need a mountain to matter. Most days the pressure is smaller: a full inbox, a house full of people who all need something at once, more open loops than hours in the day. Capture, orient, decide, review doesn't make any of that disappear. It makes sure the next move you take is an honest one, not the loudest one that happened to be standing closest.