What Happens When Nobody in the Room Can Evaluate the AI Proposal

Three scenarios play out in organisations that lack a structured way to evaluate AI proposals. All three are expensive. None of them are visible in the quarterly report until it's too late.

Scenario one: enthusiasm wins

A senior leader sees a demo. It's impressive. The vendor is credible. The use case sounds relevant. There's energy in the room. Someone says "let's pilot this" and nobody objects because nobody has a structured reason to object. They have instincts and reservations, but instincts don't survive a room full of enthusiasm.

The pilot launches. Three months later, it has consumed budget, IT resources, and the attention of a project manager. The results are inconclusive because the success criteria were never defined clearly. The tool works in isolation but doesn't integrate with the existing systems the way the vendor suggested it would. The team that was supposed to adopt it has quietly gone back to the old process because nobody invested in change management.

The pilot doesn't get cancelled. It gets extended, because cancelling would mean admitting the decision was premature. So it continues to consume resources without producing outcomes, and the organisation adds it to the growing list of "AI initiatives in progress" that appear in the board deck.

Scenario two: the loudest voice decides

AI proposals arrive from multiple directions. A vendor pitches contract review automation to legal. The operations team wants to pilot demand forecasting. Finance is exploring automated reconciliation. HR suggests an AI-powered onboarding tool.

Each proposal has merit. None of them have been evaluated against a common framework. So the decision about which one to pursue comes down to who makes the strongest case in the steering committee. Not the strongest analytical case. The strongest political case. The leader with the most influence, the best relationship with the CTO, or the most compelling narrative gets their project approved.

The chosen project may or may not be the right one. Nobody knows, because there was no structured way to compare the proposals. The ones that were rejected don't get documented evaluations explaining why. They get vague responses like "the timing isn't right" or "we need to focus." The leaders whose proposals were rejected don't understand the decision criteria because there were no decision criteria. They walk away frustrated, and the next time an AI opportunity arises in their function, they are less likely to bring it forward.

Scenario three: nothing happens

This is the most common scenario, and the most difficult to detect. Proposals arrive. Nobody says no. Nobody says yes. The proposals enter a holding pattern of "further discussion needed" that never resolves into a decision.

This happens when the people responsible for AI decisions know they don't have the expertise to evaluate them confidently, but also know that making a bad decision is worse than making no decision. So they delay. They ask for more information. They commission a review. They form a working group. Each of these actions feels productive but produces no outcome.

The cost is invisible but real. It is the cost of opportunities not taken. While the organisation deliberates, the process that could have been improved continues to run at its current level of efficiency. The team that could have been freed up for higher-value work continues to spend their time on manual tasks. The competitive advantage that could have been gained goes to the competitor who decided faster.

Delay is a decision. It is just not a documented or deliberate one.

The common thread

All three scenarios share the same root cause. The people in the room do not have a structured methodology for evaluating AI proposals. They have opinions. They have experience. They have instincts. But they do not have a repeatable framework that produces a documented, defensible verdict.

This is not a knowledge gap. These are experienced managers who evaluate complex proposals every day. They evaluate vendor contracts, capital expenditure requests, hiring plans, and market entry strategies using well-established frameworks. The reason they struggle with AI proposals is not that AI is uniquely complex. It is that nobody has given them the equivalent framework for AI decisions.

Budget approvals have a process. Hiring has a process. Procurement has a process. AI decisions, in most organisations, have enthusiasm and a steering committee. That asymmetry is where the risk lives.

What changes when a framework exists

When managers have a structured evaluation methodology, the conversation changes in specific ways.

The vendor meeting becomes diagnostic rather than persuasive. Instead of listening to the pitch and forming an impression, the manager walks in with seven dimensions to evaluate. The vendor's answers either satisfy those dimensions or they don't. The evaluation is documented, not felt.

Competing proposals become comparable. When every AI proposal is evaluated against the same seven dimensions, the steering committee can compare them on equal terms. The decision about which one to pursue becomes analytical rather than political. The proposals that are rejected get documented explanations that the proposing team can act on.

The holding pattern breaks. When a manager has a clear methodology, they can evaluate a proposal in a defined timeframe and produce a clear verdict. The verdict might be "no" or "not yet," but those are outcomes. They are better than indefinite delay, because they free up attention for proposals that are ready.

This is a capability problem, not a policy problem

Some organisations respond to these scenarios by writing AI policies. Governance documents that describe the principles and boundaries for AI use. These documents are valuable. They are also insufficient.

A policy tells people what they should do. It does not teach them how to do it. An AI governance policy that says "all AI proposals must be evaluated for risk, feasibility, and strategic alignment" does not help a manager who doesn't know how to evaluate risk, feasibility, and strategic alignment for AI specifically. The policy creates an obligation without building the capability to fulfil it.

Building that capability requires training that is different from both AI awareness sessions and AI policy workshops. It requires a programme that teaches managers a specific, repeatable methodology they can apply to any AI proposal that arrives. A methodology that produces a documented output they can share with stakeholders. A methodology that works whether the proposal comes from a vendor, an internal team, or leadership itself.

The organisations that invest in this capability early will make better AI decisions. Not because they know more about AI, but because they have a structured way to think about it. That structure is what separates a defensible decision from an expensive guess.