The Outcome Solution

In our previous article, The Outcome Problem, we argued that AI transformations fail because they begin with technology instead of focusing on an outcome that the entire organization can see itself in. The "O" in OPERA stands for Outcome — but not outcomes in the traditional project management sense.

An OPERA-grounded Outcome encapsulates the hidden craft, expertise, and judgment embedded within an organization — the hidden alchemy that creates its value. That expertise lives in the heads of a few people who "just get it." An OPERA-grounded Outcome statement makes that alchemy succinct, explicit, and visible.

If you can't name it, AI can't see it. If AI can't see it, it can't amplify it. That's where transformations stall.

The alchemy is in the middle. Can you name it?

This article is about how to write that Outcome statement — one that doesn't just describe what you deliver, but names the transformation you create. The hidden alchemy isn't in the product; once discovered, it directs everyone's attention towards: Who does the customer become? Outcomes are the north star of the OPERA decision-making framework, and when the alchemy is visible, everything changes: teams can see where AI amplifies their work and where human judgment remains essential. OPERA extends from the Outcome through Priorities, Exchanges, Risks, and Analytics — five factors that, when addressed together, turn AI initiatives from projects into organizational movements.

Two Critical Failures From This Invisible Expertise

Failure 1You can't teach what you can't articulate.

If your organization's hidden alchemy stays unnamed, you can't transfer it to new hires, you can't scale it across teams — and you certainly can't teach it to AI. The repeatable action that drives your business stays locked inside the heads of a few people who "just know."

Failure 2Teams can't see how their work creates value.

When people don't understand how their expertise connects to the organization's foundational value, they can't see where AI amplifies what they do and where their judgment is irreplaceable. They become task-completers instead of value-creators.

Why Technical Alignment Isn't Enough

In The Outcome Problem, we argued that technical alignment alone — clear data pipelines, structured processes, measurable KPIs — works for decisions made on patterns in data, but breaks down when AI transformations involve people, competing priorities, and organizational change. Most transformations aren't clean. They require human alignment.

But even human alignment isn't enough if the organization can't articulate its foundational value. I've seen this repeatedly: a leader launches a new initiative with a vision that lives entirely in their head — understood intuitively, never articulated. The organization gets lost. Everyone gets reduced to completing tasks disconnected from the company's hidden alchemy. And without naming that alchemy, there's nothing for AI to amplify.

The McDonald's AI Voice Ordering Failure

In 2021, McDonald's introduced AI voice ordering with IBM and cancelled after 3 years of investment in July 2024 after disastrous failures. The Today show reports viral TikTok videos of customers begging the chatbot to stop as it adds a total of 28 Chicken McNuggets to their order. Another is frustrated while trying to order vanilla ice cream without caramel, only to have the machine add cream, then butter instead.

The second outcome wouldn't have led to a faster deployment — it would have led to a smarter one, where AI handled the orders it could reliably get right, humans handled the rest, and the technology earned trust before it scaled.

When the outcome names the alchemy, AI shifts from replacing people to amplifying their judgment.

Wendy's FreshAI Success

Contrast this with Wendy's, which deployed FreshAI powered by Google Cloud successfully by framing the Outcome differently from the start. CIO Matt Spessard told Fortune: "Everything that we're doing is prioritized through the lens of the customer and the crew. How do we make both of their experiences better, in parallel?"

Notice the difference: Wendy's named two beneficiaries — customer and crew — and framed them as a parallel optimization, not a tradeoff. McDonald's optimized for cost and speed, with the crew as an afterthought.

Wendy's website makes the alchemy explicit: "Think of Wendy's FreshAI as an assistant — not a replacement — to empower Wendy's crew members working the drive-thru. FreshAI allows our crew to focus on what matters most: preparing and serving hot and delicious food customized for our fans and building the relationships that bring them back."

The result? The pilot handled 86% of orders without crew intervention — and those numbers have only increased.

This is what happens when you optimize for impact rather than cost. The question is: how do you construct an Outcome statement that does this? That's what we turn to next.

The Solution: Defining Outcome in Two Dimensions

An outcome — the first step in the OPERAScale™ decision-making methodology — has three elements: a verb, the action; a deliverable, the specific thing produced; and an impact, the observable change for the recipient.

Without all the elements, decisions fragment into competing interpretations. In The Outcome Problem, we explored what happens when people can't see themselves in the outcome and traced it to a legal platform where lawyers resisted a system built for them. The root cause wasn't that they were left out of the statement. It was that the outcome never named the alchemy their work depends on. The following case studies revisit that story and others to show what changes when the hidden alchemy is made explicit.

These are the structural elements of an OPERA-grounded Outcome.

Case Study: When Impact Goes Undefined

The Challenge

While working on a training program to implement an internal legal platform at a Fortune 500 IT services company, the outcome was framed entirely around technology: build a platform powered by Google and AWS. The lawyers were frustrated by yet another platform and didn't care what stack it ran on. The hidden alchemy of their work — the judgment, collaboration, and real-time negotiation that makes legal work valuable — was completely absent from the outcome.

Without impact, the outcome stops at delivery and never names the value created.

The Approach

Rather than leading with the technology, we mapped how a legal document flows through the organization — not the system architecture, but the human craft: who touches it, what expertise they apply, and where their judgment changes the result. That's where the alchemy became visible.

The Outcome Shift

The outcome shifted from a technology statement to one that named the alchemy: create a software platform that empowers lawyers to collaborate in real time. The deliverable stayed the same — a software platform — but the impact now named the hidden alchemy: real-time collaboration, which is what makes their legal work valuable. Once the lawyers could see their expertise reflected in the outcome, resistance dropped — because the system was no longer replacing their judgment; it was amplifying it.

Once impact is made explicit, strategic and team outcomes can now align.

Case Study: When Team Outcomes Go Undefined

The Challenge

While working as a lead data program manager for a top-10 investment management company, the strategic outcome was clearly understood: deliver consistent and accurate data so customers invest with us. The stakes were real — if a pamphlet showed 5% growth on a fund but the website showed 4%, trust would erode completely. But while the strategic alchemy was named, the team-level alchemy was not.

During quarterly planning, teams wrote outcomes that conflicted with each other — duplicating work, creating confusion, and burning hours in circular discussions. The strategic outcome told everyone where they were going. It didn't tell each team what value they uniquely contributed towards getting there.

While the overall strategic objective was understood, it didn't translate into consistency during quarterly planning. There was no clear mapping of each team's hidden alchemy to the larger picture.

In the investment-management case, the strategic direction was clear, but the team-level deliverable and impact were still undefined.

The Approach

Since this was a data organization, we mapped how data flowed through the system — and more importantly, where each team's expertise transformed it:

In this case, the data flow made each team’s transformation visible: ingest, integrate, curate, distribute.

Each stage had teams responsible for a specific piece of the alchemy. Once they could see their place in the flow, they could write outcomes that named their contribution and connected it to the whole.

For example, Team A could now articulate that they ingest data to deliver a clean data table to Team B — the data lake team — to integrate accurate content. The hidden alchemy at each stage became explicit, and the team outcomes stopped competing. The refined strategic and team outcomes are shown below.

Mapping the flow makes each team’s hidden alchemy visible inside the larger system.

The Results

Clarifying the outcome at both the strategic and tactical levels — and having leadership champion it — reduced quarterly review cycles from one week to 2.5 days.

Clearer outcomes translated directly into measurable time returned to the organization.

What Comes Next: Aligning Priorities

The O in OPERA is designed to create an outcome that's human enough to rally around and clear enough to build toward. But now, how do you get everyone aligned around this foundational value? In the next article, we'll discuss Priorities — how organizations allocate limited attention and resources, and why the way you rank what matters determines everything that follows.

About the Author

Laxmi Gandhi

Founder & President

1.5K followers

Versatile senior management consultant with over 20 years of experience leading transformational decision analytics programs across multiple industries, spanning startup, growth, and Fortune 500 companies.