# OP-T03 — Change and readiness: completed example

Adrian Sutherland · Version 1.0 · Refreshed September 2026

© 2005–2026 Adrian Sutherland.
Source page: https://architectureportal.org/assets/organisation-process

Fictional teaching example. Proposed decisions and checks; actual results remain unknown.

## Process areas

A Simple Architectural Framework (ASAF) describes four continuing areas of work.

Proposed mapping for this fictional change. A review can cover several areas;
accepted decisions remain in place unless a finding reopens them.

| ASAF process area | Work in this example | Information to retain |
|---|---|---|
| Visioning | Agree how the service should work and what responsibility and capacity it needs. | Role design, work scope, service expectations and alternatives. |
| Transforming | Prepare procedures, access, cover and training; rehearse the proposed change. | Changed procedures, named cover, acceptance checks and recovery arrangements. |
| Operating | Handle cases, arrange cover and support staff within agreed rules. | Case history, handovers, waiting time and improvement proposals. |
| Governing | Set delegated authority and accept changes to shared roles, rules or exceptions. | Accepted responsibilities, policy decisions and review triggers. |

## Proposed change

OP-D1 (Accepted-transfer procedure) clarifies accepted transfer during the process-only internal cancellation trial. It addresses an offer reaching another team without anyone taking the next action. O1 (Accepted resolution), learner agreement and continuous ownership are retained.

## People and records

Update the procedure, role/cover assignments and I1 (Cancellation case record) transfer history together. The service owner accepts rules and readiness; the steward checks definitions; the coordinator arranges cover. Named maintainers and effective implementation date are pending.

For the proposed software increment, name the person who reviews AI summaries, the recovery and supplier contacts, and the business owner and maintainer of executable rules. The AI assistant cannot accept learner agreement or ownership.

## Readiness and trial

Rehearse with synthetic internal cases. Confirm access, skills, response targets and cover before using real cases. The service owner decides whether to start or pause the trial. If paused, the coordinator reviews every open assignment and arranges accepted cover; records and learner commitments remain available.

In the software proposal, a locally saved mobile action remains pending until accepted in the shared record.

## Checks and observations

OP-V1 (Handover checks) checks unaccepted, inaccessible, unavailable, changed and conflicting handovers plus learner rejection. All remain unrun. Record waiting time, repeat contact, unresolved gaps, workload, correction effort and training needs. No benefit or baseline has been measured.

## Operating arrangements and change

Replacing a component may alter access, support or recovery. Review those arrangements while retaining the agreed acceptance rules. A changed service scope may require the rules themselves to change.

## Methodology configuration

Place these questions in existing change acceptance and service reviews. One review may agree staff readiness and procedure acceptance while a separate delivery review checks software.

## History and open decisions

Version 1.0, September 2026. Trial not run. Named staff, response targets, capacity, access, retention and actual implementation remain open. Partner confirmation stays the earlier L1 (Partner confirmation gap) issue outside the initial trial.