Embedded Files
July, 2024
The Problem
The Problem
Construction isn’t short on technology. It’s short on outcomes. AI, digital twins, cloud platforms, and new tools promise transformation every year. Yet most are underused, misaligned, or abandoned. When over 70% of projects run over budget or schedule (McKinsey, 2023), the issue isn’t a lack of technology.
Start with Users, Not Tools
Start with Users, Not Tools
Most construction technology fails for one reason. It’s chosen top-down, without understanding how work actually happens on site. Tools are implemented. Workflows are not.
The result:
Low adoption
Workarounds
Duplicate systems
No real impact
If technology doesn’t fit the way teams work, it won’t be used. No matter how advanced it is.
A Practical Approach That Works
A Practical Approach That Works
These methods are not new, but they are rarely applied properly in AEC.
- Design Thinking
Start with the people doing the work.
Understand:
Where time is lost
Where friction exists
What workarounds are already in place
- Jobs to Be Done (JTBD)
Don’t ask: “What features do you want?”
Ask: “What problem are you trying to solve?”
This shifts technology from a feature set to a tool for outcomes.
- Lean Startup
Test before scaling.
Pilot on a real project
Validate quickly
Scale only when it proves value.
- Value Stream Mapping
Map how work actually flows.
Look at:
RFIs
Design reviews
Coordination cycles
Find where delays happen and fix those points first.
- User Workflow Mapping
Technology must fit into daily routines.
If a design manager or site engineer can’t use it naturally within their workflow, adoption will fail.
What This Looks Like in Practice
What This Looks Like in Practice
A common scenario: A team considers implementing a new AI coordination platform.
Typical approach:
Roll out across all projects
Train teams
Hope for adoption
What works instead:
Observe real coordination issues on site
Define the problem: “Coordination delays are caused by X”
Pilot the tool on one project
Map how reviews actually happen
Design the workflow around the user, not the tool
The Result
The Result
Faster feedback loops
Higher adoption
Less rework
Measurable improvement in delivery
What Most Teams Get Wrong
What Most Teams Get Wrong
Choosing tools before defining problems
Scaling too early
Designing for features, not workflows
Ignoring how people actually work
What Actually Works
What Actually Works
Start small
Focus on real problems
Design around users
Scale only when value is proven
The Bottom Line
The Bottom Line
Construction doesn’t need more technology.
It needs:
Better decisions
Better alignment
Better systems
Technology should support delivery, not complicate it. Fix the workflow first, then bring in the tool.
Page updated
Google Sites
Report abuse