Last September, I was sitting in my truck in the parking lot behind the Halliburton Park facility—the low-slung building where our procurement team sits. I had a coffee in one hand and my phone in the other, and I was not ready for the message that popped up. It was from my manager, with no "good morning" and no emoji:
"Is Eddie going out of business?"
I knew exactly what she was asking. Eddie was the owner of a distributor we had used for two years. His company had lost its Halliburton contract two weeks earlier because of a purchase order I approved. The question wasn't rhetorical. It was a test. I didn't know how to answer.
A Quick Intro to the Person Making Mistakes
My name is not important. My role is. For the past four years, I've been a procurement coordinator for Halliburton's chemical supply chain. I order the polymers, the crosslinkers, the surfactants, and the dozens of other fluids that go into a hydraulic fracturing job. I'm the guy who sits between the engineers and the vendors. I am also the guy who has a spreadsheet of my own errors—because, as much as I'd like to pretend otherwise, I've made plenty.
In my first year (2021), I ordered the wrong viscosity grade of a friction reducer for a job in North Dakota. It cost us $3,200 in rework plus a two-day delay. I wrote that one off as "learning." The mistake I made in October 2024 was not a learning experience. It was the worst professional decision I've made so far.
Halliburton Bonuses, Meet My Bonus Gap
To understand the decision, you need to understand the incentive structure. In late 2023, Halliburton launched a cost-reduction initiative. Halliburton bonuses—the annual cash payouts—were tied to how much we saved from our individual supply categories. My 2024 target was $180,000 in savings from chemicals. By October, I was about $14,000 short. For context, that's not a rounding error. That's the difference between a target and a no-target year.
I don't think the company created these targets to make people do reckless things. But that's how it works in practice. When your bonus is sitting on the other side of a number, the number becomes the point. (Which, honestly, is the problem with many performance systems.)
Woolly Bear vs. Luna Moth
In mid-October, we needed 400 drums of a friction reducer for a frac job in the Permian Basin. The standard product we had used for years was a polymer blend that the field crews called "Woolly Bear." The name started because the material is rugged: it survives bad storage conditions, it pumps easily, and it gives consistently good viscosity when it's mixed with our standard crosslinker. It costs $1.80 per pound.
Eddie's company sent over a proposal for a lower-cost replacement. It was a lower-molecular-weight version of a similar polymer, and one of our lab techs jokingly called it "Luna Moth" because it looked beautiful on the spec sheet but seemed a little too fragile to push downhole. The data said it would deliver 90% of the performance of Woolly Bear at 75% of the cost. On an order of 400 drums, that would save close to $12,000. That was almost the exact amount I needed to hit my Halliburton bonus threshold.
I should mention: the Luna Moth product had never been field-tested in our operations. It had been lab-tested. It had been tested by the vendor. But it had not been tested in the real conditions of a Permian Basin frac job. I knew that. I also knew the rig was waiting, the pump schedule was tight, and the year-end review was close. So I told myself that the similarity between the two polymers was enough. I skipped the field compatibility test.
In hindsight, I wasn't confident. I was hopeful. I thought, "What are the odds? It's just a friction reducer." Well, the odds caught up with me on the second stage.
The Mistake That Cost $47,000
The first stage went fine. The fluid behaved exactly as the additives had on paper. On the second stage, the fluid started breaking too early—the viscosity collapsed before the sand reached the formation. The frac crew had to shut down, pump a flush, and re-run two stages. You don't need to know the chemistry details to understand the cost. The rework, additional fluids, extra pumping hours, and rig downtime came to $47,000. I have seen the accounting line. I will never unsee it.
The most humiliating part was the field engineer's reaction. He didn't yell. He just said, "You know the Woolly Bear has never failed a field test, right?" I did. I had traded a known quantity for a theory.
(Should mention: the total cost of that substitution wasn't $12,000 in savings. It was $47,000 in losses plus the loss of trust. The math is not hard.)
The Question About Eddie
The financial damage was bad. But the part that really got to me was Eddie. His company was a small distributor, not a chemical giant. The Halliburton contract was a big part of his revenue. Based on the volume our order promised, Eddie had hired two additional drivers. When we canceled the contract, he didn't have work for them. They were let go within a week.
A colleague from the district office ran into Eddie at a gas station near his warehouse. Eddie asked how the frac job went. My colleague didn't know what to say. When he told me, I felt sick. Then my manager's text arrived: "Is Eddie going out of business?"
I still don't know the answer. I hope he isn't. But the uncertainty itself is part of the lesson.
The Checklist That Finally Made Me Slower On Purpose
That was the second time in my career that I had a process failure. The first was the North Dakota mistake. The third came a month later, when a rush order for another product had the wrong mixing instructions on the packing slip—luckily, the warehouse caught it before it went out. That time, nobody lost money. But it was close.
After the third incident, I created a pre-order checklist. It is not software. It is not artificial intelligence. It is a laminated sheet that lives next to my monitor, with six boxes I have to tick before I approve any substitute product:
- Has this exact product passed a field test with our standard crosslinker?
- What is the total cost of ownership, including rework, downtime, and disposal?
- Has this product been used on a similar well in the last 12 months?
- Can the vendor survive a one-month payment delay? (That stops me from using a contract to break someone.)
- Who is the technical contact if the fluid fails downhole?
- What is the written deadline, not the verbal one?
The checklist has caught 47 potential errors in the past 18 months. I know that number because I log every time it flags something. It has stopped me from ordering a product with a hazard label that wasn't approved for the site. It has stopped me from processing a rush order that would have arrived too late anyway. And it has stopped me from making another "what are the odds" decision.
Dodged a bullet last quarter. A different vendor sent a "new and improved" surfactant that looked great in the lab. Our checklist flagged it for missing field testing. We ran the test. It separated at bottomhole temperature. That order was only $9,000, but the rework would have been in the six figures. (Surprise, surprise: the vendor's "new" formula was not ready.)
What Efficiency Actually Means
It took me two years and roughly 200 purchase orders to understand this: efficiency isn't doing things quickly. Efficiency is doing things once. A fast process that produces a $47,000 failure is not efficient. It's expensive. A slightly slower process that catches the mistake before the pump truck starts is the most efficient thing I've found in this industry.
I still keep the Laminate Six, as my teammates call it. I use it on every substitution, every rush order, and every new vendor. It hasn't made me popular. It makes me the person who says "no" to something that hasn't been tested. But I've come to believe that "no" is the most efficient word in procurement.
And Eddie? I don't know if he made it. I hope he did. But the text question—"Is Eddie going out of business?"—has become a permanent part of my mental checklist. It reminds me that behind every purchase order is a payroll. Efficiency that ignores that isn't efficiency. It's just speed.