Subject Analysis: The “Bacon Archetype” is the master of connection but the enemy of completion. He knows everyone in the building but does none of the work. His primary skill is cc’ing people until the original request is lost in the void.
Weakness: Direct Accountability.
Kevin Bacon invented a game to connect actors. Your boss invented a game to connect *you* to extra work on Friday at 4 PM. Only one of these games is fun.
The Executive Files
Swipe to identify your colleagues.
Six Degrees of “Let Me Loop In…”
The Infinite Loop of Delegation: Why a simple question has to bounce through six managers before it dies.
Jacob ZwackIt starts innocently enough. You need to know if the budget for the Q3 marketing campaign has been approved. It is a binary question. The answer is either “Yes” or “No.”
You send an email to your manager, Gary.
Gary, however, does not know. But Gary knows someone who might know. So Gary forwards your email to Susan in Finance, adding, “Looping in Susan for visibility.”
Susan is out of the office, but her auto-reply directs you to her assistant, Kyle. Kyle sees the email and panics, forwarding it to the Director of Strategy, Brenda, with the note, “Please advise.” Brenda, who has never met you and doesn’t know what Q3 is, cc’s an external consultant named Kevin.
Welcome to The Kevin Bacon Effect of corporate America.
In Hollywood, everyone is six degrees away from Kevin Bacon. In the office, every decision is six degrees away from the person who is actually authorized to make it. And just like the movie game, the goal isn’t to solve the problem; the goal is to connect it to as many famous people (Executives) as possible without actually doing any work.
The Flowchart of Doom
Why does this happen? Why can’t we just walk over to the person with the checkbook and ask? The answer lies in the Infinite Loop of Delegation.
In a healthy ecosystem, a task moves in a straight line: Request -> Action -> Result. In a bureaucratic ecosystem (your office), the task moves in a spiral. It gathers momentum and mass (in the form of “CC” recipients) but never moves forward.
The Anatomy of a “Loop In”
The Deflection: “Great question! Let me loop in [Name] who owns this vertical.” (Translation: I don’t want to deal with this).
The Expansion: “Adding [Department] to ensure we are aligned.” (Translation: If this fails, I want witnesses).
The Boomerang: The email thread gets so long that someone eventually replies, “Looping in [Original Sender] to clarify.” (Translation: We have come full circle).
This is not collaboration. This is a game of “Hot Potato” played with accountability. Nobody wants to be the one holding the potato when the music stops, so they toss it to the next person in the org chart.
The Connectors (People Who Exist to Forward Emails)
Every office has them. They are the human routers of the corporate internet. They do not generate content; they merely direct traffic.
You might recognize them by their catchphrases:
- “Adding value…”
- “Connecting the dots…”
- “Just want to make sure we’re seeing the forest for the trees…”
These “Bacons” are dangerous because they create the illusion of progress. A thread with 40 replies looks like work is happening. But if you analyze the text, 38 of those replies are just people adding other people to the thread. It is a Ponzi scheme of communication.
The Cost of the Connection:
Every time someone is “looped in,” a small piece of the project’s soul dies. Context is lost. Urgency is diluted. The original question—”Can I buy these pencils?”—transforms into a philosophical debate about the company’s procurement strategy for the next decade.
/// THE INTERVENTION ///
The Bartender Narrative
“You look like you’ve been CC’d on a thread that started in 2004,” the bartender says, not looking up from the glass he’s cleaning.
“I just asked for a login,” you sigh. “Now the VP of Engineering is involved.”
The bartender chuckles, a dry sound like shuffling papers. “Ah. The Bacon Effect. You ask a simple question. It bounces through six managers, three departments, and a consultant before landing on the intern’s desk. And the irony? The intern knew the answer the whole time.”
He sets the drink down—a Dark & Stormy.
“Here’s the thing about the chain of command,” he says, leaning in. “It’s not a chain. It’s a noose. The more people you loop in, the tighter it gets, until eventually, nobody can breathe, and certainly, nobody can approve your invoice.”
“Next time? Don’t ask permission. Just do it. It’s easier to apologize than it is to get seven signatures.”
Breaking the Chain
How do you stop the madness? How do you cut through the six degrees of separation and actually get work done?
1. The “BCC” Maneuver (The Silent Killer)
When a thread gets too heavy with “Bacons,” you must perform surgery. Reply to the person who actually knows the answer, move everyone else to BCC, and add a note: “Moving everyone to BCC to save your inboxes.” You are framing your coup as an act of mercy.
2. The “Walk and Talk” (The West Wing Method)
Email is the natural habitat of the Bacon. They thrive in Outlook. They die in person. If you physically walk to someone’s desk (or call them on Teams without scheduling it), you strip them of their ability to forward you. You force a real-time interaction. They cannot “loop in” Susan if Susan isn’t standing there.
3. The “Negative Option” Close
Instead of asking, “Can I do this?” (which invites delegation), say: “I am going to do this on Tuesday unless I hear otherwise.” This shifts the burden of labor. Now, to stop you, they have to actually do work. And since the Bacon’s primary goal is to avoid work, they will simply let you proceed.
The “Cut the Cord” Tools
If the bureaucracy won’t make a decision, maybe randomness will.
Decision Maker Dice
“Faster than a committee meeting.” Why wait three weeks for a steering committee to decide on lunch? Roll the dice. It’s just as logical as your company’s actual strategy, and significantly cheaper.
Buy the SolutionAffiliate Link