Redefining Technology

Energy & UtilitiesLeadership Insights & Strategy

AI energy strategic alignment: making a utility's AI portfolio answer to its strategy

AI energy strategic alignment is the discipline of making a utility's AI portfolio answer to its corporate strategy: every funded initiative traceable to a named strategic objective, a decision lever and an operating KPI, with strategy itself revised on model evidence. It is measured by traceability, not by how often the strategy mentions AI.

Utility control-room scene with strategy objectives and AI portfolio threads overlaid across grid operations displays
Energy & Utilities · Leadership Insights & Strategy

Key takeaways

  1. AI energy strategic alignment is a property of the portfolio, not of any model: every funded AI initiative can name the strategic objective it serves, the decision lever it moves and the operating KPI that proves it — and initiatives that cannot complete that sentence get killed or re-scoped.
  2. The unit of alignment is the thread — strategic objective → decision lever → AI initiative → system of record → strategic KPI → regulatory evidence. Most utilities have every element and no thread: a strategy on the wall, a portfolio from vendor demos, and value asserted in model units.
  3. An AI strategy document is not alignment. The mode of the ladder is the utility that published one and changed nothing: the document restates corporate ambitions at lower resolution while the portfolio is still selected by feasibility and enthusiasm.
  4. Alignment is enforced by calendar, not by conviction. The AI portfolio review belongs inside strategy governance, timed against the strategy refresh and the regulatory cycle — price control, rate case or IRP — because a review that cannot move capital between objectives is a status meeting.
  5. Mature alignment runs both ways: at the top of the ladder, model evidence revises strategic assumptions — load growth, asset condition, flexibility value — between refresh cycles, which is precisely the discipline a sector being reshaped by data-centre demand now needs.

Abbreviations used on this page

ADMS
Advanced distribution management system
CML
Customer minutes lost (GB reliability measure)
DERMS
Distributed energy resource management system
DNO
Distribution network operator
EAM
Enterprise asset management (the asset register and work management layer)
EFOR
Equivalent forced outage rate (generation availability)
IRP
Integrated resource plan (long-term supply plan filed with a regulator)
MAPE
Mean absolute percentage error (forecast accuracy)
ODI
Output delivery incentive (rewards and penalties inside a GB price control)
OMS
Outage management system
RIIO
Revenue = Incentives + Innovation + Outputs (the GB network price-control framework)
SAIDI
System average interruption duration index

Free · 8 questions · ~3 minutes

Score your strategic alignment

Eight questions, one at a time, about three minutes. Answer them and we build your personalised alignment report — your stage on the ladder, your score on each of the four dimensions, and the specific break in the thread between your strategy and your AI portfolio — and send it to your inbox. Your result doubles as the baseline for your first register review.

0 of 8 answered

Question 1 of 8Strategic traceability

Pick any funded AI initiative in your portfolio. What can it name, today, without preparation?

The thread is the unit of alignment. An initiative that cannot name its objective, lever and KPI is in the portfolio for reasons other than strategy.

How the score maps to a stage
  • 05 — Stage 1, Disconnected. AI activity and corporate strategy exist in the same organisation and never touch: the portfolio is assembled from demos, hackathons and sponsor enthusiasm.
  • 611 — Stage 2, Referenced. The strategy names AI and an AI strategy document exists — but the two are parallel artefacts with no traceability between initiatives and objectives.
  • 1216 — Stage 3, Mapped. Every funded AI initiative carries a complete thread — named objective, decision lever, KPI, baseline, owner — in a register that funding decisions actually consult.
  • 1721 — Stage 4, Steered. Alignment is enforced by cadence: the portfolio is reviewed and re-weighted inside strategy governance, and strategic commitments are made on the strength of demonstrated AI capability.
  • 2224 — Stage 5, Co-evolving. Alignment runs in both directions on a standing mechanism: model evidence revises strategic assumptions between refresh cycles, and the arrangement survives leadership change.

What AI–energy strategic alignment is — and the thread it is made of

A definition, why energy is the industry where misalignment costs most, and the strategy-to-model thread that every later section measures.

AI–energy strategic alignment is the discipline of making a utility's AI portfolio and its corporate strategy answer to each other: downward, every funded AI initiative is traceable to a named strategic objective through a specific decision lever and a KPI the strategy itself commits to; upward, the evidence the models produce about demand, assets and flexibility feeds back into what the strategy assumes. Alignment is a property of the portfolio, not of any individual model — a utility can run excellent models and a coherent strategy and still be profoundly misaligned, because the two were never wired together.

Energy is the industry where that wiring matters most, for three structural reasons. First, capital intensity: strategy here is expressed in assets that live forty years and regulated settlements that fix revenue for five, so a portfolio pulling even slightly off-axis wastes more than in any other sector. Second, the strategy is externally auditable — a price control under Ofgem's RIIO framework (opens in a new tab), a rate case before a US commission, an IRP filing — which means 'strategic fit' is eventually tested by a hostile reader with statutory powers, not by a steering committee. Third, the ground is moving: the IEA's Energy and AI analysis (opens in a new tab) describes a sector that is simultaneously AI's biggest physical dependency and one of its biggest beneficiaries, with data-centre demand rewriting load outlooks while AI-enabled operations change what networks and plants can promise. A utility whose AI portfolio drifts on enthusiasm is misaligned against a strategy that is itself going stale — two errors compounding.

The strategy-to-model thread, in three states

The unit of alignment is the thread. The top lane is the broken state most utilities run: strategy and portfolio both exist, connected only by a slideware citation. The middle lane is the aligned thread — objective decomposed to a decision lever, an initiative selected against it, output landing in the system of record, value attributed in the strategy's own KPI. The bottom lane is the loop that makes alignment durable: model evidence revising the strategy's assumptions.

  • Human in the loop
  • Where value leaks
  • AI / model
  • System-of-record action
  • Data & feeds

The process, in words

  • In the broken state, the strategy and the portfolio both exist but the causal arrow between them is a citation on a slide. Initiatives enter from vendor demos and internal enthusiasm, models mature into dashboards, and value is asserted in model units — accuracy, adoption — that no strategic commitment is written in. The strategy's trajectory is unchanged by construction.
  • In the aligned state, the thread runs through named artefacts: a strategic objective is decomposed into the specific decisions that move it, an initiative is selected because it serves that lever, its output lands in the system of record where the decision is actually taken — ADMS, OMS, EAM, market systems — and the result is attributed in the KPI the strategy commits to, against a holdout, at a standard a regulator could read.
  • In the loop state, the thread's far end bends back: portfolio telemetry feeds an assumption watchlist owned by the strategy office, tripwires fire when reality diverges from what the strategy assumed, and revisions happen between refresh cycles with the model evidence minuted as the trigger.
Step-by-step insights
The broken thread is not a caricature — it is the default
No utility designs the top lane; it assembles itself, because each step is locally rational. The vendor demo is genuinely impressive, the pilot genuinely works, the dashboard is genuinely the fastest thing to ship, and the strategic-fit paragraph is genuinely written in good faith. Misalignment is an emergent property of locally sensible decisions with no structural check between them — which is why exhortation never fixes it and a register row that can fail does.
The decision lever is the load-bearing translation
The step utilities most often skip is decomposing an objective into decision levers — the specific, recurring operational decisions that move it. 'Improve reliability' is not buildable; 'change how restoration switching is sequenced on the worst-served 11 kV feeders' is. The lever names the decision, the system it lives in, and who takes it, which is what lets an initiative be selected on strategic grounds rather than technological ones. A portfolio scoped at objective level produces platforms in search of users; scoped at lever level it produces changed decisions.
Why the thread must end in a system of record
The thread terminates in the ADMS, OMS, EAM or market system — not in a dashboard — because that is where the decision the lever names is actually taken. Output that stops short of the system of record depends on a control-room engineer or planner voluntarily adding a step to their day, and voluntary steps are the first casualty of a storm, an outage or a price spike: precisely the moments the strategic KPI is decided. This is the same integration lesson the wider maturity literature teaches, applied at portfolio scale.
Attribution in the strategy's own units
The aligned lane ends in 'CML versus holdout feeders' rather than 'forecast accuracy' because strategic KPIs are the only currency the strategy conversation accepts. The holdout — comparable feeders, plants or customer cohorts left on the old process — is what makes the delta attributable rather than asserted, and 'submission-grade' is the standard: could this evidence pack survive a price-control or rate-case challenge? If yes, it can underwrite commitments (stage 4). If not, it is an internal encouragement, and should be labelled as one.
The watchlist is the cheapest strategic instrument a utility can build
The bottom lane needs surprisingly little machinery: a list of the strategy's load-bearing assumptions, a named model-evidence feed for each, and a numeric tripwire defining how far reality may drift before the assumption is formally re-opened. Its value is timing. Strategy refreshes run on multi-year cycles; demand, asset condition and flexibility value now move faster than that — the IEA's data-centre outlook is the current exhibit. The watchlist is how a utility notices in-quarter what it would otherwise notice at the next refresh, two capital plans too late.
What the loop deliberately does not do
The evidence loop revises assumptions; it does not make decisions. The distinction is the boundary between stage 5 and abdication: an evidence brief states what the models observe, with what confidence, against which assumption — and the strategic response remains a minuted human decision that weighs politics, financing and regulatory appetite alongside the data. Utilities that collapse this boundary hand their capital plan to whoever tunes the forecast, which is not alignment; it is an unaudited transfer of power.

The five stages of alignment in detail

For each stage: what it looks like inside a utility, the diagnostic checks a reviewer can run in an afternoon, the anti-pattern that traps leadership teams there, and what leaving costs.

Each stage below is written for the people who would have to fix it — the strategy office, the executive team and the engineers who own the portfolio — rather than for a buyer. The hallmarks are observable conditions, the diagnostic signals are checks you can run against your own documents and calendars this week, and the anti-pattern is the specific mistake most often made trying to leave that stage. The ladder is a diagnosis, not a race: stage 4 is a perfectly good place for most utilities to operate, provided they arrived there honestly.

Strategic leverage released along the alignment ladder

The curve is flat through stages 1 and 2 — AI activity without strategic effect — and inflects at stage 3, when the register first changes what gets funded. The steep section is stages 3 to 4, where commitments start being priced on capability. The IEA's analysis of AI in energy systems reaches the same structural conclusion: value concentrates where AI is wired into consequential decisions, not where activity is highest.

Strategic value released by stage

  • Stage 1 · Disconnected — 26% of operators. AI activity and corporate strategy exist in the same organisation and never touch: the portfolio is assembled from demos, hackathons and sponsor enthusiasm.
  • Stage 2 · Referenced — 38% of operators. The strategy names AI and an AI strategy document exists — but the two are parallel artefacts with no traceability between initiatives and objectives.
  • Stage 3 · Mapped — 22% of operators. Every funded AI initiative carries a complete thread — named objective, decision lever, KPI, baseline, owner — in a register that funding decisions actually consult.
  • Stage 4 · Steered — 11% of operators. Alignment is enforced by cadence: the portfolio is reviewed and re-weighted inside strategy governance, and strategic commitments are made on the strength of demonstrated AI capability.
  • Stage 5 · Co-evolving — 3% of operators. Alignment runs in both directions on a standing mechanism: model evidence revises strategic assumptions between refresh cycles, and the arrangement survives leadership change.

Curve shape: logistic, plotted from the stage data above. Distribution: Consistent with IEA, Energy and AI.

Select a stage

Every stage's full detail is in the page source — the selector only changes which panel is visible, so nothing here depends on JavaScript to exist.

Stage 1

Disconnected

26% of operators sit here

AI activity and corporate strategy exist in the same organisation and never touch: the portfolio is assembled from demos, hackathons and sponsor enthusiasm.

Stage 1 is not the absence of AI — most stage-1 utilities have plenty. It is the absence of any connective tissue between that activity and the strategy the board actually steers by. The load-forecast pilot came from a vendor demo, the drone-inspection trial from an innovation allowance, the churn model from a retail team with budget left in Q4. Each is individually defensible; collectively they are a portfolio nobody chose.

The tell is the inventory question. Ask a stage-1 executive team to list every AI initiative currently consuming money or engineering time, and the list takes three weeks to assemble, disagrees between functions, and surprises everyone with its length. Ask which strategic objective each line serves and the answers are retrofitted on the spot — plausible narratives constructed backwards from what already exists, which is the opposite of alignment.

The cost of staying here is not the money the pilots burn; it is that the strategy's hardest commitments go unsupported while the portfolio grows. A utility can run nine AI experiments and still walk into a price-control review, a rate case or a storm season with no model evidence behind the commitments that actually carry regulatory or financial consequence. Activity is not coverage.

In practice

The strategy on the wall and the pilots in the basement

A vertically integrated utility publishes a strategy with three headline commitments: reliability, affordability and net zero by 2050. The same year, its data science group runs a customer-churn model, a solar-output forecast bought from a vendor, and a corrosion-detection trial on drone imagery. All three work. None maps to the three commitments — the reliability commitment, which carries the regulator's penalty regime, has no model behind it at all. At year end the board asks what AI contributed to the strategy, and the honest answer is that nobody had connected the two questions.

What it looks like

  • No AI initiative can name the strategic objective it serves
  • The portfolio's origin story is vendor demos and innovation-day winners
  • The strategy mentions AI once, as an aspiration, if at all
  • Nobody can list every AI initiative currently running

Diagnostic signals you can check this week

  • Request the full AI initiative inventory and time how long it takes to produce
  • Pick three funded initiatives and ask each owner, separately, which strategic objective it serves — compare the answers
  • Check whether the strategy document's AI references name any decision, system or KPI
  • Ask which strategic commitment would suffer if all AI work stopped tomorrow — 'none, honestly' means you are here

Anti-pattern · Commissioning an AI strategy document as the fix

The instinctive response to disconnection is to commission a Digital & AI Strategy — six months, a consultancy, a glossy document. It is the most reliable way to reach stage 2 and stop, because a document restating corporate ambitions with AI vocabulary changes nothing about how initiatives are selected, funded or killed. The cheaper, faster move is to take ONE strategic objective and build its thread end to end — objective, decision levers, candidate initiatives, KPI baseline. The register generalises from a worked example; it never generalises from a document.

What holds you here

There is no inventory and no thread, so no conversation about alignment can even start — the portfolio and the strategy are answers to different questions.

Highest-leverage next move

Inventory every AI initiative, then build the complete thread for one strategic objective — not a strategy document for all of them.

Cost of leaving

Effort
2–4 months
Team
One strategy-office lead and one senior engineer, part-time; executive sponsorship for the inventory
Risk
Low — the work is analytical; the only casualty is the comfort of not knowing what is running
To next stage
2–4 months

If this is you, the next step is

A 2-week engagement: one strategic objective decomposed into decision levers, candidate initiatives and a KPI baseline.

Build your first thread

Stage 2

Referenced

38% of operators sit here

The strategy names AI and an AI strategy document exists — but the two are parallel artefacts with no traceability between initiatives and objectives.

Stage 2 is the mode of the industry and the most comfortable place on the ladder, because it looks finished. The board asked for an AI strategy and received one. The document is competent: it names the energy transition, grid reliability, customer affordability, and commits to being 'AI-enabled' in each. Funding papers now carry a strategic-fit paragraph. Every artefact of alignment exists except the alignment.

The structural problem is that reference is one-directional and unfalsifiable. An initiative that 'supports our reliability ambition' has made a claim nobody can test, because no feeder, no KPI, no baseline and no target attaches to it. The strategic-fit paragraph becomes a genre of creative writing — every proposal passes, so the check selects for writing quality rather than strategic weight, and the portfolio composition remains what it was at stage 1: feasibility and enthusiasm, now better documented.

Stage 2 has a second, quieter cost: it inoculates the organisation against the real work. Because a strategy document exists, the executive team believes the alignment question is answered, and proposals to build a traceability register read as bureaucracy — 'we already have a strategy'. Utilities that sit at stage 2 for three years are harder to move than stage-1 utilities, because the document is evidence, to every internal audience, that the problem is solved.

In practice

The document that restated the strategy at lower resolution

A distribution utility publishes 'Digital & AI Strategy 2030'. It names the same four objectives as the corporate strategy, adds an AI ambition to each and a maturity pyramid on page nine. Eighteen months later a non-executive director asks a precise question: which of our four objectives has a materially different trajectory because of this? The team assembles a slide of pilots, adoption counts and an accuracy improvement. The trajectory question goes unanswered — not because the work is bad, but because nothing was ever wired to a trajectory in the first place.

What it looks like

  • A published Digital & AI strategy restates corporate ambitions at lower resolution
  • Initiatives cite 'strategic fit' in funding papers without naming a KPI or baseline
  • The AI steering committee and strategy governance are separate forums with separate calendars
  • Value is reported in model units — accuracy, MAPE — or generic 'efficiencies'

Diagnostic signals you can check this week

  • Put a funded initiative's strategic-fit paragraph next to the strategy and check whether any named objective, KPI or target actually connects them
  • Ask when the AI steering committee last moved money between initiatives for a strategic reason
  • Check whether the AI strategy document names any specific feeder class, plant, asset fleet or customer segment
  • Count how many initiatives report value in a KPI the strategy itself commits to. Usually zero

Anti-pattern · Refreshing the document instead of building the register

When stage 2 disappoints, the reflex is a better document — more specific, more technical, with a roadmap section. The refresh consumes another six months and lands in the same place, because the defect was never the document's quality; it is that no operational mechanism connects it to funding decisions. The move that works is unglamorous: a register with one row per funded initiative — objective, decision lever, KPI, baseline, owner — and a rule that a row must be complete before money moves. The register is smaller than the document and does more than the document ever did.

What holds you here

Reference substitutes for traceability: every initiative claims strategic fit, so the claim distinguishes nothing and the portfolio's composition never changes.

Highest-leverage next move

Stand up a traceability register — one row per funded initiative, no complete row, no funding — and accept the orphan list it produces.

Cost of leaving

Effort
3–6 months
Team
Strategy office owns the register; finance enforces it at funding gates; initiative owners complete their own rows
Risk
Medium — the first register pass exposes orphan initiatives with sponsors, and the kill conversations are political
To next stage
3–6 months

If this is you, the next step is

We draft the register against your live portfolio and run the first orphan review with your strategy office.

Turn the document into a register

Stage 3

Mapped

22% of operators sit here

Every funded AI initiative carries a complete thread — named objective, decision lever, KPI, baseline, owner — in a register that funding decisions actually consult.

Stage 3 is where alignment stops being a claim and becomes a data structure. The register is not a spreadsheet for its own sake; it is the enforcement point. A proposal that cannot complete its row — which objective, which decision, which KPI, measured how, against what baseline — is not fundable, however impressive the demo. That single rule changes the portfolio's composition within two funding cycles, because it filters at intake rather than auditing after the fact.

The register's first pass is always uncomfortable, and the discomfort is the point. A typical first pass across a mid-size utility finds a quarter to a third of live initiatives cannot complete a row. Some die, some merge, and some — often the most interesting outcome — re-scope onto an objective that was genuinely unserved: the anomaly-detection team that had been polishing a trading-floor demo discovers the storm-response commitment has no model behind it and becomes the most strategically load-bearing initiative in the portfolio.

What stage 3 does not yet have is motion. The register is accurate but static: it records alignment at the moment of funding and drifts thereafter. Strategy reviews still run without the portfolio in the room; a determination from the regulator or a revision to the demand outlook does not automatically re-open any row. Mapped is a photograph. The next stage is a film.

In practice

The register that killed four projects in its first quarter

A two-network utility builds a register for its nineteen live AI initiatives. Four cannot complete a row after honest effort: a generative-AI knowledge assistant with no named decision, two overlapping forecast pilots serving the same lever, and a computer-vision trial whose KPI belonged to a strategy retired two years earlier. Two are stopped, the forecasts merge, and the vision trial re-scopes onto the current asset-health objective. Freed budget moves to the wildfire-risk model that the strategy's resilience commitment had been waiting on. Total new spend: zero. Portfolio composition: transformed.

What it looks like

  • A traceability register exists with one complete row per funded initiative
  • Initiatives have been killed or re-scoped for failing the register, not just for failing technically
  • Value is reported in the strategy's own KPIs — CML, EFOR, MAPE-to-balancing-cost — with baselines
  • An orphan review runs on a calendar and its outcomes are minuted

Diagnostic signals you can check this week

  • Open the register and sample five rows — check each names an objective, a decision lever, a KPI, a baseline and an accountable owner
  • Ask for the minutes of the last orphan review and the list of what it killed, merged or re-scoped
  • Trace one funding decision end to end and check the register was consulted before money moved
  • Compare the register's KPI column against the strategy's own commitments — they should use the same words

Anti-pattern · Letting the register become reporting

The mapped register drifts toward theatre the moment completing it becomes a documentation exercise done after decisions rather than an input to them. The signature is a register that is beautifully maintained and never referenced in a funding paper — someone's job is updating it, nobody's decision depends on it. Protect against this structurally: the register lives inside the funding workflow (a gate checks the row, and the check can fail), not beside it. A register that has never blocked anything is not a control; it is a museum.

What holds you here

The register records alignment but nothing keeps it current: strategy moves, determinations land, demand outlooks shift, and the rows quietly go stale.

Highest-leverage next move

Move the portfolio review inside strategy governance and onto its calendar — strategy refresh, price-control milestones, IRP filings — so re-weighting is routine rather than exceptional.

Cost of leaving

Effort
6–12 months
Team
Strategy office chairs; finance wires the register into gates; operations owners accept KPI accountability per row
Risk
Medium — the calendar merge with strategy governance threatens two committees' existence, and committees defend themselves
To next stage
6–12 months

If this is you, the next step is

We design the merged review cadence — portfolio inside strategy governance, timed against your regulatory cycle.

Put the register on the executive calendar

Stage 4

Steered

11% of operators sit here

Alignment is enforced by cadence: the portfolio is reviewed and re-weighted inside strategy governance, and strategic commitments are made on the strength of demonstrated AI capability.

At stage 4 the interesting change is in what the utility is willing to promise. A stage-3 utility uses AI to help meet commitments it would have made anyway; a stage-4 utility makes commitments it could not responsibly make without the demonstrated capability — a reliability improvement priced on two years of fault-prediction performance, a totex position that assumes condition-based intervention intervals, a connections-processing commitment that assumes automated network analysis. The models have moved from supporting the strategy to underwriting it.

This is also the stage where the regulatory calendar stops being a constraint and becomes the alignment mechanism itself. Price controls, rate cases and IRPs force a utility to write its strategy down in auditable, quantified form on a fixed schedule — which is exactly the artefact a traceability register needs at its far end. Steered utilities draft regulatory commitments from portfolio evidence and re-plan the portfolio when determinations land, in both directions, on the same dates. The submission timetable becomes the portfolio's heartbeat.

The discipline that makes this safe is attribution. A commitment priced on model performance is a liability if the performance evidence would not survive scrutiny, so stage-4 utilities hold the evidence to regulatory standard: holdout feeders or plants, baselines agreed before go-live, benefit rules written down. This is why stage 4 cannot be skipped from stage 2 — the evidence habits are built at stage 3 or they do not exist when the submission needs them.

In practice

The reliability commitment priced on the model's track record

A DNO preparing its price-control business plan has run fault prediction on its worst-served 11 kV feeders for two seasons, with a holdout set and a CML baseline agreed with its regulation team at go-live. The submission commits to a reliability improvement — with the associated incentive exposure — explicitly priced on that demonstrated performance extended across the fleet, and the portfolio's next two years are re-sequenced around delivering it. The model is no longer a pilot with a good story; it is a named input to a regulated commitment, with the audit trail that position requires.

What it looks like

  • One calendar: portfolio reviews sit inside strategy governance, timed against the regulatory cycle
  • Capital moves between objectives at reviews — re-weighting is unremarkable
  • At least one external commitment (price control, rate case, IRP) is priced on demonstrated model performance
  • The strategy office, not the data function, answers for portfolio composition

Diagnostic signals you can check this week

  • Put the portfolio review calendar next to the strategy and regulatory calendars — at stage 4 they are the same document
  • Find one external commitment whose quantum was set using model evidence, and ask to see that evidence pack
  • Check who presents portfolio composition to the board — strategy office at stage 4, data function below it
  • Ask what happened to the portfolio within one quarter of the last determination or strategy revision

Anti-pattern · Underwriting commitments with pilot-grade evidence

The stage-4 failure is over-reach: pricing an external commitment on a model whose evidence is one good season, no holdout, and a baseline reconstructed after the fact. When the commitment is challenged — and price-control and rate-case processes exist to challenge it — the evidence collapses, the commitment gets re-priced, and the institution learns that model evidence is soft. That lesson costs years. The rule is asymmetric on purpose: the portfolio may promise externally only what its attribution machinery can defend to a hostile reader, and everything else stays an internal ambition until it can.

What holds you here

Information still flows one way. Strategy steers the portfolio, but what the models learn about the world — demand, asset condition, flexibility value — has no formal route back into strategy formation.

Highest-leverage next move

Institutionalise the reverse thread: an assumption watchlist owned by the strategy office, fed by model evidence, with tripwires that trigger review between refresh cycles.

Cost of leaving

Effort
12–24 months
Team
Strategy office and regulation team jointly own the evidence ladder; portfolio owners deliver to submission-grade attribution
Risk
Higher — commitments carry incentive and penalty exposure, so evidence quality becomes a financial control
To next stage
12–24 months

If this is you, the next step is

We build the route from model telemetry to strategy-grade evidence briefs your regulation team can stand behind.

Design the evidence flow-back

Stage 5

Co-evolving

3% of operators sit here

Alignment runs in both directions on a standing mechanism: model evidence revises strategic assumptions between refresh cycles, and the arrangement survives leadership change.

Stage 5 inverts the question the rest of the ladder asks. Below it, the problem is making the portfolio serve the strategy; here, the recognition is that the portfolio has become the utility's best instrument for discovering that the strategy is wrong. Load forecasts see electrification clusters before the planning cycle does. Asset-health models see a fleet ageing faster than the depreciation assumption. Flexibility dispatch sees value the connections queue is starving. A utility that only pushes strategy down is discarding the most current evidence it owns about the world its strategy describes.

The mechanism is deliberately boring: a watchlist of the strategy's ten or fifteen load-bearing assumptions — demand growth by segment, asset-failure trajectories, flexibility value, connections demand — each with a named model-evidence feed and a tripwire that defines how far reality may drift before the assumption is formally re-opened. When a tripwire fires, a decision forum convenes with a defined mandate. What that forum may decide, and how, is decision-playbook territory; what makes the utility stage 5 is that the trigger exists at all, and fires between refresh cycles rather than waiting for one.

Almost nobody should chase stage 5 directly, and the honest reading of the ladder is that its top is mostly built from its middle: a utility that cannot attribute value to a holdout (stage 3) or hold evidence to submission grade (stage 4) has nothing a strategy refresh should trust. The current demand shock makes the case concrete — a sector where data-centre connection requests are rewriting load outlooks year by year is a sector where the utilities that noticed first were the ones whose forecast evidence had a standing route to the strategy table.

In practice

The connections queue that rewrote the strategy

A utility's LV load models and connections pipeline analysis start showing heat-pump and EV clustering, plus early data-centre enquiries, running roughly two years ahead of the demand assumption its strategy was refreshed on. The assumption sits on the watchlist with a tripwire; the tripwire fires; a scheduled evidence brief puts the divergence in front of the executive strategy forum with the model lineage attached. The refresh that follows moves capital from generation optimisation toward network reinforcement and flexibility procurement — and the minutes record the model evidence as the trigger. Direction down, evidence up, on the record.

What it looks like

  • A strategy assumption watchlist exists, with named model-evidence feeds and tripwires
  • At least one strategic assumption has been formally revised on model evidence, on the record
  • Strategy refresh consumes a standing evidence brief from the portfolio as a mandatory input
  • The mechanism is institutional — documented, owned by role, and has survived at least one succession

Diagnostic signals you can check this week

  • Ask to see the assumption watchlist, its named evidence feeds and the last tripwire that fired
  • Find one strategy decision whose minutes cite model evidence as an input — reconstruct the chain from model to minute
  • Check the mechanism is defined by role and document, not by the individuals who built it
  • Test succession: has the loop survived a change of CEO, CFO or strategy director without re-lobbying?

Anti-pattern · Letting the loop become an oracle

The stage-5 corruption is treating model evidence as self-executing strategy — 'the forecast says X, so the plan is X' — which quietly transfers strategic judgement to whoever tunes the model. Evidence briefs earn their standing precisely because they are bounded: they state what the models observe, with what confidence, against which assumption, and stop. The strategic decision remains a human, minuted act that weighs the evidence alongside everything models cannot see — politics, financing conditions, regulatory appetite. Keep the boundary sharp, because the first time an unexamined model assumption steers a capital plan, the whole loop loses its licence.

What holds you here

Sustaining co-evolution is an institutional problem: the loop must survive successions, reorganisations and strategy fashions, which is governance work rather than modelling work.

Highest-leverage next move

Treat the alignment mechanism itself as a versioned, owned artefact — reviewed annually, tested against succession, and audited like any other control.

Cost of leaving

Effort
Continuous
Team
Strategy office owns the watchlist; portfolio owners staff the evidence briefs; the executive forum owns decisions
Risk
Concentrated — the failure mode is subtle (a wrong assumption steering capital), so the loop itself needs audit

If this is you, the next step is

We stress-test one assumption-to-decision chain: feed quality, tripwire design, brief discipline and the minute trail.

Audit the evidence loop

Where energy and utility leadership teams actually sit

The distribution across the ladder, why Referenced is the mode, and what the research actually measures about AI in the sector.

Most utilities sit at stage 2 — Referenced — and the shape of the distribution is unusual among maturity curves: the mode is not where the least work has been done but where the most comfortable artefact exists. The AI strategy document boom of the last few years moved a large share of the sector from Disconnected to Referenced without moving the underlying portfolio at all, which is why the distribution below has a heavier second bar than adoption curves in less document-driven industries.

Illustrative distribution of utility leadership teams across the alignment ladder

Illustrative, model-derived distribution synthesised from the IEA's Energy and AI adoption analysis and sector surveys — not a measured census. Stage 2 is the mode: the document exists, the thread does not. The sharpest drop is into stage 3, where the register first has to kill something.

Share of utilities

  • 26% — 1 · Disconnected
  • 38% — 2 · Referenced (the document, not the thread)
  • 22% — 3 · Mapped
  • 11% — 4 · Steered
  • 3% — 5 · Co-evolving

Source: Illustrative; synthesised from IEA, Energy and AI

The external research is consistent with that shape without mapping onto it exactly. The IEA's Energy and AI report (opens in a new tab) finds substantial, quantified potential for AI across generation, networks and demand — and, in the same analysis, that adoption in the energy industry remains concentrated in pilots and point solutions rather than portfolio-scale deployment. Eurelectric (opens in a new tab), the European power-sector association, has made digitalisation and data capability a standing pillar of its sector strategy work, which tells you where the industry's own leadership believes the gap is. And the demand side is moving underneath all of it: EIA's electricity data (opens in a new tab) shows US load growing again after fifteen flat years, driven in part by data centres — a structural change that makes stale strategic assumptions expensive faster than at any point in a generation.

Two features of the distribution deserve emphasis. The stage 2 → 3 transition is the sharpest population drop on the ladder because it is the first transition with victims: the register's first pass produces an orphan list, and orphans have sponsors. Utilities that cannot hold the kill conversation bounce off stage 3 repeatedly, each time with a fresher document. And the thin far end is not failure — stage 5's 3% reflects that co-evolution requires evidence machinery most of the sector has not yet needed. The honest ambition for a leadership team reading this page is Mapped within a year and Steered within a regulatory cycle.

The alignment register: the thread written down, domain by domain

Six operating domains, the strategic objectives they carry, the decision levers that move them, the systems of record the thread must end in, and the KPIs that prove it.

The alignment register is the thread made into a table: one row per funded initiative, recording the strategic objective it serves, the decision lever it moves, the system of record it lands in, and the KPI — with baseline and holdout — that will prove it. The domain map below is the template we use to build one with utility leadership teams. It matters that the vocabulary is the industry's own: a register written in generic transformation language cannot be checked against a strategy written in CML, EFOR and totex, and an initiative that cannot find its row in this map is usually an initiative in search of a purpose.

DomainStrategic objective it servesDecision leversSystem of recordStrategic KPIsEarns a row from
Generation & tradingMargin and availability from the existing fleetOutage timing, unit commitment support, bid/offer strategy, renewables output forecastingEMS, plant historian, ETRMEFOR, forecast MAPE, imbalance costStage 2–3
Transmission & system operationSecurity of supply as renewable share risesConstraint management, dynamic line rating, reserve and balancing schedulingEMS / SCADA, market systemsConstraint costs, curtailed TWh, balancing spendStage 3–4
Distribution networksReliability commitments within allowed totexFault prediction and restoration switching, vegetation management, storm rosteringADMS, OMS, GISCML, SAIDI / SAIFI, worst-served feeder countStage 3–4
Asset managementAsset life extension and reinforcement deferralHealth scoring, inspection triage, risk-based maintenance intervalsEAM / APM, asset registersAsset health index, unplanned outage rate, capex deferredStage 3
Customer & retailAffordability, debt and cost to serveConsumption forecasting, contact triage, vulnerability identification, tariff design supportMDM, CRM, billingCost to serve, bad debt, complaint rateStage 2–3
Flexibility & DERHosting capacity and flexibility ahead of electrificationLV load forecasting, hosting-capacity analysis, flexibility dispatch, BESS schedulingDERMS, flexibility platformsHosting capacity released, MW contracted, reinforcement deferredStage 3–4
The utility alignment map: where AI initiatives attach to strategy, by operating domain. 'Earns a row from' is the ladder stage at which initiatives in this domain typically justify register entry — trading optimisation is buildable early; commitments priced on network AI demand stage-4 evidence discipline.
  • The named-objective test

    The row's objective must appear, in the same words, in the corporate strategy or the regulatory submission — not in the AI strategy. If the objective exists only in the AI document, the initiative is aligned to a mirror.

  • The named-decision test

    The lever must name a recurring decision, the system it is taken in, and the role that takes it. 'Improve asset management' fails; 'set transformer intervention intervals in the EAM, decided monthly by the fleet engineer' passes.

  • The provable-KPI test

    The KPI must have a baseline that predates the initiative and an agreed attribution method — a holdout fleet, feeder set or customer cohort. A KPI adopted after go-live inherits the initiative's own effects and proves nothing a hostile reader will accept.

The register's far column — evidence — is also where alignment meets the sector's compliance frame, mechanically rather than decoratively. A GB network operator's register rows should trace to the outputs and ODIs of its RIIO price control (opens in a new tab); a US utility's to the positions it defends before FERC (opens in a new tab) or its state commission and to the reliability obligations NERC (opens in a new tab) standards impose; a European TSO's to the network-code world coordinated through ENTSO-E (opens in a new tab). The point is not name-dropping frameworks — it is that each of these regimes eventually asks the utility to evidence a quantified claim, and a register row with baseline, holdout and KPI is precisely that evidence in draft form. Alignment done properly makes the regulatory conversation cheaper as a by-product. How the funded rows are then classified and treated financially is its own discipline — the subject of the CFO budgeting page in this cell.

Why alignment fails: four pathologies and a triage rule

The recurring failure patterns that keep utilities at stage 2 — and the two-axis triage that decides what deserves a place in the portfolio at all.

Alignment fails in patterned ways, and none of the patterns is a modelling problem. Across utilities the same four pathologies account for most of the gap between the strategy on the wall and the portfolio in flight — each one locally rational, each one invisible from inside, and each one fixable with a structural change rather than a better model or a better document.

  • The parallel AI strategy

    The organisation writes a strategy about AI instead of writing AI into the strategy. Two documents now exist, each internally coherent, connected by vocabulary rather than by mechanism. Every funding paper cites the AI strategy; the corporate strategy's trajectory is unchanged. The fix is not merging the documents — it is retiring the parallel one and forcing every initiative to cite the corporate strategy directly, in its own words and KPIs.

  • The demo-driven portfolio

    Intake is where misalignment is manufactured. When initiatives enter through vendor demos, innovation days and sponsor enthusiasm, the portfolio's composition is decided by what is easiest to show, which correlates with nothing strategic. Generative assistants photograph well; storm-restoration switching support does not. A portfolio admitted on demo quality will systematically over-weight the visible and under-weight the load-bearing.

  • The calendar mismatch

    Strategy runs on refresh cycles and regulatory milestones measured in years; AI initiatives run on sprints measured in weeks. With no shared review point, the portfolio re-plans dozens of times between strategy contacts, drifting a little each time — nobody decided to misalign, and everybody watched it happen. The fix is a shared calendar with re-weighting authority, which is cadence work, not communication work.

  • Value reported in the wrong units

    A portfolio reporting MAPE, accuracy and adoption counts upward is invisible to strategy governance, whatever its real worth — boards steer in CML, EFOR, imbalance cost and cost to serve. Unit mismatch quietly demotes the AI conversation from a strategy item to a technology update, and technology updates do not move capital. Translation into strategic units, against baselines, is what buys the portfolio a seat at the table.

Portfolio triage: strategic weight against present feasibility

Score every live and proposed initiative on two axes and let the quadrant, not the sponsor, argue its case. The top-left quadrant is the one leadership teams systematically neglect — and for visionary ambitions it is the whole game: future-readiness is mostly present-readiness, and the right response to a commitment you cannot yet build is instrumentation, not a moonshot.

Instrument first

  • High weight, not yet buildable — the neglected quadrant
  • Fund the data, telemetry and baselines now
  • Every future ambition lands here first — readiness is the strategy

Commit and wire

  • High weight, buildable now
  • Complete the register row and fund to submission-grade evidence
  • These threads underwrite external commitments

Decline politely

  • Low weight, hard to build — the demo pile
  • No register row, no funding, however good the show
  • Revisit only if the strategy changes

Opportunistic, capped

  • Low weight, cheap to do — real but modest value
  • Cap the share of portfolio spend (a fifth is a common ceiling)
  • Never allowed to crowd the top row
Strategic weight — top: Carries a strategic commitment, bottom: Peripheral to any commitment
Present feasibility — left: Data or integration not yet in place, right: Buildable against today's estate

The triage matrix earns its keep on the ambitions that sound like the future — autonomous grid operation, fleet-wide self-optimising assets, AI-native system operation. The disciplined reading of every such ambition is the top-left quadrant: what is real today is decided by physics, certification and the regulatory frame, and what a leadership team can actually fund now is the instrumentation, baselines and evidence machinery that any future version would require anyway. A utility that builds the boring quadrant discovers it has also built most of the exciting one — which is the honest version of future-proofing, and the register keeps everyone honest about it. How leadership then carries these portfolio decisions into the estate — sites, control rooms, unions — is the roadshow page's territory; the recurring decision procedures they run through are the playbooks page's.

The alignment operating system, layer by layer

What actually has to exist at each stage of the ladder — from strategy artefacts to the evidence loop — and which layer you can defer.

A steered portfolio requires five layers, and the order in which you build them decides whether alignment compounds or performs. The architecture below is deliberately vendor-free: every layer is defined by what it must guarantee, and most of its components are documents, calendars and rules rather than software. That is the point — alignment is an operating system for decisions, and the models are only its instruments.

Layers of the alignment operating system, annotated by stage

Each layer is annotated with the ladder stage that first requires it. A utility trying to reach Steered without the translation and evidence layers is a Referenced utility with better meetings.

  1. Strategy artefacts

    Stage 1+

    • Corporate strategy & scenariosThe objectives everything must trace to, in their own words
    • Regulatory commitmentsPrice-control business plan, rate-case positions, IRP — strategy in auditable form
    • Assumption baseDemand, asset condition, flexibility value — what the strategy believes about the world
  2. Translation layer

    Stage 2+

    • Objective decompositionEach objective broken into named decision levers with systems and owners
    • Traceability registerOne row per funded initiative: objective, lever, KPI, baseline, owner
    • Triage scoringStrategic weight × present feasibility, applied at intake
  3. Portfolio governance

    Stage 3+

    • Single intake and kill pathNo funding without a complete row; orphan review on a calendar
    • The shared calendarPortfolio reviews inside strategy governance, timed to regulatory milestones
    • Re-weighting authorityThe forum can move capital between objectives, and does
  4. Delivery & evidence

    Stage 3+

    • System-of-record integrationInitiative output lands in ADMS, OMS, EAM, market systems — where decisions happen
    • Attribution machineryBaselines before go-live, holdout fleets and feeders, agreed benefit rules
    • Benefits registerValue in strategic units, at a standard a hostile reader would accept
  5. Evidence flow-back

    Stage 4+

    • Assumption watchlistLoad-bearing assumptions, each with a model-evidence feed and a tripwire
    • Evidence briefsBounded statements of what the models observe, as standing strategy inputs
    • Refresh integrationStrategy refresh formally consumes the portfolio's evidence, every cycle

Pipeline described

  1. Strategy artefacts (stage 1+) — Corporate strategy & scenarios: The objectives everything must trace to, in their own words; Regulatory commitments: Price-control business plan, rate-case positions, IRP — strategy in auditable form; Assumption base: Demand, asset condition, flexibility value — what the strategy believes about the world
  2. Translation layer (stage 2+) — Objective decomposition: Each objective broken into named decision levers with systems and owners; Traceability register: One row per funded initiative: objective, lever, KPI, baseline, owner; Triage scoring: Strategic weight × present feasibility, applied at intake
  3. Portfolio governance (stage 3+) — Single intake and kill path: No funding without a complete row; orphan review on a calendar; The shared calendar: Portfolio reviews inside strategy governance, timed to regulatory milestones; Re-weighting authority: The forum can move capital between objectives, and does
  4. Delivery & evidence (stage 3+) — System-of-record integration: Initiative output lands in ADMS, OMS, EAM, market systems — where decisions happen; Attribution machinery: Baselines before go-live, holdout fleets and feeders, agreed benefit rules; Benefits register: Value in strategic units, at a standard a hostile reader would accept
  5. Evidence flow-back (stage 4+) — Assumption watchlist: Load-bearing assumptions, each with a model-evidence feed and a tripwire; Evidence briefs: Bounded statements of what the models observe, as standing strategy inputs; Refresh integration: Strategy refresh formally consumes the portfolio's evidence, every cycle
Step-by-step insights
Strategy artefacts — the assumption base is the neglected component
Most utilities have the first two components and not the third: the strategy's assumptions live implicitly in planning models and consultants' appendices rather than as a named, owned list. Extracting them into an explicit assumption base is half a day's work with the strategy team and it is the precondition for everything in the fifth layer — you cannot build a watchlist over assumptions nobody has written down. Do it early; it costs nothing and reveals plenty.
Translation layer — decomposition is a workshop, not a document
Objective decomposition works when the people who take the decisions are in the room: the control-room manager knows which switching decisions actually move CML, the fleet engineer knows which intervention intervals actually move asset risk. Run it as a working session per objective — objective on the wall, decisions listed, systems and owners named — and the register's rows write themselves. Run it as a strategy-office desk exercise and you get levers no operator recognises, which is how registers lose their audience.
Portfolio governance — the kill path is the layer's licence
Governance that cannot kill is decoration. The single most diagnostic artefact in this layer is the minute of the last strategically motivated kill: it proves intake scoring binds, the orphan review has teeth and re-weighting authority is real. Utilities standing this layer up should engineer an early, visible, low-drama kill — a genuinely orphaned initiative, handled respectfully, with the freed budget visibly re-deployed — because the second kill is politically half the price of the first.
Delivery & evidence — attribution is a regulatory asset, not overhead
Baselines-before-go-live and holdout fleets read as scientific fussiness until the first price-control or rate-case challenge, at which point they are the difference between a commitment that survives scrutiny and one that gets re-priced. Utilities operating under RIIO-style incentive regimes or commission review should treat the attribution machinery as pre-built regulatory evidence — which also means involving the regulation team in designing it, so the standard it meets is the standard that will eventually judge it.
Evidence flow-back — governance frameworks give the loop its guardrails
The loop's risk is unexamined model evidence steering capital, and the emerging AI-governance standards are precisely the countermeasure: the NIST AI Risk Management Framework's govern-map-measure-manage disciplines and an ISO/IEC 42001-style management system give evidence briefs their required provenance — model lineage, validation status, known limitations — before they reach a strategy forum. A utility already building these controls for compliance reasons should notice they are the same controls the alignment loop needs, and build once.

Two of the layers deserve named external anchors. The evidence disciplines in the fourth layer are what the NIST AI Risk Management Framework (opens in a new tab) formalises as measurement and management functions, and the organisational machinery of the fifth is what an ISO/IEC 42001 (opens in a new tab) AI management system certifies the existence of. Neither framework mentions strategy alignment by name — but a utility that can pass an audit against them has incidentally built the provenance, ownership and review machinery this page's ladder requires from stage 3 upward. Sector research bodies are converging on the same point: EPRI's (opens in a new tab) AI programme work treats governed, evidenced deployment as the precondition for utility-scale value, not an afterthought to it.

A 90-day plan: aligning the portfolio behind one reliability commitment

The stage 2 → 3 transition made concrete on one distribution-utility problem — customer minutes lost on worst-served rural feeders — with no new models built and no document written.

Moving one stage takes about ninety days when it is scoped to a single strategic commitment, and multiple years when it is scoped to 'alignment' in general. The plan below runs the transition on a specific, common energy problem: a distribution utility whose price-control submission commits to reducing customer minutes lost, whose worst-served rural feeders drive the penalty exposure, and whose AI activity — a vegetation-risk model here, a fault-prediction pilot there, a storm-rostering spreadsheet somewhere else — has never been assembled behind that commitment. The quarter contains no model development: everything needed already exists, unaligned.

Referenced to Mapped on one CML commitment, in one quarter

One commitment, one register, one holdout design, one aligned review. If any phase needs more than its window, narrow the scope — fewer feeders, one lever — rather than extending the plan.

  1. Days 1–15

    Write the thread for the commitment

    Take the CML commitment from the submission and decompose it with the control-room and vegetation teams: which recurring decisions move CML on the worst-served feeders — restoration switching sequence, vegetation clearance prioritisation, storm crew pre-positioning. Pull three years of interruption history from the OMS by feeder to baseline CML and SAIDI, and name the owner: the head of network operations, because CML is already their number.

    One decomposed objective, a feeder-level baseline, one named owner

  2. Days 16–40

    Inventory the portfolio against the thread

    List every AI initiative in flight, however small, and attempt a register row for each against the CML thread and the wider strategy. Expect a quarter to fail. Triage the orphans on the weight-by-feasibility matrix in an executive session — kill, cap or re-scope — and minute the outcomes. The vegetation model and the fault-prediction pilot will almost certainly complete rows; the point is that this is now demonstrated rather than assumed.

    A complete register for the live portfolio, and a minuted orphan decision list

  3. Days 41–70

    Wire the two initiatives that serve the commitment

    Route the vegetation-risk scores into the work-management queue in the EAM, and the fault-prediction output into the OMS view the control room already uses for switching — no new screens. Designate a comparable holdout feeder set with the regulation team so the CML delta will be attributable at submission grade, and agree the benefit rule in writing before go-live.

    Two threads landing in systems of record, holdout designed, benefit rule signed

  4. Days 71–90

    Run the first aligned review on the strategy calendar

    Hold the portfolio review inside the executive strategy forum rather than the AI steering committee, timed against the next regulatory milestone. Report the two wired threads in CML terms against baseline, confirm the orphan decisions, and table the first evidence note: what feeder-level data says about the submission's assumptions. Book the next review on the same calendar before leaving the room.

    Portfolio governance merged into strategy cadence, with a standing next date

The order matters

  1. Commitment before inventory

    Inventorying the portfolio first invites every initiative to argue its own importance in the abstract, which is unwinnable. Fixing one commitment first gives the inventory a question to answer — does this serve the thread? — and the orphan conversation becomes factual rather than existential.

  2. Register before triage

    Attempting the row is the triage: an initiative that completes one has made its case in the strategy's own vocabulary, and one that cannot has made the opposite case in its own words. Scoring before attempting rows lets rhetoric outrun evidence.

  3. Attribution design before go-live

    The holdout feeders and the benefit rule must be agreed — with the regulation team — before the wired initiatives start moving the number. Attribution designed afterwards inherits the initiative's own effects, and the CML delta becomes an argument instead of a fact.

  4. One commitment before the estate

    The temptation at day 90 is to scale the register to everything at once. Resist it: run the second commitment — asset-health, say, or connections — through the same machinery next quarter. The register generalises from worked examples at a pace the politics can absorb.

Verifying alignment: metrics and the audit checklist

Alignment claimed is not alignment. The measurable signals a leadership team can read quarterly — and the seven-point audit you can run against your own artefacts this week.

Alignment is verifiable because every element of the thread leaves an artefact: register rows, funding minutes, calendars, evidence packs, strategy-forum agendas. The metrics below are readable from those artefacts rather than from anyone's self-assessment, which is what makes them worth a board's attention — each one has a defined source, a sensible cadence, and a stage at which it first becomes meaningful.

MetricHow it is readSource artefactCadenceHonest from
Register coverageShare of AI spend carrying a complete register rowRegister vs finance ledgerQuarterlyStage 2
Strategic-unit reportingShare of initiatives reporting value in a KPI the strategy commits toPortfolio review packsQuarterlyStage 3
Kill throughputInitiatives killed, merged or re-scoped for strategic reasonsOrphan review minutesHalf-yearlyStage 3
Attribution gradeShare of claimed benefits measured against a pre-agreed baseline and holdoutBenefits registerHalf-yearlyStage 3
Calendar convergencePortfolio reviews held inside strategy governance vs outside itMeeting calendars and minutesQuarterlyStage 3–4
Commitment linkageExternal commitments explicitly priced on portfolio evidenceSubmissions and evidence packsPer regulatory cycleStage 4
Re-weighting latencyDays from strategy change or determination to portfolio re-planForum minutes vs decision datesPer eventStage 4
Assumption revisionsStrategic assumptions formally revised on model evidenceWatchlist log and strategy minutesYearlyStage 5
The alignment measurement sheet. 'Honest from' is the ladder stage at which the metric first measures something real — reporting register coverage before a register exists is theatre.

The alignment audit: seven checks against your own artefacts

Run this against documents, not opinions — every item is checkable in an afternoon with the register, the minutes and the calendars in front of you. Tick as you go; the list works without JavaScript.

0 of 7 ticked

Nothing ticked — start with one thread, not a programme

A blank sheet here usually means stage 1–2: activity, a document, no mechanism. Do not respond with a bigger document. Pick one strategic commitment and run the 90-day plan above — the first complete thread produces the artefacts that let you tick items one, two and three within a quarter.

Failure modes that unwind alignment

Alignment is not monotonic. Four regressions account for most of the ground utilities lose — all of them silent, none of them technical.

Alignment regresses without announcing itself, because every artefact keeps existing after it stops working: the register still renders, the committee still meets, the document still says what it said. Four patterns account for most of the regression we see, and each has a cheap structural prevention that costs far less than the rebuild.

Likelihood: highImpact: high

The reorganisation that orphans the register

The register was built and championed by a person; the person moves on or the strategy office is restructured, and within two quarters the rows are stale, funding papers stop citing them, and the portfolio quietly reverts to sponsor-driven intake. Nothing was decided — ownership just evaporated, which is how most stage-3 utilities become stage-2 utilities without noticing.

PreventionOwn the register by role, not by name — and put its handover in the leaver checklist, like system credentials.

Likelihood: mediumImpact: high

The strategy refresh that ignores the portfolio

A new CEO or a new strategy house rewrites the objectives, and the register's entire objective column points at retired language overnight. If the portfolio is re-justified by lobbying rather than re-mapped by method, the refresh converts a mapped portfolio into a referenced one in a single planning cycle — with everyone's goodwill intact.

PreventionA standing refresh rule: every register row re-maps to the new objectives within one quarter, and unmappable rows go to the orphan review, no exceptions.

Likelihood: mediumImpact: medium

The regulatory cycle turning the register into theatre

The submission deadline approaches, the register is polished into evidence, the determination lands — and the register stops being updated the week the pressure lifts. Alignment built for a filing dies after the filing; the artefact survives as a snapshot that slowly becomes fiction, more dangerous than no register because it is still believed.

PreventionWire the register to funding gates, which run continuously, rather than to submissions, which run every five years.

Likelihood: mediumImpact: high

Faithful alignment to a stale strategy

The subtlest failure: the thread holds perfectly, but the strategy it serves has been overtaken — load growth from data centres, electrification clustering, flexibility value moving faster than the refresh cycle. The portfolio diligently optimises yesterday's problem, and every governance check passes while the world walks away. This is the failure the evidence loop exists to catch.

PreventionStand up the assumption watchlist even at stage 3 — a thin version costs a week and turns strategic staleness from a surprise into a tripwire.

Glossary

Hover a term for its definition — or expand the map full screen. The full definitions are written out below.

Strategic thread
The complete chain from strategic objective through decision lever, AI initiative and system of record to a strategic KPI and, ultimately, regulatory evidence. The unit in which alignment is built, checked and audited.
Traceability register
The table with one row per funded AI initiative recording its objective, decision lever, KPI, baseline, attribution method and owner. Alignment's enforcement point when wired into funding gates — and its museum when not.
Decision lever
A specific, recurring operational decision that moves a strategic objective — named with the system it is taken in and the role that takes it. The translation step between strategy language and buildable work.
Orphan initiative
A funded AI initiative that cannot complete a register row after honest effort — no named objective, decision or provable KPI. Orphans are killed, merged or re-scoped at a calendared review, not left to expire with their budgets.
Portfolio triage
Scoring every live and proposed initiative on strategic weight and present feasibility, letting the quadrant argue instead of the sponsor. The top-left quadrant — heavy but not yet buildable — is funded as instrumentation.
Governance cadence
The calendar discipline of alignment: portfolio reviews held inside strategy governance, timed against strategy refresh and regulatory milestones, with real authority to move capital between objectives.
Evidence flow-back
The reverse half of alignment: model-derived evidence about demand, assets and flexibility reaching strategy formation through watchlists and evidence briefs, rather than staying inside operations.
Assumption watchlist
A register of the strategy's load-bearing assumptions, each with a named model-evidence feed and a numeric tripwire that forces formal review when reality drifts — the mechanism that catches strategic staleness between refresh cycles.
Submission-grade evidence
Benefit evidence held to the standard a price-control review, rate case or IRP proceeding would apply: baseline struck before go-live, holdout agreed, method written down. The precondition for pricing external commitments on AI capability.
Holdout
A comparable set of feeders, plants or customer cohorts deliberately kept on the previous process so an improvement can be attributed to the initiative rather than to weather, load or coincidence.
CML
Customer minutes lost — the GB measure of average interruption duration per customer, carrying direct incentive and penalty exposure inside RIIO price controls. The strategic KPI in this page's worked examples.
Price control
The periodic regulatory settlement (RIIO in GB; rate cases and IRPs elsewhere) fixing a network utility's allowed revenues against committed outputs — the moment a utility's strategy becomes quantified, auditable and externally enforced.

Frequently asked questions

The questions utility leadership teams ask most often when they start pulling on the thread.

What is AI energy strategic alignment?

AI energy strategic alignment is the discipline of making a utility's AI portfolio and its corporate strategy answer to each other: every funded initiative traceable to a named strategic objective through a decision lever and a KPI the strategy commits to, and strategic assumptions revised on the evidence the models produce. It is a property of the portfolio rather than of any model, and it is measured by traceability — complete register rows, attributed value, a shared governance calendar — not by how prominently AI features in the strategy document.

Isn't having an AI strategy the same thing as alignment?

No — and the difference is the most common trap on the ladder. An AI strategy document restates corporate ambitions with AI vocabulary; alignment is a mechanism that changes which initiatives get funded, how their value is measured and when capital moves between them. A utility can hold an excellent document and a wholly misaligned portfolio, because the document constrains nothing. The test is behavioural: if the AI strategy disappeared tomorrow, would any funding decision change? For most utilities the honest answer is no, which places them at stage 2 of this page's ladder.

Who should own AI–strategy alignment in a utility?

The strategy office should own the mechanism — register, triage, calendar, watchlist — with finance enforcing it at funding gates and operations owning each row's KPI. That triangle matters: a register owned by the data function becomes a technology inventory nobody consults; one owned by finance becomes cost control; one owned only by strategy becomes a document. The accountable executive for portfolio composition should be whoever answers to the board for strategy delivery, precisely so the AI conversation cannot be delegated to a technology update.

How do we align AI initiatives with a strategy that is itself changing?

By aligning to the strategy's assumptions as well as its objectives. Objectives change at refresh cycles, and the register re-maps within a quarter under a standing rule. Assumptions change continuously — demand outlooks, asset-condition trajectories, flexibility value — which is what the assumption watchlist exists for: each load-bearing assumption carries a model-evidence feed and a tripwire that forces review when reality drifts. A portfolio wired this way does not need a stable strategy; it needs a strategy whose movements it can detect and respond to on the record.

What belongs in a traceability register row?

Seven fields: the strategic objective in the corporate strategy's own words; the decision lever — the recurring decision, its system and its owner; the initiative and its delivery state; the strategic KPI with its baseline and the date it was struck; the attribution method, usually a named holdout; the accountable operations owner; and the review date. The register's power is the rule attached to it — no complete row, no funding — so keep rows short enough that completing one is an afternoon's honest work, not a documentation project.

How does the regulatory cycle affect AI strategic alignment?

It is the strongest alignment mechanism a utility has, because it forces strategy into quantified, auditable form on a fixed calendar. A price-control business plan, a rate case or an IRP is the corporate strategy with numbers attached and a hostile reader guaranteed — exactly what a register's far end needs. Steered utilities draft submission commitments from portfolio evidence and re-plan the portfolio when determinations land, in both directions on the same dates. Utilities that ignore the regulatory calendar until submission year then discover their evidence has no baselines, which is a two-year problem discovered with one year to run.

In what units should an AI portfolio report value to a utility board?

In the KPIs the strategy itself commits to — CML and SAIDI for reliability, EFOR for fleet availability, forecast error translated into imbalance and balancing cost, cost to serve for retail — each against a baseline and, wherever possible, a holdout. Model metrics such as accuracy or MAPE are engineering telemetry: essential inside the team and meaningless to capital allocation. The translation is the portfolio's job, not the board's; a board asked to interpret model units has been handed someone else's homework, and it will respond by treating AI as a technology update rather than a strategy item.

What is an orphan initiative and should we always kill them?

An orphan is a funded initiative that cannot complete a register row after honest effort — it cannot name an objective in the strategy's words, a specific decision, or a provable KPI. Not all orphans die: the calendared review kills some, merges duplicates, and re-scopes the salvageable onto genuinely unserved objectives, which is often the most valuable outcome. What must not happen is orphans persisting by default because nobody owns the question. A portfolio that has never killed anything for strategic reasons is not aligned — it is unexamined.

Does strategic alignment kill exploration and R&D?

No — it gives exploration a budget and a boundary instead of a disguise. The triage matrix caps an opportunistic share of the portfolio, commonly around a fifth, for cheap, low-weight work that keeps teams learning; and the instrument-first quadrant funds the data and baseline work behind ambitions that are not yet buildable, which is where genuine research belongs. What alignment removes is exploration's camouflage: the demo-driven initiative that consumes a strategic budget while carrying no strategic weight. Bounded exploration survives scrutiny; disguised exploration eventually costs the whole portfolio its credibility.

How do ISO/IEC 42001 and the NIST AI RMF relate to strategic alignment?

They are the governance envelope the alignment machinery runs inside, not substitutes for it. The NIST AI Risk Management Framework disciplines how models are mapped, measured and managed; ISO/IEC 42001 certifies that an organisation-level AI management system exists with ownership, review and improvement loops. Neither asks whether the portfolio serves the strategy — that is this page's question — but both build the provenance and control machinery that evidence briefs and submission-grade attribution depend on. A utility pursuing certification anyway should design once: the same controls satisfy the auditor and power the alignment loop.

How long does it take to reach Mapped, and what does it cost?

Roughly a quarter for the first thread and a year for the estate, scoped the way the 90-day plan on this page is scoped: one strategic commitment, the live portfolio registered against it, two initiatives wired to systems of record with holdout attribution, and the review moved onto the strategy calendar. The cash cost is modest — the register, triage and calendar are documents and meetings — and the real price is political: the first orphan review creates losers with sponsors. Utilities that budget for that conversation reach Mapped in two funding cycles; utilities that avoid it refresh their documents instead.

We are a small municipal or cooperative utility — does this ladder still apply?

Yes, and it compresses well. A small utility's register might be fifteen rows, its triage a half-day session, and its 'strategy governance' the same six people who run everything else — which is an advantage, because the calendar merge that costs a large utility a year of committee politics is one agenda decision. The parts that do not shrink are the tests: named objective, named decision, provable KPI with a baseline. NB Power's publicly documented grid-modernisation portfolio, read against this page's ladder in the case studies above, shows a provincial-scale utility making the thread legible in public.

About the author

Atomic Loops Engineering

Industrial AI practice

Atomic Loops builds production AI systems for energy, manufacturing and logistics operators — load and generation forecasting, asset-health scoring, outage prediction and decision support running against live operational data, integrated into the ADMS, EAM and market-systems layer rather than delivered as dashboards.

  • · Production deployments across generation, networks and energy retail
  • · Portfolio and maturity assessments run jointly with utility leadership teams
  • · Integration-first delivery: system-of-record write-back, monitoring, rollback
  • · 13 cited sources on this page

Sources

  1. International Energy AgencyEnergy and AI (opens in a new tab)
  2. IRENAWorld Energy Transitions Outlook (opens in a new tab)
  3. EPRIEPRI research programme (incl. Powering Intelligence, data-centre load scenarios) (opens in a new tab)
  4. US Energy Information AdministrationElectricity data and analysis (opens in a new tab)
  5. EurelectricPower sector strategy and digitalisation work (opens in a new tab)
  6. OfgemNetwork price controls 2021–2028 (RIIO-2) (opens in a new tab)
  7. FERCFederal Energy Regulatory Commission (opens in a new tab)
  8. NERCReliability standards and oversight (opens in a new tab)
  9. ENTSO-EEuropean network of transmission system operators (opens in a new tab)
  10. NISTAI Risk Management Framework (opens in a new tab)
  11. ISOISO/IEC 42001 — AI management systems (opens in a new tab)
  12. AESThree ways AES and Google are innovating the energy industry of the future (opens in a new tab)
  13. NB PowerGrid Modernization — Building Tomorrow's Grid (opens in a new tab)

Find out where your thread breaks — then fix that break first

We run the assessment with your strategy office and engineering leads, walk one strategic objective end to end against your real artefacts, and leave you with the draft register, the orphan list and a costed 90-day plan for your weakest dimension. You keep all of it whether or not we build anything.

Published · Last updated

Benchmark request

Tell us where to send it

Benchmark for this page

Used once, to send this benchmark and follow it up personally. No newsletter, no automated sequences.