> ## Content Index > Fetch the complete content index at: https://russell-industrial-solutions-field-notes.ghost.io/llms.txt > Use this file to discover other available public pages before exploring further. # Whatever the Job Needed, I Learned It - URL: https://russell-industrial-solutions-field-notes.ghost.io/whatever-the-job-needed-i-learned-it/ - Published: 2026-08-31T02:09:57.000Z - Updated: 2026-08-31T02:09:57.000Z - Author: Leah Russell I didn't set out to build a career around versatility. It just kept happening. I started out running an art room and designing promotional work for clients — a creative, client-facing job that taught me something I didn't fully appreciate until years later: how to listen to what someone actually needs, not just what they say they want, and turn it into something useful. That sounds like a strange starting point for a career that eventually put me behind the wheel of a haul truck the size of a house. It wasn't. It was the same skill wearing a different uniform. From there, the path went somewhere nobody would have predicted. I picked up a welding apprenticeship and ended up on a steel bridge construction site, learning to trust a bead of weld with the same weight an engineer trusts a calculation. I managed a warehouse, tracking tooling inventory across mechanical truck shops through systems like JDE and SAP, which meant learning to think in supply chains — what's running low before it actually runs out, and what happens three steps down the line if it does. Eventually I climbed into the cab of a haul truck, then a grader, then a dozer, and stayed there for the better part of two decades, running some of the largest equipment in the oil sands — CAT dozers up through to D11, haul trucks up to 797B, machines that make you very aware, very quickly, of how much can go wrong if you stop paying attention. None of that was a plan. It was a pattern, repeating itself without me noticing at first: whatever the operation needed next, I learned it. Not because I was told to, but because someone needed to, and waiting around for someone else to volunteer never sat right with me. **\## The Part That Actually Shaped Me** Learning new equipment and new systems is one thing. What actually shaped how I think about work was everything that came after I'd learned the job — the part where people started trusting me with more than my own task list. I mentored new operators on nearly every machine I ran, which means I spent years watching how people actually learn under real conditions — not in a classroom, but with an engine running and a schedule to hit. I sat on the OH&S committee, which meant sitting in the uncomfortable middle between "the policy says" and "the site actually does." I investigated incidents and carried them through to follow-up, which teaches you fast that the goal was never to assign blame — it was to make sure the same failure couldn't happen twice, quietly, to someone else. Eventually that added up to leading a full crew as an Operations Team Lead — coordinating daily operations, safety initiatives, and performance development, while also covering as backup shift trainer. I didn't take that role because I'd always wanted to manage people. I took it because I'd spent years being the person who noticed the gap before anyone asked me to fill it, and eventually that became the job description. **\## Why the Range Actually Matters** It would be easy to describe all of this as a scattered resume — creative work, a trade, logistics, heavy equipment, leadership — like I couldn't decide what I wanted to be. That's not what it is. It's the same instinct, applied to whatever was in front of me: take what's actually needed, learn it properly, and look for how to do it better than the way it's currently being done. What that means in practice is that I don't approach a problem from just one angle, because I've had to build more than one. I can read a process the way an operator reads a piece of equipment — where the strain is, what's about to fail. I can communicate it the way a designer communicates a concept — clearly, and built for the person who actually has to receive it. And I can lead a crew through fixing it the way a supervisor holds a team accountable — with follow-through, not just a memo. Most people bring one of those lenses to a problem. I've had to build all three, because the work kept asking for them, one role at a time, over more than seventeen years. That's the same instinct behind everything I build now. It's not a new philosophy I adopted somewhere along the way — it's just the one that's carried me through every job I've ever had, long before I had a name for it.