Personal operating system: practical guide

Personal operating system is a personal agreement about how you capture obligations, choose work and review commitments. List the places where promises currently live, including messages, notebooks and calendars.

What this guide is best for: readers who need to make a concrete decision about personal operating system.

How do you put this into practice?

Use the following sequence as a starting plan, then adjust it to the work you are responsible for.

  1. List the places where promises currently live, including messages, notebooks and calendars.
  2. Keep one commitments list and use your calendar only for work that needs a time.
  3. Record the action you chose, its intended result and the next occasion on which you will check it. Keep the record in a place you can return to without rebuilding your setup.

How do the options compare?

CheckpointRecord
Failure to avoidDo not migrate every old note before testing the next real commitment

What would this look like in practice?

A consultant brings a promised proposal and a family appointment into one review, while keeping the confidential proposal in its approved workspace. This is an illustrative scenario, not a customer result or evidence of a measured improvement.

Which planning principle supports the method?

The National Cancer Institute’s archived implementation-intentions resource describes if–then plans that connect a situational cue with an intended action. Spry’s examples here are editorial applications of that planning idea, not evidence that this particular guide or product produces a measured outcome. The source is retained for reference and is no longer maintained.

Source reviewed 2 November 2026.