The Best Product Development Team Is Often on the Jobsite

Growing up in the construction business, I learned how to install roofing, siding, exterior and interior finish trim and paint. More importantly, I learned how experienced craftsmen think.

As a young laborer, I was fortunate to work alongside seasoned veterans who took pride in doing things the right way. They were constantly looking for better ways to work, not shortcuts, but improvements that increased quality, reduced waste, eliminated unnecessary steps, and made the next project go a little smoother than the last.

I think that may have been my first exposure to continuous improvement.

Years later, as I moved into manufacturing, product management, and product development roles, I found many of those same lessons still applied.

One of the biggest product development lessons learned was this:

Some of the best product development insights come from the people who have the product in their hands every day.

Contractors see things the rest of us often miss. They know which details create frustration, which instructions don't make sense in application, and which seemingly minor design changes could save hours of labor over the course of a project.

I've seen situations where a small adjustment to a fastening detail, an accessory, a packaging configuration, or an installation sequence made a meaningful difference in how a product was received in the market. At times what was overlooked in the engineering lab, or looked insignificant in a meeting room became significant on a jobsite.

The challenge (no surprise here!) is that construction doesn't embrace change easily.

And taking into consideration connected systems and potential liabilities, I guess change shouldn’t be embraced easily.

Many traditional products and installation methods have earned trust and confidence over decades of proven performance. Contractors build their businesses and reputations on systems they know will work.

New products don't just compete against existing products; they compete against confidence and experience.

That's why I've always believed one of the most important steps in launching a new product or system is getting it onto real projects as early as possible. Not just any projects, but quality projects where you can test and learn.

Projects where different variables can be evaluated. Where installation time studies can be performed. Where training effectiveness can be measured. Where unexpected challenges surface and potential advantages become clear. Projects that provide real-world feedback before decisions are made based on assumptions.

In many ways, these projects become case studies. Comparable to what you'd find in a business classroom, except the lessons are learned with tools in hand, on jobsites, under real-world conditions.

Those experiences often expose things no lab test, spreadsheet, or conference room discussion ever could.

The longer I work around construction and building products, the more I’m convinced that innovation is not about having the smartest idea. More often, it's about listening carefully, testing thoughtfully, and learning from the people doing the work.

The best product development team was always larger than I imagined.

Sometimes it's standing on a jobsite wearing a tool belt.