THE INTELLIGENT OPERATOR LEADERSHIP PROGRAMME
Carry the decision through.
30 Sessions · 25 Minutes Per Day · Six Weeks · Free · For leaders in Nigeria’s oil and gas sector
Everything this programme rests on, on one page, taken from the book. Print it and keep it in the folder you take to the operating review. The intelligent operator does not transfer responsibility to AI. Its leadership carries the decision through.
| Framework | What it says |
|---|---|
| The Operating-Intelligence Loop | Sense, decide, act and learn. A dashboard mainly supports sensing; a ranked recommendation supports deciding; a work order may support action; an independently reviewed result supports learning. None completes the loop alone. |
| The Data-Foundation Precondition | Evidence must be adequate for its intended use, and adequacy depends on consequence. More data are not automatically better data. Fix material defects at source. |
| The Autonomy Ladder | Retrieve, draft, recommend, or perform an authorised task. Permission increases only when consequences, evidence and controls justify it, and it belongs to the approved use, not to the model’s general reputation. |
| The Value-versus-Risk Map | Consider prospective benefit and failure consequence together. Some safety, legal, technical and authority conditions are necessary requirements; a stronger expected return does not cancel a failed necessary condition. |
| The Sequencing Discipline | Begin with a bounded problem. Establish the record and decision process. Compare with existing practice and simpler alternatives. Test under relevant conditions. Expand only when the evidence supports expansion. |
| The Operations-Excellence Lens | Judge the application through the operating outcome it serves. A faster report does not prove lower deferment; a better forecast does not prove a profitable intervention; an automated invoice does not prove collection. |
These frameworks are the author’s synthesis. Use them as questions for a live decision.
| Discipline | What it asks |
|---|---|
| Know which method you are using | Instrumentation, a historian, workflow automation, a physics-based model, mathematical optimisation, machine learning or generative AI. Select the least complex credible method for the intended decision. |
| Carry one decision record | The choice requested, alternatives, evidence, uncertainty, constraints, authorised owner, resources, expected consequence and review date — distinguishing recommendation, approval, execution and assurance. |
| Ask three questions at the end | What improved in the decision? What happened after approval? What evidence supports the outcome? If the answer ends at a demonstration or a recommendation, the operating loop remains open. |
| Gate | What it confirms |
|---|---|
| 1 · Input readiness | Critical definitions, asset identity, units, time basis, provenance, quality and uncertainty — and what the application does when inputs are absent or doubtful. |
| 2 · Technical fitness | The intended task tested against a relevant baseline: false positives, missed events, warning time, calibration and conditions outside the evaluated range. |
| 3 · Workflow readiness | Users can interpret outputs and take the authorised next step. A correct warning without an executable response is an incomplete application. |
| 4 · Authority and protection | Technical, operating, financial, information-security, privacy and legal reviews; access and action limits, monitoring, stop rights and recovery. Necessary conditions pass individually. |
| 5 · Economics and support | Implementation, recurring service, data work, response, staff time, support and withdrawal costs, and who maintains the application afterwards. |
Record each as pending, passed, conditional or failed. A conditional status needs a limitation, owner, expiry and required work; it should not become an indefinite waiver.
| Period | What it does |
|---|---|
| Month one | Define the operating problem, baseline, authority, source records and constraints. Identify simple changes that can resolve the problem without a model. Correct critical record defects at source. |
| Month two | Test a bounded application where the evidence and decision process are ready. Compare it with existing practice under relevant conditions. Train the actual users and rehearse unavailable or doubtful outputs. |
| Month three | Review the result and the response. Decide whether to continue, revise, stop or expand, including cost, staff effort, operating effect and unresolved risks. Preserve the evidence supporting the decision. |
Ninety days is an organisational planning frame, not a promise that every technical application can be validated within that period.
Production and delivery · reliability and integrity · commercial and cash · people and relationships · environment and assurance · the AI portfolio. Every measure has a definition, baseline, owner, source, frequency and escalation rule, and the scorecard ends in decisions with owners and dates. Count deployed systems only as activity information.
| # | Session | Plan section |
|---|---|---|
| 1 | The Responsibility to Act and the Reader's Toolkit | Section 1 — Our company, the one decision that costs us most, and where its loop breaks. |
| 2 | The Leadership Mandate | Section 2 — The mandate: owner, authority route, funding and the evidence the board can challenge. |
| 3 | Managing the Operator as One System | Section 3 — The route to payment, the binding constraint and our constraint register. |
| 4 | Building an Operating Record Leaders Can Trust | Section 4 — The record behind our decision and its data contract. |
| 5 | Connecting Field Systems Without Exposing the Plant | Section 5 — Connectivity, separation from control, vendor exit and recoverability. |
| 6 | Governing AI and Earning Autonomy | Section 6 — The system register entry, evaluation and the permission it has earned. |
| 7 | Building the Workforce That Can Use Intelligence | Section 7 — The roles, knowledge, supervision and incentives our decision depends on. |
| 8 | Exploration, Appraisal and Reserves Stewardship | Section 8 — Where AI challenges our technical interpretation, and the information worth paying for. |
| 9 | Reservoir Management and Recovery Decisions | Section 9 — Surveillance designed around decisions, and the evidence for action. |
| 10 | Drilling, Completions and Well Delivery | Section 10 — The delivery objective, the limits of prediction and our contractor interfaces. |
| 11 | Well Integrity, Workovers and Intervention Economics | Section 11 — The intervention case, its probability and the evidence that would change it. |
| 12 | Production Optimisation and Deferment Accountability | Section 12 — The volume definition, our deferment ledger and how recovered value is verified. |
| 13 | Flow Stations, Processing and Flow Assurance | Section 13 — The physical picture, testable treatment and the full consequence of change. |
| 14 | Gas Processing, Compression and Monetisation | Section 14 — The delivery basis, the priced obligation and the improvement framed as a project. |
| 15 | Refining Yield, Quality and Product Value | Section 15 — The economic boundary, evidence for quality and the cash test. |
| 16 | Reliability, Maintenance and Shutdown Execution | Section 16 — Failure consequence, the actionable condition and the closed response chain. |
| 17 | Asset Integrity, Inspection and Remaining Life | Section 17 — The bounded integrity question and an honest action register. |
| 18 | Power, Utilities and Site Resilience | Section 18 — Our utility dependencies, a consistent comparison and the degraded-operation plan. |
| 19 | Engineering Projects and Commissioning Discipline | Section 19 — The project from the operating problem, its commissioning criteria and a protected handover. |
| 20 | Evacuation, Pipelines, Terminals and Custody Transfer | Section 20 — The available route, reconciled custody evidence and what reaches the customer. |
| 21 | Physical Security, Theft Detection and Response | Section 21 — Detection without inventing a cause, preserved evidence and protected relationships. |
| 22 | HSEQ, Process Safety and Emergency Readiness | Section 22 — Barrier condition, careful document assistance and emergency readiness. |
| 23 | Emissions, Water and Environmental Performance | Section 23 — The inventory boundary, verified detection and physical progress. |
| 24 | Host Communities and the Licence to Operate | Section 24 — Duties and commitments, credible grievance handling and accountable community work. |
| 25 | Procurement, Logistics, Contractors and Nigerian Content | Section 25 — The outcome we buy, Nigerian-content duties and the contractor in operation. |
| 26 | Commercial Decisions, Trading and Revenue Assurance | Section 26 — The real alternative, the contract as commitment and revenue reconciled to the bank. |
| 27 | Finance, Treasury and Capital Allocation | Section 27 — The case from operating evidence, the funding trough and benefit verification. |
| 28 | Portfolio Growth, Acquisitions and Joint Ventures | Section 28 — The growth thesis, the diligence that tests it and joint-venture authority. |
| 29 | Regulatory Assurance and Decommissioning Stewardship | Section 29 — Obligations mapped, reports from controlled evidence and lifecycle stewardship. |
| 30 | The Intelligent Operating Review: Your Signed 90-Day Plan | The signed 90-Day Intelligent Operating Plan. |
ERW CommandOperator · built on The Intelligent Operator — A Leadership Doctrine for AI in Nigerian Oil and Gas Operations by Ritchie Wingo. Leadership training, not investment, legal or engineering advice. Back to the programme home →