You Already Have an Operating System
When people hear “system,” they picture something designed: an org chart, a playbook, a process someone built, or a tool. However, Merriam-Webster defines a system as “a regularly interacting or interdependent group of items forming a unified whole.” Nothing in that definition requires a conscious plan. The ways the parts work together can evolve over time, through habit, workarounds, or whatever else just gets everyone through the week. As a result, you can have a system, or live inside one, entirely by default. Yours might not be intentional or even effective, but it still exists.
The same is true for an organization: even the messiest of organizations has established ways that information moves, decisions get made, priorities get set, work gets reviewed, and problems get escalated. When that system is badly designed, you see the most visible symptoms: delay, confusion, duplication, workarounds, and inevitable frustration. If it doesn’t work well, instead of saying the system is broken, often we just say “oh that’s just how we do things here” and shrug.
One organization I was part of had its full company leadership meeting every Monday morning at 7 AM, but on Friday afternoons, everyone except the co-founders met to have a prep meeting so that no one “threw anyone else under the bus” on Monday. What started as a one-time fix calcified into a standing system that wasted hundreds of executive hours a year.
The same is true of each of us: whether we call the way we operate a system or not, we have established ways of managing requests that come in, deciding priorities, storing commitments, and (hopefully) finding our way back to neglected things. Your system may not be consciously designed, but it exists.
What might an accidental system really look like?
Your inbox is your to-do list, your filing cabinet, and your priority ranking all at once — so a request isn’t real until it’s an email. Everything that arrives by text, or the PTA group chat, or a hallway “hey, can you…” is invisible to the system until you re-enter it yourself, which is why you’re screenshotting texts and emailing them to yourself at 11 PM.
Monday’s plan is real when you make it. But there’s nowhere that Wednesday’s three new fires get reconciled against it, so the plan doesn’t fail so much as get quietly overwritten by whatever’s loudest. By Thursday you’re running a version that only exists in your head.
Your au pair knows exactly how pickup and homework and the after-school handoffs work — but none of it is written down anywhere. It runs perfectly, right up until the week she’s home in Germany and you discover how much of the operation was living in one person’s head. Now it’s floating in yours.
The only things with nobody else waiting on them (e.g., the workout, the dentist, the thing you actually wanted to write) get pushed to the side. They’re not lower priority; they’re just the only items where there are no witnesses to whether they happen or not. When the week compresses, those are your first casualties.
When the parts of your system don’t connect on their own, something has to connect them and, unfortunately, way too often that something is you. Fragmented or poorly designed systems that still allow you to function are doing so at the expense of time and attention that you could be spending on better things. Your brain ends up holding all the connections and your availability is what resolves the ambiguity. You find yourself lying awake remembering what your tools didn’t catch.
When the system is fragmented, you become the system.
The same attention that is doing all that work to stitch everything together also needs to find an algebra tutor or not only make it to book club but actually read the book this time.
From the outside, it looks like it’s working, but it looks that way because you keep making it work. And the more capable you are, the longer you can do it before anything visibly falls through the cracks.
The cost isn’t just what you do or don’t do and how well (or poorly) you do it — it’s the exhaustion, the dropped ball, the “why can’t I focus” moments, all of which feel like personal failures. But what feels like a character flaw may simply be a design problem.
Every busy person already has an operating system. In it, you can see exactly what gets your attention, where decisions stall, what’s stuck in your head, what only moves when you personally touch it, and what falls apart the minute you try to take some time off. The question isn’t whether you have one; it’s whether yours was designed for the life you’re leading — or whether you’ve just been the one holding it all together.
