A Conversation about the Two-Job Job

[00:00:00] 61% of you are currently working a job you were never actually hired for. Yeah, that is a wild statistic to just start right out with. It really is. I mean, if you take a moment right now, just mentally pull up that pristine, you know, neatly formatted PDF job description you got on day one. Right, the one with the tidy little bullet points. Exactly. The tidy bullet points. And compare that to the chaotic overflowing reality of your inbox today.

[00:00:29] You might actually think you are just failing at time management. Which a lot of people do. They blame themselves. Yeah, you might think you just need to prioritize better or, you know, that you're lacking personal resilience, but you aren't. No, absolutely not. You are actually the victim of a massive structural engineering failure called role sprawl. It's honestly such a relief to finally put a name to that feeling, isn't it? It really is. Because if you're sitting there feeling just completely overwhelmed, the data proves you are,

[00:00:57] are totally in the statistical majority. We are looking at a 2026 global survey from Corn Fairy today. And this is a massive survey, right? Oh, huge. They analyzed 16,000 professionals across 11 different markets. And the numbers are just staggering. We are fundamentally misdiagnosing what is happening to the modern workforce right now. Right. We treat it like a personal failing. Exactly.

[00:01:21] We are treating a systemic failure in how organizations actually design work as if it were just, you know, a psychological weakness in the worker. And that structural failure is the entire focus of our deep dive today. We are unpacking the meteoric rise of the two-job job. Which is such a great term for it. It really hits home. We're doing this by diving into a fascinating 2026 paper by Dr. Jonathan H. Westover. It was published in the Human Capital Leadership Review.

[00:01:47] And it is a must read if you work in any sort of corporate environment. Totally. Our mission here is to figure out why your workload has quietly doubled while nobody was looking. And why standard corporate advice to, like, just take a resilience workshop. Right. Don't even get me started on the resilience workshops. Right. It's practically insulting at this point. We're going to look at how the most innovative organizations are actually redesigning work before their people just completely break.

[00:02:14] The main problem with the current discourse is that corporate leadership often just lacks the vocabulary to describe what's actually happening on the ground. They just don't have the words for it. Right. So we have to move away from your personal anecdotal experience of feeling like you're drowning. And we need to look at the formal structural definitions of how your career is being reshaped literally without your consent. So let's look at that Corn Fairy 2026 data you brought up because it really paints a picture of a workforce at its breaking point. It's pretty bleak. It is.

[00:02:43] We mentioned the 61 percent of professionals who report carrying the responsibilities of more than one role. But it goes deeper than that. Hit me with the rest of the numbers. So 62 percent say their workloads are significantly heavier today than they were just two years ago. Two years. That is a massive jump in such a short time. And here's the statistic that really forces you to stop and think about what we're actually doing all day. Forty five percent of respondents said they are simply too busy to deliver meaningful results.

[00:03:14] Wow. Yeah, that is the ultimate paradox of modern work right there. You are literally too busy doing work to do the important work. Right. The day to day survival mode just completely crowds out the strategic value. You're just putting out fires all day. Exactly. And the fallout is entirely predictable. Global professional motivation has plummeted from 71 percent in 2024 down to 61 percent in 2026. A 10 point drop in two years. Yeah. That's not just a minor fluctuation.

[00:03:43] That's an absolute exodus of engagement. Which brings us to the necessity of defining our terms because in management meetings, you know, a lot of different concepts just get thrown into a blender. Right. People use words interchangeably when they really shouldn't. Exactly. And that makes solving the problem basically impossible. So we need to define role sprawl by first defining what it is not. Okay. Let's do that. First, it is not job enlargement. Okay. What is job enlargement then?

[00:04:11] Job enlargement is a deliberate planned HR strategy. It's management sitting down with you and saying, you know, we want to broaden your skill set by having you take on this specific new function. So it's intentional. Very intentional. It is discussed, planned, and ideally, you know, supported with training. Okay. Makes sense. And role sprawl is definitely not a promotion, right? Far from it. Far from it. Okay. A promotion involves a formal change in title.

[00:04:37] It's a recognized increase in authority and crucially, an increase in compensation and resources to match the new expectations. The pay bump. Right. The pay bump. Role sprawl, on the other hand, is the structural accumulation of tasks without any formal role redesign. No title change and definitely no pay increase. So it's just extra work. It is your job growing sideways in the dark. It happens through accretion.

[00:05:05] A colleague leaves, a new software is adopted, a committee is formed, and slowly these invisible responsibilities just attach themselves to you like barnacles on a ship's hull. Okay. Let's unpack this. Because you're describing a situation where the worker is essentially trapped by their own competence. That is exactly what it is. The curse of competence. To understand the psychological weight of this, the Westover paper takes us back to some foundational research from 1964. This is by Kahn and his colleagues.

[00:05:34] Oh, Kahn's work is brilliant. Yeah. And incredibly relevant right now. Yeah. They looked at the very concept of a role. They didn't define a role by a job description. They defined it as a bundle of expectations placed on you by others. Right. Which changes everything. Totally. And they identified three distinct ways those expectations can essentially break you. The first stressor he identified is role overload. Which sounds pretty straightforward. Yeah. This is basically a simple math problem.

[00:06:01] The sheer volume of expectations and tasks exceeds the physical hours you have available to actually complete them. Just too much stuff, not enough time. Right. Then the second one is role conflict. This occurs when you receive completely incompatible expectations. Like what? Give me an example. Okay. Imagine your direct manager demands you slash your department's budget by 20%.

[00:06:23] But the head of product development, who also has influence over your annual review, demands you spare no expense to launch the new feature by Friday. Oh man. That's a nightmare. You literally cannot satisfy both. Yeah. That's role conflict. And then the third stressor is role ambiguity. That's where the actual boundaries of your job are just fuzzy. You're just flying blind. Right. You don't know if you have the authority to make a decision or if you're stepping on someone else's toes.

[00:06:50] Or if a particular like orphaned task is actually your responsibility to catch before it hits the floor. Now take those three distinct psychological stressors. Under normal circumstances, you know, an employee might experience one of them during a rough quarter. Sure. Everybody has a bad month. But role sprawl creates a perfect storm where you experience all three simultaneously. All three at once. Yes. You have too much to do. You are answering to competing stakeholders who never coordinate with each other.

[00:07:19] And literally nobody knows who actually owns the work anymore. Which leads us directly into how organizational psychologists actually map this kind of systemic failure. The paper leans heavily on the job demands resources model. Ah, yes. The JDR model. Right. Originally developed by Backer and DeMaruti in 2007 and refined over the next decade. The JDR model is one of the most robust frameworks we have for understanding burnout and engagement. How does it work exactly?

[00:07:46] It posits that absolutely every job, whether you are a barista or a corporate vice president, can be broken down into two fundamental categories. Demands and resources. Okay. So think of demands as the weight of the backpack you are carrying up about it. That's a great way to picture it. It's the physical, psychological, social, or organizational aspects of the job that require sustained effort. It's the tight deadlines, the difficult clients, the emotional labor of managing a stressed out team.

[00:08:15] Just the sheer cognitive load of the workload. And carrying that backpack comes with a real physiological and psychological cost. Definitely. And resources aren't just your literal paycheck or, you know, the company providing free coffee in the break room. Right. No amount of free espresso fixes this. Exactly. Resources are the hiking boots, the map, the supportive guide, and the good weather conditions that make carrying that backpack actually possible.

[00:08:39] They are the aspects of the job that help you achieve your goals, reduce the costs of the demands, or stimulate personal growth. So what does that look like in an office? This includes having a highly supportive manager, total clarity on what your priorities are, the autonomy to actually make decisions, and properly functioning equipment. The JDR model essentially says it's a balancing act. If you have incredibly high demands, like a massive high-stakes project with a tight deadline. Which sounds stressful. Right.

[00:09:08] But if you also have incredibly high resources, a boss who clears your schedule, a dedicated team, and a massive budget, that actually drives a motivational process. You don't burn out. Yes. You actually get engaged. Yes. You feel challenged in a way that promotes growth. But the inverse is where the damage happens. High demands, coupled with low resources, drive a health impairment process. Health impairment. That sounds serious. It leads directly, almost mathematically, to exhaustion and burnout.

[00:09:38] And this is why role sprawl is so incredibly destructive. Because it messes with that balance. Exactly. It doesn't just add demands, it systematically maximizes your job demands while simultaneously stripping away your resources. Oh, wow. It adds the extra project, but it removes the clear priorities. It gives you the responsibility, but strips away the autonomy or the managerial support. You know, I look at role sprawl like inheriting a very nice standard single family house. Okay. I'm tracking with you.

[00:10:08] But over the years, you continuously build unauthorized additions onto it. You tack a sunroom onto the back because, you know, you need a place for the plants. Naturally. A year later, you build a second story over the garage because you need a home office. Then you push the kitchen outward. You keep adding these heavy structural elements, but you never once pour new concrete to expand the foundational footprint. You're just piling it on. Right. You never upgrade the plumbing or the electrical panel to handle the new load. Eventually, that house is going to collapse. It has to.

[00:10:37] And it won't collapse because you used bad lumber or because the paint was cheap. It will collapse because the fundamental structure was simply not designed to hold that much weight. That is spot on. And to take your house analogy even further, the real tragedy here is that the city inspector also quit. Oh, that's good. Right. So no one is even checking to see if these new additions are up to code. The organization has completely lost visibility into the structure it has built. They have no idea what they've created. None.

[00:11:06] And Westover illustrates this brilliantly with composite profiles of the modern workforce. Take the analytics lead, for example. Okay. What happens to them? This is someone hired specifically for their deep, specialized ability to crunch data and generate insights. But over the last 18 months, the procurement department had a hiring freeze and a key vendor manager left. Oh, I see where this is going.

[00:11:29] Suddenly, because the analytics lead uses that vendor software, they are quietly handed the responsibility of managing the vendor relationship. Negotiating the contract renewals. Exactly. Handling the procurement red tape. So they aren't doing data analytics anymore. They are doing administrative procurement. Completely. Or look at the clinic manager in a healthcare setting. Their actual job is to manage nursing schedules, handle patient flow, ensure the clinic runs smoothly. Important stuff.

[00:11:57] But upper management decides to purchase a new complex AI scheduling and diagnostic tool. Which they probably didn't ask for. They definitely didn't ask for it. And management rolls it out without hiring a dedicated implementation specialist. So because the clinic manager is relatively tech savvy, they become the informal, unpaid AI champion. Yeah. The AI champion. Right. Now they are spending three hours a day troubleshooting software glitches and training reluctant staff on a system they didn't buy and aren't paid to manage.

[00:12:27] My favorite, or rather the most tragic example from the text, is the senior individual contributor. The senior engineer, right. Yeah. The brilliant software engineer who really just wants to write code. But the company decided to eliminate middle management to save money. Because that always works out so well. Right. So who handles the one-on-ones for the junior developers? Who approves their PTO? Who mediates the interpersonal conflict between the QA team and the dev team? It all falls on the senior engineer. Exactly.

[00:12:56] They absorb all the emotional and administrative labor of people management without the title of manager. And in all three of those scenarios, the organization looks at its ledger and thinks, wow, we are operating so efficiently. Because the work is still getting done. Yep. The work gets done and payroll hasn't increased a single dime. Right. The house is still standing. So the executives assume the foundation is fine.

[00:13:19] But if we want to understand why these unauthorized additions are being built at such a rapid pace right now, we have to look at the macroeconomic weather system. We have to zoom out. We have to map out the four specific societal and corporate forces that are currently hammering the nails. The Westover paper identifies these as the primary drivers of role sprawl. They are the structural engines pumping extra volume into the system. Let's call them the four horsemen of role sprawl. I like that. And the first horseman is a massive corporate obsession right now.

[00:13:49] De-layering. Oh, de-layering. Organizations are aggressively flattening their management structures under the guise of agility. Agility is the favorite buzzword. Totally. The data here is an absolute bloodbath. In 2023, Meta cut 10,000 jobs and closed 5,000 open roles specifically to flatten middle management. Huge numbers. Citigroup went through a massive reorganization, cutting their management layers from 13 down to 8. And in the process, they dropped 60 separate corporate committees. 60 committees. 60 committees.

[00:14:19] Gone. In 2024, Amazon announced they were increasing the ratio of individual contributors to managers by 15%. Bayer cut 5,500 managerial jobs. Uber cut 3,300 roles in late 2026, which hit roughly 20% of their entire management tier. The narrative sold to the public and to the shareholders is always about speed. You know, we are removing bureaucracy so our people can move faster. It sounds good in a press release. It sounds great.

[00:14:46] But what executives consistently fail to account for is the actual mechanical function of a middle manager. The work those managers performed doesn't simply evaporate when their role is eliminated. Wait. I have to stop you there and push back on behalf of the listener. Okay. Push back. If I'm an individual contributor at Citigroup and my CEO just removed 60 layers of bureaucratic committees and five layers of bosses above me, shouldn't my life get inherently faster and easier? That is the assumption, yes.

[00:15:15] I mean, fewer pointless status meetings, fewer people needing to approve my work? Why does removing a boss suddenly make my job harder? It's a very logical question and it's exactly what the executives assume will happen. The flaw in that thinking lies in misunderstanding the difference between useless bureaucracy and vital coordination. Okay. Explain that difference. Yes. Removing a redundant approval signature saves you five minutes. But consider what else that manager was doing.

[00:15:44] Let's say you are on the product team and you need a massive chunk of the budget to develop a new feature. Okay. Standard request. But the marketing team also wants that budget for a global campaign. Previously, your manager and the marketing manager would take that conflict up the chain to one of those committees, fight it out, resolve the budget allocation, and then come back and tell you what to do. They handled the fight. They acted as a heat shield. They absorbed the organizational friction. Exactly. They did the vital coordination work.

[00:16:14] Now the manager is gone and the committee is gone. Does the budget conflict disappear? Definitely not. No. It just lands directly on your desk. You, the individual contributor, now have to go to war with the marketing individual contributor over the budget, negotiate a compromise, track the spending, and escalate it to a VP who has 80 direct reports and literally no time to listen to you. Oh man, when you put it like that.

[00:16:39] You are now doing your job, plus the coordination, conflict resolution, and shielding job of your former boss. The work was orphaned, and orphaned work always migrates to the most competent survivors. That makes terrifying sense. You didn't eliminate the bureaucracy. You just decentralized it and forced people who aren't trained for it to handle it. Which is incredibly stressful. Which leads us seamlessly into the second driver, head count restraint. This isn't a massive layoff.

[00:17:07] This is the quiet, insidious, do more with less mandate. It's the silent killer of capacity. The budget is flat. Attrition happens naturally. People leave for better offers. They move across the country. They retire. And leadership simply decides not to backfill the role. A quiet hiring freeze. Right. To protect the profit margins. So again, that invisible lateral drift of work happens. The person who left was managing 50 specific tasks a week.

[00:17:35] Management doesn't officially reassign those tasks. Of course not. Instead, those 50 tasks get quietly carved up and handed to the three remaining people on the team as a, quote, temporary measure to get us through the quarter. But in the modern corporate environment, temporary always becomes permanent. Always. If the team manages to absorb the 50 tasks and keep the department running, leadership takes that as empirical proof that the fourth head count was redundant in the first place. They are punished for their own resilience.

[00:18:05] Exactly. So you have fewer people doing the work and fewer managers to protect them. The logical executive response is, well, we'll just buy software to make everyone faster. The magic software. And that brings us to the third driver. And frankly, the greatest irony of this entire data set. AI deployment. What's fascinating here is the profound paradox of efficiency that generative AI has unleashed. Organizations are rolling out these tools with massive promises of time saving.

[00:18:33] But what does the data actually say? Well, the corn fairy data highlights a glaring, almost comedic disconnect between the C-suite and the front lines. 79% of CEOs report seeing major efficiency gains from AI in their organizations. But only 51% of workers actually agree. Exactly. And it gets worse. 52% of workers who classify themselves as AI weary state explicitly that AI has actually increased their workload.

[00:19:01] Wait, how does that mechanically happen? How is a tool specifically designed and purchased to automate work actually creating more work for the listener? Because the C-suite is completely blind to the hidden labor of implementation. They just don't see it. They look at a spreadsheet, see the subscription cost for an enterprise AI tool, read the marketing brochure that says 30% faster, and immediately bake a 30% efficiency gain into their headcount models. Just automatically. Right.

[00:19:28] But AI does not work out of the box in a highly specific corporate context. To make it useful, human beings have to perform an immense amount of invisible labor. Someone has to actually write the complex prompts. Someone has to write the prompts. Someone has to test the outputs to ensure the AI isn't hallucinating data or inventing legal precedents. Right, because we've all seen those horror stories. Absolutely. Someone has to govern the data security so proprietary information isn't leaking into public models.

[00:19:55] And because these models are constantly updating, the workflow breaks every three months and has to be completely redesigned. It sounds like a full-time job. It is highly skilled, deeply frustrating, and incredibly time-consuming labor. And it almost never appears on the employee's official job description. It's invisible. So the worker is left doing their normal job. Plus managing the erratic AI tool. Plus picking up the slack from the colleague who was laid off because the CEO thought the AI would replace them. And it's the ultimate squeeze.

[00:20:24] And you are managing a temperamental digital intern on top of your own job. That very apt description. And all of this feeds directly into the fourth and final horsemen. Coordination overhead. Just the sheer, unyielding volume of communication required to simply get through the day. Westover cites the Asana Anatomy of Work Index from 2021. They surveyed 13,000 knowledge workers. What did they find?

[00:20:52] They found that a staggering 60% of a worker's time is spent on what they define as work about work. 60%. 60%. That means only 40% of the week is spent doing the skilled labor you were actually hired to do. The rest is just managing the fact that you work at a company. It's searching for information across disjointed platforms, chasing down status updates, attending alignment meetings, toggling between a dozen different apps. It's exhausting just hearing that list.

[00:21:21] And the more recent data shows this problem is accelerating exponentially. Microsoft released telemetry data in 2025. Telemetry data, so they are looking at how people actually use the software. Exactly. Anonymized digital behavior across millions of users on their platforms. They found that the average worker is interrupted every two minutes. Every two minutes. Let that sink in for the listener. By a meeting, an email, or a Teams notification.

[00:21:47] The average worker is receiving 117 emails and 153 Teams messages every single day. A ping every two minutes means that deep, focused thought is basically mathematically impossible during standard business hours. Completely impossible. If you are a writer, an analyst, or an engineer, you literally cannot do your job between 9am and 5pm. Which is reflected in the most heartbreaking statistic from the Microsoft data.

[00:22:15] They tracked a 16% year-over-year rise in meetings that start after 8pm. Because 8pm is the only time nobody is pinging you. Exactly. Wow. So we have mapped the four structural forces pumping all this extra volume into the system. De-layering, that orphans work. Head count restraint that permanently redistributes it. The AI efficiency paradox that generates hidden labor. And the coordination overhead that fractures our attention. The four horsemen.

[00:22:44] Now, we have to examine what happens when the pipes actually burst. We are moving from the organizational causes to the catastrophic real-world costs. Because the central thesis here is that doing more does not actually yield more. It yields significantly less. The systemic damage operates on two levels. The organizational cost and the individual cost. Let's start with the organization. Westover highlights what he calls the activity productivity gap.

[00:23:12] This is the deeply flawed corporate illusion that being busy is synonymous with driving growth. We see this all the time. People running from meeting to meeting, exhausted. Feeling like they're working harder than ever. But the company's revenue is flat. That takes us back to the corn fairy finding that 45% of people are too busy to deliver meaningful results. Right. When you are forced into a two-job job by role sprawl, you stop operating strategically and start operating purely on triage. Just bleeding out.

[00:23:40] You are in a permanent state of emergency room medicine. You protect the urgent screaming fires and you prioritize the highly visible tasks that your boss actually actively monitors. So what gets dropped? The important but not urgent work. The fundamental building blocks of long-term success. Process improvement. Deep customer insight. Mentoring junior staff. Long-term strategic planning. All of it vanishes. She's gone. Perlow described this dynamic back in 1999 as the time famine.

[00:24:10] The constant manufactured crises completely crowd out focused proactive effort. And the psychological toll of that famine is severe. Lapine, Potskov and Lapine did a brilliant meta-analysis in 2005 that looked at how different types of stress impact performance. This is a vital distinction. Yeah, they made a crucial distinction between challenge stressors and hindrance stressors. Right. A challenge stressor is a demand that you experience as an opportunity for growth and mastery. Like what?

[00:24:39] It's the high-stakes presentation to the board or a tough but exciting stretch assignment. It requires massive effort. You might lose some sleep over it, but you feel good about it. You feel valued. Okay, and a hindrance stressor. A hindrance stressor, on the other hand, is a demand that you experience purely as an obstacle. It offers absolutely no growth. It's bureaucratic red tape. It's conflicting priorities from two different managers. It's the fuzzy ownership of an orphaned task.

[00:25:06] And Roll Sprawl is a massive industrialized engine for generating hindrance stressors. Oh, completely. It doesn't offer you a path to mastery. It just offers you organizational friction. You don't feel proud when you finally track down the right billing code for a vendor. You just feel drained. Exactly. And Lapine found that while challenge stressors can actually boost motivation, hindrance stressors have severe direct negative effects on performance. That makes total sense.

[00:25:33] And when performance drops and the friction becomes unbearable, the system breaks down. Bowling and colleagues conducted a massive meta-analysis in 2015, looking at 336 different studies. Wow. That's comprehensive. Very. They conclusively connected this specific type of workload strain to higher turnover intentions, increased absenteeism, and significantly lower organizational commitment. If you overload the structural capacity of your workforce, the parts eventually snap.

[00:26:02] But beyond just turnover, the really insidious organizational cost is stalled innovation. Yes. If your people are drowning in triage, they literally cannot invent the future. And this is where the paper brings in a phenomenal, incredibly detailed study by Karuna Karan, Kellogg, and Wiesenfeld from 2026. If you take one academic study away from this entire deep dive, it should be this one. It's so good.

[00:26:29] They spent two years studying how two very different organizations attempted to adopt generative AI. One was a high-powered corporate law firm and the other was an academic medical center. Okay. Two very different worlds. Very different. And the outcomes could not have been more divergent. The law firm's AI initiative completely and utterly failed. Why? What happened?

[00:26:51] Over 80% of their domain experts, the actual lawyers who needed to test and refine the AI for legal use, eventually just abandoned the innovation efforts entirely. After two years, the massive law firm ended up with only three viable firm-wide AI tools. Three tools? Three tools. After two years? Yes. And what happened at the academic medical center? They succeeded wildly. They developed 141 functional AI tools that were integrated into their daily operations.

[00:27:19] Okay, we have to pause here and really explore this. Why did the lawyers give up and fail while the doctors and medical researchers managed to build 141 tools? I mean, they're both highly educated, incredibly busy, high-stress professions. What was the mechanical difference in the organizations? The difference came down entirely to how the two organizations accounted for the hidden labor of building the AI. Unpack that for me.

[00:27:46] The law firm operated on the traditional, rigid, billable-hour model. Their entire incentive structure was based on how many hours a lawyer billed to a client. When they rolled out the AI initiative, they expected their highly paid experts to build, test, and refine these new AI tools on the side, on top of their normal punishing billable requirements. They treated innovation as an extracurricular activity. Precisely. So, it was just a second, entirely unpaid job.

[00:28:15] And human behavior is entirely rational when it comes to incentives. When push came to shove and a lawyer had to choose between testing a new AI prompt or billing an hour to a corporate client that would actually count toward their partnership track, they chose the measured, rewarded work. Of course they did. They abandoned the invisible, unrewarded innovation work. And the academic medical center did the exact opposite. The exact opposite. They recognized from day one that implementing AI requires immense human labor.

[00:28:44] They made the hidden work visible. How did they do that? They formally budgeted time for doctors and researchers to experiment. They actually built AI validation responsibilities into their official job descriptions. And crucially, they counted that innovation work toward their performance reviews and career advancement. So they actually rewarded it. Because they recognized and rewarded the work, the innovation flourished. That is such a profound lesson for any executive listening. You get what you measure. And you destroy what you hide.

[00:29:14] Destroy what you hide. Exactly. If you treat innovation as a hobby that your employees should do on weekends, your company will stagnate. But we have to pivot and look at the individual costs here. Because while the company loses innovation, the individual loses their health. Which brings us to burnout. Right. Moslock and Leiter's 2016 work on burnout is essential here. They define burnout not just as being tired at the end of a long week. It's much more severe than that.

[00:29:40] They define it as a clinical syndrome characterized by overwhelming exhaustion, deep cynicism, detachment from your colleagues, and a pervasive sense of absolute ineffectiveness. And if you look at the risk factors Moslock and Leiter identified for burnout, roll sprawl triggers almost every single one of them. Just hits them all. Your workload goes up exponentially. Your control over your day plummets because you are constantly reacting to orphan tasks.

[00:30:08] Your reward stays flat because you didn't get a promotion. And your sense of fairness is deeply violated because you know you are carrying the weight of two people for the salary of one. And this triggers what the JDR model calls the loss cycle. It's a death spiral of inefficiency. Strain leads to self-undermining behaviors. Think about it. When you are exhausted, operating on four hours of sleep, and toggling between 12 apps, you make mistakes. It's inevitable. You drop a ball. Right.

[00:30:36] A mistake then generates rework. That rework requires follow-up meetings, apology emails, and escalations to management. And where do all those new escalations and meetings land? Right back on the desk of the exact same overloaded worker who made the mistake in the first place. You are generating your own hindrance stressors. Wait. If I'm the conscientious one staying late to fix these orphan tasks, the one who catches the ball before it drops so the project doesn't fail, aren't I just masking the company's incompetence?

[00:31:06] Am I accidentally sabotaging myself by hiding the structural flaws from leadership? Yes, you are. Ouch. It's a very painful realization for high performers. But by being the hero and acting as the organizational glue, you are masking the structural failure with your own personal sacrifice. The executives look at the project, see that it launched on time, and assume the staffing levels are perfect. They don't see the toll it took. They don't see the 8 p.m. meetings or the weekend anxiety that made it happen.

[00:31:36] And worse, by taking on all that invisible glue work, you are likely falling victim to the equity gap. This is a critical piece of the research. Babcock, Ricaldi, Westerlund, and Weingart did incredible research in 2017, looking at what they call low-promotability tasks. What are those? These are the vital but completely invisible tasks that keep a company running. Organizing the committee meetings, onboarding the new hires, cleaning up the data governance, taking the notes.

[00:32:05] The office housekeeping. Yes. Their research conclusively showed that women, in particular, are disproportionately asked to take on these tasks, and they disproportionately accept them compared to their male counterparts. So the people keeping the lights on are actually hurting their own careers. Because taking notes in a meeting doesn't get you promoted to vice president. High visibility, strategic project work gets you promoted. And if your capacity is entirely consumed by low-promotability tasks, you have no room for the stretch assignments.

[00:32:35] You're just stuck. Cross and his colleagues in 2016 mapped collaborative networks across 300 different organizations. The findings were stunning. They found that a tiny fraction, just 3-5% of employees, supply 20-35% of the value-added collaborations in a company. So you take your absolute best, most helpful, most conscientious people, and you structurally transform them into bottlenecks. Everyone goes to them for help.

[00:33:02] They say yes because they are conscientious. And eventually, they break. The diagnosis is undeniably bleak. We are burning out our absolute best people. We are actively stalling our own ability to innovate. And we are embedding massive equity gaps into our promotion cycles. But there is hope, right? Yes. The turning point in Westover's paper is the realization that work design is an active choice. It is not gravity. It is not an immutable law of nature.

[00:33:31] If we built this trap through deliberate, albeit misguided, corporate decisions, we can unbuild it through deliberate redesign. We are moving into the solutions now. Let's open up the toolkit for redesign. Starting with what is arguably the most powerful, immediate, and yet utterly underutilized tool in all of corporate history. Subtraction. Response number one from the research is a mantra. Subtract before you add. Subtract before you add.

[00:34:00] Organizations are incredibly adept at adding things. They love launching new software tools, scheduling new weekly standing meetings, rolling out new reporting requirements. But they are notoriously systemically terrible at taking things away. Because there's no incentive for it. Every new initiative has an ambitious executive sponsor pushing for it so they can put it on their resume. Absolutely no one gets promoted to VP for taking a recurring Wednesday status meeting off the calendar. True.

[00:34:27] But the research on hindrance stressors is completely clear. Removing obstacles is the fastest, most efficient, and cheapest way to improve both employee well-being and actual business performance. And the paper provides some incredible, radical case studies on how to do this. My favorite is the Shopify calendar purge from January 2023. Oh, that was a legendary move. Shopify realized their people were drowning in coordination overhead. So they didn't just ask people to have fewer meetings.

[00:34:56] They enacted blunt force trauma on the calendar. Blunt force trauma is right. Over a single weekend, they went into the backend system and literally deleted every single recurring meeting that had more than two people in it. Gone. They just wiped them out. They also completely banned all meetings on Wednesdays. They wiped out 10,000 calendar events in one fell swoop. 10,000 events. And the math on that is staggering.

[00:35:20] They calculated that deleting those meetings reclaimed 76,500 hours of employee time. That is just hard to comprehend. They gave their workforce back 76,000 hours to actually do their jobs. And the brilliant part was the friction they introduced. They told employees they couldn't add any recurring meetings back to the calendar for at least two weeks. A cooling off period. And when they finally did, they had to fiercely justify its existence.

[00:35:46] It forced every single team to rebuild their coordination architecture from a completely blank slate. They had to ask, do we actually need a weekly sync or can this just be a shared document? Right. Another brilliant, highly targeted example comes from healthcare. Hawaii Pacific Health in 2017 launched a program with arguably the greatest name in corporate history. I love this one. The Getting Rid of Stupid Stuff program. That is the exact kind of plain language we need.

[00:36:15] They crowdsourced the subtraction. They asked their nurses and doctors to nominate specific electronic health record requirements that were poorly designed, redundant, or purely bureaucratic. They received hundreds of suggestions. And what did they find? One of the things they targeted was a single required documentation click that nurses had to do during patient rounding. Just one redundant click in the software. Okay, let's look at the math on this one click because this is where the scale of roll sprawl becomes visible.

[00:36:44] Removing that one single click saved an estimated 1,700 nursing hours a month across their four hospitals. Let that sink in. One stupid click was costing them 1,700 hours of highly skilled nursing care every single month. How many patients could have been seen? How much burnout could have been prevented? That is the power of subtraction. But there is a massive trap here, isn't there? I can already hear the listener thinking,

[00:37:12] Sure, doing a big subtraction sprint feels amazing in January. You delete the meetings, you remove the click. But... But by July, the weeds have grown back. A new manager gets hired and schedules a daily sync. A new compliance rule adds three more clicks. And that is exactly what the data shows. Subtraction cannot be a one-time PR-friendly event. It cannot be a gimmick. You have to maintain it.

[00:37:36] The paper cites Sarai and colleagues who studied a major initiative in the UK called the NHS Productive Ward Program. This was designed to free up nurses' time back in 2008 and 2009. Was it successful? Initially, it was highly celebrated and wildly successful. But a 10-year evaluation of the program found that without sustained, dedicated management and financial support to protect those boundaries, the gains almost entirely evaporated. The weeds grew back.

[00:38:02] The stupid stuff always creeps back in because the organizational default is accretion. Subtraction has to become a recurring institutionalized discipline with a permanent owner. Which leads us directly to response number two. Rechartering roles after restructuring. This is crucial. Think about how a company typically announces a layoff or a major restructuring. The press release or the all-hands meeting is always hyper-focused on what is being cut. The CEO stands up and says,

[00:38:31] you know, we are eliminating 5,000 roles and saving the company $200 billion. Lots of applause from the shareholders. Right. But what do they almost never explicitly detail in that meeting? They never detail how the remaining work is going to be reassigned. They focus entirely on the financial subtraction and completely ignore the operational reality. Exactly. That silence, that vacuum of communication, is the exact petri dish where role sprawl breeds. And this is where Khan's role theory comes back into play.

[00:39:01] Remember, role ambiguity causes deep, measurable psychological strain. A redesigned role has to be more than just a longer list of tasks emailed to you on a Friday afternoon. It has to be formal. It has to be formally rechartered. If a company eliminates a management tier, they must conduct orphaned task audits. Someone has to own the audit. Someone in leadership has to literally sit down with a spreadsheet and say, okay, Bob used to run the TPS report. Bob is gone. Who exactly is doing the TPS report now?

[00:39:29] And if no one has capacity, what are we dropping so it can get done? Who holds the decision rights for a budget overage now that the committee is dissolved. Exactly. Bayer is actually attempting to institutionalize this with their dynamic shared ownership model, right? Yes. Bayer is trying to replace the rigid static annual budgets with self-directed 90 day team cycles.

[00:39:50] The idea is to force a constant explicit renegotiation of what gets done and who does it rather than letting expectations quietly pile up over a 12 month period. Here's where it gets really interesting. Amazon actually recognized this vacuum of orphaned work during their aggressive delaying push in 2024. Right. Andy Jassy's initiative. Andy Jassy, the CEO, realized that just firing managers wasn't enough. He set up a dedicated bureaucracy mailbox for employees to report broken processes.

[00:40:19] He received over 500 submissions from the front lines and actually acted on 150 of them. That's significant. He recognized that if you remove the manager but keep the heavy bureaucratic process that the manager existed to run, you aren't improving efficiency. You are just moving the paint around to the survivors. It's an acknowledgement that the system itself needs to change, not just the headcount. I always compare this concept of rechartering to writing a post-nuptial agreement after a major life change.

[00:40:48] A post-nup? I like where this is going. Let's say a couple has twins. Or one partner takes a demanding new job that requires constant travel. You cannot just rely on the old unspoken rules of the marriage that you established when you were both working nine to five with no kids. Because it doesn't work anymore. The entire ecosystem has changed.

[00:41:07] You have to sit down at the kitchen table, look each other in the eye, and explicitly get down on paper who is doing the dishes, who is managing daycare drop-off, and who is doing the laundry now that the household dynamics have fundamentally, permanently shifted. Right. If you don't explicitly recharter the marriage, resentment will destroy it. That is an excellent way to frame it. You are explicitly defining the new boundaries so there is no ambiguity.

[00:41:33] And that brings us to response number three, which is perhaps the most fundamental paradigm shift proposed in the entire paper. Governing workload as a capacity budget. This one blows my mind because it exposes how irrational corporate behavior really is. Organizations guard their financial budgets with military precision. Try expensing a $50 dinner. Exactly.

[00:41:56] If I want to spend $500 on a new software license for my team, I have to fill out a form, get three levels of management approval, and provide a detailed ROI analysis. But human hours? They give those away for absolutely free. Anyone in the company can put a one-hour recurring meeting on my calendar with 10 other people in it. They just instantly consumed 10 hours of expensive corporate time and nobody had to approve that transaction. It is a massive systemic failure of resource allocation.

[00:42:24] Time is finite, but we treat it as infinite. The JDR model insists that you have to manage the ratio of demands to resources. And you logically cannot do that if you don't aggressively track the demand side of the equation. We need strict capacity planning. Organizations need to institute work in progress limits or WIP limits. This means a team or an individual is only allowed to carry a mathematically defined number of concurrent projects.

[00:42:50] So if leadership comes down and says, hey, we have an urgent new priority. We need you to launch this feature. What happens? The manager has to look at the WIP limit and say, okay, our capacity is full. If we take on this new priority, you must explicitly state which of our current priorities is being dropped, delayed or paused. It forces a choice. It forces leadership to make a visible, painful trade off rather than just silently piling it onto the team's plate.

[00:43:17] Dropbox tried to institutionalize this kind of boundary with their virtual first model. They established what they called four hour core collaboration windows. How did that work? The policy dictated that you could only schedule synchronous meetings between say 10 a.m. and 2 p.m. The rest of the day was aggressively protected for actual focused deep work. And they mandated that asynchronous communication like shared docs or recorded videos had to be the default for problem solving rather than calling a meeting. But.

[00:43:46] But I have to push back here. Go ahead. If I'm listening to this and my company just mandates meeting free Wednesdays or gives me core collaboration hours, does that actually solve the problem? Well, think about the volume. Right. If the sheer unyielding volume of my assigned work doesn't change, then blocking my calendar from 2 p.m. to 5 p.m. just means I'm going to have to do my actual job at 9 p.m. instead. Right. You haven't reduced the workload. You just shifted the time I have to do it.

[00:44:13] You are hitting on the exact critical warning that Microsoft issued in their telemetry report. Governing the calendar is completely useless and often counterproductive if you don't simultaneously govern the total volume of the workload. It just punishes the worker. Protected time just shifts the unprotected demand into the evenings and weekends. This is why Microsoft explicitly warned against using their telemetry data for individual surveillance.

[00:44:39] Right. We don't want bosses tracking our keystrokes to see if we're working at 9 p.m. Exactly. But Microsoft argued that aggregated, anonymized team level data is essential. If leadership looks at a dashboard and sees that the marketing team is consistently logging on and sending emails post 8 p.m., that is not a sign of great dedication. No, it's a red flag. That is a blaring structural red flag that the team's capacity budget is overdrawn. It means the WIP limits are failing.

[00:45:06] And to budget capacity accurately, you have to actually know what the work is, which leads to response number four, make hidden work visible and count it. We talked about this with the AI implementation, but it goes much deeper. Right. Starr and Strauss explored this concept way back in 1999. They called it articulation work. Articulation work is the invisible ecology of tasks that keep the visible tasks functioning.

[00:45:32] It's the prep work, the coordination, the cleanup, the emotional labor of keeping a team functional. If we connect this to the bigger picture, the entire future of organizational AI depends entirely on solving this specific problem. Let's look back at the Karuna Karan study with the law firm in the hospital. Okay. Remind us.

[00:45:50] If a company continues to treat AI implementation as a side hustle for its domain experts, those experts will rationally, predictably prioritize the work they are actually measured and rewarded on, like billable hours or direct patient care. And the innovation will simply wither and die. To succeed, you have to formally allocate hours in the week for AI experimentation. It has to be on the ledger. You have to track assists in performance reviews, rewarding the people who do the articulation work that helps others succeed. You have to value the support work.

[00:46:20] And crucially, going back to the equity gap, you have to transparently rotate those low promotability tasks. The office housekeeping cannot fall disproportionately on women and the most highly conscientious employees. You have to literally put figuring out how to use ChatGPT without breaking compliance on the official end of year performance review rubric. Otherwise, it's just a second unpaid job that leads to burnout. Exactly. So we've established the policies. We need to budget time like money. We need to enforce whip limits.

[00:46:50] And we need to reward hidden labor. But policies sitting in an employee handbook PDF somewhere don't manage people. Human beings manage people. Very true. The final piece of this puzzle requires looking at the role of the manager and how you, the listener, can actively reshape your own reality. And this brings us to response number five. Resource managers and enable job crafting. The corn fairy data provides a blaring alarm bell regarding management.

[00:47:17] 55% of remaining managers are exhausted. More than a half. They are burning out just as fast as the front lines. Yet simultaneously, 52% of workers report that they rely entirely on those same exhausted managers to encourage experimentation, protect their time and shield them from role sprawl. It's a broken chain of support. Managers are currently being viewed by executives purely as overhead to be minimized. They are targets for delayering.

[00:47:43] But the research insists that managers are actually vital capacity allocating resources. They are the heat shield. If an organization decides to widen a manager's span of control, if they go from managing five direct reports to managing 15, that manager's own administrative load must drop proportionally. It has to. You cannot ask a human being to conduct three times the performance reviews,

[00:48:08] hold three times the one on ones and still expect them to be a strategic coach who shields their team from burnout. They will fail. They need to be resourced. But while we fix the management layer, we also have to empower the employees on the ground through what Wersnowski and Dutton in 2001 called job crafting. Job crafting is a fascinating psychological concept. It's the process where employees don't just passively receive their job descriptions.

[00:48:35] They actively make physical and cognitive changes to the task or relational boundaries of their work. They shape their jobs to better align with their strengths and capacities. Tim's, Bacher and Dirks expanded on this in 2012, specifically looking at how employees can proactively decrease hindering demands. I see the value in that, but there is a huge, dangerous pitfall here, right? Oh, massive pitfall.

[00:49:01] If an organization just tells you, the listener, hey, go craft your job, set some boundaries, protect your peace, but they don't provide systemic support or reduce the total volume of work, what actually happens? The most aggressive, politically savvy negotiators on the team will successfully craft away their annoying tasks. And they will just dump all that garbage work onto their least powerful, quietest colleagues. You are absolutely right. Job crafting in a vacuum is a disaster. The total organizational burden doesn't change.

[00:49:31] It just shifts to the most vulnerable, highly conscientious people, which is exactly why Westover concludes the papal by outlining three long term capabilities every single company must build to ensure this doesn't happen. Let's walk through those three capabilities. First, institutionalizing workload governance. Organizations need to develop capacity impact statements for every new initiative, just like a city requires an environmental impact statement before building a new highway. That's a great idea.

[00:49:59] If an executive wants to launch a new software tool, they must formally state exactly whose hours it will consume to implement and maintain it. Second is building role architecture that actually flexes. The paper references Hackman and Oldham's 1976 work on the core characteristics of good jobs, task identity, autonomy and feedback. Roles need a stable, protected core of meaningful work. But they also need a limited rotating number of flex responsibilities.

[00:50:28] We have to acknowledge that the work will change. So the role must be designed to adapt without breaking the core. And third, companies must develop a continuous capability for redesign. Managers and employees need the actual skills, the vocabulary and the explicit permission to renegotiate boundaries constantly. It shouldn't just happen once a year during a crisis or a performance review. It should be a normal weekly conversation. This new demand came in.

[00:50:56] What resource are we adding or what demand are we dropping? So what does this all mean for you? It means synthesizing this massive academic structural theory into your daily life. It means that as you look at the overwhelming weight of your inbox tomorrow morning, you need to understand that it is a systemic failure, not a personal one. You are not failing at time management. You are operating within a collapsed structure.

[00:51:22] And crucially, it means giving you the formal, scientifically backed permission to decline outside role requests. Establishing role boundaries and demanding prioritization isn't you being difficult or lacking resilience. It is a continuous, vital organizational competence. It is the only way organizations will survive the current chaotic technological transition. The two-job job is not an accident of history.

[00:51:49] It is the predictable mathematical product of organizations aggressively removing capacity faster than they remove work, while blindly introducing technologies that require massive hidden human effort to maintain. We have been on quite a journey today. We started by diagnosing the two-job job, recognizing the immense psychological toll of role overload, conflict, and ambiguity. We mapped the four horsemen driving this crisis. The delayering that orphans' vital coordination work.

[00:52:18] The head count restraint that permanently redistributes it. The profound paradox of AI efficiency that creates invisible labor. And the crippling overhead of constant digital coordination. We examined the catastrophic costs. From individual burnout and the widening equity gap to the complete stalling of corporate innovation. And then we laid out the hard, evidence-based solutions. The brutal power of subtraction. The necessity of explicitly rechartering roles.

[00:52:48] And fundamentally treating human capacity like a hard, finite financial budget. And as we close, I want to leave you with one final deeply provocative question. A question that builds entirely on all this research into unmeasured, hidden labor. We are rushing headlong into an AI-driven future. Assuming these tools will eventually save us. But will they?

[00:53:09] But if every single new piece of efficiency technology we adopt generates a massive hidden trail of maintenance, testing, prompting, and articulation labor, are we rapidly approaching an event horizon where the unseen overhead of managing our productivity tools entirely eclipses the actual work those tools were meant to automate in the first place? That is a terrifying and essential thought to end on. If the tools take more time to manage than the work takes to do, the system collapses.

[00:53:40] Thank you so much for joining us on this deep dive. I want you to go back and look at that pristine PDF job description you thought of at the beginning of the hour. And then look at your actual to-do list. Don't look at it as a personal burden anymore. Look at it as a structural blueprint. It is a map showing exactly where the foundation is failing and exactly where you and your organization need to finally begin redesigning your work. Until next time.