I've spent a lot of time thinking about why enterprise AI transformations fail. I've watched pilots stall, platforms overspend, and leadership decks get replaced faster than the underlying capabilities they were meant to describe. After a decade of watching the pattern, one insight keeps holding up.
Enterprises don't fail at AI. They fail at sequencing.
They do the right things in the wrong order. They deploy Next-Best-Action on un-mastered identity. They scale platforms before they've proven a single product. They chase Performance metrics on foundations that can't carry a single quarterly review. Sequencing errors are the quiet, expensive, career-shortening reason so many well-intentioned AI investments end up buried in the appendix of the next strategy refresh.
What I didn't fully appreciate until recently is that enterprises fail at sequencing on two different planes at once. And each plane needs its own framework.
The two sequencing questions
Any leader who's tried to move enterprise AI beyond pilot has faced two very different questions, often without realizing they were different.
Identity, data foundations, governance, orchestration, workflows — the substrate any AI capability has to run on. Get this order wrong and every AI capability you build inherits the instability.
Example. A Next-Best-Action engine deployed on un-mastered HCP identity produces confidently wrong recommendations. The AI didn't fail. The sequence was broken before it ever ran.
Any given AI use case has to move through stages of maturity — proof-of-concept, pilot, real product, platform, compounding outcomes. Get this order wrong on any individual capability and it stalls at Platform, mistaken for progress, quietly failing to move the business.
Example. A generative AI copilot with 8,000 active users. High engagement. Zero measurable impact on cycle time, quality, or revenue. The tool works. The 5Ps stage was skipped.
These are not the same question. They live on different planes. But almost every enterprise transformation leader I've talked to has been treating them as one problem — and losing to it.
Sequencing operates on two planes: the enterprise's commercial technology stack, and each AI capability's maturity progression. Skip either sequencing question and the whole transformation stalls at Platform.
Two frameworks, each for its own plane
Over the last few years I've been developing two practitioner frameworks — one for each of these sequencing questions. They aren't a merger or a two-in-one system. They're distinct tools for distinct problems. But they complement each other in ways worth naming explicitly, because most transformation leaders will need to use both.
The B·E·A·T Framework is a commercial technology investment sequencing model for enterprises — particularly (though not exclusively) pharmaceutical commercial technology. It maps a leader to one of four investment tiers: Build, Enable, Accelerate, Transform.
Each tier is load-bearing for the next. You cannot skip Enable and hope to Accelerate on solid ground. You cannot Transform without a Build tier that's actually stable. The killer scenario the framework is designed to prevent: a leadership team that skips Enable, deploys an agentic NBA engine on un-mastered HCP identity, then can't figure out why the field force stopped trusting the recommendations. The sequence was structurally broken. The AI was the messenger, not the failure.
The 5Ps of Outcomes-Driven AI Transformation is a maturity progression model for any single AI capability. Five stages: POC, Pilot, Product, Platform, Performance.
The 5Ps extends the New 4Ps of AI Product Transformation I published on LinkedIn in June 2026. That original piece named the ladder any AI capability climbs from experiment to production. The 5Ps adds the fifth stage — the one every 2026 strategy paper kept pointing at but none of them named: Performance. The state where AI stops being a project and becomes part of how the enterprise actually creates value. The state where the flywheel starts.
How they complement
Because these two frameworks live on different planes, they can be used separately without confusion. A pharma commercial technology lead thinking about their next CRM investment probably reaches for B·E·A·T and never needs to touch the 5Ps for that decision. A product leader stewarding a specific AI-powered adherence agent probably reaches for the 5Ps and never needs to touch B·E·A·T for that particular capability.
But most enterprise transformation leaders live at the intersection. And at the intersection, the frameworks do something more useful than they can do alone: they explain why the same organization can be brilliant at one plane and failing at the other. Which is exactly the state most enterprises are in.
Where they depend on each other
Here's the piece that took me longest to see clearly: you can start the 5Ps on shaky B·E·A·T foundations, but you can never finish it there.
A POC will run on anything. Pilots too. That's why every enterprise you know has POCs and pilots in flight regardless of whether their B·E·A·T foundations are solid. The activity looks real, and for a while, it is real.
Product mindset — the third stage of the 5Ps — requires reliability. Reliability requires Enable-tier maturity in your B·E·A·T stack: mastered identity, functioning governance, orchestrated workflows. Without those, Product-stage AI produces confidently wrong outputs, and adoption collapses just as leadership finally notices.
Platform mindset requires reusability. Reusability requires that Accelerate-tier B·E·A·T work has produced shared services worth reusing. Without those, "Platform" becomes a costume: it looks like a platform in the org chart, but every new capability rebuilds identity, data, and governance from scratch. That's not a platform. That's a shared team maintaining a growing pile of one-off systems.
And Performance — the fifth P, the flywheel state where AI compounds — is impossible without both. You cannot compound outcomes on top of unmastered identity, ungoverned decisions, or one-off platforms. The flywheel needs the substrate to turn.
Most enterprises stuck at what looks like Platform are stuck for the same reason. They aren't stuck because they skipped a step in the 5Ps. They're stuck because they skipped a tier in B·E·A·T two years earlier and the debt has finally caught up. This is the Q3 Build First posture in disguise — enterprises that ran 5Ps stages while foundations were unstable, and are now discovering that Product-stage AI on Q3-level foundations produces the same confidently wrong outputs the framework was designed to prevent.
Where are you on both planes?
A three-slider version of the full Decision Tool. See your B·E·A·T posture and your 5Ps AI Transformation Readiness at the same time. Adjust the sliders to see how each dimension changes both scores.
Using them together
The most useful thing about naming both frameworks explicitly is that it changes the diagnostic question a leader can ask about their own transformation. Instead of "Are we behind?" — which almost always produces the answer "Yes, so let's spend more" — the question becomes:
"Which sequencing question have we been ignoring?"
Enterprises brilliant at B·E·A·T sequencing but sloppy about the 5Ps end up with beautifully architected stacks producing an endless supply of impressive pilots that never scale. Their commercial technology investment is disciplined; their AI capability progression is not. They mistake stack readiness for outcomes.
Enterprises brilliant at the 5Ps but sloppy about B·E·A·T end up with beautifully-productized AI capabilities that hit a ceiling nobody can explain. Their AI teams run Product- and Platform-stage work with real discipline, but the stack underneath is compensating for missing Enable-tier maturity in ways nobody wants to say out loud. They mistake capability velocity for outcomes.
Enterprises brilliant at both, sequenced together, are the ones that actually reach Performance. They are also — not coincidentally — a much smaller number than the industry press releases suggest.
B·E·A·T sequences the enterprise. The 5Ps sequences the capability. Skip either and the whole transformation stalls at Platform.
The Sequencing Series is a multi-volume practitioner project mapping the sequencing thesis onto enterprise AI transformation — how organizations actually move from experiments to compounding, measurable business outcomes.
The macro-thesis. Introduces both sequencing frameworks and the interlock between them.
How foundation maturity predicts your 5Ps ceiling. Walks each of the four investment quadrants (Build Deep, Parallel B+E, Build First, Triage & Compress) and which 5Ps stages are safe to pursue in each.
Operating-model implications: how organizations that run both frameworks in parallel design their teams, funding, and governance differently from organizations that use only one.
Each volume is standalone and interlinked. The full series builds the case for sequencing as the central discipline of enterprise AI transformation.
Where I go from here
If you're working through either sequencing question — or, more likely, both at once — I'd love to hear where the frameworks fit your reality and where they don't. This is practitioner work. It gets sharper the more practitioners push on it.