I’ve written before about the trap of being needed everywhere. What I hadn’t fully named yet is what that trap actually does to a portfolio while you’re inside it.
Normal Tuesday
Three calls before lunch. “Only you can decide this.” “We need your sign-off.” “Can you look at this before it goes out?”
Every one of those calls used to feel like proof. Proof he mattered, proof his judgment was irreplaceable, proof everything he’d built genuinely needed the person who built it. He’d hang up the third call and go back to whatever the first one had interrupted, and underneath the exhaustion there was a quiet satisfaction. Nothing moves without him. That has to mean something.
It does mean something. Just not what he thought.
What those calls actually proved was that authority had never been distributed. Not in the business that called first, not in the one that called second. The portfolio was being held together by one person absorbing gaps that structures should have closed years earlier, and the non-stop calendar wasn’t evidence of importance. It was the sound an architecture makes when it never finished building.
You already know the boiling frog metaphor. Forget it. It’s wrong for this, and it’s wrong in a specific way.
That metaphor assumes one pot. You have three. Four. Seven, if you count the ones you’ve stopped mentioning at dinner because explaining them takes too long. And in every single one, you are the heat source. You’re not sitting passively while the temperature climbs around you. You’re the one adjusting the flame, business by business, telling yourself each adjustment is temporary. Just this week. Fine for now.
None of it is fine. All of it is drift.
Two names are worth knowing here, not because you need the theory, but because they’ll save you from mistaking this for a personal failing.
Diane Vaughan studied how the Challenger disaster happened and found that nobody made one bad decision. Engineers watched the O-rings show damage, nothing exploded, and the damage quietly got reclassified from warning to acceptable. She called it normalization of deviance.
Sidney Dekker took it further. Drift doesn’t come from incompetence. It comes from success. From every moment the shortcut worked and the corner cut didn’t cost anything, filed away under “fine, I’ll deal with it later.”
Both were writing about one contained system. One organization, one hierarchy, one set of instruments. Nobody wrote the version for someone running three or five or seven businesses at once, where the compensating behavior that looks like leadership is actually the mechanism spreading the drift sideways. You take the call from Company B. While you’re on it, Company A and Company C drift exactly the amount you weren’t there to notice. You are the connective tissue holding the portfolio together, and connective tissue stretched across seven entities isn’t holding anything together. It’s the reason nothing gets caught until it’s already everywhere.
Control doesn’t collapse. It migrates. Quietly, continuously, in a direction you’d never choose if you could see it happening in real time.
How Control Migrates
Migration isn’t one event. It’s four currents running at once, and every one of them is disguised as something that looks like competence.
From systems into your calendar
Somewhere along the way you became the only decision authority left standing. Not because your team is incapable. Because you never built the conditions that would let them be capable without you in the room. “Nobody can decide without me” isn’t proof of your value. It’s proof that authority was assumed to exist because you were always there to exercise it personally, never actually handed to anyone else.
From documented standards into tribal knowledge
The new hire doesn’t read a process document. They learn what actually happens by standing near whoever’s been there eighteen months and absorbing whatever gets said in the hallway. What was unacceptable two years ago is now just how things are done, and nobody remembers deciding that. It accumulated, one exception at a time, the exact mechanism Vaughan documented, running quietly through your operations instead of a launch pad.
From structured rhythms into fire response
Look at your calendar honestly. It doesn’t look like a calendar anymore. It looks like a sequence of responses to things that already happened. Meetings that used to be decision forums have collapsed into status updates, because deciding anything costs bandwidth that’s already gone to reacting. And the dashboards stay green through all of it, which feels like proof things are fine. It isn’t proof of excellence. It’s the absence of visible crisis, and those are not the same thing.
From strategic judgment into operative judgment
Forward-looking review goes first. It’s expensive, cognitively. It asks you to hold uncertainty and sit with questions that don’t have an immediate answer. Backward-looking review survives because it’s safe. The data already exists. You stop asking where the portfolio is going, not because you decided to stop, but because answering that question costs bandwidth you no longer have.
Here’s what makes all four dangerous in a way a single warning sign never could be. Each one looks like you’re doing a good job. Responsive. Hands-on. Across the details. Every migration path produces behavior that would get praised in a review, which is exactly why nobody, including you, flags it while it’s happening.
Nice Fantasies That Look Like Success
None of what follows will trip an alarm on its own. That’s not an oversight. That’s the entire mechanism. These are the specific things you tell yourself that sound like competence and function as cover.
From the calendar migration:
- “Every critical decision comes to me” instead of “I’m the bottleneck”
- “My calendar is non-stop” instead of “I’m the only one who sees the full picture, and that’s a structural failure, not a strength”
- Meetings that used to decide things, now just reporting what already happened
From the standards migration:
- The venture you love gets your A-game. The others get whatever’s left, and you stopped noticing the gap
- “It works” quietly replaced “it’s excellent” somewhere in the last eighteen months, and you can’t name the day
- That same “good enough” data becomes the input for capital allocation across the whole portfolio, and nobody flags that the number was never reliable
From the rhythm migration:
- Forward-looking review shrank to bookkeeping, gradually enough that you never consciously chose it
- Difficult conversations with your team keep getting pushed, not from conflict avoidance, but because you genuinely don’t have the bandwidth this week, and “this week” repeats
- Your team absorbs cracks silently before they reach you, and you read the silence as things running smoothly
From the strategic migration:
- “I used to have time for positioning work. I don’t know where it went.”
- Your most trusted people start making bigger calls without checking in, and you genuinely can’t tell if that’s empowerment or absence
- You’re reacting to everything, all day, and somewhere in the last year you stopped being the architect and became the emergency response unit for a portfolio that used to have a plan
None of these trigger alarms individually. Most of them feel like success right up until you total the cost. Naming them isn’t about making you feel bad about any one of them. It’s about learning to tell the difference between genuine operational maturity and a system quietly masking its own degradation behind behavior that looks identical to leadership.
The Cascade Math
A single company has structural buffers built in whether the founder designed them or not. Middle management. Delegation layers that exist because headcount demanded them. Review loops nobody personally engineered, but that formed anyway because the organization needed somewhere for information to go that wasn’t directly through the founder. The organization compensates. It has to.
A portfolio run by one operator doesn’t have that. It has you.
Every time you compensate for a gap in one entity, you thin the bandwidth holding the others steady. You can watch one dashboard with the attention it deserves. Split across three, that same attention becomes a tax, and the tax itself becomes another source of drift, because the act of trying to stay aware across everything is what’s degrading your ability to see any one thing clearly. The instrument built to catch the drift is what’s generating the blind spot.
Run the arithmetic honestly. The gap between operating at seventy percent and operating at eighty-five percent inside one interconnected portfolio isn’t fifteen points. It’s that gap compounding at every intersection where the ventures share people, capital, decisions, or your attention. Every quarter. For however many years it’s been running.
And underneath the number sits a cost you can feel but can’t always point to:
- The talent that would have stayed if they’d been trusted with real authority instead of a title
- The repositioning that died in a queue behind thirty things that felt more urgent in the moment
- The decisions that landed two weeks late because they were waiting on you, and two weeks was exactly long enough for the window to close
- The market move you didn’t see because your attention was fully committed to a fire inside your own operations
Ask yourself the one question that actually matters. What are you genuinely not measuring right now. Not what you think you’re tracking. What you’ve verified with your own eyes in the last ninety days. Most multi-business operators don’t have a real answer to that if they’re honest. The silence where the answer should be is the drift, made audible.
The Flagging System
This isn’t a reflection exercise. It’s three instruments. Each one gives you a number, and the number tells you what to do next.
The drift load checklist.
Ten questions. Yes or no. One point per yes, multiplied by ten.
- Has a decision come to you this week that a documented process should have resolved without you?
- Is there a business you haven’t personally inspected, beyond the dashboard, in over sixty days?
- Has a standard that used to be non-negotiable quietly become “how we do it now” without anyone deciding that on purpose?
- Did a meeting this month turn into a status report when it was supposed to be a decision forum?
- Have you postponed a difficult conversation with someone on your team more than twice?
- Is there a system everyone’s routing around instead of fixing?
- Has forward-looking review been replaced by backward-looking review for more than one quarter?
- Have you caught yourself reacting to something a functioning early-warning system should have flagged weeks earlier?
- Did someone make a decision without checking in, and you genuinely can’t tell if that’s empowerment or absence?
- If you disappeared for two weeks with no contact, is there more than one business you’re not confident would keep moving in the right direction?
Score Zone – What it means
The calendar split.
Pull your last full week. Real hours, not scheduled hours. Categorize every block:
- Decision forum: A meeting or conversation where a real choice was made. Not discussed. Decided. If nobody left with a different position than they arrived with, it wasn’t a decision forum.
- Status update: Information passing in, no decision required. Reporting. Reviewing. Listening to updates where your only job was to be present.
- Reactive response: You were responding to something. Email, Slack, a text, a crisis. The hour was shaped by something arriving, not by something you planned.
- Deep work: You were alone with a strategic problem. Not solving today’s fires. Looking ahead. Building something that takes sustained focus without interruption.
Now add up the hours in each category. Divide by total working hours for the week. That gives you four percentages.
If decision forum is above twenty percent: your architecture still functions. You’re spending enough time in real choices that the structure holds.
If it’s between ten and twenty: migration is happening. You’re reacting more than deciding, and the ratio will keep shifting unless you intervene.
If it’s below ten percent: you’re no longer leading. You’re being led by urgency. Pick one decision forum this week and protect it as non-negotiable. Not because it fixes everything. Because it’s proof the architecture can still hold if you insist on it.
The question this answers: are you still the architect, or have you become the emergency responder who happens to have a calendar?
The extraction evidence log.
Pick one function inside one business. List every decision, review, or input that currently routes through you. Sort each into three buckets.
Genuinely strategic: direction, capital, relationships only you can hold. Smaller than you think.
System gap: you’re the one deciding because nobody was ever given the authority, the criteria, or the boundaries to decide instead. This is infrastructure failure, not CEO necessity.
Habit and comfort: you do it because you always have, and stopping feels irresponsible even though it isn’t.
Extract everything in the habit bucket immediately. Transfer every system-gap item to a named owner, with real criteria and real boundaries, not a vague “you handle it” that quietly guarantees the next failure gets blamed on delegation instead of on the missing infrastructure.
Keep a log. Two columns: what you feared would happen, what actually happened. The gap between those columns, once you’ve run it a few weeks, is the whole game. It’s almost always wider than you expect, and it’s the only evidence that will actually update the part of you that’s been reading silence as danger.
The Calibration
You don’t fix migration by adding another system on top of the ones already straining. You fix it by removing the structural reason your personal involvement is still required.
- Three moves. One each. This month. Replace the person carrying a role they were never equipped for, and everyone, including them, already knows it. Migrate the one system generating friction you’ve normalized past the point of noticing. Kill the process consuming real bandwidth without producing decisions of any real quality.
If anyone needs more than thirty days, the scope is too wide. Narrow it until something moves inside this month.
- The cadence rule. Run the drift load checklist again every quarter. Track the number, not as a scorecard for your ego but as an instrument. A flat trend across two or three quarters doesn’t mean nothing’s wrong. It means the diagnostic is running and the execution isn’t, which means the discomfort of changing something that technically still works is winning against the discipline of fixing what’s quietly bleeding you dry.
- The twelve-month math. Over a year, that’s twelve high-drag items resolved. Twelve friction points removed from a portfolio where every entity shares resources, attention, and decisions with every other one, which means reducing drag in a single place lightens everything sitting next to it. That compounds harder than any new initiative you’ll launch this year, and it will never once produce the dopamine of a launch day. It produces something better: a portfolio finally running at the standard you’re actually capable of, instead of the one you’ve been quietly settling for in the places you stopped inspecting.
The real problem underneath all of this isn’t willpower. It’s that drift is invisible without a structural way to sense it. You can’t fix what you can’t see arriving, and you can’t see it arriving because the instruments you’re using were designed for single-company review, not portfolio-wide degradation. The calibration moves above buy you time. They create space. But space without a sensing mechanism just means the drift has more room to accumulate before you notice it again.
What you actually need is a systematic operating rhythm built into how the portfolio runs day-to-day – not bolted on during a crisis, not dependent on your personal attention to catch it. I’m building Back2Control because I kept watching the same pattern repeat. A sensing mechanism that surfaces migration before you’re the one who has to personally absorb it. That’s the only kind of fix that lasts. It doesn’t require you to be more intentional. It requires the architecture to be more intentional than you are, which is exactly what you failed to build the first time around.
The Question That Remains
Control migration isn’t failure. It’s the default behavior of any complex system left without a structure actively working against it. The operator who catches it early isn’t smarter than the one who doesn’t. They’ve built the sensing architecture that makes catching it possible, and everyone who hasn’t built that is running exactly the same risk, whether the dashboard is green today or not.
The wrong question is “am I losing control.” By the time you’re asking it out loud, some part of you already knows the answer, and the question has become a way of delaying the part where you act on what you know.
The real question is this. What has already migrated without you noticing, and where is the cost compounding right now, inside the entities you don’t visit enough to see it happening?
“Adequacy has no alarm. That’s why it runs forever. Migration doesn’t either, until you build the instrument that gives it one.”
Sources
- Diane Vaughan, The Challenger Launch Decision (1996) – normalization of deviance, referenced once inline as the origin of the pattern.
- Sidney Dekker, Drift into Failure (2011) – drift as a product of success rather than negligence, referenced once inline as contrast.
- Daniel Krynzel, Entrepreneur, 2026 – “The quality of your leadership is determined long before your first meeting.” Relevant to the calendar and strategic migration sections but not currently woven into the draft. https://www.entrepreneur.com/leadership/entrepreneurs-lose-control-of-attention
- Cognitive Load Theory / decision fatigue research – the mechanism behind why the four migrations accelerate under sustained portfolio load. Not currently woven into the draft. https://thedecisionlab.com/reference-guide/psychology/cognitive-load-theory and https://www.linkedin.com/pulse/decision-fatiguethe-silent-productivity-killer-small-business-horton-4wv2e
- Pitt-Walker, Forbes, April 2026 – the “boiling frog” leadership dilemma entering mainstream business discourse. Not currently woven into the draft. https://www.forbes.com/councils/forbescoachescouncil/2023/04/05/is-it-the-new-normal-or-a-tale-of-a-boiling-frog-a-leadership-dilemma/
- Zuzana Konupkova, “Nothing Is Broken. That’s the Problem.” (May 26, 2026) – the adequacy framework and closing quote lineage. https://www.zuzana.pro/intel-hub/vault/focuspath/nothing-is-broken-thats-the-problem/
- Zuzana Konupkova, “You’re Not Holding It Together. You’re Holding It Back.” (May 19, 2026) – the indispensability trap and the Tuesday scene, entry point for this piece. https://www.zuzana.pro/intel-hub/vault/focuspath/youre-not-holding-it-together-youre-holding-it-back/
