InsightsAI Strategy & Transformation
← All insights All tools

Insight

What Aurelia Taught Me About Becoming an Agentic Enterprise

Published 2026-05-16 · Mike Kennedy

Agentic EnterpriseStrategyReal People ImpactData FoundationChange Management & CultureOperating Model & GovernanceSecurity & GuardrailsFuture of WorkAgent Lifecycle (ADLC)Industry FuturesLeadership

Part 9 of 9 — Series Recap

Eighteen months ago, The Aurelia Worlds Company was a fictional composite I built to walk through the agentic maturity journey concretely in this series. The patterns inside the composite are real. They are drawn from the engagements I have led, the rooms I have sat in, and the executive conversations I have had on every continent except Antarctica (give it time).

This article is the closing of the series. It pulls the seven focus areas together, names the meta-lessons that hold across all of them, and offers the things I want every executive starting this journey to internalize before they spend another quarter funding work that is not yet ready to scale.

The Seven Focus Areas, Re-stitched

Let me put the map back on the table:

  1. Strategy — choosing what to build, what to retire, who owns the P&L, and how value is measured (Aurelia's Big 3: Guest Concierge, Yield Optimization, Production Operations)

  2. Operating Model — the org design, pilot discipline, and supervision muscle that lets agent work happen at scale (the COE plus embedded pods inside Studios, Streaming, Parks, Voyages, Skies, Live, and the rest)

  3. Expertise & Culture — the workforce literacy, manager capability, and change-management discipline that brings the people with you (and the Principal Imagineer who came back)

  4. Security & Guardrails — the trust framework, audit, compliance, and design discipline that stands between you and a very bad day (the day the Guest Concierge agent told the wrong guest the wrong thing)

  5. Agent Development Lifecycle — the engineering practice for building, validating, and supporting agents like the production systems they are

  6. Technology Platform — the consolidated architecture that makes the marginal agent cheap instead of expensive

  7. Data Foundation — the substrate that determines whether your agents hallucinate or perform (the 14,000 tribal-knowledge documents that nobody wanted to fund and everybody needed)

Thirty-three capabilities across those seven areas. Each one scoreable on a 1-to-5 maturity scale. Each one a different muscle.

The Five Meta-Lessons

If I had to compress everything I have learned in the last 18 months of this work into five lessons, this would be the list.

Lesson 1: The seven areas are interdependent

You cannot fix Strategy without touching Operating Model. You cannot fix Operating Model without touching Expertise & Culture. You cannot fix Data Foundation in isolation; it lifts every other area when it improves and drags every other area when it stagnates.

This is the single biggest mistake I see in early-stage programs: treating the seven areas as independent workstreams that can each be optimized in their own lane. They cannot. The areas reinforce each other or they undermine each other. There is no neutral state.

The implication for executives: stop asking "which focus area should we work on first?" The right question is "what is the lowest-maturity area we can lift in the next six months that will unlock progress in two or three of the others?" That question has different answers for different companies, but it is always the right question to ask.

Lesson 2: Maturity is a portfolio, not a project

The instinct in most enterprises is to treat agentic transformation like a program with a beginning, middle, and end. It is not. It is a portfolio of capabilities that the enterprise will continue to develop indefinitely, the same way it continues to develop financial reporting, talent management, or supply chain capabilities.

Average maturity is the right unit. A company at 3.4 average maturity is in a meaningfully different place than a company at 1.7 average maturity, even if both companies have impressive demos. The portfolio view also forces honesty: you cannot hide a 1.2 in Data Foundation behind a 4.1 in Strategy. The average tells the truth.

This means staffing, budgeting, and governance should look like portfolio management, not project management. Quarterly capability reviews. Standing investment committees. Long-range capability roadmaps. The companies that get this right look more like the companies that built durable IT capabilities in the 2010s than like the companies that ran one-off ERP implementations in the 2000s.

Lesson 3: Some focus areas are systematically over- or under-claimed

In every assessment I have done, the same pattern repeats:

If you read those four sentences and recognize your company in two or three of them, you are not alone. You are typical.

Lesson 4: RPI is the only metric that survives contact with reality

Real People Impact — the test of whether the work made things better for the humans on the other end — is the only metric I have found that survives the full lifecycle of an agentic transformation.

Other metrics break under load:

RPI is harder to game because it is grounded in human outcomes. Did the senior concierge get to spend her time making magic for guests instead of looking up reservation details? Did the post-production coordinator move into the creative producing role he had wanted for years? Did the gate agent at Aurelia Skies get the rebooking advice that let her resolve a delay without calling six other departments? Did the Imagineer who thought he had no place in the new world come back and design something he could not have built before?

If your maturity is climbing but your RPI is flat, you are maturing the wrong things.

Lesson 5: The journey is multi-year, and that is OK

The most damaging expectation set inside enterprises right now is that agentic transformation can be compressed into a 12-month sprint. It cannot. The capabilities that matter — the platform consolidation, the data foundation work, the cultural change, the supervision discipline — take 18 to 36 months to build, even with strong executive air cover and adequate funding.

This is not a problem. It is a feature. The companies that try to compress the timeline do shallow work and pay for it later. The companies that commit to the longer timeline build durable capabilities that compound over years.

The right unit of accountability is not "results in 12 months." It is "the right capability investment in 12 months that compounds over the next 5 years." Boards that understand this distinction will get an agentic enterprise. Boards that do not will get a series of impressive demos followed by an inflection point of disappointment.

What to Do With All of This

If you have read all nine articles in this series, and a few of the patterns have made you uncomfortable about your own program, here is the work I would actually do in the next 90 days.

Days 1–30: Run an honest maturity assessment across all seven focus areas. Use the framework or another one — the framework matters less than the honesty. Score on a 1-to-5 scale. Get cross-functional input. Resist the urge to soften the scores.

Days 31–60: Pick the one or two focus areas where your maturity is lowest and where lifting them would most unblock the others. For most companies, this is some combination of Data Foundation and Operating Model. For some companies, it is Expertise & Culture. The diagnostic will tell you.

Days 61–90: Make the executive case for a multi-year investment in those areas. Be honest about the timeline. Be honest about the cost. Be specific about the RPI you expect. Get the air cover before you start, because retrofitting executive support after the fact is the hardest job in this work.

That is it. That is the playbook. It is not glamorous. It is not fast. It is also the path that the companies who are getting this right are actually walking.

A Last Word

The agentic enterprise is not a product you buy. It is not a transformation you complete. It is a way of running the company that, over time, makes more of the work better — for guests, for cast members, for partners, and for the long-term competitiveness of the enterprise.

In an industry like Aurelia's — where every guest interaction is the show, every cast member is the performance, and every minute of operational reality is in front of an audience — the stakes for getting this right are higher than in most industries. The good news is that the stakes for getting it right are also higher in your favor: when an agentic enterprise works in entertainment and hospitality, the impact is visible, immediate, and remembered. Guests remember the trip where everything went right. Cast members remember the night when the show came together. Audiences remember the season where the streaming service knew exactly what they wanted to watch next, and brought them to the parks because of it.

The companies that figure this out in the next 18 months will pull ahead in ways that will be very hard to catch up on. Not because their technology is better. Because their capabilities are deeper, their culture is more aligned, their data is cleaner, and their people are more engaged.

If you want to be one of those companies, the work starts with an honest assessment, a multi-year commitment, and the willingness to invest in the unglamorous areas — Data Foundation, Culture, Supervision — that most of your competitors are still trying to skip.

I will keep writing about this work as the field continues to mature. The framework will evolve. The lessons will sharpen. The Aurelia story will keep growing because the engagements that informed it keep growing.

If something in this series has resonated with you, or has made you angry, or has named a problem you have been struggling to articulate to your own executive team — I'd genuinely like to hear about it. The collective field is still young enough that we are all writing the playbook together. There is plenty of room for more voices.

Thanks for reading.


This is the final article in a 9-part series on agentic enterprise maturity. The previous articles covered Strategy, Operating Model, Expertise & Culture, Security & Guardrails, Agent Development Lifecycle, Technology Platform, and Data Foundation. The full series is available on my profile.