← BackSee all toolsAutomation Estate: Keep, Pilot or ReplaceWorking demo · sample data · shows a method I used, not a real event
Automation governance · weighted matrix

Automation Estate: Keep, Pilot or Replace

An inventory of running workflows, a weighted keep-or-replace matrix for the tool stack and a governed migration plan.

I ran a review like this when a consolidation question reached the executive team. Capabilities are generic and the scores are invented.

The inventory

What was running.

A snapshot of the workflow estate before the consolidation question was asked. Illustrative figures in the spirit of one real review.

77Workflows active in one snapshot
~40Only post a notification
89.6%Critical-flow success this weekTarget: 95%
24Stale, to prune
NotificationsData syncApprovalsAgent commandsScheduled reports

The decision

Keep, pilot or replace.

Choose a weighting. The same eight capabilities move between keep, pilot and replace as the priorities change. That is the point: the decision follows from the stated priorities, not from habit.

CapabilityReplace scoreVerdict
Team chat67
Replace
Identity and single sign-on8
Keep
Endpoint protection25
Keep
Remote device management25
Keep
Code hosting and tickets17
Keep
E-signature42
Pilot first
Compliance automation83
Replace
Workflow engine8
Keep
Why

Tap a row for the reasoning.

Each capability is scored 0 to 3 on four things: saving from replacing it, how much only it can do, migration risk and how much else depends on it. Weights change with the preset.

The pattern

Every workflow follows the same five steps.

  1. 1

    Trigger

    An event, a schedule or a message.

  2. 2

    Condition

    Is this case in scope and complete?

  3. 3

    Wait for approval

    A person approves anything that sends, spends or changes a record.

  4. 4

    Action

    The step runs under a service account.

  5. 5

    Notify and log

    The result and an audit trail, every time.

The migration

A governed transition.

  1. 30 days: pilot. Move one team and one external space. Measure what breaks.
  2. 60 days: roll out. After integrations and settings are validated.
  3. 90 days: read-only. Keep the old tool readable, then reduce licences.
  4. Archive properly. Restricted storage, chain of custody, retention rules. No default migration of private messages.

More in AI & Automation

See all tools