Chris M.Updated
From denial to leadership: the AI conversation worth having this week
The first step is not a strategy, a platform or a budget. It is one honest conversation with someone who has already tried it. Everything else follows from that, and nothing useful happens before it.
If you want a neutral starting point rather than a vendor's, the industry bodies are publishing on this now: CIOB and RICS both cover technology adoption and the professional obligations that come with it, and neither is trying to sell you a licence.
The built environment is in an unusually good position here. Firms that engage are already taking hours out of their admin, winning contracts and reducing waste, and the encouraging part is how ordinary the winning moves are: no moonshots, just admin handed to machines and people freed for the work that needs judgement. The opportunity is open to any leader willing to start the conversation, and the edge compounds for whoever starts it first.
Why do capable leaders avoid this?
Not because of a considered judgement. Because of uncertainty, and uncertainty has a specific shape here.
AI arrives wrapped in jargon, sold by people who have never stood on a site, and accompanied by headlines about job losses. Faced with that combination, avoidance is a reasonable-feeling response rather than a stupid one. It is worth naming that plainly, because leaders rarely admit to avoidance and will instead call it caution.
The distinction that matters: caution produces rules and a controlled trial. Avoidance produces silence, and silence is not neutral, because your people are using these tools anyway, just outside any rules you would have written.
What is AI actually taking?
The tasks, not the jobs, and specifically the tasks nobody wanted.
| What your week contains | Who should do it |
|---|---|
| Trawling specifications for one clause | Automatable |
| Building the weekly report from five sources | Automatable |
| Updating trackers by hand | Automatable |
| Chasing information you know exists somewhere | Automatable |
| Deciding what the delay entitlement is | A person, always |
| Negotiating with a subcontractor | A person, always |
| Judging whether a design is safe | A person, always |
The top half is where AI thrives, and it is exactly the work your best people resent. Delegate it and your professionals get their time back for the bottom half, which is what they were hired for. For most of them that is the best thing to happen to their working week in years, not a threat, and the person most relieved is usually the one currently drowning in admin.
What does leadership actually look like here?
Curiosity, not technical fluency. Nobody expects a construction director to become a technologist.
The leadership move is smaller and more human: be the person in the room willing to ask four questions.
- Where do we lose the most hours to admin?
- What would we do with those hours back?
- Who do we know who has already tried this?
- What would a small, safe first step look like?
The fourth question is the one that converts a conversation into a result, and it has a known good answer: one workflow, six weeks, a measured baseline and a named owner.
Where does the first conversation come from?
Your existing network. A colleague, a consultant, a curious friend already doing it.
Ask what tools they adopted. Ask which workflows genuinely improved. Ask what they tried that did not work, because that answer is worth more than the other two and nobody volunteers it. Just discussing AI's role in a business like yours strips away the mystique that makes it feel unapproachable.
When it is demystified, application stops being frightening and becomes obvious. The firms pulling ahead did not begin with a grand strategy. They began with one conversation, one workflow and one proof that it worked, and built from there.
Before dismissing it, have the conversation. One honest discussion turns uncertainty into clarity, and sparks the kind of change your competitors will eventually be forced to copy.