Smarter Construction Still Depends on the People Using the Technology

Construction technology is often introduced through a list of capabilities. The team hears what a platform can collect, display, automate, or predict. A more useful conversation begins with the people who must use that capability to make a decision.

In a 2018 Smart Community Podcast interview with Zoe Eather, I talked about the intersection between technology and the built environment. The conversation covered BIM, mobile tools, virtual and augmented reality, blockchain, and connected buildings. The durable point was simpler: technology should support human connection, transparency, trust, and collaboration.

A tool enters an existing relationship

A new system does not arrive in an empty project. It enters a network of owners, designers, contractors, trade partners, operators, and end users. Those people already have responsibilities, habits, and different reasons to share or protect information.

That context changes the adoption question. A tool may be technically capable of moving model data from one platform to another, but the team still has to decide who should see it, what they may do with it, and how an exception is handled. In the 2018 conversation, permissions and security were already part of the information-sharing problem.

If those decisions remain vague, the technology can move confusion faster. If they are clear, the same technology can make a handoff easier to inspect.

Start with the work, not the feature list

The technologies discussed in 2018 belong to that point in time. Some products and adoption expectations have changed. The operating question still holds: what work should become clearer or easier for the people responsible for it?

For BIM, that might mean helping an owner understand a design decision or giving an operator usable equipment information. For a field tool, it might mean reducing the gap between what was observed onsite and what the office can review. For a visualization tool, it might mean helping a community or end user see a proposed space well enough to respond.

Each example has a human action attached. Without that action, adoption becomes a software deployment rather than an improvement in the work.

Adoption is visible in decisions

A pilot should be judged by what changed for the people doing the work. Did the right person receive the information? Could someone challenge a wrong assumption? Did the team know which record governed the next decision? Was the exception easier to resolve?

These questions do not promise that a tool will save money or eliminate rework. They create a practical review point. They also allow the team to decide that a technology is not appropriate for the current use case.

Choose one proposed technology and name the decision it is supposed to improve. Then identify the person making that decision, the information they need, and the permission boundary around it. If those answers are not clear, the next step is not wider adoption. It is a better definition of the work.

Smarter construction is not technology placed around people. It is technology shaped around the way people need to understand, decide, and follow through.

About the source conversation

This article is based on Zoe Eather's 2018 Smart Community Podcast interview with Brittanie Campbell-Turner. Listen to the original Making Construction Smarter conversation.