Digital Construction Podcast
The answer lives in this podcast

Answer extracted from the Digital Construction Podcast — listen to the full episode below.

🎧 Listen to the episode on Listenly

What is the key difference between leadership in government agencies versus private engineering consulting firms?

Government agencies operate with compliance-driven processes and political agendas that slow decision-making, but they command greater resources and scale to invest in emerging technologies like autonomous vehicles, drones, and robotics. Private engineering consulting firms make decisions much faster for deliberate business reasons, yet they typically explore these breakthrough innovations only on mega projects due to their smaller resource base.

The compliance versus agility trade-off

When leading in a government environment, your decision-making cycles are constrained by regulatory oversight and shifting political priorities. Every major initiative must navigate formal approval processes and align with broader government mandates. This creates organizational inertia that can frustrate engineers accustomed to rapid iteration.

Private consulting firms operate under a different pressure: deliver results for the client within budget and schedule. This urgency translates into faster approvals and leaner decision chains. As Devon Middleditch describes in the Digital Construction Podcast, consulting firms can say yes or no to a proposal in days, whereas government agencies measure those cycles in weeks or months.

Scale and investment capacity: the government advantage

The trade-off favors government when it comes to innovation ambition. Because government agencies operate at a much larger scale—managing entire transportation networks, infrastructure portfolios, or systems of public works—they have budgets and long-term horizons to justify investment in experimental technologies.

A government agency can fund a drone program, a robotics pilot, or a sustainability initiative across dozens of projects simultaneously. A private consulting firm, by contrast, can only explore these technologies when a single client's mega project has the scale and budget to absorb the innovation cost. As discussed in this episode on engineering leadership, many cutting-edge tools remain locked in the hands of a few large public sector employers simply because only they can afford the upfront risk.

Devon Middleditch — Head of Digital Engineering and Technology at Varys, formerly Technology Architect on the Doha Expressway Program and leader at AECOM. Middleditch has spent his career straddling both sectors, building teams and pioneering digital frameworks in government infrastructure and private consulting, giving him direct experience with the distinct cultures, constraints, and opportunities of each environment.

The leadership lesson is clear: success in government means mastering stakeholder alignment and long-term vision; success in consulting means speed and efficiency. Neither is inherently better—they reward different skill sets. What works in Transport for New South Wales will not work at a tier-one consulting firm, and vice versa.

See also

What early-career development helped Devon Middleditch succeed in transitioning from technical to leadership roles?

Two half-day training modules were transformative: Understanding Self and Others, and Managing Self and Others. These modules provided essential frameworks for moving from a technical focus to people leadership.

How can technical experts successfully transition into leadership roles without losing effectiveness?

You have to get off the tools and leave behind your technical work to move forward. Organizations do not expect you to do two roles—they want you to do one with full attention and commitment.

What is the most important skill for the next generation of engineers working with AI-generated solutions?

Critical thinking is going to be essential for the next generation of engineers because they will receive a lot more information generated by different AI agents, and they need to validate results rather than blindly accept machine outputs.

Listen to the episode on Listenly