When someone says, “we should use AI,” how do you unpack what’s really being asked?

Great question.

When someone says “we should use AI,” the conversation is rarely about technology itself.
It is usually about pressure for speed, efficiency, innovation, or competitive leverage. The first step is to clarify intent.

Three signals help distinguish what is really being asked.

First, decision proximity.
Is AI automating a task, augmenting human judgment, or moving toward managing objectives autonomously?
These are fundamentally different categories of work.
The closer AI gets to consequential decisions, the stronger the need for governance, traceability, and explicit oversight.

Second, problem clarity.
Is there a clearly defined business problem with measurable impact, or is AI being treated as the starting point?
When the solution precedes the problem, misalignment and inflated expectations follow.

Third, accountability design.
Who owns the outcome if an AI-driven recommendation fails?
When responsibility becomes diffuse, risk scales faster than performance.

In many organizations, “AI” simultaneously means efficiency, experimentation, and cost reduction to different stakeholders.
Misalignment becomes visible when decision flows and ownership are unclear.
A common tipping point is when stakeholders use the same word “AI” but describe different success metrics.

The real shift is not from manual to automated.
It is from “man in the loop” to “man in control.” Without deliberate design of responsibility, capability increases while accountability erodes.

Clarity of purpose, category of AI work, and ownership separates disciplined transformation from technological noise.

When someone says, “We should use AI,” they’re not giving you a requirement; they’re giving you a signal. From a PMI perspective, your role is to translate that into value by first asking what problem we’re actually trying to solve.. If the outcome isn’t clear, the solution shouldn’t be either. From there, identify the real need (automation, augmentation, insights, or user interaction), validate whether the necessary data actually exists and is usable, and define success in measurable terms. Only after assessing feasibility, technical, organizational, and governance constraints, should scope be defined. And in some cases, the right answer is not to use AI at all.