The Quiet Cost Of Escalation Culture In An AI-Accelerated World

InnovationThe Quiet Cost Of Escalation Culture In An AI-Accelerated WorldByRob Versaw, Forbes Councils Member. for Forbes Technology CouncilCOUNCIL POSTExpertise from Forbes Councils members, operated under license. Opinions expressed are those of the author. | Membership (fee-based)Jun 04, 2026, 07:45am EDTRob Versaw, Product Strategy at Dynatrace, bridging innovation and business impact. getty​For two decades, escalation culture has been the default operating system of ambitious tech companies. Push harder. Add headcount. When a problem appears, throw engineers at it until it surrenders. The logic was simple: more inputs, more outputs. That logic is dead. A single engineer with Cursor, Claude Code and a decent CI pipeline now ships what a squad of six shipped in 2021. The leverage is real and compounding monthly. Yet most organizations are responding by doing what they have always done—escalating. More dashboards. More syncs. More approval chains layered on top of tools designed to remove them. The companies that will define the next decade are going lean. Not lean as in cost-cutting, but lean as in the deliberate removal of everything between a capable person and the work. What Escalation Actually CostsEscalation culture rarely announces itself. It arrives through reasonable additions. A weekly steering committee because a launch is important. A second approver because someone shipped a regression last quarter. Each addition is defensible alone. Together, they form a system where the best engineers spend most of their day managing the system rather than producing through it. The cost shows up first in talent. The people most capable of using AI to compress weeks into hours are precisely the people who escalation exhausts. They did not join to attend the alignment meeting about the alignment meeting. When their tools become more capable while their environment becomes more bureaucratic, they leave. I watched a team's roadmap sit for 18 months from implementation at a large tech company while we waited for the CEO to weigh in. I left, and so did many engineers. Atlassian, Canva and Linear were all built in part by people who walked out of larger orgs where the meeting calendar had eaten the calendar. The second cost is slower: The organization stops being able to tell what is working. An escalation-heavy company will happily mistake a flood of AI-generated PRs, decks and Jira tickets for progress, right up until the quarter ends. Functional Silos Vs. Value Stream TeamsThe structural choice underneath all of this is functional organization versus value stream teams. Functional orgs group by craft—a frontend tribe, a design tribe—and coordinate across them through tickets, rituals and escalation. Every meaningful change touches three managers and four backlogs. Value stream teams group by outcome—checkout, onboarding, search relevance—and contain everything needed to ship that outcome end to end. In a pre-AI world, functional silos at least offered economies of specialist scale. In an AI era, that justification collapses. AI compresses the gap between disciplines: Engineers ship passable design, designers ship working prototypes, PMs ship analysis that used to require an analyst. Value stream teams capture this compression. Functional silos waste it on handoffs. Atlassian's product triads—a PM, a designer and an engineering lead owning a product area end to end—are a cleaner version of the same idea: The team that decides is the team that ships. Larry Culp's GE turnaround pushed it at scale, breaking the functional org into smaller P&Ls—both on the digital and manufacturing portions of the business—with speed, ownership and results following. Why Lean Wins The AI EraAI rewards speed of iteration. The teams learning fastest with these tools are not the ones with the most sophisticated AI strategies; they are the ones whose engineers can try something, see the result and try again before lunch. Every layer of escalation adds latency to that loop. A lean team running 10 experiments a week will out-learn an escalation-heavy team running one, regardless of GPU budget. Lean also preserves the cognitive surplus AI leverage requires. The bottleneck shifts from execution to judgment—what to build, what to ignore, what to ship, what to kill. A staff engineer who spends six hours a day in status meetings cannot make the calls AI now demands hourly. The Burnout Pattern Nobody Is NamingEscalation culture in an AI era does not just slow companies down—it breaks the people inside them. The pattern is consistent. A talented engineer adopts Copilot or Claude and discovers they can do in a morning what used to take a week. Instead of being given the freed time as leverage, they are handed five times the workload, three new stakeholders and a request for weekly written updates on it all. The tools made them faster; the culture made them responsible for more. And the org compounds the problem by treating AI as a dumping ground, generating slop faster than anyone can sort it. This is the burnout signature of the moment, and it is a culture problem, not a tools problem. ​You Cannot Hire Lean—Leaders Have To Live It​The most common failure mode is treating lean as a hiring filter or a reorg announcement. It is neither. Lean is what leaders do with their own calendar, their own decisions and their own tolerance for ambiguity. Culture Amp's async-first communication and Canva's small-team product pods worked because the founders modeled the behaviour at the top, not because it was written into a values deck. Lean is observable in what the most senior person does on a Tuesday afternoon. And more than empowering teams, it means taking action over digesting data. A Larry Culp running a software business goes to the gemba—the Cursor session, the stuck code review, the Sentry queue—not the status summary. Marc Onetto brought GE's lean discipline to Amazon and put senior managers on the customer service floor, hearing live calls instead of reading dashboards ​ The DiagnosticLook at your best engineer's last week. How many hours did they spend producing? How many hours did they spend reporting on producing? If the second number is close to the first, you are running an escalation operation with AI tools bolted on. The tools cannot save you. Only the culture can. The era rewards the leaders willing to make the cut. Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify? Editorial StandardsReprints & PermissionsLOADING VIDEO PLAYER...FORBES’ FEATURED Video