The phrase shows up most often in internal decks, not board minutes. Usually on slide seven or eight, after safety and before talent. “Systems leadership” sits there as a kind of philosophical garnish—something everyone nods at before moving on to more immediate problems like capex discipline or offtake risk.
But the industry keeps circling back to it. Not because it’s fashionable, but because the old reflexes are starting to break under pressure.
Oil and gas has always rewarded clarity of command. Someone owns the asset. Someone signs off. Someone answers when production drops or a compressor trips. That logic still holds. What’s changed is the number of interfaces wrapped around every decision. Regulatory. Financial. Digital. Geopolitical. Supply-chain. Reputation. None of them sit neatly inside a reporting line anymore.
So decisions travel. Committees grow. Emails multiply. Authority diffuses, even when accountability hasn’t kept pace.
That’s where the discomfort begins.
In practice, most leadership structures in the sector still assume problems are linear. Identify, analyze, decide, execute. The trouble is that the problems no longer behave that way. A procurement choice now reverberates through emissions reporting. A maintenance deferral ripples into workforce retention. A messaging tweak meant for investors lands with regulators instead. The cause-and-effect math doesn’t resolve cleanly, but leaders are still rewarded for sounding decisive.
So they simplify. Publicly, at least.
Inside organizations, this creates a quiet tension. Senior leaders talk about “systems thinking” while managing through fragments. Digital sits over here. Sustainability over there. Operations firefight as usual. Communications is brought in late, often after positions have hardened. Everyone understands the interdependencies. Few are structurally set up to act on them without friction.
The result is not chaos. It’s something subtler: drag.
You feel it in decision velocity. In how long it takes a pilot to become a program. In the way initiatives stall between regional autonomy and corporate oversight. In meetings where no one is wrong, but nothing quite moves.
Systems leadership, when it’s taken seriously, threatens some comfortable habits. It implies that authority is often distributed rather than centralized. That influence matters as much as control. That outcomes emerge from interaction more than instruction. None of that sits easily with an industry built on hierarchies that once worked very well.
There’s also a reputational angle that doesn’t get discussed openly.
Externally, oil and gas leaders now operate in visible ecosystems. Partners, governments, financiers, communities, technology vendors—all watching, all interpreting signals. A technically sound decision can still erode trust if the system around it isn’t aligned. And once credibility softens, it’s hard to recover. Procurement grows cautious. Regulators lose patience. Internal teams hedge before committing.
Those downstream consequences rarely show up in post-project reviews. They’re attributed to “context” or “headwinds.” But they accumulate.
Internally, systems leadership exposes another awkward reality: some influence already exists, unofficially. The project manager who brokers alignment between functions. The communications head who quietly reframes decisions to keep stakeholders onside. The country manager who reads political shifts before they hit headquarters. These people operate systemically, whether or not the org chart recognizes it.
Formal leadership models don’t always reward them. Sometimes they even get in trouble for “overstepping.”
That sends a message. Not stated, but heard.
There’s a reason many executives say they want more cross-functional leadership, then default to silos under pressure. Silos are legible. They allow clean performance metrics. They reduce ambiguity when quarterly numbers loom. Systems leadership, by contrast, makes it harder to point to a single owner. It complicates incentive structures. It asks leaders to stay in the mess longer.
And staying in the mess is uncomfortable.
But avoiding it comes at a cost. Over time, organizations become excellent at local optimization and poor at collective outcomes. Projects look efficient in isolation and underperform in aggregate. Strategy decks tell a coherent story the enterprise struggles to live.
That gap doesn’t usually trigger a crisis. It triggers fatigue.
You see it in how often strategies are re-articulated without materially changing behavior. In how skeptically middle management receives yet another “integration push.” In how external partners sense misalignment before contracts are signed, not after.
None of this means the industry needs to abandon decisiveness or technical authority. Those remain core strengths. What’s being quietly tested is whether leadership can tolerate fewer straight lines. Whether executives can hold multiple truths at once without forcing premature closure. Whether influence can be acknowledged without feeling like loss of control.
Some organizations are feeling this earlier than others—those with complex joint ventures, aggressive digital overlays, or heightened public scrutiny. They don’t call it systems leadership. They just notice that old coordination mechanisms don’t scale anymore.
Still, the language persists. Partly because it gestures toward what’s missing. Partly because no one has a better shorthand.
The risk is treating it as a competency to be trained rather than a structure to be confronted. Workshops are easier than redesign. Vocabulary is safer than redistribution of power. And so the term circulates, increasingly abstract, while the underlying frictions remain stubbornly concrete.
At some point, leaders will have to decide what they’re willing to let change. Not rhetorically. Structurally.
Until then, systems leadership will continue to live where it does now: widely referenced, selectively practiced, and most visible in the gaps it was supposed to close.
