The Structural Trap of Entangled Work

So what if the reason you're burning out at work isn't because you just have, you know, too much to do, right? But because your company is secretly forcing you to do like 3 completely contradictory jobs at the exact same time. Yeah, it's wild when you actually see it happening. It really is. And if you're listening to this right now and you consistently feel like you are just drowning at your job, even though you're working harder than ever, exactly, working longer hours, trying your best, but still feeling like you're failing to keep your head above water? Well, this deep dive is specifically for you. Mm-hmm. Today we're opening up a brilliant document. It's called The Conditions of Entangled Work, and our mission today is to speak directly to this specific group of people that the text calls the coordinating middle, the unsung heroes. Really? That's totally— if you're one of the people basically keeping your organization from collapsing under its own structural weight, We're going to look at why your exhaustion is not a personal failure. That's such an important point. We're also going to explore why your company's generic leadership training is actually making you feel worse. And of course, we'll walk through the specific practices that can help you survive and actually thrive. So, okay, let's unpack this. What's fascinating here is that the foundational premise of this text is that we are living in this business era that just routinely misdiagnoses a structural contradiction as a personal weakness. Right, like blaming the person instead of the system. Exactly. To really understand why you feel so drained, we have to look at the actual environment you're operating in. And the author illustrates this beautifully by introducing a leader named Maya. Oh yeah, her story is so relatable. Right. So during her first 100 days at a new company, Maya decides to just observe. She's just taking it all in, and she immediately spots this massive canyon between the company's official laminated framework. Like the glossy all-hands presentations. Yeah, the ones screaming about agility and transformation and customer centricity. She sees the gap between that and the punishing, confusing reality of the daily grind that the employees are actually experiencing. Which is such a universal experience. I mean, the formal language on those corporate slides is basically just a wish list. A total wish list. The organization is demanding to be faster and more integrated and more innovative and more disciplined all at once. And that brings up a really crucial distinction that the text makes. There's a massive difference between having difficult work and having what the author calls entangled work. Yes, because difficult work, you know, it makes logical sense. It might be a technically complex project or an urgent deadline or navigating tricky personalities. Exactly. But the objective is clear. You know what success looks like. You can actually orient yourself and measure your progress. But entangled work is functionally different. It forces you to carry contradictory logics at the exact same time. Yeah. And there's no clear rule for which one takes priority when they inevitably collide. Right. And they always collide. They always do. So the text breaks this down into 3 specific colliding logics of work: run, serve, and change. Okay. Break those down for us. Sure. So run is the logic of stability and control. It's reliability. It's about keeping the core operations functioning without any errors at all. Just keeping the lights on, basically. Yeah. Yeah. Then you have Serve. Serve is the logic of responsiveness to stakeholders. It's about adapting immediately to whatever a specific client or partner or internal team needs right in that moment. Dropping everything to fix a problem for an angry client. Exactly. And finally, you have Change. This is the logic of disruption, experimentation, and moving the organization toward a totally different future state. So to picture how these conflict, it's like, well, think of it like being asked to fly a commercial airplane, which is your run logic. Keep it in the air. What an analogy. But at the same time, you have to serve customized drinks to every single passenger. So that's your serve logic. Right. And while doing all of that, you are ordered to rip out and redesign the engine mid-flight. That's the change logic. Oh, wow. Yeah, that's a terrifying way to visualize it, but it's spot on. The system doesn't just slow down under that pressure, it functionally crashes. And when those three logics crash into each other, the organization simply doesn't have a mechanism to resolve the conflict. Let me play devil's advocate for a second here, though. Go for it. If I'm a senior executive listening to this, my immediate reaction might be, well, welcome to the modern economy. Right, suck it up. Yeah, like markets move incredibly fast. We have to be stable, responsive, and innovative all at once to survive. So if someone can't handle multiple priorities, don't they just need to manage their time better? Or build up some resilience. Yeah. I mean, hasn't work always been hard? Why is this structurally different from just having a very demanding modern job? Well, the text actually anticipates that exact executive argument. What is structurally new here is the fusing together of these demands combined with incredibly weak ranking. Weak ranking. Yeah. So in previous decades, an organization would separate those logics by department. The operations team handled the run work. The account managers handled the serve work. Oh, I see. And the R&D or strategy department handled the change work. But today, those contradictory logics are folded into the exact same role, the exact same team, and the exact same time horizon. That sounds impossible. It is. And the organization refuses to rank them. It simply mandates that all 3 are top priorities. So everything is a priority, which means nothing is. Exactly. And that lack of ranking privatizes the contradiction. The system is essentially telling the individual, you know, we aren't going to make the hard choice of what matters most, so you need to figure out silently and deliver all of it. And the cost of forcing individuals to silently figure out those contradictions is what the text brilliantly calls the confusion tax. Yes, the confusion tax. It's the hidden, exhausting burden of constantly interpreting and repairing and translating these conflicting demands. You don't just do your work anymore. No, you spend hours figuring out how to do your work without triggering a political landmine. Exactly. The system ends up paying for unclear work with more work. And this confusion tax manifests in organizational habits that will sound painfully familiar to anyone listening. The first one is coordination theater. Oh, coordination theater is so real. Because the actual priorities are just a tangled mess, people start generating highly visible activity to compensate. You see a sudden multiplication of cross-functional syncs, status updates, governance committees. Let's look at what that actually looks like in practice. Mm-hmm. It's the biweekly 45-minute alignment meeting with 15 different stakeholders where absolutely nothing is decided. Yes. You spend the whole time looking at a status tracker. Right. And no one wants to make a definitive call because if you prioritize a serve request for a client, you might get penalized later by the compliance team. Enforcing the run metrics. Oh, man. So instead of acting, everyone just updates each other endlessly. It mimics the look of collaboration, but it's actually a defense mechanism. It's just an illusion of coherence. And because making a decision in that environment is politically and morally expensive, it leads to the second symptom, which is decision latency. Decision latency. Decisions just hover in the air. They recirculate for more input, more socialization, more alignment. Over and over. When everything is a top priority, pulling the trigger on any single action carries immense risk. And if the executives at the top of the hierarchy are refusing to resolve these contradictions, gravity dictates that the unresolved mess has to roll downhill. It always does. It lands squarely on the group of people the text calls the coordinating middle. So if you are a project lead, a regional operator, a department head, or a chief of staff, this is you. You're in the crosshairs. You are close enough to the ground to feel the operational friction of actually delivering the work, but you are senior enough to absorb all the strategic ambiguity cascading down from the executives. And the defining trap for the coordinating middle is a condition of full accountability with partial control. You're carrying the implementation risk, the timeline, the client relationship, but you exist in a matrix structure, meaning your authority is scattered. Right. You might be held totally accountable for launching a new product, but the engineering team you need to actually build it reports to a different boss in a different time zone. Yep. And they have an entirely different bonus structure based on different KPIs. You don't have the sovereign authority to force them to do the work, but if the launch fails, your name is on the postmortem. Exactly. You are carrying all the exposure with none of the leverage. And in this middle space, The text points at a really tragic dynamic between two types of workers: the quiet operators and the visible politicians. Okay, tell us about the quiet operators. The quiet operators are the ones doing the vital invisible repair work. They're the ones who notice that three different departmental agendas are on a collision course, and they spend hours quietly brokering peace deals and adjusting timelines to prevent a disaster. They actually build functional coherence. But the system rarely recognizes or rewards that invisible repair work. Almost never. Instead, it promotes the visible politicians. These are the individuals who operate in that coordination theater by signaling absolute certainty. They attach themselves to whatever project has executive sponsorship. They speak in confident bullet points, and they seamlessly export all the messy ambiguity downward onto their teams. They look highly legible to the executives. Yeah, they look like go-getters. It's a profound misalignment of incentives. The environment rewards performative confidence while burning out the people who are actually keeping the operations from shattering. Which brings us to the toxic downward rhetoric used by senior leadership when the middle inevitably starts showing signs of strain. Maya, the leader we discussed earlier, she keeps hearing executives use variations of the exact same phrase. Oh, this part is so frustrating. They sit in boardrooms and say, you know, my people just aren't good enough. They complain that the middle managers aren't strategic enough, or they lack a growth mindset, or they simply aren't resilient enough to handle the pace of change. The author identifies this language as a displacement device. A displacement device? Yes. It's a psychological mechanism that allows leadership to avoid a terrifying reality, which is that the system they built is structurally broken. Right. It is much easier for an executive to say our managers lack resilience than it is to admit we have designed an incoherent organization that convert a structural failure into a personal defect located safely below them on the org chart. And if you are operating in the coordinating middle right now, you really need to hear this next point clearly. When you're immersed in that environment, it is incredibly easy to internalize that impossible structure as your own personal failing. So easy. You look at your to-do list, you see the conflicting demands from different stakeholders, and you think, I'm failing. If I just managed my time better or read the right productivity book, I could get on top of this. But you're not. Exactly. You are not a failing self. You are acting as the human shock absorber for a poorly designed system. You are physically carrying the gap between the coherence the company wants on paper and the messy reality it actually has. And when you understand that, you start to see why the organization's default solution to this burnout is so ineffective. Yeah, because when the coordinating middle shows exhaustion, what does the company do? They send them to leadership training. There is a really revealing anecdote in the text about this. Maya is having coffee with a senior executive, and they're discussing the company's expensive new leadership development program. And the executive just rolls his eyes and says, the training is fine if what you need is more confident PowerPoint skills and slightly better eye contact. Right. But it has absolutely nothing to do with how the company actually runs. The reason traditional leadership development fails you is that it was designed for what what the text calls clean roles. Hmm. The curriculum assumes you are either a first-line supervisor managing a very bounded, highly visible team on a factory floor. Where you can literally see everything happen. Right. Or it assumes you are the apex CEO who can just decree a strategic vision from the mountaintop and have it executed. It assumes a simple linear world. But you don't live in a simple world. You live in a deeply entangled world. Your job is cross-boundary integration without direct authority. Exactly. And the text labels this traditional training approach as self-heavy and structurally thin. I love that phrase. It's so accurate. The seminars focus entirely on your mindset. They want to talk about your emotional intelligence, your executive presence, your personal resilience. They take a massive structural problem and they psychologize it. They tell you to fix yourself. Yes. Completely ignoring the fact that the Matrix system you return to on Monday morning is practically designed to break you. And this brings us to one of the most sobering concepts in the entire document, which is moral injury. Yeah, let's talk about that. We typically reserve this term for medical or military contexts, right? Mm-hmm. The trauma of being unable to do what you know is right. But the text argues it happens in corporate organizations constantly. This goes far, far beyond standard burnout or fatigue. Moral injury is the ethical strain of being forced to repeatedly act in ways you cannot fully respect. So what does this all mean? We need to pause and acknowledge the gravity of using a term like moral injury for a corporate manager. Let's look at what that ethical strain actually feels like. Okay. Imagine you are handed a mandate from above to cut your department's budget by 15% while simultaneously increasing your output by 20%. A classic impossible mandate. Mathematically, it cannot be done without breaking the product or breaking the team. You know it, the executives know it, but you have to stand in front of your team, put on a brave corporate face and say, you know, this is an exciting challenge and we can do this if we just work smarter. Yeah. You are actively lying to the people who trust you in order to protect the structural incoherence above you. That is exactly the mechanism of moral injury. You are forced to perform support for a strategic plan you know is doomed. When your leadership training tells you to take extreme ownership and be decisive, but your actual role gives you zero legitimacy to make a real call. It's madness. It becomes a form of psychological torment. It increases your ethical strain because the organization is pretending to support you while refusing to change the conditions causing the harm. If you've ever sat in a corporate mindfulness seminar and felt a deep cynical disconnect. That is why you aren't crazy. The organization is trying to put a psychological bandaid on a structural wound. Right. So if generic resilience training and better eye contact are not the answer, what is the actual toolkit? How do we help the listener navigate this and actually survive? The practical toolkit begins with a foundational step, which is better distinctions. You cannot manage a tangle you cannot accurately name. When you learn to look at your workload and categorize the tasks specifically as run, serve, or change, you gain immediate leverage over them. That makes a lot of sense. The work stops being an undifferentiated mass of panic and becomes a set of competing logics. And from there, the text offers a new framework. You have to read three elements together: self, role, and system. You must stop automatically blaming the self, your own mindset or ability, for what is actually a contradictory role design or a broader system failure. Once you separate With those three, the text lays out a chronological practice for entangled leaders. It moves through three phases. First is the interpretive phase. Okay. This is where you pause and read the colliding logics in the room. You diagnose the tangle. You ask, where exactly is the confusion being generated? Are we arguing because one person is defending a run metric while another is pushing a serve demand? Oh, wow. Yeah. Then you move to the navigational phase. You don't just blindly act. You figure out who actually has the legitimacy and authority in this specific matrix situation. Right, who has the juice? Exactly, who needs to be brought into relation? Where can you elevate a trade-off and make it discussable with an executive sponsor? Finally, you move to the experimental phase. You do not try to redesign the entire matrixed organization. Please don't do that. Attempting to fix the whole system from the middle usually just creates more coordination theater. Instead, you create local small-scale redesigns that immediately lower the burden for your specific team. This actually calls for an analogy to see how those three phases connect. Let's hear it. It's like being a triage medic on a chaotic battlefield. First, you have to read the room. That's the interpretive phase. You diagnose who is hurt and what kind of injuries you're dealing with. Then you move to the navigational phase. You figure out who actually has the authority to move the stretchers and call for the medevac. Mm-hmm. You don't just start dragging people randomly, right? You find the leverage points. And finally, you apply a local tourniquet to stop the immediate bleeding. That's the experimental phase. You aren't trying to build a brand new hospital on the battlefield. You are just stabilizing the patient directly in front of you. If we connect this to the bigger picture, that is precisely how it works in practice. We can look back at how Maya executed her first untangling. She didn't walk in and try to fix the company's entire culture, she sat her immediate team down and asked them to look at their tasks through the lens of those 4 categories. Uh, what work is genuinely about keeping the core business running? What work is truly about serving stakeholders? What work is driving change? And what work is simply fused together because no one ever bothered to separate it? The mechanism of how that solves the problem is fascinating. Let's say Maya's team identifies a heavy weekly reporting process. For years, it's been categorized as an urgent necessity, but by using these distinctions, they realize it's actually a legacy run task. Right. However, the team's mandate from executives for this quarter is heavily focused on change. By naming the logic behind the report, Maya gives her team the legitimacy to finally say, well, because our priority is change, we are legally allowed to kill this run meeting. The company didn't suddenly become a utopia. Uh-huh. But locally, for her team, the confusion evaporated. They stopped doing redundant work. She created local coherence. In the modern entangled workplace, value creation is not about unveiling a grand strategic vision. Right. Value creation is about these local acts of coherence building. Shielding your team from contradictory executive demands by clarifying what actually takes priority this week. That is an act of profound leadership. To synthesize the journey we've been on today, if you are operating in the coordinating middle, you must remember that you are functioning in a deeply entangled system. Deeply entangled. The exhaustion you feel is real, but it is not a defect in your character. Your imperative moving forward is to stop absorbing all of this organizational confusion privately. Stop internalizing the system's failure as your own. Start using these distinctions to make the tangle discussable. Build local coherence where you have influence and release yourself from the guilt of structural noise you simply cannot control. Changing how you view the source of the friction frees up an immense amount of cognitive and emotional energy. When you stop trying to fix yourself, you can finally start working on clarifying the work. Here's where it gets really interesting. I want to leave you with a final thought to take with you into your work week. The next time you are sitting outside a conference room or waiting for a Zoom call to launch and you feel that familiar suffocating wave of imposter syndrome creeping in, pause. Take a breath. Yeah, take a breath and ask yourself, is this actually imposter syndrome or are my run, serve, and change logics currently at war with each other in a system that refuses to rank them. What if your imposter syndrome is just a perfectly rational, highly perceptive response to structural entanglement? That reframes the entire experience of modern work. It really does. Thank you so much for joining us on this deep dive. Stay curious, give yourself some grace this week, and we will catch you next time.