Where Strategic Constraint Held, and Where It Didn’t
The companies that successfully scaled AI without a public rollback share one structural trait: they built the governance framework before deployment, not after their first incident.
The Agent Scope Map from week 2 of the “Exercise Strategic Constraint” series makes a specific case: governance architecture should precede agent deployment, not follow the first incident that makes its absence obvious. The four examples that follow, JPMorgan Chase, Maersk, ServiceNow, and Atlassian, bear that out.
THE PATTERN
The successful deployments share a structure
JPMorgan Chase, Maersk, and ServiceNow look like an unlikely comparison: a global bank, a shipping company, and an enterprise software firm. Each operates under completely different business pressures and deployment models.
Yet their structural similarity is worth noting. Every successful deployment relied on a clear foundation that included:
Named KPIs and written mandates
Defined kill switches to halt out-of-scope agent actions
Clear accountability assigned to specific individuals before agents went live
In every successful case, the governance framework preceded the deployment. This sequencing is what separates them from companies that scaled first and were forced to explain their reversals later.
Atlassian sits in a different category. The company made a structural bet on AI’s future performance rather than its demonstrated results. That distinction is where strategic constraint either holds or falls apart.
JPMORGAN CHASE
Governance at scale: 450 use cases, one operating principle
JPMorgan Chase is the playbook for enterprise AI done right. The bank runs more than 450 AI use cases in production, 200,000 employees utilize its proprietary “LLM Suite” daily, and the firm publicly tracks annual AI-driven business value at $1.5 to $2 billion, growing at a clip of 30 to 40 percent year-over-year.
The scale is impressive, but the discipline behind it is the more instructive story.
JPMorgan didn’t arrive at 450 use cases by approving every pilot project and seeing what survived. Instead, they treated every single deployment as a governed, independent bet. Before external AI tools were ever permitted near their ecosystems, leadership built internal capability first, a deliberate sequencing decision that prioritized governance architecture over deployment pressure.
Chief Analytics Officer Derek Waldron described it to McKinsey as managing the distance between what the technology can do and what the enterprise can actually capture.
JPMorgan closes that distance administratively. Every use case requires three things before it goes live:
A named owner accountable for its output
A measurable outcome tied directly to its output
A defined mechanism to halt the agent if it deviates
At JPMorgan, governance is not a technology decision. It is an operating system decision made before any agent goes live.
MAERSK
Two use cases, three years of groundwork
Maersk’s AI story is less about what the company deployed and more about what it chose not to. While competitors rushed to announce company-wide AI transformation initiatives, Maersk spent three years, from 2021 through 2024, doing the unglamorous work: cleaning foundational data and building the infrastructure required to support commercial-scale AI.
When they finally deployed, they launched two domains: vessel route optimization and predictive maintenance across their global fleet. Both domains share three traits that make them well-suited for agents:
Errors are recoverable. A suboptimal route or missed maintenance signal creates cost, not an irreversible relationship or brand damage.
Success depends on data that agents can access. Weather patterns, fuel consumption rates, sensor readings, and voyage history are all machine-readable inputs; No relationship context is required.
Outcomes are measurable against an objective standard. Fuel consumption percentages and vessel downtime are among the most trackable metrics in industrial operations.
The BCG AI Radar 2025 finding maps directly to Maersk’s approach: leading AI companies concentrate on an average of 3.5 use cases while laggards spread themselves thin across 6.1, cutting their ROI in half. Maersk ran a shorter list. The results followed.
SERVICENOW
The kill switch as a design feature, not a contingency plan
Most organizations treat the ability to stop an AI deployment as something to figure out after an agent causes an unexpected outcome. ServiceNow built it into the product before anything went wrong, then turned that capability into a market position.
In a 2026 Fortune interview, CEO Bill McDermott described the company’s approach as an AI Control Tower: the ability to pause, redirect, or stop any agent anywhere in the enterprise in a single action.
This framing matters:
A kill switch positioned as a contingency is a panicked reaction.
A kill switch as a design feature is an architectural decision made before the first agent goes live.
By productizing the kill switch, ServiceNow gave its enterprise clients the psychological safety required to scale. Enterprise AI scales when organizations can control it, and ServiceNow made control the product.
Three governance elements define readiness for enterprise AI at scale: a defined kill switch, a human review point before live accounts, and a documented incident response process. For ServiceNow, these are not abstract ideals. They are product features the company sells. That alignment between internal governance practice and external product strategy is what makes ServiceNow the clearest operational model in this set.
ATLASSIAN
When a forecast becomes the mandate
On March 11, 2026, Atlassian announced the elimination of 1,600 roles, representing 10 percent of its global workforce. More than 900 of those cuts came directly from software research and development, to “self-fund further investment in AI and enterprise sales.”
CEO Mike Cannon-Brookes directly acknowledged the implications: “It would be disingenuous to pretend AI doesn’t change the mix of skills we need or the number of roles required in certain areas.”
The critical context here is that Atlassian was not cutting from a position of financial distress. Heading into the announcement, the company posted 26 percent cloud revenue growth. These cuts were a strategic bet, not a bid for survival.
Atlassian’s move represents a fundamentally different approach to AI than the guardrails built by JPMorgan Chase or ServiceNow. Instead of waiting for AI agents to prove their operational value before restructuring, Atlassian restructured first; the decision came before the evidence.
This is the case most likely to be misread as disciplined. Cutting headcount in the name of AI efficiency can appear like a focused, constraint-driven decision. But strategic constraint requires evidence before action. Atlassian made those cuts before that evidence existed.
Investors read the announcement favorably. The stock rose roughly 2 percent on the news. Whether the underlying bet proves right remains to be seen. Atlassian’s “forecast first, prove later” decision structure stands as the clearest test case for a new leadership thesis: can organizations successfully front-run AI disruption by restructuring before the results arrive?
THE SYNTHESIS
The sequencing spectrum
A clear spectrum of strategic constraint emerges across these four cases:
The Disciplined (JPMorgan & Maersk): prioritized risk mitigation. They built rigorous governance and refused to scale or expand until their internal data and infrastructure were ready.
The Enablers (ServiceNow): prioritized control. They built the “AI Control Tower” first, giving themselves and their clients the psychological safety to deploy at scale.
The Bettors (Atlassian): Accelerated past traditional guardrails, trading immediate organizational stability for a head start in an AI-first economy.
Avoiding a public walk-back requires governance discipline. Leaders must ensure their governance architecture matches their appetite for speed. The Agent Scope Map—the three-gate framework for AI agent deployment decisions —does just that.
This series, in four parts:
Part 1 — The Leadership Brief: The mandate that was never written (published)
Part 2 — The Framework: The Agent Scope Map (published)
Part 3 — Real-World Examples: Where strategic constraint held, and where it didn’t (this post)
Part 4 — The Debrief: What Nadia decided, and the question she’s still carrying
Sources
JPMorgan Chase & Co. Investor Day Presentation. U.S. Securities and Exchange Commission, 2025. https://www.sec.gov/Archives/edgar/data/0000019617/000001961725000483/investordaypresentation.htm
JPMorgan Chase AI Strategy: $18B Bet Paying Off. AI News, December 16, 2025. https://www.artificialintelligence-news.com/news/jpmorgan-chase-ai-strategy-2025/
BCG. “As AI Investments Surge, CEOs Take the Lead.” BCG AI Radar. January 15, 2025. https://www.prnewswire.com/news-releases/as-ai-investments-surge-ceos-take-the-lead-on-decision-making-and-upskilling-themselves-302661849.html
Maersk 2025 AI Strategy. Industry analyst reports, 2025–2026. [Secondary reference]
ServiceNow Q1 2026 Earnings. Fortune, April 23, 2026. https://fortune.com/2026/04/23/servicenow-earnings-forecast-blistering-growth-ai-product-sales/
ServiceNow at ATxSG 2026: Autonomous AI, Enterprise Workflows and the Future of Productivity. The Fast Mode, May 2026. https://www.thefastmode.com/expert-opinion/48645-servicenow-at-atxsg-2026-autonomous-ai-enterprise-workflows-and-the-future-of-productivity
Atlassian to Cut Roughly 10% Jobs in Pivot to AI. Reuters, March 11, 2026. https://finance.yahoo.com/news/atlassian-lay-off-1-600-212610757.html
Atlassian Follows Block’s Footsteps and Cuts Staff in the Name of AI. TechCrunch, March 12, 2026. https://techcrunch.com/2026/03/12/atlassian-follows-blocks-footsteps-and-cuts-staff-in-the-name-of-ai/
About Kim
Kim Celestre is a strategic advisor and executive coach who helps B2B marketing leaders navigate AI transformation without eroding judgment, trust, or human value. Her work is grounded in AIGP-certified responsible AI expertise, executive coaching, and 25 years of Silicon Valley marketing leadership, including 4 years as a Forrester industry analyst.