Keep Adding Knowledge to Your Fire

What do you look for in a new opportunity: a better title, a little more money, or a chance to become capable of something you couldn't do before? We can get so focused on the immediate comparison that we miss the experience a role might give us. That matters in any career, but it becomes especially important in an industry where the technology and the work keep changing. A tool you learned once isn't the same thing as a habit of learning.

On The Matthew Byrd Podcast, I interviewed Ken Smerz, founder and owner of ZELUS. The company works in existing conditions, scan-to-BIM and virtual design and construction, but Ken's background started in construction leadership. He shared how that understanding of the build process helped him move into scanning. His path also included a difficult reset when a group of colleagues joined him and the team spent months meeting in a park. He still had to find a way to make payroll.

Focus on the client's outcome

Ken didn't tell that story as a clean formula for someone else to copy. He talked openly about decisions that didn't work, including trying to serve too many markets early on. The ability to capture information created many possible uses, but pursuing every possibility wasn't the same as building a focused business. We can make that mistake in our own work when an interesting tool pulls us toward every problem it might solve. Choosing a direction requires us to think about the people we can serve well and the work they continue to need.

His description of the service was direct: "We make the build process more efficient, period, end of story." That sentence shifts the conversation from what a model looks like to what someone can accomplish with it. Ken described how the person issuing a purchase order can have a different expectation from the person who will actually use the data. If we don't surface that difference early, a technically completed assignment can still leave somebody disappointed. Understanding the intended use is part of doing the job.

Collaborate before you compete

Ken also pushed us to reconsider how we think about other service providers. When skilled people are limited, a competitive mindset can make every resource problem something we have to solve alone. I described the waste in flying across the country for a short scanning job when a trusted provider closer to the site might be able to handle it. Sharing work requires clear expectations and dependable relationships, but it can free a team to take on something else. The useful question becomes where another company's strengths could complement ours.

That conversation connected with what we're trying to do by bringing people together through RCN. I talked about giving providers, technology companies, universities and others a place to share perspectives and hear what the work actually requires. A podcast lets people listen to a discussion; an in-person community can let more of them take part in it. We won't solve every workforce or education challenge through one conversation. We can still make those challenges easier to understand by creating more opportunities for the people involved to compare experience.

Match the tool to the job

The same issue shows up in equipment choices. "At the end of the day, you have to put the right instrument with the right job," Ken said. I brought up the familiar office scan used to demonstrate a device, because nearly everyone in this space has seen one. A small office doesn't test the same challenges as many accumulated floors or a much larger warehouse. We need to ask how the workflow behaves on the project in front of us, rather than treating one successful demonstration as an answer for everything.

Keep adapting with your people

The personal side of Ken's story added another layer. He described search-and-rescue experience and the effect of seeing how quickly people's lives can change. That experience shaped his willingness to take chances, but he also kept returning to the people who helped him build a business. Entrepreneurship wasn't presented as effortless freedom. We talked about resourcefulness, responsibility for a team, and being willing to change direction when the original plan no longer fits.

Keep putting logs on the fire

At the end, Ken's advice to someone starting out was to seek an opportunity and expect the company to provide training. His image was to keep putting logs on the fire, with the logs representing knowledge rather than just money. We can make that concrete by asking whether we're communicating better, managing time more effectively, or becoming ready for a responsibility we couldn't handle before. It gives us a way to discuss progress with a manager and to take a more active part in our own development.

That brings us back to what makes an opportunity valuable. The immediate pay matters, but it doesn't tell the whole story of what the work could help us become. A useful next step can give us skills, relationships and judgment that remain with us when the tools change again. Keep adding to that fire, and make sure you're learning how to use the heat.

Catch the full conversation on YouTube, Apple Podcasts, or Spotify: Build the Skills, Not Just the Model | BIM & VDC with Ken Smerz. You'll also hear Ken's thoughts on operational digital twins, client relationships, and building a team in a changing industry.

Watch the full conversation

Previous
Previous

Keep the Knowledge With the Building

Next
Next

Building Confidence Before You Feel Ready