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

When someone says “we should use AI,” my first reaction as a construction PM is simple:
Where exactly do you see it helping on our project?

On site, everything comes down to time, cost, and quality. If AI can clearly improve one of those — great, let’s define where and how. If not, it risks becoming just another layer without real impact.

Curious how others in construction are approaching this—where have you actually seen it work?

Absolutely. “We should use AI” is a directional impulse, not a requirement. It’s no different from someone saying “We need automation” or “We need a dashboard.” It signals ambition, not clarity.
The real work begins when we translate that impulse into something operationally meaningful:

• What outcome are we trying to improve—speed, accuracy, cost, experience, or decision‑making
• What process is actually breaking or underperforming
• What data exists, what condition it’s in, and whether it can support the ambition
• What constraints—technical, organizational, ethical, or governance—shape the solution space

Only after that discovery can we define whether AI is the right tool, one of the tools, or not needed at all.
In practice, the most responsible AI decisions come from teams that are willing to say “AI isn’t the answer here” just as confidently as they say “AI can help.”

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.

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.