KPI Design for Floods: Map Pressure Response, Then Act

We often think that more injection always leads to more production, but the reservoir does not work on our timeline. This is about learning to map the pressure response so you can move capital where the signal is strongest and have the courage to pause where it is not. If you want to lead a successful flood, you have to stop shouting at the formation and start listening to what it is telling you.

I have seen operators treat a waterflood like a simple faucet. They think if they just turn the handle harder and pump more water, more oil will eventually have to come out the other end. But a reservoir is a complex, living system, and it does not respond well to being bullied.

I remember a project where we were pumping thousands of barrels of water a day, hitting all our injection targets perfectly. On the surface, the KPIs looked great, but the production response was nowhere to be found. We were so focused on the activity that we missed the signal. We were essentially spending money to move water in a circle while the oil stayed exactly where it was.

Force is a poor substitute for understanding in a complex drive mechanism.

The Signal in the Noise

In a waterflood or any drive mechanism, success is not just about "injecting more." It is about an operating rhythm of see, decide, and adjust. You have to map how the reservoir responds across both time and space. If you do not have a clear signal, you are just guessing with your investors' capital.

Wisdom in the field is knowing that the reservoir is a better teacher than a textbook. You need KPIs that actually tell you the story of the subsurface, not just the status of your pumps.

• Pattern Pressure Balance: Are your injectors and producers telling the same story, or is the pressure disappearing into a fault or an out-of-zone thief?

• Response Time by Pattern: You must know exactly how long it takes from the "push" of injection to the "production" effect at the wellhead.

• Anomaly Density: Unexpected behavior is a gift because it flags mechanical failures or surveillance issues before they become disasters.

• Unit Economics per Pattern: We have to track dollars per incremental barrel, not just total barrels.

Success in a flood is not about doing more: it is about being right more often.

The Operating Rhythm of a Leader

Taking a risk on a new surveillance tool or a different injection pattern is a calculated move to gain efficiency. It requires a level of patience that many quarterly-driven organizations struggle to maintain. But resilience is built on data, not on hope.

If you want an operating rhythm that actually works, you have to be willing to test your assumptions. This means running "push-pause" tests with clear limits and observation periods. If a pattern does not answer when you push, you have to be disciplined enough to stop and ask why.

A disciplined pause is often the smartest play you can make in a mature field.

Operational Lessons from Robert Wichert

Leadership is about creating a culture where the truth can be spoken plainly. When I look at how Robert Wichert manages complex assets, it is clear that he values the "map" over the "mandate." Here is how you can build that same intelligence into your team:

• Visualize the Map: Put your pattern-level dashboards—pressures, rates, and voidage replacement—on the wall. Let everyone see exactly where the reservoir is saying "yes."

• Reward the Discipline: Do not just reward high injection numbers. Reward the engineer who has the courage to suggest a pause when the data does not support the spend.

• Escalate the Exceptions: When you see no response or adverse interference, get a root-cause review started immediately. Do not let a bad pattern bleed your margin for months.

• Codify the Method: Write down what worked and what did not. Ensure the next engineer who steps into the role does not have to learn the same hard lessons from scratch.

Final Thought

There is a deep sense of stewardship in how we manage a reservoir. We are responsible for extracting every possible drop of energy while protecting the integrity of the asset. Stewardship is about having the patience to wait for the right signal and the conviction to act when you find it.

Taking the time to map your response is an act of respect for the resource and your team. It is a declaration that your foundation is built on intelligence, not just activity. Stop shouting at the wellhead and start listening to the reservoir.

________________________________________

If this question hit home, you will want to hear how it plays out in real operations. Join Robert Wichert on Wisdom at the Wellhead as he unpacks the systems, mindset, and data that turn a standard operation into a legacy business.