Skip to content
Edition 1 ReferenceDownloads Search Start here
Search
PlayP12 Transformation · Implementation and scale · Editorial rank 12 of 12

Replicate useful work and retire operating debt

Useful pilots remain isolated while old reports, processes and tools continue consuming capacity and cost.

Decision
Repeat, adapt, maintain, simplify or retire the workflow and its predecessor?
Primary commercial metric
Net realised value after replication, support, transition and retirement cost, with no duplicate benefit booking.
Readiness
Proven workflow first
Agent role
No new agent required for replication; inherited agent permissions are re-evaluated for the target context.
01

Fit

When to use this Play

A workflow has credible value and reliable operation, with another justified user or an obsolete predecessor to retire.

When not to use it

The result is immature, economics fail against the best alternative, or no owner can support the second context.

Why it should work

Controlled replication reuses proven work; deliberate retirement realises savings and limits operating complexity.

Basic version

One second user or population, explicit support and closure of one obsolete report/handoff/tool.
02

Prepare

Required maturity
Basic proof and a funded owner; Connected for shared services. Ready with transfer assumptions and a fallback. Not ready merely because a pilot demo succeeded.
Check readiness for P12 (D02)

Inputs

Signed readout, costs, source/target population differences, workflow version, control tests, support roster, old-work inventory and export/exit needs.

Audience or customer

The next team or eligible population and the people responsible for ongoing operation.

Human role

Business owner owns value and acceptance; Operations owns transition and fallback; Finance verifies expense action; functional managers release capacity.

Systems required

Existing workflow, documentation, access and work-tracking tools; shared service only with funded recurring users.

Guardrails

Continuity, recoverability, preserved records, lawful retention, absence cover and no forced transfer of invalid evidence.

How to configure a Play

Copy the Play you need and complete only the relevant parts of T1–T5. Name the people responsible, define the customer group, agree economic and customer limits, and set a review date before starting. An empty decision threshold is not permission to act. Basic, Connected and Advanced describe how the work is configured; Experimental describes its evidence. AI is optional: compare each AI step with a simpler way of doing the same work.

03

Do the work

Intervention

One bounded replication and a dated retirement of genuinely replaced work.

Workflow

  1. Review proof and transfer limits.

  2. Price replication and ongoing support.

  3. Assign owner/cover.

  4. Train through actual work.

  5. Run a capped release.

  6. Verify quality and economics.

  7. Retire the predecessor safely.

  8. Review continued use and cost.

AI role

Optional assist Optional documentation and training drafts grounded in the approved workflow; no evidence promotion or deletion authority.

Automation role

Version distribution, monitoring, access revocation, archive/export checks and review reminders.

Agent role

No new agent required for replication; inherited agent permissions are re-evaluated for the target context.

Failure modes

  • Scaling before outcomes mature
  • permanent dual run
  • new titles without workload
  • treating training attendance as competence.
04

Measure and decide

Measurement

Compare target-context quality, outcomes, cost and adoption; verify old expense/process closure rather than counting deployment alone.

Primary commercial metric

Net realised value after replication, support, transition and retirement cost, with no duplicate benefit booking.

Leading indicators

Useful active use, task competence, incident/review load, completed retirement and reduced duplicate work.

Experiment

Small target-context comparison or staged rollout appropriate to risk; rehearse fallback and verify replacement before ending dual run.

Guardrails

Continuity, recoverability, preserved records, lawful retention, absence cover and no forced transfer of invalid evidence.
Scale when
Repeat again only when transferability and economics hold and service ownership can support the next unit.
Stop / reassess when
Revert or retire on failed transfer, unowned maintenance, native replacement superiority, low useful demand or negative ongoing value.
05

Learn and progress

Learning

Record adaptation, local validation, support cost, benefits actually realised, decommissioning and reasons for retirement.

Practical tool

Next action
identify exactly what old work ends if the new workflow is adopted.
Open T2 Economics and benefits ledger
06

Optional depth

Advanced versionPrerequisites: see Required maturity above.

Reusable platform services, persistent teams or dedicated roles only when recurring demand and net coordination value justify them.

Evidence for this Play1claim reviewed, with confidence ratings, limits and sources.

Claim classifications

Accepted means a principle or mechanism survived critical review, not that it guarantees a return. Accepted with conditions means prerequisites apply. Qualified means the original claim has been narrowed. Advanced needs substantial readiness. Experimental needs a capped comparison. Unresolved means the evidence cannot settle the claim. Rejected means the recommendation is excluded.

High, Medium and Low describe confidence in the stated target, not the chance of a positive ROI. For a Qualified or Rejected historical claim, confidence applies to the decision to narrow or reject it and to the supported limit—not to the original headline. Read the headline and classification together. An accounting identity or design principle is not empirical evidence of a commercial outcome. Follow the linked chapters, Plays and tools to see where each claim applies.