Every System Discovers the Same Thing

The accidental consensus

If you’ve bounced between enough productivity systems, you start noticing something odd. GTD tells you to get everything out of your head and work from a short list of next actions. Agile tells engineering teams to limit work-in-progress to one or two items per person. OKRs demand you pick three to five objectives per quarter - and reject everything else. Deep Work tells you to protect uninterrupted blocks because even a quick Slack check destroys your focus for the next twenty-three minutes.

Different decades. Different industries. Different problems. And yet they all landed on the same constraint.

Not because they copied each other. Because they each ran into the same wall.

The wall has a name

Cognitive psychologist Nelson Cowan spent years refining what George Miller first mapped in 1956. The updated research is clear: your working memory holds three to four items at once. Not seven (that number was a misreading of Miller’s data), not the twelve priorities on your quarterly plan, and definitely not the forty-seven tasks in your backlog. Three to four.

This is Cowan’s limit, and it’s not a suggestion. It’s a hardware constraint. Your prefrontal cortex physically cannot juggle more than a few chunks of information simultaneously. Every additional item you try to hold doesn’t just compete for attention - it degrades your ability to think about any of the others.

Here’s what that looks like in practice. You sit down to work on a client proposal, but you’re also holding “reply to that email,” “follow up on the invoice,” and “prepare for Thursday’s call.” Four items. You’re at capacity. Now someone pings you about a fifth thing, and suddenly you can’t think clearly about any of them. That fog isn’t a character flaw. It’s a buffer overflow.

How each system works around the same limit

Once you see the constraint, each methodology’s design choices stop looking like philosophy and start looking like engineering.

GTD’s “mind like water” is literally about emptying working memory. David Allen’s core insight - “your mind is for having ideas, not holding them” - is a direct response to Cowan’s limit. Capture everything externally so your three to four slots are free for actual thinking. The weekly review exists because you can’t maintain both tactical execution and strategic awareness simultaneously - your brain’s task-positive and default-mode networks are antagonistic. You need a scheduled moment to switch between them.

Agile’s WIP limits operationalize the same constraint for teams. When engineers carry one or two active items instead of five, they stop paying the twenty-three-minute context-switching cost that Gloria Mark’s research documented at UC Irvine. That’s not a productivity hack. It’s removing a tax that was eating a third of every engineer’s day.

OKRs’ “three to five objectives” force what most organizations refuse to do - say no to good ideas. When Google standardized this framework, the numerical constraint wasn’t arbitrary. Three to five objectives is the range where leadership can keep major priorities in working memory during operational decisions. Go above five, and people start quietly pursuing their own interpretation of what matters.

Deep Work’s time blocks protect continuous attention because Newport understood that even brief interruptions don’t just cost the interruption time - they leave “attention residue” that fragments your thinking for minutes afterward. The four-hour daily limit on deep work isn’t discipline advice. It’s a metabolic constraint imposed by the prefrontal cortex’s energy demands.

The pattern behind the pattern

What’s striking isn’t just that these systems converge on the same limit. It’s that they were developed by people in completely different contexts - a productivity consultant, software teams in the 1990s, Intel and Google executives, a computer science professor - and they each independently arrived at the same set of solutions:

1. Externalize - get commitments out of your head and into a trusted system
2. Constrain - limit active work to what working memory can actually hold
3. Protect - guard focused time because switching costs are devastating
4. Review - create scheduled moments to step back from execution and assess direction

These aren’t four different ideas. They’re four facets of one idea: respect the bottleneck.

The implication is uncomfortable for productivity enthusiasts. The search for the perfect system is the wrong search. GTD, Agile, OKRs, and Deep Work aren’t competing philosophies. They’re different languages describing the same physics. Switching from one to another won’t fix anything if the real problem is that you’re trying to hold twelve commitments in a brain that handles four.

What actually matters

Masicampo and Baumeister’s research at Florida State added an important footnote to all of this. They found that you don’t have to complete a task to free up the mental slot it occupies. You just need a specific plan - a concrete “when and where” for handling it. The brain treats a real plan the same way it treats a completed task: the open loop closes, and the working memory slot frees up.

This means the most valuable thing any productivity system does isn’t organize your tasks. It’s help you make credible commitments about a small number of things so your brain can stop running background processes on everything else.

The freelancer who picks three priorities each morning and writes them down is doing the same cognitive work as the Agile team limiting their sprint to four stories. The founder who sets three quarterly OKRs is doing the same work as the writer who blocks off two hours for deep focus. They’re all closing loops and clearing slots.

The liberating conclusion

You can stop looking for the right system. There is no right system. There’s only the constraint - and any system that helps you respect it will work.

The question isn’t “GTD or OKRs?” It’s “Am I trying to hold more than three or four things at once?” If the answer is yes, no methodology will save you. If the answer is no, almost any methodology will serve you.

This is what Compass is built around. Not a new framework. Not a better to-do list. Just a daily practice of narrowing your commitments to what your brain can actually hold - and helping you let go of the rest. Because every great system already discovered the same thing. The difference is whether you’re willing to actually live within the limit.