The Inquisitive Engineer: Why Understanding the System Matters More Than Mastering the Part

There's a moment in our conversation with Eric Fidler on Wisdom at the Wellhead that I think gets overlooked if you're not listening carefully. He was talking about his early career, how he was given opportunities to tune processes that weren't working, things other teams were struggling with. And then he said something that deserves more attention than it got.

He said that work gave him "a deep knowledge of how the production processes interact with one another."

Not how individual pieces of equipment work. How they interact. That's a different kind of knowledge entirely. And it's the kind that separates the engineer who can fix what's in front of him from the engineer who can see what's about to go wrong three systems over.

Two Kinds of Curiosity

Here's what I've seen over the years. Most engineers start their careers by getting good at one thing. A pump. A controller. A metering system. They learn it inside and out, and that's valuable work. The operation needs people who understand individual components deeply enough to keep them running.

But there's a ceiling on that kind of knowledge. You can be the best pump specialist in the basin and still not understand why production dropped across three wells when you changed the settings on one. You can know everything about a separator and still miss the fact that a pressure shift on the gathering line is about to cause a backflow through a check valve two pads over.

Eric's curiosity didn't stop at the component level. When he was wiring gas turbines, he didn't just learn the wiring. He learned the pneumatics, the hydraulics, and the early electronics. He learned how the performance controller talked to the rest of the system. And when he moved into the field, he carried that habit with him. He didn't just learn what each process did. He learned what each process did to the ones around it.

That's the difference. Component-level curiosity makes you a specialist. Systems-level curiosity makes you the person everyone calls when nobody else can figure out what's wrong.

Where Systems Thinking Shows Up

You can see this play out at every stage of Eric's career. When he led the design of a complete production facility in the Xinjiang Province of China, the project required drawing on the expertise of multiple engineering design institutes, each with their own unique knowledge. He had to understand how all of those pieces fit together, not just technically, but operationally. The result was the first project in China that flowed first oil on the promised date, on budget, with the automation working. They had never done that before. He said they still haven't done it since.

That didn't happen because Eric knew more about any single system than the Chinese engineers did. It happened because he understood how the systems connected. He could see the whole facility as one thing instead of a collection of parts.

The same instinct showed up when he talked about the check valve problem. An operator optimized one well, increased pressure on the grid, and caused a backflow through a failing valve on a neighboring well. Net result: less production than before. The operator who made that call wasn't incompetent. He just didn't have visibility into how his adjustment affected the rest of the system. He was thinking at the component level when the problem was living at the system level.

Why This Matters More Now Than Ever

My approach is, I've always told people, AI is going to be good at augmenting what you do. But without the knowledge of what you're doing, it's worthless. And the knowledge I'm talking about isn't just knowing how to run a piece of equipment. It's knowing how that equipment fits into everything around it.

Eric made the same point when he talked about the shrinking pool of subject matter expertise in the industry. That pool is not going to expand. The experienced people who understand how entire production systems interact are retiring, and the knowledge they carry doesn't automatically transfer to the next generation. AI and automation can help bring younger engineers up to speed faster, but only if someone with that systems-level understanding is involved in building the logic.

That's the risk nobody talks about enough. We're building smarter tools, but if the people using them only understand the part and not the system, we're automating at the wrong level. We're making individual components more efficient while missing the connections between them. And those connections are where the real problems live.

What Eric's Career Teaches About Developing Systems Thinkers

Eric went from wiring turbines to designing entire production facilities to leading digital solutions at Sensia. Every step of that progression was built on understanding how things connect, not just how they work in isolation. Here's what that means for anyone building or leading a team.

Give people problems that cross boundaries. Eric learned how processes interact by being thrown into situations that required him to work across multiple systems. If your engineers only ever work inside their own discipline, they'll never develop the ability to see the connections. Put your best people on problems that force them to look beyond their corner.

Ask different questions in your production meetings. Don't just ask how each well is performing. Ask what changed on the system when you adjusted that well. Ask what the gathering line pressure looks like downstream. Train your team to think about effects, not just assets.

Pair your specialists with your systems thinkers. The specialist knows the equipment better than anyone. The systems thinker knows what the equipment does to everything around it. When those two people work together, you get solutions that hold up under real conditions, not just in isolation.

Capture the connections, not just the procedures. When your experienced people document what they know, make sure they're recording how the systems interact, not just how to operate individual components. That relational knowledge is what's hardest to replace and most critical to preserve.

Final Thought

Making energy smarter isn't about buying smarter hardware. It's about developing people who understand what the hardware is managing at a level deep enough to know when something is right, when something is off, and what's likely to happen next.

Eric Fidler built a career that spans a hundred countries because he never stopped at the drawing. He didn't just learn how things worked. He learned how they worked together. That systems-level understanding is the rarest and most valuable thing in this industry right now. It's what the next generation needs most, and it's what we're at the greatest risk of losing.

The heart of making energy smarter has never been the technology. It's always been the mind behind it.

If this hit home, you'll want to hear the full conversation.

Join Eric Fidler on Wisdom at the Wellhead as he explains how systems-level thinking built a global career, why the shrinking pool of expertise is the industry's biggest risk, and what operators can do to develop the next generation of engineers who see the whole picture.