Thought Leaders
The Hardest Part of Enterprise AI is Prioritization, Not Innovation

Most organizations have plenty of AI ideas. But how can they successfully turn those ideas into implementations that are truly impacting ROI?
For business and technology leaders, this question sounds simple but is surprisingly difficult: there is a lot that goes into identifying, evaluating, and prioritizing the AI opportunities that will actually create value.
Although technology is ready and creativity is present, most AI initiatives tend to fail before they ever reach implementation. The gap between experimentation and execution is clear: S&P Global found that organizations abandoned an average of 46% of their AI proof-of-concept projects before they reached production. This is a result of organizations evaluating AI ideas before they’ve fully defined the problem they’re trying to solve.
Many organizations are now past their experimentation phase, where they try to figure out which AI bets to make and in what order. Yet adoption does not necessarily translate into business impact: McKinsey’s 2026 State of AI survey found that while 44% of organizations now report scaling AI across the enterprise, only 37% report any measurable impact on operating earnings from AI. What these organizations need is a repeatable decision system that separates quick wins, strategic opportunities, prerequisites, and non-AI problems before resources are committed.
The Problem Starts With How Ideas Arrive
Across leadership teams, AI ideas don’t come in as neat, discrete opportunities. They often come in as bundles—rich, messy, ambitious statements like, “AI is needed to help with communications, reporting, meetings, knowledge transfer, performance management, and maybe even have AI agents running our projects.”
That’s a problem that doesn’t require one idea. It requires at least six, with each fundamentally different in scope, complexity, governance requirements, and expected value.
Hidden inside a single statement like “we need AI for reporting” could be:
- A repetitive task that can be automated in weeks
- A process that needs redesigning before AI can help
- A genuinely new capability AI makes possible for the first time
- A data or systems problem that AI alone cannot fix
Treating all of these the same way with the same evaluation criteria, timeline, and ROI method leads to poor prioritization and wasted effort. The quick wins get buried under governance designed for major initiatives. The revolutionary ideas never get the sponsorship they need. And the ones that aren’t AI problems at all consume capacity that should go elsewhere.
A Framework for Prioritizing AI Opportunities
What organizations need is a standardized set of principles that help them identify what opportunities are the right fits for AI solutions. I propose the following:
- Decompose before you prioritize. The quality of AI decisions depends entirely on the quality of the ideas entering the process. Breaking broad requests into discrete opportunities, each with a defined outcome, a single owner, and a realistic scope, is the most important step. When broad ideas are evaluated this way, a handful of initial statements can become several distinct, scoreable opportunities. Several may be piloted immediately. Others may need prerequisites resolved first. Some may not be AI problems at all.
- Type determines governance. Score determines sequence. The type of AI implementation that’s needed to address a business challenge, and its score (or potential to create value) are two completely different questions that most prioritization processes conflate. What kind of opportunity is the idea? Is it task automation, process redesign, a net-new AI capability, or something else? The answer determines how it should be managed: the approval process, the timeline, and how to measure value. How it compares to others determines when it should be pursued. A quick automation and a tactical AI capability may both be valuable. They should never follow the same governance path.
- Define the problem before choosing the technology. One of the easiest traps with AI is moving too quickly to questions about models, platforms, or vendors. A better starting point is understanding the problem itself: who is experiencing it, what is causing friction, and what outcome needs to improve? That distinction matters because organizations can have confidence in their AI strategy while still lacking the underlying capabilities to execute it: a 2026 UST survey found that 44% of enterprise leaders identified data quality as a barrier to AI adoption. If the technology discussion begins before there is agreement on those fundamentals, it is usually too early. Keeping early conversations focused on the problem can make the eventual technology decisions much clearer.
- Surface blockers as explicitly as opportunities. A high score isn’t sufficient on its own. An idea with strong impact and leadership backing, but a hard feasibility blocker, such as missing data, an unresolved system dependency, or a compliance constraint, should be visible in the roadmap but not actioned until the blocker is cleared. Governance and compliance are already among the most significant obstacles to scaling AI: Moody’s 2025 survey found that 33% of respondents cited regulatory uncertainty or compliance risk as a challenge to adopting AI at scale, while 30% cited difficulty integrating AI with legacy systems. For example, an opportunity may score highly on every dimension except feasibility because it depends on another team resolving a data gap. That item can remain clearly flagged on the roadmap and ready to advance once the dependency is resolved.
- Keep the roadmap adaptable. Technology capabilities evolve, business priorities shift, and dependencies change over time. A strong portfolio should make it easy to reassess individual opportunities as conditions change, without requiring the entire plan to be rebuilt. Annual planning cycles are often too rigid for an area moving this quickly.
Putting It Into Practice
Notably, AI itself can help operationalize this framework. Organizations can use tools such as purpose-built AI skills and lightweight roadmap management applications to guide leaders through opportunity intake, decomposition, classification, scoring, and prioritization. Rather than relying entirely on workshops and manual facilitation, AI can review unstructured ideas, identify distinct opportunities, surface clarifying questions, challenge assumptions, and generate structured opportunity assessments for review.
Those assessments can then flow into a centralized roadmap where opportunities, dependencies, blockers, and priorities are managed consistently across the organization. Leaders gain visibility into what opportunities exist, which ones are ready to move forward, and which require prerequisites or additional evaluation. That changes the conversation from “what are our ideas?” to “what should we tackle first?”
This can lead to much more productive prioritization sessions. Leaders come in having already worked through the core questions, so the discussion can focus on aligning priorities and making decisions rather than starting from scratch.
Instead of managing AI ideas through disconnected spreadsheets and meetings, organizations can create a repeatable decision system that continuously evaluates and prioritizes opportunities as business needs and technology capabilities evolve.
What This Means for Enterprise AI
The organizations that will create sustained value from AI aren’t necessarily the ones with the most high-level models or the largest budgets. They’re the ones who build the organizational capability to rigorously evaluate AI opportunities before committing resources. The challenge is increasingly one of disciplined investment: Deloitte’s 2025 AI ROI research found that most organizations reported achieving satisfactory ROI on a typical AI use case within two to four years, compared with an expected seven- to 12-month payback period for technology investments.
That means helping business leaders break broad ideas into clearly defined opportunities before moving forward, while giving technical teams room to test assumptions and identify potential challenges early. It also means maintaining a roadmap that accounts for blockers, dependencies, and opportunities that may make more sense later.
Ultimately, creating value from enterprise AI depends on more than the models or agents an organization adopts. It depends on making thoughtful decisions about where, when, and why to use them.












