Using the records
Use these records in an existing document or repository, or download them as a starting point. Markdown files open in an ordinary text editor; the comma-separated values (CSV) relationship table opens in a spreadsheet. The blank and completed copies use the same headings; the examples answer the blank records’ prompts.
Combine, rename or omit fields to suit the scope. Several concerns may belong in one existing record; one concern may be distributed across several.
Business intent and scope
Record the decision needed, affected people and services, intended outcome, principles, scope, assumptions, owner and questions for judging results. The business owner maintains it when purpose or constraints change.
Business architecture and relationships
Connect capabilities, value streams, processes, roles, information and rules. Show current and proposed arrangements and the relationships affected by a change. Keep stable identifiers where they make later decisions traceable. Named owners maintain the affected definitions and records.
- Blank architecture record — Markdown
- Completed architecture record — Markdown
- Blank relationship table — CSV
- Completed relationship table — CSV
Cycles, decisions and change
Record the trigger, accepted starting position, options, decision authority, affected records, checks, handover and next review trigger. Map the cycles to your method’s meetings and activities. Preserve the decision and its reason when the next iteration changes part of it.
Diagram sources
The diagrams are new illustrations for this edition. Their structured records and Mermaid descriptions are included so their relationships can be inspected and adapted.
Methodology configuration
Start with the completed example. For each record, use your method’s terms for the people, information and activities it describes. Identify where it fits in your process and who will use it next. For example, a service brief may hold both the intended outcome and the responsibilities for delivering it.
Keep fields that help a decision or handover. The Methodology configuration section introduces how to adapt the framework and records to your own approach.
Edition and reuse
Version 1.0 · September 2026 · © 2005–2026 Adrian Sutherland.
Refreshed for the September 2026 website update. Keep the edition note with the files and identify adaptations by their source asset, version and filename. The completed examples are fictional; proposed checks need actual results before they can support a service decision.
Read the edition note for authorship and version history.
The Portal-authored downloads use CC BY 4.0: reuse and adapt them with credit, a licence link and changes identified. The edition note records the scope and any separate notices.