Insights
Quality First in practice: what it actually takes on site
By Brodie Lombe, Senior Mining Engineer At Go Engineering, one of our core values is Quality First. It is easy enough to put a value like that on a website. The harder question is what it means on a Tuesday morning, on site, with a plan that needs t…

By Brodie Lombe, Senior Mining Engineer
At Go Engineering, one of our core values is Quality First. It is easy enough to put a value like that on a website. The harder question is what it means on a Tuesday morning, on site, with a plan that needs to be delivered.
Having worked across a number of sites now, my view is that providing quality support is a combination of two things — and most people only think about the first.
Technical skill and knowledge is the entry ticket
The first is technical skill and knowledge. That part is non-negotiable. You need to know the engineering, be able to do the work properly, and be able to stand behind the numbers you produce. If that is not there, nothing else matters.
But technical capability on its own does not produce a quality outcome. I have seen technically strong work land badly because it did not fit how the site actually operated, or because it was delivered in a way the team could not pick up and run with. Correct is not the same as useful.
The second half is being able to integrate into the team
Every site has its own dynamic. Its own way of approaching problems, its own rhythms, its own history of what has been tried before and how it went. Two operations mining similar ore bodies can have completely different cultures, different decision-making structures, and different expectations of what an engineer is there to do.
So being malleable and open to change is very important. Turning up with a fixed method and applying it regardless of context is a reliable way to produce work that is technically defensible and practically ignored.
Integrating into a team means understanding how that operation runs before trying to change anything within it. It means listening to the people who have been there longer than you. It means adapting how you communicate, how you present recommendations, and how you sequence a piece of work so that it fits into what the site is already doing rather than cutting across it.
When you get that right, the technical work lands. When you don't, it doesn't — regardless of how good it is.
Working across multiple sites sharpens both
With Go Engineering I have been lucky enough to work across multiple sites, alongside a range of skilled engineers. That variety is genuinely valuable, and I would recommend it to anyone early in their career.
Each new operation forces you to re-examine assumptions you had stopped noticing you were making. Something that was standard practice at one site is done completely differently at the next — and often for a good reason specific to that ore body, that fleet, or that workforce. You accumulate a much broader sense of what actually works, and under what conditions.
It also builds the adaptability I mentioned above. If you have had to integrate into five different site cultures, the sixth is a lot less daunting.
Passing it on
Something I take real pride in is being able to upskill junior engineers by sharing the knowledge I have built up over my career.
Quality First is not something one person delivers. It is a standard that has to be held across a team, which means the people coming through need to be brought up to it deliberately — not left to work it out on their own. Practically, that looks like explaining the reasoning behind a method rather than just handing over the method, letting people do real work rather than only checking it, and being available when they hit something they have not seen before.
That is also how the standard survives beyond any individual. A quality outcome delivered once is a good result. A team that consistently delivers quality outcomes is a capability — and that is worth considerably more, both to us and to our clients.
Raising the bar, not just meeting it
For us, Quality First is not about meeting expectations. It is about consistently raising the bar, and pushing past what the industry treats as standard, so that what we hand over is something we are prepared to put our name to.
That takes technical skill, it takes the ability to work inside somebody else's team, and it takes a genuine investment in the people coming up behind you. All three, every time.
If quality matters to your operation, let's talk.
Client and site details are kept confidential. We describe the nature of the work — commodities, methods and outcomes — rather than naming engagements.
Explore
