Expertise · Arcadis
James Robinson is Principal Structural Engineer at Arcadis in Sydney, and also develops engineering automation tools. An engineer who writes tools to remove repetitive work might be expected to argue for speed. The Warringah Freeway Upgrade account argues for something else, and gives most of its attention to the assumptions a team should question before it commits to a design.
In James Robinson's own words.
"A successful design must be safe, practical, buildable, maintainable, and capable of delivering value throughout its life."
Engineering decisions have long-term consequences, so I believe our responsibility extends beyond meeting programme requirements or achieving technical compliance.
I have worked on many complex transport infrastructure projects where competing priorities, tight timelines, and challenging constraints create pressure to compromise. In those situations, I have always believed it is our duty as engineers to challenge assumptions, communicate risks openly, and advocate for the best outcome, even when those conversations are difficult.
One example that stands out is my work on the Warringah Freeway Upgrade, where I led the design and delivery of two complex bridge packages involving major widening works and interfaces with existing infrastructure.
The project presented several challenges. We were working within a highly constrained corridor, maintaining traffic operations while integrating new structures with existing bridges that had been designed and constructed decades apart. Many of the standard design approaches did not neatly apply, and decisions needed to balance structural performance, constructability, programme requirements and long-term durability.
My role was not simply to find the technical answer, but to help the project team understand the implications of different options and make informed decisions. This involved working closely with designers, construction specialists, clients and stakeholders to challenge assumptions, evaluate risks and develop practical solutions that could be successfully built in the field.
One area where technical judgement was particularly important was assessing how the widened structures would behave and ensuring that design assumptions remained aligned with construction realities. Rather than focusing solely on compliance with design standards, we took a broader view of performance, constructability and whole-of-life outcomes. This collaborative approach helped avoid potential construction issues, improved confidence in the design and ultimately delivered a more robust solution.
The experience reinforced my belief that engineering expertise is not just about technical knowledge. It is about applying sound judgement, asking the right questions, and bringing together the collective expertise of the wider team to achieve the best outcome.
Q. What stands out most from your time with MIDAS?
The moment that stands out most is not a single project, but the opportunity to work closely with the MIDAS team as an industry tester for several beta versions of their software years before MIDAS Civil NX became publicly available.
As a practising bridge engineer, it was a unique experience to collaborate directly with the people developing the software. Rather than simply being an end user, I was able to provide feedback on workflows, test new capabilities, and discuss how engineers actually apply these tools on real projects. It became a genuine exchange of ideas between software developers and engineers, with both sides learning from one another.
This is a perfect reminder that expertise is as much about asking the right questions as about technical knowledge, and it comes back to James Robinson's own Right, that a successful design must deliver value throughout its life.