When a new designer comes on board—especially one with experience—there’s a good chance the onboarding process involves setting up their computer, pointing them to the right network folders, handing them a relatively simple job, and giving them a vague suggestion to “jump in” and call Joe, Sally, Roger, or whoever might answer if they run into trouble.
Even with over 40 years in this business, I know there’s a long list of things I need to learn to properly mesh with how a new truss company operates. And with that experience, I’m not afraid to ask a bunch of questions—because I know they’re valid. But what about a designer with just a few years under their belt? Will they feel comfortable speaking up? Or will they assume their new employer expects them to already know everything? After all, they did say they were experienced, right?
The same challenges probably exist within your current design team. Some may have been trained entirely in-house, which means they’re 100% convinced your way is the only right way. That might be true—or not. But is everyone really doing things the same way? Or at least close enough?
You can help new hires feel more confident—and save everyone a lot of frustration—by putting together a guide that outlines key information and company preferences. Ideally, this guide would cover dozens of topics, but here are a few areas I think are especially important, and why they should be communicated early on.
Local terminology
Even now, I occasionally hear a term in the truss world that’s new to me. I’ve worked for five different truss companies and collaborated with at least 50 or 60 more from across North America while training designers. You can’t assume that just because someone is experienced, they know your lingo—especially if they’ve relocated to join your team.
Building codes and local requirements
Make sure your new hire knows which building codes apply in your area(s). Does your company go beyond code minimums as part of your quality standards? Also, what does your local market expect? For example, are gables dropped all the time, some of the time, or never? Are hips framed Atlantic-style, Midwest-style, California-style?
Truss layout information
What details must appear on your layouts? And, just as importantly, what should be left off?
Truss configuration
Do you have preferences for webbing arrangements or chord sizes? Do you always—or never—want a king post? Do all trusses over a certain length require 2x6 chords?
Truss labeling and file naming
If your truss software doesn’t automatically label everything exactly how you and your clients want (and let’s be honest, none of them really do), what’s your system for making truss placement clear to the folks on site? How do you name job files, layout files, etc., and where should they be stored?
Of course, all the above is just scratching the surface. I know that if I were starting a new job as a designer, I would likely fire a hundred questions at my new supervisor or team member. At this stage in my career and experience, I understand that there is more than one “right” way to do almost every part of a truss designer’s job, and I’m comfortable asking for more information when things aren’t as clear as they should be. Your new hire or even your existing staff may not be as comfortable asking those questions. You can help yourself and them by compiling a list of what is important to your company and your clients.
If you’ve got ideas or experiences of your own, I’d love to hear them. What information do you think is essential for helping new designers hit the ground running? Feel free to reach out and share your thoughts—I’m always looking to improve the way we bring people into this industry.