This is the story of how a routine quality review for a new project turned into a deep dive on hydrogen mobility for a remote site in Alberta. It’s a story about specifications, assumptions, and the one thing I didn’t see coming.
The Assignment: Hydrogen for a Pickup Truck Fleet
Back in Q1 of last year, I got pulled into a spec review for a project that was a bit left of center for our usual bulk gas delivery contracts. The project was for a client operating a fleet of pickup trucks in a remote area north of Fort McMurray. They weren't your standard logistics fleet; it was a specialized service crew that needed to stay mobile for weeks at a time on-site. Their goal was to reduce their diesel dependency for a sensitive ecological area, and the solution on the table was a mobile hydrogen refueling unit from Air Liquide.
The conventional wisdom in these situations is to focus solely on the gas purity and the delivery pressure specs—the standard stuff for a bulk gas contract. But the keyword in the project brief was not 'hydrogen' or 'purity'; it was 'trevor.' Not a typo for 'trailer,' but the name of the on-site logistics coordinator. This was going to be a human factors problem as much as a technical one.
The Setup: Standard Specs, Unusual Logistics
Our initial proposal was standard fare: a dedicated hydrogen tube trailer, a dispenser with a standard nozzle, and a delivery schedule that aligned with their estimated consumption. I reviewed the specs for gas purity (99.99% for fuel cell grade), the dispenser's flow rate, and the safety cut-offs. Everything looked solid.
My role at Air Liquide involves reviewing every deliverable—contracts, spec sheets, safety procedures—before it reaches the customer. On a typical week, I review maybe 30-40 items. For a project like this, with a value well north of $250,000 over the contract term, I was digging in deep. But one thing kept nagging at me (note to self: always listen to that feeling).
The problem wasn't the hydrogen; it was the pickup truck.
The Twist: What a Pickup Truck Driver Knows
Everything I’d read about mobile refueling said the limiting factor was the dispenser's flow rate. In practice, I found the limiting factor was the human who had to operate it. I requested a site visit—call it a gut check. When I got there, I met Trevor. He’s a guy who spends 12 hours a day in a modified F-250. He knows his truck, his tools, and the bush. He does not know—nor should he have to—the intricacies of cryogenic hydrogen storage.
When I asked him how he saw the process working, he said, "Like a diesel pump, right? Pull up, stick the nozzle in, wait, and go." That was the moment of my 'experience override.' The dispenser we'd specced had a complex multi-step start-up procedure, a digital authorization key, and required the operator to don a full set of PPE including a gas monitor. For a guy who refuels his diesel truck in two minutes with gloves and a cap, this was a non-starter.
I had a ton of concerns. The vendor who built the dispenser claimed it was 'intuitive' (circa 2023 industry standards). Trevor's face when I showed him the instructions said otherwise. I went back to our engineering team and said, "This proposal is technically perfect, but operationally flawed." We had to redesign the interface and the operational protocol.
The Solution: Simplified Interface, Rigorous Training
This is where the shift happened. Instead of arguing that Trevor's team needed to adapt to the technology, we adapted the technology. We redesigned the dispenser's HMI (Human-Machine Interface) to be a three-step process: Authorize, Connect, Dispense. We moved the emergency stop to a bright red button that was easier to hit than the old one. We also changed the dispensing nozzle to a lighter-weight, shorter hose configuration. The cost increase per dispenser was about $4,200. On a single unit for a pilot, it felt like a lot. But on a program that might scale to a dozen locations, the difference in user acceptance and safety was way bigger than the price.
Then came the training. I ran a blind test with our HSE team: we showed two different training modules to a group of drivers. Module A was the standard 45-minute technical deep-dive. Module B was a 20-minute visual walkthrough that answered only three questions: 'Where do I put the truck?', 'What do I touch?', 'What do I do if [emergency]?'. The results were stark. Module B resulted in a 95% pass rate on a practical test. Module A resulted in the same pass rate, but after an average of two retakes and a lot of frustration. (note to self: measure comprehension, not information delivery).
The Result: A Successful, if Humble, Launch
The project went live in late summer. The refueling system was used for the first time on a Tuesday morning. Trevor was the first operator. He completed the cycle without a single prompt from the support team. The system has been running for over six months now with zero safety incidents and an uptime of 97%.
But I have mixed feelings about how we got there. On one hand, our initial proposal was technically sound and met every industry standard for hydrogen fueling. On the other, we missed the operational reality of the user. Part of me is proud we fixed it. Another part of me is embarrassed it took a site visit—and a conversation with a guy named Trevor—to see it.
The Takeaway: A Specialist's Boundaries Are a Feature, Not a Bug
This project taught me that being a specialist—even one that reviews specs all day—has limits. I know gas purity, pressure, and materials compatibility. I do not know how a guy like Trevor works in his truck. The vendor who said, 'Yeah, our user interface is not designed for that environment' earned my respect. We didn't just buy their equipment; we partnered to fix their weakness.
The bottom line: A vendor who says 'this isn't our strength—here's how we can solve it together' is way better than a vendor who says 'everyone can use this, no problem.' It’s a no-brainer. We're already applying this principle to our next two hydrogen mobility projects in Canada, and we've built a standard 'User Reality Checklist' into our spec review process. It has only one question: Who is physically doing the work, and have you asked them what they think?