A scanner can give us a detailed picture of a space. It can't tell us whether the person receiving that information understands why it matters. That was one of the practical questions in my conversation with Morgan Drivas, VDC and Innovation Manager at JTM Construction. As she's expanding into reality capture, she's also working through how to explain its value to owners and architects.
We talked about much more than scanning, including her MMA background, professional relationships, remote work, and family priorities. Across those subjects, the conversation kept returning to understanding the person behind the role. These five takeaways connect the technical work with the people who need it, the teams delivering it, and the life someone wants that work to support.
Show how the work gets better
A construction team and an owner can look at the same scan and see different things. Morgan described checking whether sleeves were installed where they needed to be. The benefit made sense to the team doing the work, while an owner could see accurate installation as something they already expected. Explaining the technology means finding out what problem the other person actually needs solved.
Morgan put one information gap plainly: “When we get as-builts, they are not actually what is built.” She was describing her team's experience with the documents they receive, and why capturing conditions can matter later. I brought up comparing similar projects and looking at the effort already going into site visits, documentation, and missing information. A new service has a visible price, while an existing process can hide its costs because we're used to them. Start with real project evidence and ask what would show that the work improved.
Let people know the person
Technical credentials tell people something about your experience, but they don't explain everything about working with you. Morgan's MMA background gave people a reason to begin conversations that her job title alone might not have started. As she said, “I think people wanna work with other people that they enjoy working with.” Sharing a little of your story gives someone more to connect with than a list of services.
We talked about personal brand in that context. It doesn't require every post to become a pitch, and it doesn't mean everyone needs an unusual background. You can share an experience that helps someone understand how you think, what you care about, or how you approach a problem. The useful question is what people would know about you if they saw more than your role and your most recent project.
Build trust into remote work
Morgan's remote arrangement includes intentional time with the people in the main office. Talking about those visits, she said, “Most of my time there is building relationships and spending that face-to-face time with everyone.” Those relationships support the work when she returns home. The visits are part of the arrangement, alongside the technical tasks she gets done remotely.
I shared some of the challenges I've had managing remote work, while recognizing that different roles need different arrangements. Access to the software doesn't settle every question about collaboration, accountability, or communication. Before arguing for one location policy, look at the responsibilities of the role and how the team stays connected. What needs to happen in person, and what helps people work dependably when they are apart?
Keep learning as the tools change
Morgan wants to understand more about scanning and registration so she can recognize the problems her field team might encounter. That is a different goal from simply knowing which button to press. We discussed the disappointment that can follow buying equipment and expecting the result to appear on its own. Training, checking the information, and knowing when to ask for help remain part of the work.
Her MMA experience offered another way to think about unfamiliar situations: “I know that I can solve problems, and so that's the skill that I'm gonna depend on.” She couldn't predict everything an opponent would do, but she could prepare to respond. I connected that with curiosity about how a project could be done differently or a deliverable made more useful. The community matters here, too: sharing workflows and asking what others have tried gives us a way to learn beyond our own team. The tools will change, but we can keep practicing how to ask a useful question and check the result.
Decide what success means to you
Morgan was open about enjoying her career while still feeling tension around being present for her children. Faith and family are part of how she evaluates opportunities. In her words, “Work is fun and it's fulfilling, but family is forever.” That perspective belongs to her, and it helps explain the choices she's trying to make.
It also gives the rest of us a useful question: what do we want work to support? A title, a new opportunity, or someone else's career path can look appealing without fitting the responsibilities and relationships we already have. Understanding those priorities doesn't mean every choice becomes easy. It gives us something more personal and practical to use when deciding what success should look like.
The connection across these lessons is paying attention to the person involved. An owner needs a reason to use the information, a colleague needs a way to keep learning, and a work arrangement needs to fit the people doing the job. We can ask better questions before assuming the tool or title explains everything. Catch the full conversation, Make the Value Clear | VDC, Reality Capture & Career Growth with Morgan Drivas, on YouTube, Apple Podcasts, or Spotify.