Field Development Manager Training: Choosing the Concept, Winning the Sanction, and Delivering the Field That Was Promised

The Decision That Cannot Be Undone Later

By EuroQuest Editorial Team · Updated 2026-08-30

A discovery is not a development. Between the two sits a person who has to decide how a reservoir will be produced, what it will cost, how long it will take, and whether the whole thing is worth doing at all. The field development manager owns that space. It is the point in the life of an asset where the largest amounts of money are committed on the least information, and where a choice made in a study room governs everything that follows for thirty years. This guide is written for subsurface and facilities engineers moving into development planning, project and asset managers taking a field from discovery to first oil in upstream operations, commercial and joint venture staff who have to defend a sanction case, and the operations leaders who inherit whatever was built. It covers concept selection, the development plan, the economics that decide sanction, delivery against cost and schedule, and the handover that determines whether the field ever performs as promised.

What a Field Development Manager Actually Owns

The Bridge Between a Discovery and a Producing Asset

Exploration finds hydrocarbons. Operations produces them. Between those two stands a phase in which nothing is yet built and everything is still reversible, and the field development manager is the person accountable for what happens in it. The output is a development plan: how many wells, drilled from where, into what facilities, tied back to which host, at what cost, on what schedule, and generating what return.

The role is unusual in that its most important work is subtractive. Most of the value is created by ruling concepts out early, cheaply, and for stated reasons. A subsea tieback that was never seriously evaluated is not a saving; it is an option the asset gave away. Doing that well starts with genuinely understanding the reservoir, which is why development managers are drawn from people with real depth in reservoir characterization rather than from general project management.

Why the Early Decisions Dominate Everything After

Cost influence is highest when information is lowest. By the time a project is sanctioned, the concept, the location, the recovery mechanism and the facility type are fixed, and the remaining levers are small. Everything the operations team will live with for decades was settled in a phase that consumed a fraction of the total spend.

That asymmetry is what makes the role senior despite commanding no large permanent organization. A development manager influences more future cost in eighteen months than an operations manager can influence in fifteen years, and does it while the technical picture is at its least certain.

The Money Involved Is Not Shrinking

The capital environment around the role is not one of retreat. On a projection published by the International Energy Forum with S&P Global Commodity Insights, annual upstream oil and gas capital spending would need to rise by 22 percent by 2030, reaching 738 billion dollars, to keep supply adequate against demand and cost inflation.

That is a forecast rather than a recorded outturn, and it was made with a commercial data house rather than by a statistical agency, so it describes an expectation of direction rather than a certainty.

What it does establish is that the work of choosing and sanctioning developments is not a niche skill in decline. Somebody has to convert that spending into fields that produce.

From Concept Selection to Sanction

Concept Selection Is a Structured Elimination

Concept selection compares genuinely different ways of producing the same reservoir: a fixed platform against a floating facility, a standalone development against a tieback to existing infrastructure, phased drilling against a full field drilling campaign, gas reinjection against early export. Each option carries its own recovery profile, capital shape, operating cost and abandonment liability.

The discipline lies in comparing them on the same basis. Options evaluated at different levels of definition are not comparable, and the concept that happens to have been studied hardest usually wins for that reason alone rather than on merit. Guarding against that is the practical content of reservoir engineering applied at development scale.

The Development Plan Is a Commitment, Not a Study

In most jurisdictions the plan submitted for approval becomes a binding reference point. Cost estimates in it are later measured against outturn, production profiles are compared with what the field actually delivers, and in several countries the local content and personnel commitments inside it are enforceable obligations rather than intentions.

That is directly relevant across the Caspian. Kazakhstan makes a minimum share of in-country value in personnel a mandatory term of the subsoil contract, and we set out how those categories and thresholds work in our guide to in-country value in personnel. A development plan that ignores those commitments is not a technical document with a compliance gap; it is a plan that cannot be delivered as written.

Sanction Is an Economic Argument, Not a Technical One

At the final investment decision the audience is not technical. A board is comparing this field against every other use of the same capital, under price assumptions nobody believes precisely, over a horizon longer than most careers. The development manager has to present a case that survives being pushed on: what breaks it, at what price, and how much of the downside is recoverable.

Fluency in how those numbers are built and challenged is not delegable to the finance team, because the technical assumptions underneath them belong to the development manager. That combination of subsurface judgment and petroleum economics is the single clearest marker of readiness for the role.

Delivering What Was Sanctioned

What Good Delivery Actually Looks Like

Industry conversation about project performance tends to run on anecdote, so it is worth anchoring on something measured. The Norwegian Offshore Directorate reviewed 66 developments approved on the Norwegian shelf between 2007 and 2018 and found that just over 80 percent were delivered within or below the uncertainty range of the estimate in their approved plan, with projects completed on average about three and a half months later than planned.

Two caveats matter before that figure travels anywhere. The uncertainty range is a band around the approved estimate rather than a fixed number, so this is not a claim that four in five projects came in on budget. And it describes one mature, heavily regulated shelf with a long-established planning regime, not the industry at large. Read carefully, it says that disciplined estimating and approval processes produce predictable outcomes, which is an argument about method rather than about geography.

Phasing Is the Most Underused Lever

Brownfield expansion of a producing field is often the highest-return development available, because the subsurface is understood, infrastructure exists and the market position is proven. The Tengiz Future Growth Project in Kazakhstan is the visible example in this region: when its third-generation plant reached first oil in January 2025, the operator expected the expansion to add 12 million tons per annum of crude output as production ramped up.

Phasing also changes the risk profile of a sanction case. A development built in stages lets later phases be informed by what the first phase learns about the reservoir, at the cost of some capital efficiency. Deciding where that trade sits is a judgment call, and it is one that gets easier once a manager has seen a first phase disappoint.

Most Development Work Is Portfolio Work

Flagship megaprojects dominate the coverage, but they are not where most development managers spend their careers. At the end of 2025 there were 97 fields producing on the Norwegian continental shelf, a portfolio that requires continuous small development decisions: infill wells, tiebacks, compression, debottlenecking, late-life extension.

That work rewards a different instinct than a greenfield project does. The constraint is rarely the reservoir and usually the existing facility, so asset integrity limits become development limits, and a manager who cannot read them ends up proposing things the host cannot physically carry.

The order matters. Subsurface judgment and concept selection come first because they set the ceiling on everything else, and no amount of delivery excellence recovers a badly chosen concept. Economics and estimating then decide whether the choice survives contact with a board. Contracting strategy and handover are where a sanctioned project either becomes a producing asset or becomes a dispute, and both are routinely treated as someone else's problem until they are not.

How People Reach the Role, and Where It Leads

The Usual Route In

Most field development managers arrive from one of two directions. Subsurface people, reservoir engineers and development geoscientists, move toward facilities and cost. Facilities and project engineers move toward the reservoir. Neither starts complete, and the transition is uncomfortable in both directions, because each group has to begin taking seriously a set of constraints it previously treated as someone else's.

What cannot be shortcut is having seen a full cycle. A manager who has only worked on studies has never watched an assumption fail in the field, and that experience is what separates a plausible plan from a deliverable one.

Contracts Are Half the Job

Very little of a development is built by the operator's own staff. The plan is delivered through contractors, and the contracting strategy chosen before tender decides how risk is allocated, how change is priced, and how much visibility the operator retains once construction starts.

Development managers who treat this as procurement's business tend to discover their error during the first major variation. Solid grounding in contract management is closer to core skill than to supporting knowledge, particularly where a production sharing agreement or a joint venture adds partners who must approve what changes.

Where the Role Leads

The natural next steps are asset manager, projects director, or country manager, because the role already spans subsurface, facilities, commercial and stakeholder work. Some move toward portfolio and strategy roles where the same judgment is applied to which fields to develop at all.

A growing number move in the other direction along the asset life cycle, into late-life management and decommissioning, where the discipline is the same and the liability is now the product. Development and abandonment are the two ends of one skill, and managers who understand both write better plans at the start.

Where Field Development Teams Train: Istanbul and Kuala Lumpur

Host city matters for this subject because the room decides which developments get argued about. The method transfers everywhere; the fields people bring into the discussion do not.

Istanbul and Kuala Lumpur sit at two useful poles. Istanbul draws Caspian, Black Sea and Middle Eastern operators, so the discussion tends toward large onshore expansions, sour service, and developments carried out under contractual local content commitments. Kuala Lumpur brings Southeast Asian offshore experience, where the recurring problem is marginal fields, tiebacks to ageing hosts, and deepwater economics that only work when phased.

The wider program set also runs in Dubai, Amman and Vienna, which tend to attract commercial, regulatory and joint venture participants rather than purely technical cohorts.

Choosing Between the Two

Delegates whose hardest problem is defending a large capital commitment to a state partner usually gain more from the Istanbul cohort. Delegates whose hardest problem is making a small field pay at all tend to learn faster in Kuala Lumpur.

The method taught is identical in both rooms. What differs is whether the expensive mistake in the delegate's world is an oversized facility or an unsanctionable one.

A development plan is a promise about a place nobody has yet built anything. The job is to make that promise narrow enough to keep and honest enough to be worth keeping.

Frequently Asked Questions