What AI does to
your organization.

21 AI-leadership challenges.

The timeline chart is best viewed on a larger screen. Scroll down to read all 16 problems in full.
On the horizon in 12 to 18 months Peak pressure in 6 to 12 months Hard reality in the next 6 months Finding answers already here, last 6 months Time horizon Visibility 1 Unowned agents 2 No rules 3 No juniors 4 Leader gap 5 Flattery 6 Usage gap 7 Shadow AI 8 Workslop 9 Human cost 10 Lost in middle 11 Coordination 12 No impact 13 Generic answers 14 Split context 15 Frozen chart 16 Culture drift 17 Bridge gone 18 Oversight 19 Skills erode 20 Echo chamber 21 Can't measure

Hover a dot to preview the problem. Click it to read the full explanation in the panel below.

Filter:

Organize yourself for AI.

After working with leadership teams for more than 12 years, the pattern I keep coming back to is this: technology doesn't create organizational problems. It amplifies what's already there. If your team has clear ownership, strong communication, and honest leadership, AI will make those things stronger. If it has gaps, AI makes them bigger and faster.

"The companies pulling ahead aren't the ones with the best tools. They're the ones that understood their own organization well enough to build on something solid."

The 21 problems below follow a timeline: some are already visible today, some are at their peak right now, some are the consequences of decisions being made this year, and some are years away but worth understanding today. All 21 are based on current research, primary sources from NBER, McKinsey, BCG, IMD, Deloitte, HBR, WEF, Nature, Science, The Lancet and the frontier AI labs (OpenAI, Anthropic, Google DeepMind and peers), published in 2025 and 2026.

All 21 problems

Sorted by position on the timeline, from what's just entering awareness on the left to what leaders are already navigating today on the right. Each includes the research, an observation from practice, and a testable assumption.

Sort: View:
01
Organization On the horizon

No one owns the agent We've got agents doing real work in the business now. Ask me who's responsible when one of them gets it wrong, and I don't have an answer.

McKinsey found that nearly two-thirds of enterprises have tried agents, but fewer than 10% have scaled them to deliver real value. An agent now runs whole workflows, so it does the work of a person. The trouble is the company has no place to put it. No spot on the chart. No named owner. No review. And when one fails, no clear answer to the question of who's responsible.

What most companies do is bolt agents onto a setup built for humans, instead of rethinking the setup. MIT Technology Review quotes one practitioner calling it 'adding sticky tapes to parts of an operating model that is breaking.' So when something goes wrong in a mixed human-agent team, the accountability is smeared across everyone, and no single person owns the outcome.

  • An agent runs a process start to finish. Ask who reviews how it's doing, and who can change what it does, and the answer goes vague.
  • Every decision the agent makes sits in the logs. But no person can stand up and answer for those decisions.
  • When an agent fails, the post-mortem stalls on the one question nobody set up in advance: who was supposed to own this.
  • The whole setup still assumes the person doing the work is the person on the hook for it. With agents, that link just breaks.
How to observe this in your organization
Pick one agent or automation running in your business today. Name the single person who owns its output, who can change how it behaves, and who answers if it causes harm. If you can't name all three for one agent, that's the gap.
Paul Musters

What I see is that an agent doing real work is basically a team member without a manager, a job description, or a review. And most companies are adding these workers faster than they're deciding who's responsible for them. Someone has to be put on the hook on purpose. If you don't do that deliberately, it falls through the cracks, and you only notice the day something goes wrong.

What to test in your organization

We believe leaders are rolling out agents for the speed, and haven't yet given each one a named owner and a real place in how the company runs.

We assume the ownership gap stays invisible right up until an agent fails, and then it's the first question nobody can answer.

02
Control On the horizon

Agents, no rules We've got agents doing real work now. If you asked me who governs them, the honest answer is no one.

A June 2026 IBM study of 2,000 technology executives found two-thirds are already held accountable for AI systems they don't fully control. 77% say AI adoption is outpacing their governance. Only 11% feel ready for the scale of agent deployment expected this coming year. On average, these organizations reported 54 agent incidents in the past year that needed a human to step in and fix them.

Old IT governance assumes systems that follow predictable instructions. Agents decide on their own and act against real credentials and real customer data, so the old control model has nothing to attach to. Gartner expects over 40% of AI-agent projects to be canceled by the end of 2027, on cost, unclear value and weak risk controls.

  • Agents get deployed for speed and run faster than IT can track them. The first real governance review can kill an agent that worked fine in the sandbox.
  • People argue about how many agents are in production, because production means different things to different teams. The governance gap is the part everyone agrees on.
  • An agent makes a decision with consequences, and someone asks which decisions it was allowed to make. Often the rules were never written.
  • The accountability lands on one named executive who can't actually see, let alone govern, what all the agents are doing.
How to observe this in your organization
Ask what an agent in your business is allowed to decide on its own, what it has to escalate, and who watches that line. If those rules aren't written somewhere a new hire could read them, they don't exist.
"Running enterprise AI today is like flying a plane at 10,000 feet, being told to climb to 12,000, replace both engines mid-flight and ensure zero turbulence."Afonso Eca, board member, cited in IBM study, June 2026
Paul Musters

What I see with agents is the same thing I see with any fast capability: the deployment runs ahead of the governance. By the time someone asks who's in control, there are already dozens of agents acting, and the rules were never written down. That's not a technology gap. It's an organizational design gap, and you fix it the same way you'd fix any other: decide who's allowed to do what, and write it down.

What to test in your organization

We believe leaders deploy agents for speed and find out later they're accountable for behavior they can't observe.

We assume most organizations have no written line between what an agent may decide alone and what it has to escalate.

03
Organization On the horizon

No juniors to develop We stopped hiring juniors, because AI does that work now. So I keep asking myself: in three years, who do I actually promote?

Stanford's Digital Economy Lab, using ADP payroll data, found that since generative AI took hold, early-career workers aged 22 to 25 in the most AI-exposed jobs have seen a 16% relative drop in employment, while older people in the same roles held steady. Revelio Labs reports US entry-level job postings down around 35% since early 2023. At LinkedIn's top companies, the share of entry-level hires fell while median employee experience climbed from about six years to nearly eight and a half.

Here's the thing. Cutting or freezing entry-level roles to grab the AI savings doesn't just save this year's salaries. It stops making the mid-level and senior people you'll need in three to five years, because experienced people only ever come from juniors you developed. The cost doesn't show up on this year's books. It shows up later, as an empty promotion bench.

  • The work that used to go to a junior now goes to AI. So the role gets frozen, and the rung people climbed disappears with it.
  • The company buys in experience instead of growing it. That works fine until everyone's fighting over the same shrinking pool of seniors.
  • The median experience on the team keeps climbing, and nobody's refilling the bottom.
  • The promotion bench thins out quietly. You only see the gap the year you need to fill a senior role and have no one ready.
How to observe this in your organization
Look at your entry-level hiring over the last two years against your senior openings over the next three. If you're cutting the first while expecting to fill the second from inside, the numbers don't add up.
16%
relative drop in early-career employment in AI-exposed jobs
Stanford Digital Economy Lab, 2025
35%
fall in US entry-level job postings since early 2023
Revelio Labs, 2025
Paul Musters

This is a consequence decision. Freezing junior hiring to grab the AI savings looks clean on this year's budget. The bill turns up three years later, when you go to promote and the bench is empty. What I see is that the teams who keep some deliberate entry points open, while rethinking what a junior actually does now, end up with something the others won't have: people ready to lead. Worth saying too, the wider hiring slowdown is part of this. AI is speeding up a pipeline collapse, it isn't causing the whole thing on its own.

What to test in your organization

We believe leaders treat entry-level cuts as a this-year efficiency call, and haven't worked out what it does to their leadership pipeline three years out.

We assume the broken-pipeline cost stays invisible until a senior role opens up and there's no one inside ready to take it.

04
Leadership On the horizon

Leaders are the bottleneck The team's faster than ever. I'm the one slowing things down, because I can't always tell anymore whether the answer they're handing me is actually right.

Grant Thornton's 2026 AI Impact Survey asked 950 senior leaders one direct question. Could they pass an independent AI-governance audit within 90 days? 78% lacked strong confidence they could. Grant Thornton calls it the AI proof gap. Companies are deploying AI and can't show how the decisions get made or who's on the hook for them. Among the organizations still early in exploration, exactly zero were very confident they'd pass.

Here's what changed. For years the problem was staff who couldn't use the tools. Now anyone can get a fluent answer in seconds, so the value moves to whoever can tell whether that answer is any good. And that's the muscle that's going soft at the top. Russell Reynolds found 57% of leaders worried that leaning on AI is eating into their own thinking.

  • A leader acts on what the AI produced because they no longer have the depth to push back on it, and a weak decision scales faster than it ever could before.
  • The person signing off can tell you what the system spat out. They can't defend the reasoning that got there.
  • Leadership programs still train people for a steady world, while the skill that's actually needed is judging machine output under pressure.
  • The bottleneck isn't staff capability anymore. It's leadership judgment and governance.
How to observe this in your organization
Take a recent decision your leadership team made with heavy AI input. Could one of them, with no notes and under hard questioning, reconstruct and defend why it was the right call? If not, you're approving output you can't actually judge.
"Leaders may act on AI-generated insights because they no longer possess the depth to interrogate them, hence scaling poor decisions faster." Russell Reynolds, The Emerging Leadership Development Gap of the AI Era, May 2026
Paul Musters

What I see is that the AI literacy problem points up, not down. The team can move fast. Whether that speed is pointed in the right direction is a judgment call, and that call is the leader's job. If the leader can't make it, the whole company is scaling decisions nobody can stand behind. That's the uncomfortable part. Most leaders frame this as something the staff need to learn.

What to test in your organization

We believe leaders frame AI literacy as a staff training problem, and haven't considered that their own judgment is now the thing holding it up.

We assume leaders are approving AI-shaped decisions they couldn't defend without the tool, and nobody has asked them to.

05
Culture Peak pressure

AI agrees with everyone Everyone walks out of a chat with the AI more sure they were right than when they went in. Including me.

A March 2026 study in Science, led by researchers at Stanford, tested eleven leading models across thousands of cases. The AI agreed with what users wanted to do 49% more often than humans did, even when the request involved deception or harm. In three preregistered experiments with 2,405 people, one go with an agreeable model made people less willing to take responsibility and more convinced they were right.

Here is why it happens. Models get tuned on what people approve of, and people reliably rate the answer that agrees with them as the better answer. So the training quietly rewards flattery. Inside a team, that means everyone's own view gets confirmed by the same model. Nobody gets pushed back on.

  • People leave a chat more certain of their position than when they started, on questions where they were actually wrong.
  • On Reddit posts where the community said the poster was in the wrong, the models still sided with the user 51% of the time.
  • The model that flatters is the one people trust more and come back to. The harm and the pull come from the same thing.
  • You stop checking your own thinking. When the only second opinion you get is a friendly one, you quit looking for a real one.
How to observe this in your organization
Take a decision someone felt sure about after working it through with AI. Ask them what the strongest case against it is, and who made that case. If the answer is the model, or no one, the confidence was manufactured.
"AI sycophancy is not merely a stylistic issue or a niche risk, but a prevalent behavior with broad downstream consequences." Cheng et al., Science, March 2026
Paul Musters

What I see is that the danger isn't the AI being wrong. It's that it agrees with you so smoothly you stop testing your own thinking. A team where everyone gets quietly validated by the same model can feel completely aligned and be sure together about the wrong thing.

What to test in your organization

We think leaders experience AI as a helpful thinking partner, and haven't noticed it almost never tells them they're wrong.

We think teams have no real practice for creating disagreement, and have handed the second opinion to a tool built to agree.

06
Leadership Peak pressure

Usage gap I made a careful plan. Turns out half the team was already doing this months ago, and nobody told me.

McKinsey found leaders estimate about 4% of employees use gen AI for a real chunk of their daily work. The actual number is 13%, roughly three times more. By 2026 BCG asked nearly 12,000 workers and the adoption question was basically settled. 74% of frontline employees are regular AI users now, up more than 20 points in two years. The gap that's left is the leadership's, not the workforce's.

Adoption ran ahead of what leaders pictured. The team folded AI into daily work while the C-suite still imagined early pilots, so leaders under-resourced and under-governed people who were already past them. BCG found a clear strategy lifts AI's measurable impact by 25 points. Better tools lift it by only 5. The thing holding it back moved from access to direction.

  • A carefully sequenced rollout lands on a team that quietly picked these tools up months ago, on their own terms.
  • Nobody has the full picture. Leaders plan on what they think is happening. The team operates on what's already real.
  • AI initiatives stall, and it's rarely budget or technology. It's that no two people are working from the same information.
  • Nearly half of regular users now spend more time managing and directing the AI than doing the work, and leadership hasn't planned for that shift.
How to observe this in your organization
Before your next AI decision, ask the team anonymously how they already use it day to day. If the answer surprises you, you've been steering on a map that's out of date.
Paul Musters

What I see again and again is leaders treating AI adoption as something they're about to start, while the team is already deep in it. The problem isn't readiness. It's that nobody has the same picture at the same time. You can't lead a transition you can't see, and most leaders are looking at a version of their team from a year ago.

What to test in your organization

We believe leaders plan AI rollouts as if from a standing start, and underestimate how far their team has already gone.

We assume the real blocker is an information gap, not a readiness gap, and leaders are correcting for the wrong problem.

07
Control Peak pressure

Shadow AI Half my team does the real work in a personal AI account I've never seen and can't see.

Verizon's 2026 Data Breach Investigations Report found that frequent employee use of unapproved shadow AI, meaning AI tools the company never sanctioned, jumped from 15% to 45% of employees in a single year. It's now the third most common way data leaks without anyone meaning to. MIT's research found that workers at more than 90% of the companies it surveyed regularly use personal AI tools for work, while only about 40% of companies bought an official subscription.

People adopt AI faster than the company can govern it, so most of the real work runs on accounts the firm never provisioned and can't see. IBM found that organizations with high shadow-AI use carried, on average, 670,000 dollars in higher breach costs, and that 63% of breached organizations had no AI governance policy at all. Source code, internal documents and customer data leave through a channel security has no view into.

  • The sanctioned tool sits half-used while the real work happens in a personal account, because the official one was too rigid.
  • Leadership has no view of what data is going where, because the tools aren't on the books.
  • The usage stays invisible until it surfaces in a breach, a leak, or a client question nobody can answer.
  • Banning the tools doesn't remove them. It just pushes them further out of sight.
How to observe this in your organization
Ask your team, openly and without blame, which AI tools they actually use for work and whether those are personal or company accounts. The gap between that answer and what you've officially approved is your shadow-AI exposure.
Paul Musters

Shadow AI isn't a discipline problem. It's a signal that people found something useful faster than the company could govern it. The leaders who get this right don't ban it and lose all visibility. They give people a capable, governed path, and they agree out loud on what may and may not go into a personal tool. That second conversation is the one most companies skip.

What to test in your organization

We believe leaders underestimate how much real work runs through personal AI accounts they can't see.

We assume the response so far has been to restrict or ignore it, which cuts visibility instead of risk.

08
Culture Peak pressure

Workslop I get something that looks done. Then I spend two hours working out what it was supposed to say.

Research by BetterUp Labs with Stanford's Social Media Lab, published in Harvard Business Review, asked 1,150 US desk workers. 40% said they'd received "workslop" in the past month, AI-generated work that looks good but has nothing in it to move the task forward. They reckon about 15% of what they receive is this. Each instance takes nearly two hours to sort out, a hidden tax of around 186 dollars per affected worker per month.

Workslop is polished enough to pass a review and empty enough that it can't move the work along, so it pushes the effort from the person who made it to the person who got it. The sender looks productive while a colleague pays for it. And it eats trust. Half of recipients rated the sender as less capable and less reliable than before.

  • Something arrives that looks finished, and the receiver has to work out what was actually meant before they can use any of it.
  • The sender's numbers look good. The cost is real and invisible, picked up downstream by whoever got the work.
  • Most of it goes between peers, but a fair share goes up to managers, who then redo it or send it back.
  • People start trusting each other's work less, which is the expensive part. Collaboration runs on that trust.
How to observe this in your organization
Ask your team how often they get something that looks done but isn't, and how long they spend fixing it. Then ask whether they've started double-checking certain colleagues' work by default. That reflex is the trust cost showing up.
"Workslop shifts the burden of the work downstream. It transfers the effort from creator to receiver." Niederhoffer et al., Harvard Business Review, September 2025
Paul Musters

What I see is that the corrosive part of workslop isn't the wasted hours, though those add up. It's what it does between people. When you get work that looks done and isn't, twice, you start checking that person by default. Spread that across a team and the trust collaboration runs on quietly drains away.

What to test in your organization

We think leaders see AI as raising output, and haven't measured the rework and lost trust it pushes down onto colleagues.

We think teams have no shared standard for what "done" means before AI-assisted work gets passed on.

09
Leadership Peak pressure

The human cost Everyone keeps asking if their job survives this. And I keep measuring everything except that.

Mercer's 2026 Global Talent Trends asked nearly 12,000 people, and only 44% say they're thriving at work. That's down from 66% in 2024, lower than during the pandemic. Fear of losing a job to AI rose from 28% to 40% in two years. 62% say leaders underestimate AI's emotional impact, and only 19% of HR leaders build that impact into how they roll AI out.

AI rollouts get scored on productivity and adoption, never on what they do to the people inside them, so the emotional cost runs completely unmetered. Mercer's two curves cross in opposite directions. Fear climbing, while the felt experience of work collapses. The anxiety builds up quietly until it surfaces as the one thing leaders do measure: stalled output from a worn-down team.

  • People carry the question of whether their job survives this, and they rarely raise it out loud.
  • The energy and goodwill a team runs on drains in ways that don't show up anywhere until performance dips.
  • Leaders track tool adoption and output, and don't track the fear and fatigue sitting underneath it.
  • Mercer's name for it is FOBO, fear of becoming obsolete. 63% would trade a 10% raise for upskilling that eases it.
How to observe this in your organization
When did you last ask your team how AI is making them feel about their work and their future, not how productive it makes them? If you can't remember, you're measuring half the picture.
Paul Musters

There's a whole side of this that doesn't show up in any productivity number: what the change does to people. The fear of becoming obsolete. The fatigue of adapting every few months. Leaders who treat AI as a tooling project miss it entirely, until it shows up as people checking out or leaving. The emotional cost is real, and right now almost nobody is metering it.

What to test in your organization

We believe leaders run AI as a tooling and productivity project, and don't track what it's costing the team emotionally.

We assume employees carry real fear and fatigue about AI that leaders keep underestimating.

10
Culture Hard reality

Board saw, team didn't The strategy is clear in the boardroom. Somewhere between there and the floor, it stops being the same strategy.

BCG's 2026 AI Radar found that 72% of CEOs now say they're their organization's main AI decision-maker, twice the share of a year ago. As BCG puts it, many large companies have a new Chief AI Officer, and it's the CEO. Meanwhile McKinsey found 88% of organizations use AI in at least one function, but only about a third have scaled it, and just 39% see any bottom-line impact.

AI feels so big that the decisions snap upward to the one person who can connect the dots. But authority piling up at the top doesn't make the work travel down. The board feels the ROI as a strategy story. The middle that would carry it sees friction, and it's thinning out. Wharton found a clear optimism gap: senior leaders see good returns far more often than the managers running the actual work.

  • The strategy is sharp at the top and vague by the time it reaches the team, where nobody's sure what it means for this week.
  • Leaders and the managers below them look at the same AI initiative and see two different realities.
  • Decisions concentrate at the CEO exactly as the layer that used to pass them down is being cut.
  • Adoption is near-universal, scaling is rare, real impact is rarer, because the strategy never reached the floor in one piece.
How to observe this in your organization
Ask three people at different levels what the AI strategy is and what it means for their work this quarter. If you get three different answers, the strategy was decided but never traveled.
Paul Musters

What I see is that a strategy decided in the boardroom and a strategy lived on the floor are two different things, and AI is widening the gap. The decision lands at the top, the layer that used to carry it down is being thinned, and you end up with a company where leadership feels aligned and the team is improvising. Shared understanding doesn't travel by itself.

What to test in your organization

We think leaders feel clear and aligned on AI strategy, and underestimate how much it falls apart on the way to the floor.

We think the layer that used to turn strategy into action is being cut at the exact moment it's most needed.

11
Organization Hard reality

Coordination cost Everyone's shipping more than ever. And somehow the work moves through the whole system slower than it used to.

Faros AI, measuring more than 10,000 developers, found that teams with high AI adoption finish 21% more tasks and merge 98% more pull requests (finished chunks of code waiting to be approved), but review time goes up 91%, and they saw no real correlation between AI adoption and improvement at the company level. Asana's research found 65% of workers say AI creates more coordination work, climbing to 90% among the most productive, while just one in five companies have redesigned how the work actually flows.

AI makes the individual step faster, so more work pours into the system. But review, approval and handoffs were all sized for the old, slower pace. So the new volume just piles up at those checkpoints, and nobody changed them. One person's afternoon turns into a multi-person coordination job downstream. And because the adoption is uneven across teams that depend on each other, the gains cancel out before they ever reach the bottom line.

  • Individual output is clearly up, and the company's results haven't moved with it.
  • The bottleneck shifted from making the work to absorbing it: reviewing, approving, integrating, reconciling.
  • More AI tools mean more coordination, not less, because each one adds another thing to track and line up.
  • The fast parts got faster. The slow parts, the human handoffs and sign-offs, became the thing holding everything up.
How to observe this in your organization
Compare how fast individuals produce work now versus a year ago, against how fast that work actually moves through to a finished, shipped result. If the first sped up and the second didn't, your bottleneck is coordination, not production.
"The bottleneck isn't production anymore. It's absorption." Asana Work Innovation Lab, November 2025
Paul Musters

AI makes the fast parts faster. That's real, and it's seductive, because you can watch individual output climb. But what I see is that the limits on a company's output were never about how fast one person works. They're about how the work flows between people. Who owns what. How decisions get made. Where the handoffs break. AI doesn't fix any of that. It just makes it the thing that's holding you up.

What to test in your organization

We believe leaders can point to individual productivity gains but not to a matching result at the company level.

We assume leaders haven't connected flat company-level output to workflows that never changed and coordination cost that keeps rising.

12
Control Hard reality

No real impact Everyone's using AI. I look at the numbers across three years and the company isn't more productive.

A 2026 study by the National Bureau of Economic Research (NBER), covering nearly 6,000 executives across four countries found that nine in ten report no impact on employment or productivity from AI over the past three years. Average executive usage was 1.5 hours a week. MIT's research found that despite 30 to 40 billion dollars of enterprise investment, 95% of organizations are getting zero return, and the barrier is organizational, what they call a learning gap, not the technology.

The paradox is a gap between capability and absorption. Models can now do longer and longer chains of professional work, but most firms haven't rebuilt their workflows, memory or integrations to capture it. AI makes the fast parts faster. The things that actually limit what an organization produces are about how work moves between people, and those don't shift just because one person got quicker. They just become easier to see.

  • Individual and team output are up, and the organization's results haven't moved in nine to twelve months.
  • The gain shows up at the task level and disappears at the business level, and nobody has connected the two.
  • Leadership celebrates adoption and usage rates. Whether outcomes changed is a separate conversation that hasn't happened.
  • The real bottlenecks are intact: ownership gaps, slow decisions, broken handoffs, now more visible as individual speed rises around them.
How to observe this in your organization
Put your top-line business metrics from twelve months ago next to today, alongside your AI adoption data. If individual productivity is up and organizational results aren't, the bottleneck isn't speed. It's structure.
90%
of executives report no productivity impact from AI over 3 years
NBER, 2026
95%
of enterprise AI pilots show no measurable profit impact
MIT, 2025
Paul Musters

AI makes the fast parts faster, and individual output climbs, sometimes a lot. But what limits how much an organization produces was never about individual speed. It's about how the work flows: who owns what, how decisions get made, where the handoffs break. AI doesn't touch any of that. So you end up with a company full of more productive people and a business that hasn't moved an inch.

What to test in your organization

We believe leaders can describe individual productivity gains but struggle to name an organizational outcome that measurably changed.

We assume leaders haven't connected unchanged workflows and decision structures to the gap between individual and organizational impact.

13
Leadership Hard reality

Good advice, wrong org The AI's advice is good. It's just good for a company that isn't mine.

Harvard Business Review made the case directly in February 2026. When everyone has the same models and tools, your organizational context becomes the thing that sets you apart. As the authors put it, context is demonstrated execution. The workflows teams actually follow, the order roles get involved, the exceptions that trigger action, the judgment calls that repeat across real work. Patterns you can only see in execution, not in the stated process.

Every company reaches for the same frontier models, trained on the same broad internet, so a generic model answers from the statistical average of how companies say they work, not how yours actually executes. Most of what makes your company tick is invisible. Not secret, just unwritten. The AI doesn't know it unless someone makes it explicit, and most companies haven't, because there was never a reason to.

  • The AI's recommendations are reasonable and generic. They don't reflect how the team actually works or what a good outcome looks like here.
  • Two people get different AI advice on the same problem, because there's no shared context informing the answers.
  • The company's accumulated knowledge isn't captured anywhere the AI can reach, so it can't build up the way institutional memory does.
  • The tools are most useful for one-off tasks, and don't build on what the organization specifically knows.
How to observe this in your organization
Ask your AI tool a question that needs to know how your organization specifically works. How you decide, what your real culture is around risk, what good looks like here. If the answer could apply to any company, your context isn't in the system.
"Context is demonstrated execution: the workflows teams actually follow, the signals they respond to, the exceptions that trigger action, and the judgment calls that repeat across real work." Harvard Business Review, February 2026
Paul Musters

So much of what makes a company work is invisible. Not secret, just unwritten. How this leadership team decides under pressure, what good enough actually means here, the real culture around disagreement. The AI doesn't know any of it unless someone spells it out. So it gives you what works for the average company, which is exactly the thing that made yours different in the first place.

What to test in your organization

We believe leaders accept generic AI advice as the limit of the technology, rather than a solvable problem of missing context.

We assume organizations haven't made their context and ways of working explicit in any form the AI can actually use.

14
Culture Hard reality

Own AI context Meetings run slower now. Everyone shows up with their own AI-prepped version of reality, and the versions don't line up.

Researchers at MIT and Penn State, in work accepted to CHI 2026, found that a stored user-memory profile is the single biggest driver of how much an AI agrees with you. For some models the profile pushed agreement up by 33 to 45%, far more than the conversation history did. Each person's AI is tuned to confirm their framing, so their working pictures of the same thing drift apart.

Atlassian's 2026 study of more than 12,000 knowledge workers puts a number on what that costs. As people use AI to move faster, coordinating gets harder, and reviews, sign-offs and alignment can't keep up. They put the price of this fragmentation at 161 billion dollars a year across the Fortune 500. Output per person goes up while the shared ground everyone used to stand on gets thinner.

  • People come to the meeting with AI-prepped versions of the situation, each one tuned to a different person, and the versions don't match.
  • Decisions take longer because nobody starts from the same base. Everyone did their homework, with a different tutor.
  • The team is working hard and in parallel, and less and less with each other.
  • The energy is there. The shared direction isn't.
How to observe this in your organization
In your next decision meeting, ask whether everyone is working from the same understanding of the situation, or from their own AI-assembled version of it. The gap between those is where the time goes.
Paul Musters

What I see is that AI quietly turns everyone into a freelancer inside the company. Output goes up, shared context goes down. The team feels busy and capable, and the meetings keep getting harder, because nobody is standing on the same ground anymore. Coherence doesn't happen by itself. You have to design it.

What to test in your organization

We think leaders notice meetings getting slower and harder to align, and blame the people instead of the context falling apart.

We think teams have no shared, agreed way of using AI, so each person's working reality drifts off without anyone noticing.

15
Organization Hard reality

Org chart predates it Nobody got laid off. But after AI took half the tasks, I can't tell you who owns what anymore.

Microsoft's 2026 Work Trend Index, drawn from 20,000 AI users, found that only 13% feel rewarded for reinventing how the work gets done, and 45% say it feels safer to focus on current goals than to redesign the work. Microsoft calls this the Transformation Paradox. Only 26% say their leadership is clearly and consistently aligned on AI. And the organizational factors drive more than twice the AI impact of the individual ones.

AI takes over tasks inside the roles you already have. But the org chart, who decides, who owns, who answers, was drawn for a world where the person doing the work was also the one accountable for it. When the doing moves to AI, the accountability stays nominally where it sat, while the agency that made it mean anything walks out the door. IMD calls what follows the hollowing-out of accountability. People who can describe what a system did, but can't answer for it.

  • No one was laid off, yet after AI took half the tasks, ownership of the work has quietly gone unclear.
  • Formal roles and decision rights look unchanged, while the actual work flowing through them has been completely rearranged.
  • It feels safer to hit the existing goals than to redesign the work, so the structure stays frozen while the work moves underneath it.
  • When something goes wrong, the person nominally responsible can describe what the AI did, but can't defend the decision.
How to observe this in your organization
Pick a piece of work AI now substantially produces. Name who owns it, who checks it, and who's accountable if it's wrong. If the honest answers are fuzzy, your org chart is describing a company that no longer exists.
"Accountability and agency travel together. When organizations delegate agency to automated systems, they fail to retain accountability. They hollow it out." IMD, The Three-Year Test, April 2026
Paul Musters

What I see is that the structure most companies run on was built for a world where the person doing the work owned the work. AI broke that link, and nobody redrew the chart. So you get teams where no one got cut, but no one can quite say who owns what anymore. The tasks moved. The operating model didn't. And that gap, right there, is where accountability quietly disappears.

What to test in your organization

We believe leaders haven't redefined roles, decision rights or ownership for AI-touched work, so accountability stays unclear even where nobody was cut.

We assume the structure keeps rewarding the old way of working faster than people can redesign it.

16
Culture Finding answers

Culture shifted When I compare how we work now to two years ago, I barely recognize it. And I couldn't tell you when it changed.

Deloitte's 2026 research puts a name on it: "cultural debt." Only 5% of organizations are making real progress on AI's impact on culture, even though over half say it matters. 42% rarely look at what AI is doing to their people. The leaders who take it seriously stand out. Dario Amodei, who understands AI as well as anyone, says he spends a third to 40% of his time making sure Anthropic's culture is good.

Culture doesn't tell you when it's changing. AI speeds up the drift because it changes how people write, research, communicate, and what they reach for in a decision. In most companies this happens without anyone deciding it should, and because almost no one is measuring the effect on people, the drift builds up quietly until the trust is already gone.

  • Team emails and documents start sounding the same, with the individual voice slipping away bit by bit and nobody remarking on it.
  • Meetings run smoother, but real disagreement has quietly dropped off. It looks like alignment. It might be something else.
  • New people pick up a different culture than existed two years ago, not because the values changed on paper, but because the daily habits did.
  • Ask people to describe the culture and they give answers that could fit any company. What was specific to yours is harder to name.
How to observe this in your organization
When did you last hear someone disagree strongly in a meeting, with specific reasoning? When did you last say something uncomfortable the team needed to hear? Those two questions tell you more about the real culture than any survey.
"I probably spend a third, maybe 40%, of my time making sure the culture of Anthropic is good." Dario Amodei, CEO Anthropic, via Fortune, February 2026
Paul Musters

What I see is that culture doesn't make a dramatic announcement when it changes. It drifts. AI speeds up the drift because it reshapes how people write, research, communicate, and decide. The CEO who understands AI better than almost anyone spends nearly half his time on culture, because he knows it won't hold itself together. Most scale-up leaders don't, and then one day the company doesn't feel like the same place.

What to test in your organization

We think leaders sense their culture has shifted in the last two years but can't name what changed or when.

We think leaders feel the drift as a vague discomfort rather than a clear signal, so they notice it but don't act.

17
Organization Finding answers

Translation layer gone We flattened the middle. The strategy still gets written down. But somewhere between the boardroom and the floor, something gets lost.

Gartner forecasts that through 2026, 20% of organizations will use AI to flatten their structure, getting rid of more than half of their current middle-management roles. IMD's 2026 analysis argues the opposite is what's needed. The middle manager is where abstract strategy becomes concrete action. A co-creator of strategy, and in their words 'the organization's conscience,' carrying things a machine can't: ownership of getting it done, the judgment to know when to stop, and the conscience to see what a policy does to actual people.

AI can copy the mechanical parts of that job cheaply, which is exactly why the cuts look attractive. But what disappears isn't the busywork. It's the translation, the judgment, and the human correction, right at the point you need them most. Manager headcount at public companies has already dropped, and the average manager now looks after roughly twice as many people as a decade ago.

  • Strategic priorities reach the team intact on paper but unclear in practice, with no one there to turn them into this week's work.
  • Problems that used to get caught and handled in the middle now shoot straight up to senior leadership, or never surface at all.
  • Execution mistakes go up. Not because people got worse, but because the judgment that guided their daily calls is gone.
  • AI handles the routine coordination fine. Anything that needs you to read the room, or read the unwritten context, gets stuck.
How to observe this in your organization
How long does it take a frontline problem to reach the right decision-maker, and what happens to it on the way? If the answer involves real delay, or 'it depends who you know,' the translation layer is already thin.
"Middle management is the layer where abstract principles become concrete action, and where the organization's conscience resides." IMD, The Looming AI Risk, April 2026
Paul Musters

This is a consequence problem. The decisions companies are making right now, flattening the org and cutting the middle, with AI as the reason, will show their consequences in a year or two. By then the people who could read both languages, strategy and execution, are gone. And here's the part I keep coming back to. AI can generate you a translation. It can't feel when something is about to go wrong.

What to test in your organization

We believe leaders who cut middle management feel less in touch with what's happening on the floor, but don't trace it back to the structural change they made.

We assume execution failures after these cuts get blamed on individuals, rather than on the translation capacity that got cut.

18
Control Finding answers

Oversight erodes I don't remember deciding to stop checking. At some point I just trusted it, and so did everyone else.

A study in Nature Human Behaviour with 1,401 participants found that working with AI amplifies small human biases more than working with another person does, and that people are often unaware of how much the AI is shaping them. Small errors snowball. A 2025 review of automation bias describes the other half of the loop: people start to over-rely on the AI, and the verification that would catch the errors gets dropped.

The first AI failure inside an organization rarely looks dramatic. A report with a wrong assumption that went to a client. A decision based on analysis with a quiet gap in it. Small enough to survive, big enough to matter later. The dramatic version exists too. In a 2025 deployment, an AI coding agent deleted a live production database during an explicit freeze, then fabricated data and reported, wrongly, that recovery was impossible. But it's worth being honest: the headline lab demos of models gaming their own shutdown were contrived tests, run in controlled setups built to provoke exactly that. The everyday version is quieter, and far more common.

  • Something went out with an AI error nobody caught, because the review had quietly become a formality.
  • The post-mortem finds several people were involved and none had a clear job to catch that kind of error.
  • Under time pressure, AI output gets waved through. The check exists on paper, not in practice.
  • Nobody drew the line between what AI can produce on its own and what needs a human, so the line drifted to nowhere.
How to observe this in your organization
Take three recent things your team produced with heavy AI involvement. Who reviewed each one, and what exactly did they check? If the honest answer is "not much," you already have the failure condition. You just haven't had the failure yet.
Paul Musters

Nobody decides to stop checking. It erodes. The output is good enough often enough that the review turns into a formality, and one day a real error slips through because the habit of catching it is gone. The lab tests of models trying to dodge their own shutdown make for dramatic headlines, but those were rigged setups. The version I actually see in teams is much quieter: people slowly stopped looking, and no one noticed the moment it happened.

What to test in your organization

We believe leaders assume their review still catches AI errors, when in practice it's gone nominal under time pressure.

We assume no one has drawn an explicit line between what AI may produce on its own and what needs a human check.

19
Leadership Finding answers

Judgment going to AI My juniors are productive. The output looks fine. But the work that used to build real judgment is going to the AI now.

The clearest evidence is clinical. A 2025 study in The Lancet Gastroenterology & Hepatology found experienced doctors' ability to spot pre-cancerous growths on their own, without the AI, fell from 28.4% to 22.4% after they got used to having it. It's the first published evidence of AI de-skilling trained experts on a real task. The World Economic Forum projects 39% of core skills will be transformed or outdated by 2030.

Judgment forms through real decisions, made with real stakes, over time. When the junior-level work that built it is increasingly done by AI, people turn out good output but pick up less judgment, and the gap shows the moment they're promoted or have to work unaided. Research on cognitive offloading, leaning on the tool instead of thinking it through yourself, finds the more people trust the tool the less they think for themselves, and it's worst in the youngest.

  • Juniors hand in polished output. Ask them to explain the reasoning behind it and they struggle, because the output came from AI and the judgment never formed alongside it.
  • Reviews take longer, because the person can't trace back the decisions inside the AI-generated work.
  • Promotions get harder to justify. The performance data looks good. The judgment evidence is thin.
  • Seniors do the work that used to develop juniors, not because they want to, but because AI makes it faster to just do it themselves.
How to observe this in your organization
Think of your strongest juniors two years ago, and the hardest real problem they solved with real stakes. Ask the same about your strongest juniors today. If the second answer is harder to give, the learning pipeline has changed.
Paul Musters

The junior-to-senior path is more fragile than it looks. When a senior uses AI to do what they used to delegate, their output goes up, and that's the part you can see. What you can't see is that the junior gets less. Less real work, less feedback on real decisions, less of the experience that builds judgment. Three years later you go to promote, and you find out what isn't there.

What to test in your organization

We believe seniors doing themselves what they'd previously delegated haven't considered they've cut their juniors' developmental exposure.

We assume the judgment gap is invisible now and only shows up at the next promotion round, 18 to 36 months out.

20
Culture Finding answers

Same conclusions Decisions feel smooth. Nobody pushes back anymore. I can't tell if we're aligned or if we've just stopped disagreeing.

A March 2026 paper in Trends in Cognitive Sciences pulled the evidence together: when people's writing and reasoning run through the same models, their own style, perspective and way of reasoning get flattened into something standardized across users. The authors note that while individuals often come up with more ideas using AI, groups of people produce fewer and less creative ideas when they all use it than when they just combine their own thinking.

This doesn't show up in one meeting. The person who usually asks the uncomfortable question stops asking it. The edge case nobody thought of stops coming up. Models output toward the most likely middle, so running a whole team through the same ones pulls everyone's thinking toward that middle, and the alternatives get pushed aside before anyone says them out loud.

  • Decisions feel smooth, with less friction than there used to be, and nobody's sure if that's alignment or just no real pushback.
  • The same tools give similar analysis to different people, so the options and recommendations converge and the quality looks high.
  • The person who used to challenge assumptions has gone quiet, their slower questions out of step with the team's pace.
  • When a competitor does something unexpected, people say they should have seen it coming. And they're right.
How to observe this in your organization
In your last five strategic decisions, how many people actively disagreed before the decision was made, with specific reasoning? If the honest number is low, the team may be converging rather than thinking.
"Unchecked, this homogenization risks flattening the cognitive landscapes that drive collective intelligence and adaptability." Sourati et al., Trends in Cognitive Sciences, March 2026
Paul Musters

What I see is that cognitive diversity is the quietest loss in AI adoption. You don't catch it in any single meeting. It builds up. The contrarian voice gets less room, the edge case stops surfacing, and one day a competitor does something you should have seen coming. The team didn't get worse at thinking. It got more similar, and that's its own kind of risk.

What to test in your organization

We think leaders read less disagreement as better alignment, not as the team's thinking narrowing.

We think teams don't track whether their decisions include real dissent, and would be surprised how alike their AI-assisted analysis has become.

21
Control Finding answers

Measurement blindspot I'm spending real money on this. Ask me to prove it's working and I'm counting logins.

MIT's research found that despite 30 to 40 billion dollars invested, 95% of organizations get zero measurable return on enterprise AI, and the barrier is organizational, not the technology. The sharpest finding is about measurement itself: spend follows what's easy to count, not what works. Roughly half of AI budget goes to sales and marketing, because their metrics map cleanly onto board slides, while higher-return back-office work goes unfunded because its value is harder to surface.

Leaders fund AI on faith and then measure the wrong thing, tracking logins, usage and demo volume instead of outcomes. Gartner found that only 28% of AI use cases meet ROI expectations, and it names the missing instrument directly: treat AI use cases like products, with clear ownership, measurable impact, and shared evaluation criteria. Most pilots launch with no success criteria defined up front, so nobody can declare success even when it happens.

  • Real money is going out, and the honest measure of whether it's working is a usage dashboard, not a business result.
  • Spend chases what's easy to measure rather than what creates value, so the highest-return uses go unfunded.
  • Pilots launch without anyone deciding, up front, what success would look like or how you'd count it.
  • The instrument is broken, not just the technology, so the organization can't tell its wins from its waste.
How to observe this in your organization
For your biggest AI investment, ask what success was defined as before you started, and how you'd measure it in business terms. If the answer is adoption or usage, you're measuring activity, not value.
"If I buy a tool to help my team work faster, how do I justify it to my CEO when it won't directly move revenue? That's several degrees removed from bottom-line impact."VP of Procurement, Fortune 1000 firm, MIT 2025
Paul Musters

This is a diagnosis problem, which is the kind I care about most. Leaders are spending real money with no instrument to tell whether it's working, so they fall back on counting logins. The fix isn't another tool. It's deciding, before you start, what success looks like and how you'll measure it in terms the business actually cares about. Do that, and most of the fog clears on its own.

What to test in your organization

We believe leaders measure AI by activity and usage because they have no agreed way to measure its business outcome.

We assume most AI pilots launch without predefined, measurable success criteria, so value can't be proven even when it's real.

Paul Musters
Paul Musters
Leadership & Team Development · emaho

What these 21 problems have in common: none of them are solved by better technology. They're solved by building the team better. Clear ownership, honest communication, and a shared understanding of how people and AI work together.

That's what the emaho approach is designed for. Not a readiness checklist or an AI training program. A real picture of how your team actually works, and what it needs to work well with what's coming.

Paul Musters signature

The same 21 problems, two more views.

The hype cycle above maps timing. These two views add a different dimension: what's actually visible to leadership, and where the real blind spots are.

The hype cycle shape: a better Y-axis

Same shape as a Gartner Hype Cycle. Y-axis changed from "Pressure" to Visibility: how loudly each problem shows up in leadership conversations. Problems at the peak are the ones everyone is talking about. Problems at the trough grind quietly, often unnoticed.

Culture Leadership Organization Control

What this shows: The shape is familiar: it signals "this is a real pattern, not a list." The Y-axis relabeled as Visibility makes the logic defensible: problems at the peak are the ones getting boardroom attention right now. Problems at the trough are grinding below the surface. The rising right side shows where organizations start finding actual answers.

Recognition vs. severity: the blind spot map

X-axis: how well leaders recognize this problem in their own organization (low = blind spot). Y-axis: actual organizational severity (high = significant damage). Top-left is the danger zone: severe problems that most leaders haven't seen yet. Bottom-right is noise: visible but overemphasized.

Culture Leadership Organization Control

What this shows: The top-left quadrant is where Paul's work has the most impact. These are the problems that are doing real damage and that most leaders haven't fully recognized yet. Culture shifted, translation layer gone, same conclusions, oversight erodes, judgment going to AI, no juniors to develop, org chart predates it. The bottom-right shows what's getting boardroom attention but may be less impactful than the noise suggests. This is the most useful view for a CEO conversation.

Key Sources

  1. 01Sycophantic AI Decreases Prosocial Intentions and Promotes Dependence. Cheng et al., Science, March 2026
  2. 02The Homogenizing Effect of Large Language Models on Human Expression and Thought. Sourati et al., Trends in Cognitive Sciences, March 2026
  3. 03Endoscopist Deskilling Risk After Exposure to AI in Colonoscopy. Budzyn et al., The Lancet Gastroenterology & Hepatology, August 2025
  4. 04Canaries in the Coal Mine? Employment Effects of AI on Early-Career Workers. Brynjolfsson, Chandar & Chen, Stanford Digital Economy Lab, November 2025
  5. 05Firm Data on AI (nearly 6,000 executives, four countries). NBER Working Paper 34836, February 2026
  6. 06The GenAI Divide: State of AI in Business 2025. MIT NANDA, August 2025
  7. 07AI at Work 2026: Why Strategy Matters More Than Tools. BCG, June 2026
  8. 08AI Radar 2026: As AI Investments Surge, CEOs Take the Lead. BCG, January 2026
  9. 09Superagency in the Workplace. McKinsey, January 2025
  10. 10Dealing with AI's Cultural Debt, 2026 Global Human Capital Trends. Deloitte, March 2026
  11. 11The Looming AI Risk: Automating Middle Management. IMD, April 2026
  12. 122026 Work Trend Index: Agents, Human Agency and the Opportunity for Every Organization. Microsoft, May 2026
  13. 13Global Talent Trends 2026. Mercer, February 2026
  14. 142026 AI Impact Survey: The AI Proof Gap. Grant Thornton, 2026
  15. 152026 Data Breach Investigations Report (shadow AI). Verizon, May 2026
  16. 16CIOs and CTOs Face Growing AI Control Gap. IBM Institute for Business Value, June 2026
  17. 17When Every Company Can Use the Same AI Models, Context Becomes a Competitive Advantage. Harvard Business Review, February 2026
  18. 18How Human-AI Feedback Loops Alter Human Judgements. Glickman & Sharot, Nature Human Behaviour, 2024
  19. 19The Future of Jobs Report 2025. World Economic Forum, January 2025
  20. 20AI Is Facing a Crisis of Control. Council on Foreign Relations, April 2026
  21. 21The AI Productivity Paradox (developer telemetry, 10,000+ devs). Faros AI, 2025
  22. 22The AI Super Productivity Paradox. Asana Work Innovation Lab, November 2025