# The Magic Click Is Just Plumbing *When systems work, the work feels like magic. The magic is engineering you stopped noticing.* # The Magic Click Is Just Plumbing *When systems work, the work feels like magic. The magic is engineering you stopped noticing.* ![[HERO] The Magic Click Is Just Plumbing](https://cdn.marblism.com/TTquaTGEcgD.webp) You've been waiting for it. The Sunday-night moment where, after two weeks of grinding, the strategy finally locks in. The morning after a hard sleep where the answer to the team problem is suddenly obvious. The mid-shower epiphany where the architecture you've been chewing on for nine weeks resolves into something elegant. You call it "getting clear." You call it "the click." You read the productivity blogs that promise it as the reward for the right morning routine, the right meditation app, the right journaling practice. You write down the question on a notecard and put it under your pillow. The click does not come. The reason is not that you haven't tried hard enough. The reason is that the click was never going to come the way you've been waiting for it. The click is not a moment. The click is an output. It is the *result* of a system that's working, observed from the outside, after the fact. People who experience constant clicks are not more in tune with the universe. They've built better plumbing. They've fixed the right bottleneck. They've made the right behaviors automatic. The clarity they describe is the *receipt* the system gives them once the system actually runs. You are waiting for the receipt without ever having installed the system. ## What Eli Goldratt named in 1984 In 1984 an Israeli physicist named Eliyahu Goldratt published a strange business novel called *The Goal*. The book follows a fictional plant manager named Alex Rogo as he tries to save his factory from being shut down. The plot is forgettable. The framework inside it has been read by every operations executive of the last forty years. Goldratt called it the Theory of Constraints. The argument is short. In any system — a factory, a company, a team, a personal calendar — there is exactly one bottleneck at any given moment. The bottleneck is the slowest step. The throughput of the entire system is determined by the throughput of the bottleneck. Improving anything that is not the bottleneck does not improve the system. Most of the time it makes the system worse, because it builds up inventory in front of the bottleneck. Find the bottleneck. Fix it. The bottleneck moves to the next slowest step. Find that one. Fix it. Repeat. The reason Goldratt's framework matters for senior operators is what it implies about all your other work. If you are not currently working on the bottleneck, the work you are doing is not improving the system. It feels productive. It looks productive. It is not productive at the system level. The reason your project hasn't shipped is not that you haven't worked hard enough. It's that you've been working hard on the third-most-important step. The bottleneck has been somewhere else, untouched, all along. Most senior operators don't know what the bottleneck is on their own project, because they've never sat down and asked. They've been busy. Busy is not the same as un-bottlenecked. The first move of any plumbing fix is identifying the clog. ## What Donald Norman documented in 1988 Donald Norman is a cognitive scientist who spent his career studying the gap between how systems are designed and how humans actually use them. In 1988 he published *The Psychology of Everyday Things*, retitled *The Design of Everyday Things* in the 1990 paperback. The book has sold over a million copies and is on the syllabus of every design program in the world. Norman's central observation, which has been replicated across forty years of HCI research, is that good design is invisible. When a door works, you don't notice the handle. You walk through. When a system works, you don't notice the system. You operate inside it. The systems you notice — the broken doors with confusing handles, the apps with bewildering nav, the workflows that require six clarifying messages to complete — are the broken ones. Functioning systems disappear into the background of your attention. This is what makes them so hard to build, and so hard to value while they're running. Most senior operators have built broken systems on their own projects, and they have grown so accustomed to operating inside them that the brokenness has become invisible to them. Not because they don't see it, but because they see it so often that it stopped registering as a problem. The friction has become the texture. The "magic click" you keep waiting for is what would happen if the friction wasn't there. If the project were built on systems that disappeared when they worked, the click would happen continuously. You wouldn't have to wait for it. The system would produce it as a side effect. Norman's whole career is the answer to your question. Build systems that work. Stop noticing them. The click will arrive on its own. Until then, the noise you keep wading through is the cost of the systems you didn't build. ![A stick figure juggling tasks next to organized pipes, illustrating systems that work invisibly when built right.](https://cdn.marblism.com/ROwK1rPZskT.webp) ## What Charles Duhigg explained in 2012 Charles Duhigg is a former *New York Times* reporter who in 2012 published *The Power of Habit*. The book sold over three million copies and made the basal ganglia famous. The neuroscience underneath the book is real and decades old. When a behavior becomes a habit, the work shifts from the prefrontal cortex (the deliberate-thinking layer) to the basal ganglia (the automatic-pattern layer). The same physical action that took 90% of your attention on day one takes 5% of your attention by day 60. The behavior didn't get easier. It moved to a different part of your brain that runs on different metabolic rules. Duhigg's argument is that this is not just true for tying your shoes. It is true for every recurring behavior in your operation. Decision-making patterns. Meeting cadences. The way your team handles a stuck ticket. The way you respond to a customer complaint. The way you decide whether to ship. When the behaviors are habits, they happen automatically. They don't draw on the limited prefrontal layer. They run cheap. When the behaviors are *not* habits, every instance requires deliberate thought. Every meeting starts from scratch. Every decision is re-litigated. Every Tuesday feels like the first Tuesday. The system never gets cheaper because it never moves out of the deliberate layer. This is what builds the noise that drowns out the click. You're running every operation as a fresh decision, drawing on a finite resource, every time. Of course you don't get clarity. There's no metabolic budget left for clarity. It all went to deciding the same Slack reply you've decided forty times before. The fix isn't more thinking. The fix is fewer decisions, more habits, more of the work moved to the cheap layer where the basal ganglia handles it without you. ## Three plumbing fixes You don't fix this with a retreat. You fix it with three concrete moves. **1. Find the actual bottleneck.** Open a doc. List every step required for your project to ship. For each step, write how long the step is currently taking. Find the step that is taking the most time. That's the bottleneck. Don't optimize anything else. The Goldratt move. Most senior operators discover the bottleneck is not where they thought it was, and the first hour spent in front of it is the most leveraged hour they've spent in months. **2. Make the broken systems visible.** Walk through your operation tomorrow with a notebook. Every time you have to ask a clarifying question, every time you re-explain something to someone, every time you re-decide a thing you've decided before — write it down. By Friday you'll have 30-50 entries. Each one is a Norman-style invisible-broken-system. Pick the three that hurt the most. Build small systems for them. Watch the noise drop. **3. Convert one decision per week into a habit.** Pick one recurring decision you make multiple times a week. Make the rule once, in writing, on a single page. Stick it on the wall. Run the rule for two weeks without thinking. Duhigg's move. After two weeks the decision has moved out of the deliberate layer. The metabolic budget that decision was eating is now available for clearer thinking elsewhere. If you want a second voice in the room while you do this, that's exactly what a [6-Week Build Partnership](https://www.unstuckwithmolly.com/work-with-me/build-partnership) is. ## The reframe You are not unclear because you haven't journaled enough. You are unclear because the operation you're running is producing noise faster than you can process it, and the noise is masking the click that would otherwise arrive on its own. The click isn't a moment. The click is the receipt the system gives you for being well-built, and you've been waiting for the receipt while skipping the construction. Pick the bottleneck. Make one broken system visible. Habituate one decision. The water flows when the pipes are connected. There is no other way. ![Messy hoses versus a clean valve handle, showing the difference between effort and infrastructure.](https://cdn.marblism.com/MkLX0I611bf.webp) ## Sources - [Eliyahu Goldratt, *The Goal: A Process of Ongoing Improvement* (1984)](https://www.toc-goldratt.com/en/product/the-goal/) — the foundational Theory of Constraints novel - [Donald Norman, *The Design of Everyday Things* (1988, revised 2013)](https://www.basicbooks.com/titles/donald-a-norman/the-design-of-everyday-things/9780465050659/) — chapters 1-2 on invisible-when-working systems - [Charles Duhigg, *The Power of Habit* (2012)](https://charlesduhigg.com/the-power-of-habit/) — chapters 1-3 on the basal ganglia and the structure of habit formation - [Eliyahu Goldratt & Jeff Cox, "What Is This Thing Called Theory of Constraints"](https://www.toc-goldratt.com/) — the operational follow-up to *The Goal* with the five focusing steps in summary form ## About the Author Molly Shelestak is a Build Partner for Side-Project Shippers. With 20+ years in tech — from Google to Heap to Contentsquare — she helps senior tech employees stop tinkering and actually ship their side projects in 6 weeks. ## Related - [Wait for Clarity Fallacy](https://www.unstuckwithmolly.com/writing/wait-for-clarity) - [Decision Debt Is Why You're Tired](https://www.unstuckwithmolly.com/writing/decision-debt) - [Systems for the Unreliable Human](https://www.unstuckwithmolly.com/writing/systems-for-unreliable-human) - [Work With Me](https://www.unstuckwithmolly.com/work-with-me)