Make the Technology Useful to the Work

What problem are you trying to solve when you ask for a digital twin? We can get caught up in what a tool looks like and the possibilities it suggests before we’ve worked through what needs to change. Then the demonstration ends, and someone still has to make it useful in the middle of an ordinary workday.

On The Matthew Byrd Podcast, I talked with Kelly Watt about the path that took him from telecommunications into forensic laser scanning, reality capture services, and consulting at DFW Airport. His work has put him close to both the people capturing information and the people trying to use it. That experience gives us a practical place to start: understand the problem, test the promises, and pay attention to how people actually work.

Test the promise in practice

Kelly’s early scanning work involved people who were willing to ask difficult questions about equipment. What happens in extreme heat or cold? What happens on a large scene or a difficult surface? As he put it, “You really don’t know until you put it through the tests.” Knowing the limits matters when another person is relying on your advice about what the technology can do.

He described learning that lesson on a large documentation project at the Gaylord Palms in Orlando. Capturing the hotel was ambitious, and the workflow didn’t always behave as expected. Repeated geometry and surface patterns became things to understand through experience rather than details to discover after promising a result. The lesson for a team evaluating equipment is to build a test around the conditions it will face, then work through the full deliverable before deciding it’s ready.

I told Kelly that the growing number of capture options can make it difficult for someone entering the industry to know what to choose. A handheld, a backpack, and a tripod system can each look impressive without answering the same question. Useful education needs to explain what was tested, what happened, and what the result can support. Sharing that work gives other people a better starting point than a claim that something is simply good.

Start with the business problem

The next lesson came from Kelly’s shift toward consulting. He found that clients who first wanted visualization soon asked for measurement, modeling, or connections to other systems. Those requests changed the conversation from which product to buy to what the business needed to do. Sitting with the people doing the work became important. A question as simple as why they perform a task a certain way can reveal constraints that never show up in a software demonstration.

At DFW Airport, Kelly worked within a much larger environment of existing systems, processes, and responsibilities. He described ambitious goals alongside legacy infrastructure and work moving more slowly than he initially expected. Breaking that environment into smaller, achievable business problems gave him a way to approach it. The questions also needed to include dependencies: what else must be connected or working for this particular improvement to help?

Bring people into the change

That is where people become part of the implementation. Kelly said change management took significant time, including finding people willing to use a different workflow. “You don’t need everyone on the boat. But you need a couple people on the boat with you.” An early supporter can help you see what the change feels like in practice. Start with someone who understands the problem and is willing to work through a better approach with you.

Connect information around the work

We also spent time separating a visual interface from the information behind it. Kelly’s example was a facilities person trying to find something in records organized by contract or project number. That person may know the building, level, room, or asset, while the contract reference means very little to them. If the information is organized only for the people who created it, the next user has another problem to solve before they can even begin.

Kelly described the value of relationships between information and shared ways of referring to it. I compared that connection to a thread running through the separate systems a business already uses. The aim is to make the relevant information accessible in a context people understand. Pick one question a user needs to answer, then follow the route from their language to the records. That exercise can tell you more about the missing connection than adding another dashboard.

Keep your judgment in the loop

AI can help with some of the effort of organizing and checking information, but it introduces another question about responsibility. Kelly was optimistic about the tools while warning against allowing them to do the thinking for us. We talked about people using experience to question an output instead of accepting it because a system produced it. A workflow becomes more useful when the person responsible knows what needs review and can recognize something that doesn’t make sense.

That brought the conversation back to learning. Kelly encouraged people to spend time around others with knowledge they can learn from, and his own path shows how experience can carry across different roles. We don’t have to understand every internal detail of every tool, but someone still needs to test it and know what a trustworthy result looks like. Begin with the work you want to improve, make one useful change, and keep enough curiosity to question what comes next.

Catch the full conversation on YouTube, Apple Podcasts, or Spotify: Start With the Problem | Digital Twins with Kelly Watt. You’ll also hear about Kelly’s international technology work, the evolution of digital twin terminology, and how he thinks about opportunity in a changing industry.

Watch the full conversation

Previous
Previous

Better Hiring Starts With a Real Conversation

Next
Next

Keep the Knowledge With the Building