You’re a reservoir engineer before lunch and a land manager by 2 p.m.
At a lean E&P team, the org chart says “engineer,” but the actual job spans engineering, land, and A&D. If you’re running a lean operation, you already know this. With limited time and resources, the job requires you to be nimble and wear many different hats.
The Job Behind the Title
The formal title might be reservoir engineer, VP Operations, or simply “Engineer,” full stop. The actual workday includes:
- Scoping areas and screening prospects before committing capital
- Pulling data to build type curves in Harmony, PHDWin, or Aries
- Evaluating AFEs and checking nearby activity before a partner meeting
- Running a land workup (because the land person is out or there isn’t one)
None of this is a stretch assignment. It’s Tuesday. And every one of these tasks routes through a different tool, a different login, and a different mental model of the same well.
A Typical Day for a Multi-Hat Engineer
Ask this person where most of their time goes and the answer is rarely “engineering.” It’s cross-checking.
Quick lookup tools get you speed: a fast answer, a light footprint, minimal setup. Depth platforms get you the bigger picture: full type curves, reserve-grade forecasts, the analysis that partners trust. Neither tool gets you both. To compensate, the day becomes a relay race between the two with a spreadsheet as the baton. Pull production data from one system, forecast assumptions from another, reconcile the numbers by hand, all to answer the fundamental question: is this well, this lease, this deal worth pursuing?
The data needed to answer that question already exists somewhere in the tech stack. The issue is in the time it takes to go from question to answer while hopping between tools.
Why Small-Team Workflows Break Down
It’s tempting to read this as a workflow or organization issue, solved easily by a better process or folder structure. It won’t, because the culprit isn’t organization, it’s headcount.
For a lean operator with a two- or three-person technical team evaluating 20 or more deals a year, every hour spent stitching together a type curve is an hour not spent finding the next deal. Slower deal evaluation doesn’t just mean a longer day and being late for dinner. It means fewer prospects get a thorough review, and the ones that do take longer to reach a decision. In a market where secondary basins are absorbing more deal flow and competition for the same acreage is climbing, decision speed isn’t a nice-to-have. It’s the difference between closing the deal and losing out on prime acreage.
The Pattern Is Bigger Than One Role
Talk to enough lean operators and you’ll hear the same story from people with different titles. The engineer running land workups on the side; the A&D or BD lead doing full technical evaluations without an analytics team behind them; the independent buyer piecing together tract history by hand before a deal earns a second look. Different job descriptions, same root cause: small teams doing work that used to require a department, using tools that were never built to work together.
That pattern is where the next question starts: with limited time and resources, how are lean teams rethinking their software and tech stacks? We’re covering that next. Subscribe to the Enverus blog so you don’t miss it.
