I spent years adding things to my life to become more productive. More tools, more habits, more systems, more goals. Every January looked the same: a list of things I would start doing. Read more. Exercise more. Write more. Ship more.
None of it lasted. And for a long time, I thought the problem was discipline.
It wasn’t. The problem was the frame. I was trying to engineer productivity by adding. The answer was to engineer it by removing.
———
There’s a line from complexity science that changed how I think about this: “Emergent phenomena are not more than the sum of their parts. They are fewer. Emergence is defined by what is not there. By constraints.”
Emergence is about removing options until the remaining ones have no choice but to combine in interesting ways.
Shakespeare’s best work came out of the tightest boxes. Fourteen lines, strict rhyme, iambic pentameter. The limitations forced creative solutions that unlimited freedom never produces.
The same principle applies to work.
———
When our team went from producing 15 pieces of content a month to 150, the breakthrough was constraining the process. We reduced the number of content formats from twelve to three. We cut the review cycle from five stages to two. We limited each piece to a single core idea with a single call to action.
Output went up. Quality went up. Stress went down. We eliminated the decisions that were eating our energy without producing results, and everything else took care of itself.
Every decision you don’t have to make is fuel for the decisions that matter. Most people exhaust themselves choosing between twelve formats before they’ve written a word. We removed eleven of those choices. The writing got easier because there was less to think about before thinking could begin.
———
Goals work the opposite way. A goal says: here’s something to add to your life. Run a marathon. Launch a product. Hit a revenue number. Goals are aspirational. They point you toward more.
Constraints say: here’s something to remove. No meetings before noon. No more than three active projects. No content piece longer than 1,000 words. Constraints are architectural. They shape the space you operate in.
The difference matters because goals require motivation and constraints require only compliance. You have to want to run a marathon every single morning. You just have to not schedule a meeting before noon. One depends on how you feel. The other doesn’t.
This is why constraints compound, and goals fade. By March, most goals are dead. A well-designed constraint is still working in December because it doesn’t ask anything of you. It just removes an option that was hurting you.
———
The practical application is uncomfortable because it means your job as a leader is to figure out what to eliminate. Which meetings. Which approval steps. Which tools. Which options.
Most organizations are drowning in optionality. They have fourteen communication channels, nine project management tools, and an infinite number of ways to format a slide deck. Every one of those options costs cognitive energy. Every one is a micro-decision that adds up to decision fatigue by 2 pm.
The most productive teams I’ve seen all have one thing in common: a leader who’s willing to kill things. Who looks at a workflow and asks, “What can I remove?” before asking what to add.
Subtraction is harder than addition because it requires judgment. Anyone can add a tool. Knowing which tool to remove requires understanding what actually matters. But that’s the work. Emergence is defined by what is not there. Build your systems the same way.