Ask anyone who has spent a career in infrastructure design where projects go wrong, and the answer is rarely the engineering itself. It is the handoffs. The roadway team passes files to the bridge team. The bridge team passes files to drainage. Reviewers receive plan sets weeks later. Every transfer is a chance for versions to drift apart, and the gaps usually stay hidden until construction, where they are the most expensive to fix. Managing all of that coordination carried real overhead, and it was one of several reasons the biggest projects tended to belong to the biggest firms.
One Project, One Source of Truth
Cross-functional design software is dismantling that model. In connected environments built on platforms like Bentley Systems’ ProjectWise, design applications such as MicroStation, OpenRoads Designer, OpenBridge Designer and OpenFlows no longer produce separate, disconnected files. Every firm and every discipline contributes to one live, shared project model. When the roadway alignment shifts three feet to avoid a utility conflict, the bridge engineer sees it immediately. The drainage designer sees it immediately. Nobody is unknowingly working against last month’s version, because the current state of the model is always the one in front of them.
Conflicts between disciplines now surface on screen, while they cost a design revision instead of a change order. Project managers, reviewers and owner agencies interact with the model directly rather than waiting for printed submittals. A growing number of Departments of Transportation are moving toward these connected workflows on major programs. Increasingly, the question for a firm is not how large it is, but whether it can work fluently inside the project’s shared environment.
A Level Playing Field for Small Firms
That change is quietly redistributing opportunity. A 15-person firm with strong skills in connected design tools can plug directly into a major transportation project ecosystem alongside national primes. For small business certified firms, the timing is powerful. Agencies are actively seeking certified sub-consultants for inclusive contract participation, and a technology barrier that once kept small firms on the sidelines is falling. The seat at the table is there. The software no longer decides who fills it.
Getting Started: A Practical Path
The opportunity comes with one requirement: capability. The encouraging news is that building it is more achievable than most firm owners expect. For a focused starting workflow, production-ready skills in model-based design can be developed in weeks, not years, and a firm does not need to transform everything at once. The firms that make the leap successfully tend to follow a similar path.
Start with one application and one champion. Rather than retraining an entire office, choose the discipline closest to your core work, often roadway design in OpenRoads Designer, and develop one or two people into confident internal users. A single champion who understands the live-model workflow becomes the anchor for everyone who follows, and removes the fear that often surrounds a new way of working.
Learn on a pilot, not a deadline. The most common mistake is attempting to learn connected design in the pressure of a live project with a hard delivery date. Choose a smaller, lower-risk project, or rebuild a recently completed one, as a training ground. This lets your team make and correct mistakes in the model where they cost nothing, and it builds genuine fluency before the stakes are high.
Invest in structured training, then reinforce it. Self-teaching from scattered videos is slow and leaves gaps. Structured, role-specific training compresses the learning curve dramatically, but the real gains come from reinforcement afterward, when learners apply the skills to real work with support available for the questions that inevitably arise. Pairing initial instruction with ongoing mentoring is what turns a class into a capability.
Use the funding that exists. Many US firms do not realize that workforce development grants in numerous states will subsidize exactly this kind of up-skilling. These programs can offset a significant share of training costs for engineering and technical staff, making the investment far easier to justify. It is worth checking what your state offers before assuming the cost falls entirely on the firm.
Build standards as you go. As skills grow, capture them. Simple internal standards for how your firm names files, structures models and organizes data inside the shared environment protect the investment and make every future project faster. This is also what allows a small firm to look and perform like a much larger one when it joins a prime’s project team.
A trusted implementation partner can accelerate every one of these steps, but the essential point is that none of them require a large firm’s budget. They require intent.
An Industry Becoming More Open
Innovation in design software is usually described in technical terms. The more important story is human. Professionals fluent in these tools are becoming the connective tissue of project teams, and they are in short supply, which makes the skill one of the clearest paths to greater responsibility and influence. For thousands of small and woman-owned firms, and for professionals at every career stage, the door to the industry’s biggest work is open right now. It belongs to the people willing to learn the new way of working and step through it.
If you’re ready to build that fluency, CAD Journey can help you get there, starting with a conversation about where your team stands today.