Building an Automation Strategy

Executive perspective

How do we move from a list of use cases to a funded, sequenced program is the question that stalls most automation efforts, even after leadership has correctly identified where the opportunity lies. A ranked list is analysis. A program is a recurring operating discipline with owners, budgets and dates.

Many organizations treat automation as a portfolio of one-off projects, each pitched and funded separately. That approach produces isolated wins and very little institutional muscle for finding the next one.

The organizations that build durable advantage instead treat automation as an ongoing operating rhythm — a repeating cycle with the same steps, the same cadence and the same accountability, applied to a constantly refreshed pipeline of opportunities.

Business context

A regional bank spent a year building a strong business case for automating loan document review, secured funding, delivered it well, and then had no process for identifying what to fund next. The team that built the first win was reassigned, and momentum stopped.

A national utility took a different path: it created a standing quarterly review where new candidate processes were scored, prior initiatives were measured against their original targets, and underperforming initiatives were formally retired rather than left to quietly decay. Three years in, the utility had a portfolio of over twenty live automations, not one showcase project.

The difference was not better use cases. It was a repeating operating rhythm that treated automation as an ongoing capability rather than a sequence of individual projects.

The core insight

A strategy is not a document that ranks opportunities once. It is a recurring cadence that keeps finding, funding, delivering, measuring and retiring initiatives on a fixed schedule, with named owners at every stage.

A prioritized list is a snapshot. A strategy is a rhythm that keeps producing new snapshots on its own schedule.

This is the practical complement to a broader strategic framework: where an enterprise strategy canvas sets direction and priorities across the organization, the operating rhythm below is what turns that direction into delivered automation, quarter after quarter.

The Automation Operating Rhythm

Five stages, run on a quarterly cadence, each with a named owner. No initiative skips a stage, and no stage runs without a decision at the end of it.

Discover

Owner: business unit leaders, supported by a central automation team. Each quarter, business units nominate candidate processes using the opportunity criteria already in place. This keeps the pipeline fed from the people closest to the work, not only from a central team.

Qualify

Owner: a cross-functional review board including finance, risk and the sponsoring business unit. Candidates are scored, sized and checked against governance requirements before any funding is committed. This is where marginal ideas are filtered out before they consume delivery capacity.

Deliver

Owner: a named delivery lead accountable for a fixed-length build, typically within a single quarter. Delivery is scoped tightly enough to show a result within the quarter, even if full rollout continues afterward.

Measure

Owner: the sponsoring business unit, reporting against the target set during qualification. Every initiative is measured against the number it was funded on, not against a new, more flattering metric invented after the fact.

Retire

Owner: the review board. Initiatives that miss their targets after a fair trial are formally closed, and the capacity is reallocated. This stage is the one organizations most often skip, and skipping it is what quietly fills a portfolio with underperforming initiatives no one wants to discuss.

How often should an automation portfolio be reviewed?

Quarterly is generally the right cadence: frequent enough to keep momentum and catch underperformance early, but not so frequent that delivery teams spend more time reporting than building.

What this looks like in practice

An insurer runs its qualify stage as a ninety-minute quarterly session where finance and risk sit with each business unit, and no initiative proceeds without a named delivery lead and a measurable target.

A telecom operator formally retires two automation initiatives in its second year, freeing capacity that is redirected to a higher-scoring opportunity discovered in the same quarter's review.

A manufacturer times its discover stage to align with its annual operating plan, so new automation candidates are nominated alongside regular budget requests rather than as separate, competing asks.

A hospital network assigns a single accountable executive to the measure stage across all automation initiatives, ensuring that every result is reported against its original target rather than a revised, softer one.

Executive checklist

• Do we have a recurring cadence for discovering new automation candidates, or does the pipeline depend on individual champions?
• Is every live initiative assigned a named owner at each of the five stages?
• Does our qualify stage include finance and risk before funding is committed?
• Are we measuring initiatives against the target set at funding, or against a target set after delivery?
• Have we ever formally retired an underperforming initiative, or do they simply fade from view?
• Is delivery scoped tightly enough to show a result within a single quarter?
• Does this rhythm connect clearly to our broader enterprise strategy, or does it run as a separate exercise?

Key takeaways

• A ranked list of use cases is analysis, not a strategy; a strategy is a recurring operating rhythm.
• The five stages — discover, qualify, deliver, measure, retire — need a named owner and a fixed cadence.
• Retiring underperforming initiatives is as important to program health as launching new ones.
• Measuring against the original funding target, not a revised one, is what keeps the program honest.
• A quarterly cadence generally balances momentum against reporting overhead well.

Continue reading

Next article: Scaling Automation Across the Enterprise. With a working operating rhythm in place, the next challenge is why momentum typically stalls after the first wave of wins, and how to design past it.