The Missing Investment
The previous article looked at the disconnect between field crews and office staff — how communication gaps create costly redesigns. But there’s a different kind of gap inside the office itself, and it’s harder to see because it doesn’t show up in broken Xrefs or missing survey data. It shows up in the people.
Throughout this series, I’ve talked about documenting workflows, building templates, and creating systems that capture institutional knowledge. All of that matters — but systems don’t develop people. A project template can show a junior designer how sheets should be organized. It can’t teach them why. It can’t explain the design intent behind a grading plan, or walk them through the judgment calls that turn a technically correct plan set into a good one. That part requires a person — and in most firms, that person doesn’t have the time.
What Changed — and What Got Lost
Mentorship used to happen naturally in this industry. Senior staff had the bandwidth to sit with new hires, walk them through plan sets, explain how a reviewer thinks, and share the lessons they’d learned through years of corrections and fieldwork. The learning wasn’t formal — it was built into the pace of the work.
That pace doesn’t exist anymore. The valley’s development cycle has compressed timelines to the point where teaching feels like a delay rather than an investment. Senior designers are overloaded — moving between projects, managing reviews, putting out fires. Junior staff are expected to produce billable work almost immediately, often on tasks they’ve never done before, with minimal context.
I’ve watched a firm hand a junior designer a set of redlines on a grading plan with no explanation beyond “make these changes.” The designer spent three hours making the changes — and got it wrong, because they didn’t understand what the redlines were trying to accomplish. The senior engineer was frustrated. The designer was demoralized. Neither of them was wrong — the process just didn’t have room for the five-minute conversation that would have prevented the whole thing.
This isn’t intentional neglect. It’s what happens when every hour is accounted for and mentorship doesn’t show up on the project budget.
The Confidence Problem
The technical skills gap is real — I covered that in The Civil 3D Training Gap. But the mentorship void creates a different kind of problem: a confidence gap. And confidence, in production work, is just as important as technical ability.
When junior staff don’t receive consistent guidance, they begin to question their own judgment. They second-guess decisions that should be routine. They spend extra time on tasks — not because the task is complex, but because they’re not sure they’re doing it right. They avoid asking questions because they don’t want to look slow, or because the last time they asked, the senior designer was clearly too busy to help.
I’ve watched promising junior staff sit quietly through meetings, afraid to ask a question about a grading design because they assumed everyone else already knew the answer. When no one takes the time to say “here’s why we do it this way,” people stop asking — and that’s when they start looking for the door.
The distinction matters: The Civil 3D Training Gap is about whether people know how to use the software. The mentorship void is about whether people believe they belong in the profession. One is a skills problem. The other is a development problem. Both cost firms good people, but they require different solutions.
What Firms Actually Lose
When mentorship is absent, firms don’t just lose productivity — they lose their pipeline. The junior designers who struggle without guidance today are the same people who should be leading projects in five years. When they leave — and they do leave — the firm doesn’t just lose an employee. It loses the years of context, corrections, and growth that person accumulated. Then the cycle starts over with the next hire, in the same environment, with the same result.
I’ve seen firms cycle through three or four junior designers in two years, each one leaving for the same reasons — not enough support, not enough feedback, not enough growth. The firm blamed the labor market. But the labor market wasn’t the problem. The environment was.
The firms that retain good people aren’t necessarily the ones that pay the most. They’re the ones where junior staff feel like they’re actually developing — where someone is invested in their growth, where feedback is constructive instead of reactive, and where asking a question doesn’t feel like an interruption.
Making Mentorship Work Without Slowing Down
The pushback I hear most often is: “We don’t have time for mentorship.” And I understand that — billable hours are real, deadlines are real, and there’s no line item in a project budget for “teach the junior designer how to read agency comments.” But mentorship doesn’t have to mean sitting next to someone for two hours. It just has to be intentional.
The first layer is what I’d call structured feedback — and it’s the one most firms skip entirely. When a senior engineer reviews a plan set and sends back redlines, those redlines are a mentorship opportunity. Right now, in most firms, redlines go to the drafter with no explanation. The drafter makes the changes, sends them back, and the cycle repeats. If the senior engineer spends two minutes writing a short note on one or two of the redlines — “I changed this because Henderson wants the invert callout on the profile, not the plan” — that drafter learns something they’ll carry to the next project. Two minutes. That’s it. Over time, those notes compound into real development.
The second layer is giving junior staff context, not just tasks. Instead of “draft the grading plan for this project,” it’s “draft the grading plan — here’s the site plan, here’s the engineer’s design intent, and here’s what the agency is going to look for.” That extra 60 seconds of context doesn’t slow the project down. It speeds it up, because the drafter is less likely to produce something that needs to be redone.
The third layer is creating a path. Junior designers need to know what growth looks like at the firm — not a corporate career ladder, but a practical understanding of what skills they should be building and what they’ll be expected to handle in a year, two years, five years. Most junior staff I’ve talked to have no idea what their firm expects from them beyond “do good work.” That’s not a development path — it’s a hope. Firms that take 30 minutes to sit down with a junior hire and say “here’s where we’d like to see you in a year, and here’s what we’ll do to help you get there” retain people at dramatically higher rates than firms that don’t.
I don’t build mentorship programs at Frye CAD Consulting — that’s an HR function. But I do build the systems and documentation that free up senior staff to actually mentor. When the templates are solid, the workflows are documented, and the tools handle the repetitive work, senior designers get time back. What they do with that time is up to the firm — but the firms that invest it in their people see the biggest return.
A Void Worth Filling
The mentorship void isn’t a staffing problem or a generational problem — it’s a structural one. The industry compressed its timelines without adjusting how it develops people, and the result is a generation of designers who have the talent but not the support. Fixing it doesn’t require a training department or a formal mentorship program. It requires intention, small investments of time, and a recognition that developing people is not a cost — it’s how a firm builds its future.
This is the sixth article in a multi-part series exploring the real challenges facing Southern Nevada’s engineering and surveying workforce. In the next article, I’ll examine how constant agency revisions create hidden costs for production teams across the region.