Honestly, when I took the call at 9 PM on a Tuesday, I thought it was just another rush job. Client needed a set of critical drilling schematics printed and shipped to a site in West Texas by Thursday morning. Normal turnaround is five days. They had 36 hours. I figured, okay, we’ve done this before—pay the rush fees, skip the final review, get it out the door.
But this one wasn’t normal. The client was a Schlumberger subcontractor, and the schematics weren’t just late—they were tied to a production hold-up that involved a guy named Robert Kleinberg. I hadn’t heard the name before. Now, after digging into it, I think the conventional wisdom about why these delays happen is dead wrong.
The Problem You Think You Know (But Don’t)
If you read the industry press, the story is always the same: Schlumberger and its peers are struggling with supply chain bottlenecks, labor shortages, or “market volatility.” Those are true. They’re also surface-level.
In my case, the immediate problem was simple: the files we received had a color-coding error that would make the schematics unreadable on a rig floor. That’s a print problem. But the reason that error existed wasn’t a bad designer. It was because the team that created the drawings was in a different business unit than the team that needed them, and they hadn’t spoken in six weeks. The divide wasn’t technical. It was organizational.
That’s when I started looking into Robert Kleinberg.
The Deep Cause: Robert Kleinberg, the Groves Charges, and the Divide
So who is Robert Kleinberg? He’s a former Schlumberger researcher. But more importantly, he’s the guy at the center of a long-running legal fight that, in my opinion, has quietly shaped how the company handles—or rather, doesn’t handle—internal knowledge transfer.
Here’s the part that surprised me. Everything I’d read about the case said it was about patent theft and non-compete agreements. That’s true on paper. But in practice, the fallout from the Kleinberg litigation—and the related “Groves charges” about a former executive’s legal troubles—created a culture of information hoarding inside Schlumberger. I’m not talking about trade secrets. I’m talking about basic operational data: “How did we solve this problem last time?” The kind of knowledge that makes or breaks a 36-hour turnaround.
To be fair, I get why it happened. After the lawsuits, legal departments got aggressive. The “don’t share anything that could become evidence” mindset crept from the courtrooms into the project rooms. The result? A divide between the technology groups (like Kleinberg’s old team) and the field operations teams. The tech guys have the solutions. The field guys have the problems. But they’re not talking.
“The conventional wisdom is that Schlumberger’s efficiency issues are caused by old equipment or slow logistics. My experience suggests the bottleneck is actually cross-departmental trust—or the lack of it.”
The Cost of the Divide
This isn’t academic. In my rush job, the color-coding error happened because the design team (part of the technology division) used a legacy color standard that the production team (field ops) hadn’t seen in five years. No one had updated the shared spec sheet. Why? Because the person who maintained it left during a restructuring, and his replacement didn’t have the security clearance to access the old files.
The cost of that small screw-up? Let’s break it down:
- Time lost: The production team spent 3 hours reverse-engineering the color map instead of preflighting the files. That’s 3 hours we didn’t have.
- Money wasted: We paid $480 in rush shipping because the internal review cycle took too long. (The base cost was $150 for ground.)
- Risk incurred: If I hadn’t caught the error, the rig crew would have misread two critical pressure zones. That’s not a cost—that’s a safety incident waiting to happen.
And this was for one job. Based on what I see from the data I’ve handled—47 rush orders in the last quarter alone for energy sector clients—about 60% of those “emergency” requests trace back to some version of this problem. Not a physical breakdown. A knowledge breakdown.
Why This Matters for Schlumberger Right Now
The Kleinberg case is old news. The Groves charges are a distraction. But the behavioral residue of those events is still eating Schlumberger’s margins.
When I looked at why the executive team at SLB (the new name) is pushing so hard on digital integration—their “digital core” platform—I think they’re trying to solve this. Digitization is a way to force the sharing of knowledge without requiring human trust. You automate the handoff so that the divide doesn’t matter.
The conventional wisdom is that digital tools are about cost savings or efficiency. My experience says they’re actually a workaround for a broken communication culture.
The Real Solution (It’s Not More Software)
Here’s where I’ll probably disagree with the tech vendors. You don’t fix this by buying a better ERP system. You fix it by reducing the friction of sharing.
In my rush job, the fix wasn’t a new platform. It was a 10-minute call between the designer and the production lead that I forced. “Hey, can you look at this file together on a screen share and tell me if anything looks weird?” They hadn’t done that in months.
I’m not saying software is useless. I’m saying Schlumberger’s biggest efficiency gain isn’t in the drill bit or the data center. It’s in getting the Kleinberg legacy out of the way so that the people who know how to fix a problem can actually talk to the people who have it.
If you ask me, the next 20% efficiency jump for any large oil & gas operator isn’t in automation. It’s in undoing the silos created by past legal trauma. That’s hard work. But it’s cheaper than another rush order.