A focused course, tailored for you
Oil and Gas Engineer's Capability-Authorship Playbook
How an engineer at a national oil company anchors a capability when the firm tightens around energy-transition operating-model evolution.
When national oil companies tighten around energy-transition operating-model evolution, engineers without published capability-authorship narratives read as legacy-asset cost.
$199 one-time
Tailored to your situation. Access within 24 hours. 30-day money-back.
Includes a hand-built implementation playbook delivered alongside course access, generated for your specific situation.
Why this course
National oil companies running energy-transition operating-model evolution reorganise engineer functions in the same operating-model cycle. Senior engineers above are protected by their asset-area ownership; technicians below are protected by their direct contribution. The IC layer is the band the deck reviews most carefully.
The engineers who survive own a documented capability narrative with measurable asset and transition outcomes, a technical-decision record adjacent teams cite, and a quarterly capability-state artefact the engineering manager forwards.
The course covers the three artefacts and the 90-day path to capability-authorship framing. Plus a hand-built implementation playbook against your real engineering scope.
The 12 modules
Module 1. Reading energy-transition operating-model evolution for engineer implications
Energy-transition operating-model evolution at national oil companies reaches engineer functions in three phases: enterprise platform review, business-line review, and IC-portfolio review. The diagnostic decodes which signals (capex compression, energy-transition investment ratios, asset-area performance benchmarks, AI-augmentation revenue contribution) indicate that the engineer function is in the redraw set. Which engineers survive on task coverage and which survive on capability-authorship.
Module 2. Generic engineer vs capability-authorship owner
Two structurally different framings of the same oil-and-gas engineer seat read very differently to the deck. Generic engineer shows up as billable technical headcount on an asset-area budget. Capability-authorship reads as the technical leadership the business structurally depends on across operating-model evolution: documented capability narrative, technical-decision record adjacent teams cite, and quarterly state artefact the engineering manager forwards.
Module 3. Your documented capability narrative
Pick one engineering capability you currently anchor (reservoir characterisation, well-completion optimisation, refinery-process improvement, carbon-capture pilot, hydrogen-pilot integration, AI-augmented operations). Write the narrative as a Senior-engineer-grade two-page document under your byline anchored to measurable asset metrics: production performance, OPEX per barrel, emissions per barrel, safety incident reduction, and energy-transition contribution. Three structural templates.
Module 4. Technical-decision record
A technical-decision record (TDR) adjacent teams cite is the most defensible capability-authorship artefact at national oil company scale. The TDR covers context (asset constraint, regulatory overlay, transition target), considered options, decision (process pattern, technology selection, transition path), consequences, and rollback path. The packaging that makes TDRs cited by adjacent engineering teams and the way to surface them as your authorship in operating documentation.
Module 5. Quarterly capability-state artefact for the engineering manager
The quarterly artefact is a two-page state document covering capability-area momentum, asset-performance trends, energy-transition outcomes, safety and reliability outcomes, cost trajectory, and emerging risks. Cadence is end-of-quarter delivery to engineering manager with copies to operations and HSE leadership. Three worked examples from real national oil company engineer capability portfolios at different transition stages.
Module 6. Working with operations, HSE, and adjacent engineering teams
Engineer work overlaps operations (asset reliability, maintenance, production optimisation), HSE (safety, environmental, occupational health), and adjacent engineering teams (subsurface, surface facilities, automation, ML and data engineering). The collaboration pattern that strengthens defensibility: shared TDR adoption, joint operational reviews, cross-team capability reviews credited by engineer name. Examples that elevated an engineer to Senior.
Module 7. Energy-transition and carbon-management overlays
National oil companies are increasingly judged on energy-transition metrics: Scope 1 and 2 emissions reduction, methane intensity, carbon-capture pilots, hydrogen pilots, renewables integration, and disclosure under TCFD and emerging standards. The compliance overlays that strengthen the capability narrative as transition-aware engineering. How to position transition rigor as engineer-grade IP the engineering manager cites in board-level transition narratives.
Module 8. Cross-asset leverage
Reusable engineering practices that scale across asset areas: TDR templates, operational-runbook frameworks, observability instrumentation models, AI-augmented operations playbooks, transition-pilot integration patterns. The leverage pattern that signals capability-authorship engineering rather than asset coverage. How to convert delivered work into published practice the engineering manager cites in operating-model defence.
Module 9. AI augmentation as accelerator
Use AI augmentation to strengthen capability rather than absorb it. The narrative documents how AI augmentation (predictive maintenance, reservoir simulation, automated process optimisation, AI-driven safety-and-emissions monitoring) increased asset performance, accelerated decision cadence, and protected production-and-transition outcomes. Three patterns and how to document each.
Module 10. Scope statement: Engineer vs Senior Engineer / Technical Lead
Two overlapping seats with different scopes. Engineer scope covers capability delivery, TDR contribution, IP authorship at workload level. Senior Engineer scope adds multi-capability technical leadership and adjacent-engineering partnership. Technical Lead scope adds cross-asset technical strategy, TDR ownership, and asset-cabinet participation. The scope statement that puts you in the Technical Lead track defensibly.
Module 11. Promotion mechanics inside national oil companies
Internal path from Engineer to Senior Engineer to Technical Lead. The promotion artefact (capability narrative, TDR-adoption record, cross-team partnership outcomes, energy-transition contribution) and the cycle calendar (annual performance review, technical-track committee, announcement). What gets an engineer shortlisted, what blocks an engineer who is otherwise qualified, and how to time your move with the engineering manager's succession plan.
Module 12. Your 90-day move to capability-authorship framing
Day-by-day plan with daily artefacts. Days 1-7: capability narrative scaffold drafted with technical-metric inventory. Days 8-21: TDR v1 drafted with adjacent-team adoption confirmed. Days 22-45: quarterly artefact v1 delivered to engineering manager. Days 46-60: multi-capability technical-leadership conversation. Days 61-90: Senior or Technical Lead conversation scheduled with asset-cabinet sponsor identified in module 11.
How this addresses your situation
Specific modules that map to what you said you are dealing with.
Modules 1 and 2 cover the diagnostic.
Modules 3 to 5 produce the three artefacts.
Modules 6 to 9 cover cross-function cadence, transition overlays, leverage, and AI accelerator.
Modules 10 to 12 cover scope, promotion, and 90-day execution.
FAQ
Will adjacent teams actually cite my TDR?
Module 4 is built around the format adjacent teams cite.
What if my capability spans subsurface and surface facilities?
Module 3 covers that case.
Why pay for this instead of reading free engineering content?
Free content covers technique.
Is Technical Lead actually open?
Module 11 covers that diagnostic.
What is in the implementation playbook for me specifically?
A draft capability narrative; a draft TDR; a 90-day plan with conversations against your engineering manager.
