A decision can return
A cancelled course leaves a learner waiting for an alternative. The service first needs an agreed outcome and someone responsible for reaching it. A small process trial can then test the handover. A later finding about partner confirmation may reopen one responsibility while the learner-agreement rule and other sound decisions remain in place.
An architecture cycle is a recurring question, work to answer it, checks, an accepted result and feedback. Cycles can be nested or run alongside one another: a team may repeat several delivery cycles within a wider review of the service.
Four process areas
A Simple Architectural Framework (ASAF) describes four continuing areas of work across its aspects. Their names describe the work; a methodology decides how to organise its stages, reviews and iterations.
| Process area | Work | In the course example |
|---|---|---|
| Visioning | Describe the intended or ideal future and the reasons for it. | Agree accepted resolution and continuous ownership as the intended outcome. |
| Transforming | Plan and introduce changes towards that direction. | Prepare the shared register, handover procedure and proposed trial checks. |
| Operating | Run, support and maintain current arrangements. | Handle cancellations, resolve uncertain outcomes and observe delays. |
| Governing | Set and review policy, authority, assurance and exceptions. | Agree who may accept a trial, change responsibility or decide a wider exception. |
These areas overlap. Governing continues around direction, change and operation. An operational finding can prompt a correction in Transforming, a policy decision in Governing or a reconsideration of the future in Visioning. The process-area guide distinguishes this work from the Process aspect and the level of design detail.
Recurring questions
Six recurring questions help connect work within and across the areas. A question may recur at several scopes and at different levels of detail.
| Question | Where it recurs |
|---|---|
| Purpose and outcomes | Visioning frames the result; Operating tests the assumptions and Governing reviews priorities. |
| Domain and organisation | Visioning considers future work; Transforming develops roles and information; Operating exposes gaps. |
| Architecture and blueprint | Visioning compares options; Transforming develops the affected design; Governing reviews shared constraints. |
| Delivery and experiment | Transforming introduces a change with operational readiness and agreed acceptance. |
| Operations and support | Operating handles the service; preparation and recovery checks also shape Transforming. |
| Assurance and learning | Governing sets required assurance; checks and observations occur across all four areas. |
A wider learning cycle asks whether a lesson should change shared guidance or remain local. Retain the actual situation, result, limitations and decision behind that judgement. One local success supplies a candidate lesson to examine.
Retained decisions
Record what remains agreed, the intended difference, affected records, accepting authority and required checks. A failed recovery rehearsal may reopen the storage arrangement and operating procedure. It need not reopen learner agreement or every component in the blueprint.
An artificial intelligence (AI) assistant can prepare alternatives, code, configuration and checks within that defined change. Its output returns to the same acceptance process. More generated candidates can increase review and rework; assess elapsed time to an accepted result as well as generation time. Preserve decisions and checks between turns so the solution can develop incrementally. The assessment guide distinguishes method effort from the quality of the resulting service.
Methodology configuration
Map these areas and questions to the activities, stages and reviews your team already uses. A service review might cover all four areas; a wider programme may coordinate separate reviews. Name the responsible roles, retained records and triggers that connect them. See Methodology configuration.
Dials
| Dial | What is being chosen? |
|---|---|
| Cadence | When work recurs: on an event, per increment, at a stage or on a review date. |
| Batch size | How much scope or change is considered together. |
| Coordination | How participants prepare, exchange and accept work. |
| Decision authority | What a person, team or tool may decide, and what must be referred. |
| Automation and checking | What tools may prepare or perform, and which checks and judgement support acceptance. |
| Learning reach | Whether a finding changes a local record, a shared design or wider guidance. |
Delivery arrangements
| Arrangement | How the cycles can fit together | Trade-off to examine |
|---|---|---|
| Predominantly staged | One large change cycle, with wider direction and design agreed before delivery; feedback can reopen a stage. | Earlier coordination of dependencies, with later feedback from use. |
| Incremental | Retain wider direction and shared decisions while introducing a succession of useful changes. | Earlier use of a smaller scope, with coordination during transition. |
| Agile or evolutionary | Short cycles revisit detailed decisions and use findings to select the next change. | Quicker feedback, with continuing effort to maintain shared meaning and support. |
| AI-assisted | Tools may shorten selected activities within any of these arrangements. | More candidates and faster checks where suitable, with acceptance, authority and recovery still defined. |
These are illustrative arrangements. Higher assurance can apply to any of them, with independent review and additional checks matched to the consequence of error.
The proposed trial
A possible setting is daily review of open cases and a trial review after two weeks, covering one provider-run cancellation path. Booking and course leads agree the handover. Staff act within the agreed learner-choice rule; shared responsibility changes return to the service owner. Begin with the manual record and the proposed ownership checks. The fictional trial remains unrun.
The business cycles develop these settings. The blueprint shows the connected design, and its change record follows a finding across the areas.