top of page
Search

Ambient Effort™: Agents Aren't on the Org Chart

Updated: May 8

A powerful wave crashing onto ancient rocks — representing the force of agentic AI meeting organizational structures that were never designed to absorb it, and the Ambient Effort™ concentrated on the people caught between them.
Built for another ocean.

What Happens to Your Organization When the Technology Outpaces the Structure

Article 2 of 3


If you read Article 1, you know what Ambient Effort™ feels like from the inside. The exhaustion of keeping up with a moment that won't slow down, the cost of the pivot that saved your organization, the market pressure arriving from clients who expect the technology to have already changed what they pay.


This article is about what that same moment looks like from the outside, from the 30,000-foot view of the organization itself.


And what it looks like from up there is this: a structure built for one century being asked to run technology designed for another.


The agents aren't on the org chart. They weren't there when it was drawn. They weren't considered when the reporting lines were established, when the decision rights were assigned, when the accountability frameworks were built. They arrived — fast, capable, autonomous, and completely outside every assumption the organization was designed around.


And many organizations are now being asked to absorb them. Immediately. Without restructuring. Without new governance. Without updated accountability frameworks. Without telling the people in the middle what any of it means for them.


That is not a technology problem. It is a structural and human one. And it was always going to be.


A note before we go further.

This article looks at what happens when agentic AI enters organizational structures that weren't designed to receive it — in conditions where even thoughtful leaders are being asked to move faster than careful consideration allows.

That is not a criticism of intent. The competitive pressure is real, the window feels narrow, and the cost of hesitation appears high. But the cost of haste has its own accounting.

What follows is my analysis of the risk to organizations when the pace of deployment outstrips the time available to consider what deployment actually requires. It is offered not as certainty, there is much we don't yet know, but as a caution.

Breaking and broken are not the same condition. One is recoverable. The other compounds.


The Structure Was Never Built for This


Here is the history of our "modern" day corporate structure and understanding it reframes the entire problem.


The modern corporate org chart traces directly to the Roman Army. Their nested hierarchy — eight soldiers, then a centurion, then a cohort, then a legion — was an information routing protocol. It was designed around one fundamental human constraint: a leader can effectively manage between three and eight people. Because that is the bandwidth of human attention, human communication, and human accountability.


That structure entered American business through the railroads in the 1840s, carried by West Point engineers who brought military organizational logic with them. Frederick Taylor then optimized what happened within that hierarchy — breaking work into specialized tasks, managed through measurement and control. Every corporation still runs on this logic today.


Jack Dorsey and Sequoia's Roel of Botha named what this means in their recent essay "From Hierarchy to Intelligence": "Most companies using AI today are giving everyone a copilot, which makes the existing structure work slightly better without changing it.


"A copilot in a Roman hierarchy."


The org chart was designed to solve a specific problem: how do you coordinate thousands of people across vast distances when information moves slowly and human bandwidth is finite? Every feature of it was designed to answer that problem; the reporting lines, the management layers, the span of control, the division of functions.


Agentic AI doesn't just change the answer. It eliminates the problem the structure was built to solve.


Agents don't need information routed through management layers. They don't need a centurion to translate strategy into action. They don't have bandwidth constraints and they don't clock out. They coordinate laterally, execute autonomously, and operate continuously. They move across every function, every level, every boundary the org chart was designed to maintain.


When you deploy agents into a structure built around the logic they make obsolete, you don't improve the structure. You create a fundamental mismatch between the technology and the container it's living inside.


And the container cracks.


Where Ambient Effort™ Concentrates


Ambient Effort™ is being felt at every level of the organization right now. The C-suite is carrying it too — often in ways that don't get named.


This is worth saying clearly, because we live in a moment that is quick to assign blame. The pressure at the top is real, even when it looks different from the pressure being felt below. C-suite leaders are making consequential decisions about technology they don't fully understand yet. These decisions are made at a pace that doesn't allow for the deliberation those decisions deserve, in a competitive environment that punishes hesitation. That is a specific and significant form of Ambient Effort™.


It matters, not because it excuses the decisions that follow but because it explains them. And understanding what drives decisions is the first step toward influencing them.


When leadership pressure goes unacknowledged, it tends to move downward. — as urgency, as mandate, as the expectation that the organization will simply absorb whatever the technology demands. When it gets named and supported, something different becomes possible: leaders who can slow down enough to bring their people with them, rather than simply pulling them along.


In this agentic moment individuals are feeling Ambient Effort™ personally; across every role, every function, every level of seniority. The fear of keeping up. The anxiety about relevance. The question that nobody is asking out loud in most organizations but nearly everyone is carrying privately: am I going to be able to hold my place in a world that is moving this fast?


That fear is not limited to junior employees. It is being felt by experienced professionals, by senior leaders, and by people who have built careers over decades. They all are watching the foundations of their expertise shift beneath them.


The middle is where the two realities meet. The C-suite's competitive urgency presses down. The workforce's anxiety and uncertainty presses up. And the middle leaders, directors, and team leads are the structural load-bearers of both. Without updated governance, without clear decision rights, and without answers to the questions their people are actually asking they carry the load.


That is the full picture of the workplace right now. Everyone is carrying something. The weight is not evenly distributed. And the path forward requires understanding all of it — not to assign fault, but to find where support is needed most.


And the pressure isn't only coming from inside the organization. Clients and customers are watching the same headlines, sitting through the same demos, absorbing the same promise — that agentic AI makes everything faster and cheaper. They are drawing a conclusion that is simple, human, and nearly impossible to argue with: if you have agents doing the work, it shouldn't take as long or cost as much. The organization is being compressed from the outside at exactly the moment it is cracking from the inside.


McKinsey's State of Organizations 2026 report was unambiguous: transformation is no longer episodic. It is a permanent condition. It is no longer business as usual. It is business as change.


The middle of your organization was not built for permanent transformation. Nobody's was. But the middle is where the weight of it lands first, hardest, and longest.


Are you the person in the middle of this — absorbing the urgency from above and the anxiety from below, without clear answers for either direction?


Or are you the leader considering whether to incorporate agents into your organization? Have you considered what the structure you're deploying into needs in order to hold what you're asking it to carry?


The Five Places the Structure Is Already Breaking


1. The Accountability Gap


The org chart was built on a foundational assumption: a human being signs off, a human being is responsible, a human being can be called into a meeting to explain what happened and why.


Agentic AI distributes decision-making in ways that assumption was never designed to handle. When an agent executes a complex workflow, the question of where decisions were made and by whom is often genuinely unclear. The accountability question this creates is not yet resolved by most organizational governance frameworks.


That is not a technology failure. That is a structural failure and it requires structural answers, not just better prompting.


The legal dimension of this gap is only beginning to be understood. In March 2026, the UK's Competition and Markets Authority published guidance making clear that when an AI agent interacts with customers, makes decisions, or executes tasks — the business that deployed the agent bears full legal responsibility for what it does. Not the company that built the model. Not the platform. The organization that pressed deploy.


Most accountability frameworks inside organizations were not built with that in mind. They are about to need to be.


2. The Communication Collapse


Every organization runs on translation.


The C-suite sets direction. Senior leaders interpret it. Middle leaders communicate it. Team leads deliver it. Employees act on it. Each arrow in that chain represents a human being taking information from one level and making it meaningful for the next. That translation function is not bureaucracy. It is the architecture of how organizations actually work. It is why those layers exist.




Two side-by-side diagrams illustrating the communication collapse in organizations adopting agentic AI. The left panel shows the traditional organizational flow — C-Suite sets strategy, senior leaders translate it, middle leaders communicate direction, team leads deliver clarity, and employees receive it. Every arrow represents a deliberate human translation. The right panel shows the agentic AI reality — agents operating simultaneously across all levels, bypassing senior leaders entirely, whose box appears faded with the label "function bypassed." Agents communicate directly to middle leaders, team leads, and employees with no translation layer, no governance, and no human filtering between them.
The translation layer is bypassed. The need for it has never been greater.

Agentic AI doesn't enter that chain. It bypasses it entirely.


Agents operate across every level simultaneously — continuously, autonomously, without asking permission from the management layer. They don't follow the org chart. They don't know it exists. And the communication structure that held everything together wasn't designed for a participant that doesn't use it.


The result is a gap that sits exactly where the translation function used to be. Senior leaders who built careers on translation and interpretation find one of their core functions bypassed. Middle leaders are now accountable for agent outputs they didn't create. Team leads are managing employees who interact directly with agents without updated context for what that means. Employees are working alongside autonomous systems and looking to their managers for meaning and reassurance while those managers are themselves without the guidance they need to provide it.


This is not a communication failure. It is a structural gap. And it will not be closed by better town halls or clearer memos.


It will be closed by intentional leadership. By C-suites that recognize the guidance their middle and senior leaders need is not optional. By organizations that plan the human transition as carefully as they plan the technology deployment. By leaders who understand that you cannot ask people to translate something they haven't been given the language for.


This technology, more than any that has come before it, requires serious thought and thoughtfulness in its implementation.
Even with that, things will break.
Without it, things will be broken.
Those are not the same condition.

3. The Authority Question


This dynamic is worth naming carefully because it is emerging in organizations and has the potential to create real tension. This is the case even if it doesn't surface the same way in every team or every context.


In many organizations right now, the people who are most fluent in agentic AI are not the most senior people in the room. They are often the youngest and the most recently hired. They are the most technically native, the ones for whom continuous technological change is simply how work has always felt.


Middle leaders and team leads may find themselves managing people who understand the tools better than they do. That is a meaningful shift in the traditional relationship between seniority and expertise. The org chart has no existing mechanism for navigating it.


This could show up as friction in decision-making conversations. It may surface in performance dynamics or in the quiet gap between what a manager feels confident directing and what their team is actually capable of doing. It may not be visible at all in some organizations, and acute in others. What matters is that it is acknowledged and that organizations create space to address it thoughtfully rather than waiting for it to become a problem that names itself.


4. The Measurement Problem


Organizations measure what their structures were designed to measure: hours worked, outputs produced, headcount justified, utilization rates tracked.


Agentic AI challenges every one of those metrics simultaneously.


When two people and agents produce the output of twenty, how do you evaluate individual performance? How do you justify headcount in the next budget cycle? How do you measure the contribution of the person who designed the agent workflow versus the person who monitors its outputs versus the person who steps in when something goes wrong?


Middle leaders will be the ones having those conversations — with their teams, with HR, with their own managers — before any organizational consensus exists on how to answer them.


This is not a reason to avoid the technology. It is a reason to update the measurement frameworks before the gap between what you measure and what actually happens becomes too wide to bridge.


5. The Trust Deficit — In Both Directions


Employees don't fully trust the agents yet. They are anxious about what autonomous systems mean for their roles, their relevance, and their futures. That anxiety is legitimate and it is not going away on its own.


Leadership is pushing adoption anyway because the competitive pressure is real and the window to move feels narrow.


Middle leaders are caught directly in that gap. They are being asked to advocate for technology their teams are anxious about, while privately sharing some of that anxiety themselves. They are expected to project confidence they may not fully feel, answer questions they haven't been given answers to, and hold people together through a transition that few completely understand.


This is where trust either gets built or destroyed; not in the C-suite announcement, not in the all-hands presentation, but in the daily conversations between managers and their people.


And here is what I know from working with organizations navigating this: bringing people into the conversation early is not a risk. It is the only way to find where things will break before they break and to fill the cracks rather than create new ones through distrust.


The organizations navigating this well are not the ones that announced the technology and expected adoption. They are the ones that opened the conversation before the deployment, listened to what their people are actually worried about, and used that intelligence to design a transition that holds.


What This Moment Actually Demands of Humans


Here is the argument I want to make clearly — especially for the leaders and professionals carrying the weight of everything described above:


Agentic AI does not reduce the need for human judgment. It increases it.


Think about what the technology actually requires to function well inside an organization:


  • Someone must decide which workflows to automate and which to protect

  • Someone must establish the ethical guardrails that determine what agents are permitted to do

  • Someone must be accountable when an agent drifts from its intended behavior — and agents can drift, quietly, over time, in ways that traditional governance practices were not designed to detect

  • Someone must communicate what is changing and why in ways that build trust rather than erode it; to teams, to clients, to stakeholders

  • Someone must hold the culture together while the structure is being rebuilt around it

  • Someone must know the domain deeply enough to recognize when a technically correct agent output is organizationally wrong

  • Someone must lead the humans who are doing all of the above while also doing their actual jobs


Governance is the word that holds all of this together and it cannot be absent from agentic AI deployments. What governance actually looks like in an agentic organization; who decides what agents are permitted to do, how drift gets detected, how accountability gets assigned when something goes wrong, is the practical question that Article 3 addresses directly. For now, naming the gap is the first step toward filling it.


The agentic moment is not the end of human work. It is a clarification of which human work was always irreplaceable and a demand that organizations invest in that work rather than assume it will happen on its own.


The Generation That Was Ready Before We Asked


There is something that needs to be said here and it belongs in this article. It is both a structural observation and a genuine source of hope.


The organizations now scrambling to incorporate agentic AI are doing so, in many cases, without the people most naturally equipped to help them.


In an earlier series, I wrote about Gen Z and the vanishing on-ramp — how organizations systematically eliminated entry-level roles, replaced junior positions with AI tools and senior hires, and closed the pathways that allowed the next generation to build domain knowledge and organizational fluency.


Those decisions made a certain kind of economic sense at the time. They make almost no sense now.


Because the generation that was shown the door are the digital natives for whom perpetual change is not a disruption but a baseline. They grew up in perpetual beta and adopted new technology by instinct rather than instruction — that generation carries exactly the fluency and orientation that the agentic AI moment requires — a case I made in depth in [Gen Z in the Workplace: Strategic Assets for the AI Era.]


Gen Z didn't need to be taught that technology evolves overnight. They never experienced it any other way. They didn't need to be convinced that old structures might not hold new realities — they arrived in a workforce already straining under that tension.


The organizations that kept their Gen Z talent, that built the on-ramps, that took seriously the instincts and values this generation brought — those organizations have something the pivoting, scrambling, all-hands-on-deck organizations are now trying to find:


People who were already ready for this.


This thread deserves more than a paragraph — and it will get it in Article 3, where we'll look at what readiness actually looks like and who is positioned to lead it.


But I want to plant it here, clearly: the answer to the agentic AI challenge is not less human. It is more human, better positioned, more intentionally supported, and given the authority to do what humans can do.


The opportunity is real. It is not evenly distributed. And the organizations that see it now will have an advantage that no amount of technology spending can replicate.


The Question for Article 3


We have named the structural failure. We have traced where Ambient Effort™ concentrates and why. We have identified the five places the organization is already cracking under the weight of technology that outpaces its structure.


And we have pointed toward something genuinely hopeful — not as consolation, but as a strategic insight:


The humans this moment needs are not a future hire. They are already in your organization, or they can be.


Article 3 asks the question that follows naturally from everything here:


What does readiness actually look like — and how do you build it before the next wave arrives?


Before You Go


If this article landed — if you recognized your organization in the communication collapse diagram, if you felt the weight of what middle leaders are being asked to carry, if you saw your Gen Z colleagues in the generation that was ready before we asked — I want to offer you something.


Not answers. Not a framework. A conversation.


I offer a free 30-minute consultation. A real conversation about where your organization is in this transition and what readiness looks like for you specifically.


[Book your free 30-minute consultation →]

And if you haven't read Article 1, start there:

Article 3 — What Readiness Actually Looks Like — is coming soon.


The Ambient Effort™ Series


Understanding the hidden energy required to remain effective in workplaces shaped by constant transition.



This article draws on research and reporting from McKinsey's State of Organizations 2026, Sequoia Capital's "From Hierarchy to Intelligence," Harvard Business Review, Deloitte's 2026 Global Human Capital Trends, the World Economic Forum, Gartner, and HumanX 2026 (San Francisco, April 6–9). 

 
 
bottom of page