# Northstar Equipment Services: Connected Service Promise

**Version:** 1.1  
**Published:** 2026-08-22  
**Status:** Fictional teaching case  
**Primary user:** Business architect

## Purpose and evidence boundary

This fictional case provides one institutionally realistic enterprise scenario for the Applied Business Architecture work-product collection. It shows how a business architect can connect strategy, value, capabilities, organization, information, initiatives, evidence, operating-model change, readiness, value realization, and governed decisions without claiming authority that belongs to business, investment, risk, finance, or technology leaders.

The case is told in three evidence-bounded episodes:

- **Episode A: Authorize.** Decide whether to fund a bounded first release before buying a platform.
- **Episode B: Prepare.** Define the operating change and decide whether the three branches are ready to begin.
- **Episode C: Realize.** Review 30- and 90-day evidence and decide whether to continue, adapt, scale, procure, or stop.

Later evidence must not be used to make an earlier decision appear inevitable. Each evidence item and decision states when it became available.

The case is entirely fictional. Names, figures, facts, costs, and decisions do not describe a real employer, client, customer, or supplier. Financial and capacity ranges are order-of-magnitude planning assumptions, not estimates or vendor quotations.

## Enterprise context

Northstar Equipment Services is a fictional $780 million commercial-equipment maintenance and rental company operating 48 branches in twelve U.S. states. Its 3,200 employees serve construction, utilities, manufacturing, and municipal customers. Branches control daily service execution. Regional operations coordinate capacity across branches. Enterprise functions set commercial policy, financial controls, technology standards, shared information definitions, and common operating measures.

Customers value rapid restoration of equipment availability, but Northstar's service promises have become unreliable. Branch personnel often commit dates before confirming technician skills, parts availability, or travel capacity. Regions use different terms for the same business objects and different definitions for promise adherence. A scheduling-software vendor has proposed an enterprise platform replacement, but executives do not yet know whether the central problem is technology, policy, capability, information, incentives, capacity, or some combination.

## Canonical architecture backbone

The following identifiers remain stable across all episodes and work products:

- Objectives: `O-*`
- Measures: `M-*`
- Evidence: `E-*`
- Value streams and stages: `VS-*` and `ST-*`
- Capabilities: `C-*`
- Business objects: `BO-*`
- Organizational actors: `ORG-*`
- Policies: `POL-*`
- Initiatives, releases, and change packages: `I-*`, `R*`, and `CP-*`
- Decisions and open items: `DEC-*` and `OI-*`

Section identifiers such as `SRC-*` may be used by a tool to locate text. They are not evidence identifiers and must not replace `E-*` lineage.

---

# Episode A: Authorize a bounded change

## Executive request and architecture decision

The original request is:

> Create a capability map for the Connected Service Promise transformation and validate the scheduling platform.

The business architect reframes it as this decision:

> Which bounded response, if any, should Northstar fund now to improve service-promise reliability, preserve usable branch discretion, protect margin, reduce avoidable customer disruption and repeat work, and learn whether enterprise scheduling technology is necessary?

The Investment Council owns the funding decision. The EVP of Service Operations sponsors the work. The business architect owns the architecture analysis and recommendation but does not approve the investment, select the vendor, interpret financial controls, or own operational performance.

## Strategic intent

| ID | Objective | Intended outcome | Principal guardrail |
|---|---|---|---|
| O-01 | Improve service-promise reliability while preserving appropriate branch operating discretion | Customers receive commitments that can be kept, changed transparently, or escalated through a usable exception route | A common policy must not prevent branches from responding to legitimate local conditions |
| O-02 | Protect service margin | Reliability improves without transferring hidden cost or capacity burden to branches, technicians, or adjacent work | Margin, technician productivity, implementation cost, and capacity remain visible |
| O-03 | Reduce avoidable customer disruption and repeat work | Fewer customers experience preventable return visits, missed commitments, and recoverable escalations | Cause coding, customer escalation, and branch-level variation remain visible |

## Canonical measure register

Measures marked **provisional** require approval or rebaselining before they can govern a release or scale decision. An interim release threshold is not the 2027 strategic target.

| ID | Supports | Measure and working definition | Episode A baseline | 2027 target or guardrail | Status and evidence lineage | Accountable owner |
|---|---|---|---:|---:|---|---|
| M-01 | O-01 | Promise-date adherence: eligible promises fulfilled within the approved promise window, excluding only governed cancellations | 82% | 95%; R1 feasibility threshold 92% | Regional definitions differ; E-001 baseline, E-008 approval, E-009/E-010 results | EVP Service Operations |
| M-02 | O-03 | Avoidable repeat visits: eligible completed work requiring another visit for a cause Northstar could reasonably prevent | 14% | 8% | Sample and cause coding disputed; E-002 baseline, E-009/E-010 results; rebaseline before R2 | VP Field Service |
| M-03 | O-02 | Gross service margin using the governed finance definition | 31% | At least 31% cumulative at each investment review | E-005 governed baseline; E-009/E-010 Finance-reviewed results | Chief Financial Officer |
| M-04 | O-01 | Confirmed commitment rate: eligible promises committed only after required part and skill signals are confirmed; approved exceptions remain visible but are not counted as confirmed | 38% | 90% in R1 | E-006 provisional baseline; E-008 approval; E-009/E-010 results | EVP Service Operations |
| M-05 | O-03 | Customer escalation rate: escalations attributable to a missed or changed promise per 100 eligible commitments | Unknown | Day 30 no more than 0.5 per 100 above the approved pre-release baseline; improve directionally by day 90 | E-001/E-003 identify the gap; E-008 definition, baseline, and tolerance; E-009/E-010 results | VP Customer Operations |
| M-06 | O-02 | Technician productivity: productive service hours per paid field hour for eligible work | Governed branch baselines vary | No more than 3% deterioration without approved explanation | E-007 planning view; E-008 comparable baseline and tolerance; E-009/E-010 results | VP Field Service |
| M-07 | O-01 | Compliant-promise use: eligible commitments following either the confirmed path or a complete, approved POL-01 exception | Not applicable | At least 85% by day 30 and 95% by day 90 | E-008 definition and audit method; E-009/E-010 results | Regional VP Operations |
| M-08 | O-02 | R1 cost and capacity: cumulative external/internal change cost and peak temporary FTE-equivalent demand | Not applicable | Remain within $300,000 and six temporary FTE equivalent unless the Investment Council approves a change | E-007 planning inputs; E-008 Finance/Delivery validation; E-009/E-010 results | Chief Financial Officer |

## Stakeholders, actors, and decision rights

| ID | Actor | Contribution or interest | Formal authority |
|---|---|---|---|
| ORG-01 | Customer operations manager | Needs equipment restored when promised | Accepts, changes, or cancels the customer commitment on behalf of the customer |
| ORG-02 | Branch manager | Balances customer commitments, capacity, margin, and local conditions | Owns branch adoption, local capacity choices, and use of the approved exception route |
| ORG-03 | Dispatcher | Creates feasible promises and sequences work | Applies policy and raises exceptions; cannot waive enterprise guardrails |
| ORG-04 | Field technician | Executes work and records actual conditions | Confirms execution facts and exception causes |
| ORG-05 | Regional VP Operations | Coordinates capacity and resolves cross-branch operating conflicts | Approves defined regional exceptions and is accountable for readiness across participating branches |
| ORG-06 | VP Customer Operations | Represents customer outcome and service recovery | Owns customer-disruption definition and service-recovery practice |
| ORG-07 | VP Field Service | Owns field work planning, scheduling, execution, and workforce capacity | Approves operating practices within delegated authority |
| ORG-08 | VP Supply Operations | Owns part-availability operating performance | Approves part-reservation rules and operating remediation |
| ORG-09 | EVP Service Operations | Sponsors I-01 and owns the service outcome | Accountable for C-110 and C-170 performance and approves POL-01 with required contributors |
| ORG-10 | Chief Data Officer | Owns enterprise information-governance policy | Confirms business-object ownership and stewardship; does not own service performance |
| ORG-11 | Chief Information Officer | Owns technology standards and service risk | Approves technology standards; does not own service-policy outcomes or vendor value claims |
| ORG-12 | Chief Financial Officer / Finance delegate | Protects financial definition and investment discipline | Governs M-03 and validates cost and margin evidence |
| ORG-13 | Investment Council | Balances value, capacity, risk, and opportunity cost | Approves, conditions, defers, or rejects funding and later scale/procurement gates |
| ORG-14 | Business architect | Maintains the decision frame and architecture trace | Frames, models, tests, recommends, and records; does not take the business decision |
| ORG-15 | R1 Readiness Forum | Brings Operations, Customer, Field, Supply, Information, Technology, Finance, and Delivery evidence together for the authorized release | Under authority delegated by ORG-13, may activate, stagger, adapt, pause, or stop R1 within the approved scope and cost/capacity band. Only where a governed guardrail explicitly permits, it may authorize one contained remediation interval to the next formal review after the named owner validates the breach; it may not waive or renew the exception, expand to R2, exceed an investment boundary, or reopen procurement. |

### Accountability, ownership, and stewardship

- A **capability accountable executive** is answerable for the capability's business performance and accepts material operating tradeoffs.
- A **capability steward** maintains the capability definition, decomposition, relationships, assessment record, and review triggers. Stewardship does not transfer performance accountability.
- A **business-object owner** approves the business meaning, lifecycle rules, quality thresholds, and authorized use of an object.
- A **data steward** maintains agreed metadata and quality evidence under the object's owner. A steward is not automatically the authoritative source system owner.

## Value stream

The relevant value stream is **VS-01 Restore Equipment Availability**. The primary stakeholder is ORG-01, the customer operations manager whose equipment is unavailable or at risk.

| ID | Stage | Stakeholder state entering | Stakeholder state exiting | Illustrative exit criterion |
|---|---|---|---|---|
| ST-01 | Identify need | Equipment problem is emerging or known | A valid service need is accepted and classified | Asset, urgency, requester authority, location, and contact data are valid |
| ST-02 | Define service promise | Need is accepted but timing is uncertain | A feasible commitment is understood and accepted | Promise reflects POL-01, skill, part, geography, capacity, and any approved exception |
| ST-03 | Prepare service | Commitment exists but work is not ready | Work is ready to execute | Work order, technician assignment, required reservation, and access conditions are confirmed |
| ST-04 | Perform service | Work is ready | Equipment condition is restored or otherwise dispositioned | Work outcome, consumption, and exceptions are recorded |
| ST-05 | Confirm outcome | Service occurred but value is unconfirmed | Customer accepts the outcome or a recovery path is owned | Promise and work outcome reconcile; acceptance or recovery is recorded |

## Capabilities and clean boundaries

| ID | Capability | Decision-relevant definition and boundary | Accountable executive | Architecture steward |
|---|---|---|---|---|
| C-100 | Customer Need Management | Identify, accept, qualify, and maintain a service need. Does not promise a service date or authorize work. | VP Customer Operations | Customer architecture lead |
| C-110 | Service Promise Management | Propose, validate, communicate, monitor, and change a customer commitment. Uses resource signals but does not plan work, reserve parts, assign technicians, or confirm final customer value. | EVP Service Operations | Service architecture lead |
| C-120 | Work Planning | Translate an accepted need into authorized work scope, method, and prerequisites. Does not assign capacity or execute work. | VP Field Service | Field-service architecture lead |
| C-130 | Resource Scheduling | Match authorized demand to qualified people, time, geography, and capacity. Does not establish part status or own the customer promise. | VP Field Service | Field-service architecture lead |
| C-140 | Parts Availability Management | Determine, reserve, position, consume, release, and expire required part availability. Does not assign technicians or make customer commitments. | VP Supply Operations | Supply architecture lead |
| C-150 | Field Service Execution | Perform and record authorized equipment service work. Does not confirm customer acceptance or set promise policy. | VP Field Service | Field-service architecture lead |
| C-160 | Service Outcome Management | Reconcile promise and work outcomes, confirm customer acceptance, initiate recovery, and authorize outcome closure. Does not perform the work or define enterprise measures. | VP Customer Operations | Customer architecture lead |
| C-170 | Service Performance Management | Define, measure, explain, review, and govern service performance and guardrails. Does not own source transactions or operational remediation. | EVP Service Operations | Performance architecture lead |
| C-180 | Business Information Governance | Define shared business information, assign ownership and stewardship, govern quality thresholds, and approve semantic change. Does not make operational service decisions. | Chief Data Officer | Information architecture lead |

## Business objects and lifecycles

| ID | Canonical object and aliases | Decision-relevant lifecycle | Owner and source status |
|---|---|---|---|
| BO-01 | Service Request; ticket, service call, case | Draft → Submitted → Accepted → Qualified → Planned → Resolved or Declined/Cancelled. A material new need creates a new request rather than silently reopening a closed record. | VP Customer Operations; current service record is accepted for R1 |
| BO-02 | Customer Promise; ETA, commit date, appointment | Proposed → Validated → Committed → Fulfilled, Broken, or Cancelled. A committed promise may be superseded by a linked Revised promise; a Broken promise opens a recovery record before outcome closure. | EVP Service Operations; R1 source remains provisional until readiness acceptance |
| BO-03 | Work Order; job, service order | Proposed → Authorized → Scheduled → In Progress → Completed → Closed, with explicit Suspended and Cancelled paths. Completion records work; closure follows reconciliation. | VP Field Service; current work-order record accepted for R1 |
| BO-04 | Equipment Asset; unit, machine, serial | Registered → Available → Unavailable → Under Service → Restored → Available, or Retired. Restoration is an event; availability is the continuing state. | VP Customer Operations; enterprise asset register accepted |
| BO-05 | Part Reservation; allocation, hold | Requested → Confirmed → Picked → Consumed, Released, or Expired. A released or expired need requires a new linked reservation. | **Proposed owner:** VP Supply Operations. **Candidate source:** inventory reservation record. Both require confirmation; no current system is declared authoritative by this case. |
| BO-06 | Technician Assignment; dispatch, route assignment | Proposed → Accepted → Dispatched → Arrived → In Progress → Completed, with Rejected, Reassigned, and Cancelled paths retaining lineage to the replacement assignment. | VP Field Service; scheduling record accepted for R1 subject to skill-data validation |

## Evidence register and lineage

| ID | Available | Evidence | Claim supported | Authority / confidence | Limitation |
|---|---|---|---|---|---|
| E-001 | Episode A | Twelve-month service-performance report | M-01 is approximately 82%; promise failures and customer escalations are material | High directionally | Regional definitions and cancellation handling differ |
| E-002 | Episode A | Regional repeat-visit sample | M-02 is approximately 14% | Medium | Sample selection and preventable-cause coding are disputed by two regions |
| E-003 | Episode A | Five branch workshops and dispatcher observation | Promises often precede part, skill, and capacity confirmation; exception practices vary | Medium-high as convergent observation | Not a controlled measure; participant incentives may affect accounts |
| E-004 | Episode A | Vendor discovery and demonstration | A proposed platform can automate several desired controls | Medium for product functionality | Does not establish enterprise fit, adoption, or realized value |
| E-005 | Episode A | Governed Finance margin report | M-03 is 31% | High | Enterprise result may mask branch and work-type variation |
| E-006 | Episode A | Two-week review of 180 candidate-branch commitments | M-04 is approximately 38% under the provisional definition | Medium | Small purposive sample; definition not yet approved |
| E-007 | Episode A | Branch volume, travel, work-mix, staffing, and change-calendar review | Candidate branches expose materially different operating conditions and have bounded capacity for R1 | Medium | Planning data, not proof of adoption or representativeness |
| E-008 | Episode B | Approved POL-01; accepted BO-02 R1 source; confirmed BO-05 owner and provisional source; approved branch sample and minimum volume; readiness evidence; 30-day pre-release baseline | The R1 operating model, evidence design, and guardrails are sufficiently defined to start under conditions | Medium-high | BO-02 is accepted for R1 but not declared the enterprise future state; the BO-05 source requires reconciliation and is not authoritative enterprise-wide |
| E-009 | Episode C, day 30 | Governed 30-day R1 measure extract, exception log, adoption audit, and Finance, Field Service, and Delivery Management validation | R1 is being used but several thresholds are not yet met | Medium | Short observation period and launch effects |
| E-010 | Episode C, day 90 | Governed 90-day R1 measure extract covering 486 eligible promises (176 metropolitan, 166 mixed-fleet, 144 rural), branch segmentation, adoption audit, and Finance review | R1 is feasible under bounded conditions, and the approved minimum evidence volume was met, with unresolved repeatability and branch-exception issues | Medium-high | Three purposively selected branches cannot establish enterprise repeatability |

## Initiative, alternatives, cost, and capacity

The proposed initiative is **I-01 Connected Service Promise**. Episode A compares genuine alternatives rather than treating R1 as the only responsible choice.

| Alternative | Scope | Planning cost band | Internal capacity band | Evidence gained | Principal tradeoff | Episode A disposition |
|---|---|---:|---:|---|---|---|
| A0: Maintain local practices and improve reporting only | No operating-policy change; clarify current measures | $25,000–$75,000 | 0.5–1 temporary FTE equivalent | Better baseline | Lowest near-term cost; reliability problem and fragmented controls persist | Not recommended |
| A1: R1 bounded three-branch change using existing systems | POL-01, confirmation signals, exception route, adoption, measures, and manual controls | $150,000–$300,000 | 4–6 temporary FTE equivalent plus branch participation | Feasibility, limiting conditions, operating burden, and automation gaps | Bounded disruption and manual work; results not automatically scalable | **Recommended with conditions** |
| A2: Immediate twelve-branch operating expansion | A1 scope across one quarter of branches | $800,000–$1.5 million | 10–15 temporary FTE equivalent plus regional capacity | More variation sooner | Commits capacity before basic definitions and controls are proven | Defer |
| A3: Procure and deploy the proposed enterprise platform | Vendor selection, implementation, integration, adoption, and enterprise controls | $4–$7 million over 18–24 months | 20–30 temporary FTE equivalent plus sustained branch and technology capacity | Product fit and automated operating results, after material commitment | High irreversibility and opportunity cost while causal problem remains uncertain | Defer |

The ranges are sufficient for an investment-class decision but are not delivery estimates. Finance and Delivery Management must replace them before contractual or committed funding decisions.

## Release logic

| Release | Question it is allowed to answer | Scope and evidence | Gate |
|---|---|---|---|
| R1: Three-branch feasibility release | Can the defined policy, information, exception, and operating practices work under three intentionally different conditions and produce decision-grade measures using existing systems? | Limited work types; manual controls allowed; 90-day evidence | Begin only after Episode B readiness. R1 does **not** prove repeatability or justify procurement. |
| R2: Twelve-branch repeatability release | Can the operating model be repeated across regions and broader work types without unacceptable local workarounds, cost, or performance variance? | Refined rules, controlled integrations, adoption pattern, and segmented results | Requires R1 feasibility, resolved blocking conditions, capacity authorization, and a separate Investment Council decision. |
| R3: Enterprise enablement | What enterprise operating model and automation are justified by repeatable evidence? | Enterprise rollout and only the technology required for confirmed residual gaps | Platform procurement requires its own business case and decision after repeatability evidence; R2 success does not automatically select a vendor. |

The R1 M-01 threshold of 92% is an interim feasibility gate, not a revision of the 95% strategic target.

## Purposeful branch sampling

The three R1 branches are selected to expose variation, not to claim statistical representation:

1. a high-volume metropolitan branch with dense travel and broad technician coverage;
2. a lower-volume rural branch with long travel times and constrained skill substitution; and
3. a mixed-fleet branch with material part constraints and cross-branch dependencies.

Each branch must have sufficient eligible commitments for the approved denominator, stable local leadership for 120 days, auditable source records, no concurrent major operating-system rollout, and capacity to train, observe, and report without unsafe workload transfer. A branch is excluded if an extraordinary event would make its evidence uninterpretable. Exclusion and replacement decisions are recorded; they are not used to remove unfavorable results.

## Change packages

| ID | Change package | Outcome | Principal dependencies | Episode A status |
|---|---|---|---|---|
| CP-01 | Promise definition and policy | One usable rule for creating, changing, cancelling, and recovering customer commitments | O-01/O-02/O-03, BO-02, Operations and Customer approval | Proposed; not approved merely because R1 is funded |
| CP-02 | Parts and skills confirmation | Dispatcher can distinguish confirmed, provisional, and unavailable prerequisites | BO-05 owner/source decision; skill-data validation | Proposed |
| CP-03 | Scheduling and branch-exception practice | Promise reflects geography and capacity while legitimate local discretion remains usable | POL-01, M-07, the one-shift exception criterion, and named escalation authority | Proposed |
| CP-04 | R1 enablement and adoption | Three branches can operate, audit, support, and reverse the change | CP-01–CP-03 and readiness evidence | Proposed |
| CP-05 | Measurement and investment review | Decision forums can continue, adapt, scale, procure, or stop using governed evidence | M-01–M-08, E-008–E-010 | Proposed |

## Governed guardrails

| Guardrail | Authority | Breach response |
|---|---|---|
| M-03 cumulative gross service margin falls below 31% at a formal review | CFO validates; ORG-15 may authorize one contained remediation interval to the next formal review; Investment Council owns any renewal or broader exception | Do not expand. Diagnose mix, cost transfer, and measurement before continuation. A material unexplained decline can pause affected work types. |
| M-05 customer escalation exceeds the approved pre-release tolerance | VP Customer Operations assesses harm; EVP Service Operations authorizes continuation | Pause the affected branch or work type for severe harm; otherwise adapt and review within five business days. |
| POL-01 exception route is unavailable, consistently bypassed, or resolves fewer than 90% of requests within one operating shift | Regional VP Operations owns correction | Do not treat noncompliance as employee resistance. Repair authority, capacity, or policy usability before enforcement or scale. |
| M-06 technician productivity deteriorates more than the approved 3% tolerance without explanation | VP Field Service and Finance validate | Investigate cost or workload transfer; no scale while unresolved. |
| M-08 is forecast to exceed $300,000 or six temporary FTE equivalent | CFO and Delivery Management validate; Investment Council owns any exception | Reduce scope, add authorized capacity, or return for a funding decision before exceeding the band. |
| Required information cannot be verified and no approved exception is recorded | Relevant object owner and branch manager | Do not issue a normal confirmed promise; use the transparent exception or escalation route. |

## Episode A decisions and open items

The initial architecture review records exactly two governed decisions:

- **DEC-001:** Conditionally authorize A1/R1 within the $150,000–$300,000 planning band, subject to approved POL-01 and measure definitions, confirmed object owners and source statuses, purposeful branch selection, a readiness decision, and 30/90-day review gates.
- **DEC-002:** Defer A3 enterprise scheduling-platform procurement. Reopen only after R2-quality repeatability evidence identifies material residual automation gaps and a separate business case compares vendor and non-vendor responses.

Open items:

| ID | Item | Owner | Required disposition |
|---|---|---|---|
| OI-01 | Approve M-01, M-04, M-05, M-06, M-07, and M-08 definitions, denominators, tolerances, and exclusions | EVP Service Operations with Finance, Customer, Field, and regional contributors | Before readiness decision |
| OI-02 | Confirm BO-05 owner and whether the candidate inventory reservation record is authoritative for R1 | Chief Data Officer and VP Supply Operations | Before readiness decision |
| OI-03 | Approve POL-01 and its branch-exception authority | EVP Service Operations | Before training and readiness acceptance |
| OI-04 | Confirm the three branch samples and minimum evidence volume | Regional VP Operations and business architect | Before readiness decision |
| OI-05 | Validate cost/capacity bands and release opportunity cost | Finance and Delivery Management | Before funds are committed beyond the planning range |

---

# Episode B: Define the operating model and decide readiness

Episode B may use E-001 through E-008. It may not use R1 performance from E-009 or E-010.

E-008 closes OI-02 for its stated R1 scope: ORG-08 is confirmed as the BO-05 business-object owner, and the inventory reservation record is accepted as the provisional R1 status source subject to twice-daily reconciliation. It also opens **OI-06**, owned jointly by ORG-08 and ORG-10, to decide the authoritative enterprise/future-state BO-05 source before any R2 activation or enterprise source standard is approved. E-008 also accepts the current service-promise record as the R1 source for BO-02 under POL-01 versioning, linkage, and audit rules; it does not declare that record the required enterprise future-state source.

E-008 closes OI-04 for R1 by confirming the three purposeful branch selections and a minimum 90-day evidence volume of 100 eligible promises per branch and 450 in aggregate. A lower realized volume must remain visible as a confidence limitation; an unfavorable branch or result cannot be excluded merely to meet the threshold.

## Recipe 40 completed example: organization-to-value contribution

| Relationship | Organization | Capability / stage | Contribution and right | Material friction | Evidence |
|---|---|---|---|---|---|
| OR-01 | ORG-02 Branch manager | C-110 / ST-02 | Operates the promise practice; accountable for branch adoption and local capacity choice | Local authority was previously implicit | E-003, E-008 |
| OR-02 | ORG-05 Regional VP Operations | C-130 / ST-02 | Governs cross-branch capacity and approves defined regional exceptions | Escalation capacity is limited during peak demand | E-007, E-008 |
| OR-03 | ORG-08 VP Supply Operations | C-140 / BO-05 | Accountable for part-availability performance and confirmed BO-05 business-object owner | Provisional R1 source can lag physical stock changes and is not authoritative enterprise-wide | E-003, E-008 |
| OR-04 | ORG-09 EVP Service Operations | C-110 and C-170 | Accountable for capability performance and POL-01 | Cannot make Finance or customer-risk decisions alone | E-008 |
| OR-05 | ORG-10 Chief Data Officer | C-180 / BO-02 and BO-05 | Governs ownership, stewardship, and semantic change | Stewardship had been confused with operational accountability | E-008 |
| OR-06 | ORG-15 R1 Readiness Forum | C-170 / R1 | Integrates readiness and early-life evidence and exercises delegated R1 release authority | Cannot expand to R2, waive the investment band, or reopen procurement | E-008 |

**Finding:** value depends on coordinated contributions across branches, regions, Supply, Customer, Finance, and information governance. No reorganization is required for R1, but explicit exception and object rights are.

## Recipe 41 completed example: capability improvement assessment

**Capability:** C-110 Service Promise Management  
**Required outcome:** meet the R1 feasibility thresholds for O-01 without breaching O-02 or O-03 guardrails.

| Dimension | Observed condition | Disposition | Causal status | Response |
|---|---|---|---|---|
| Policy | Regions use incompatible promise and cancellation rules | Material constraint | Supported by E-001 and E-003 | CP-01 / POL-01 |
| Information | BO-05 status and skill confirmation are not consistently usable | Material constraint | Supported; the R1 source condition is accepted, while enterprise/future-state authority remains open | CP-02 and OI-06 |
| Governance | Exception authority is implicit | Material constraint | Supported by workshops | CP-03 and POL-01 |
| Capacity | Rural travel and specialist coverage constrain feasible dates | Contributing | Supported as planning evidence, not yet performance evidence | Purposeful sample and exception route |
| Technology | Whether existing tools impose material manual-confirmation burden | Unknown before R1 | E-004 demonstrates automatable functionality only; E-003 does not quantify burden | Measure manual effort and failure modes in R1; do not procure yet |
| Skills / adoption | New practice is unfamiliar | Unknown before use | Hypothesis | Training, observation, M-07 |

**Conclusion:** policy, information, and decision rights are the primary known constraints. Technology may become a limiting condition only after the operating design is tested.

## Recipe 42 completed example: operating-model change record

| Element | Current condition | R1 target condition | Owner | Evidence of completion |
|---|---|---|---|---|
| Policy | Local promise rules and informal overrides | POL-01 defines normal confirmation, change, cancellation, recovery, and exception paths | ORG-09 | Signed policy and versioned job aid |
| Organization / right | Dispatcher and manager authority varies | ORG-03 applies rules; ORG-02 approves branch exceptions; ORG-05 resolves cross-branch exceptions | ORG-05 | Role acceptance and scenario test |
| Information | Part and skill statuses are interpreted locally | BO-02 is accepted for R1 under versioning/audit rules; ORG-08 owns BO-05; its inventory reservation source is provisional for R1 and reconciled twice daily, not authoritative enterprise-wide | ORG-08 / ORG-10 | Object decisions and source-quality tests |
| Operating practice | Promise can precede prerequisite confirmation | Normal promise requires confirmation or a transparent approved exception | ORG-02 | Observed scenario and adoption audit |
| Measures | Definitions and denominators vary | M-01 and M-04–M-08 are approved and reproducible | ORG-09 / ORG-12 | Parallel-run reconciliation |
| Technology | Current tools plus informal calls and spreadsheets | Current tools retained; controlled manual log bridges unresolved automation | ORG-11 | Support and access acceptance |

Detailed organization design, procedures, training material, data remediation, technology configuration, and delivery planning remain with their accountable disciplines.

## Recipe 45 completed example: internal policy impact

Recipe 45 is applied to Northstar's internal policy, not to an invented law or regulation.

| ID | Authoritative source | Internal obligation | Architecture impact | Control / evidence | Authority |
|---|---|---|---|---|---|
| POL-01 | Service Promise Policy v1.0, approved in Episode B | A normal committed promise requires valid BO-02 data and required part, skill, geography, and capacity confirmation | ST-02; C-110, C-130, C-140; BO-02, BO-05, BO-06 | Confirmation timestamp and source status | ORG-09 |
| POL-01 | Same | When confirmation is unavailable, the dispatcher must use an approved exception that names reason, approver, expiry, and customer communication | C-110 and C-170; ORG-02/ORG-05; M-07 and the one-shift exception criterion | Exception record and weekly exception review | ORG-09; regional rights delegated to ORG-05 |
| POL-01 | Same | A changed promise preserves the superseded promise and triggers customer notification | ST-02 and ST-05; BO-02; C-160 | Linked promise version and notification record | ORG-06 |
| POL-01 | Same | A broken promise opens a recovery path before outcome closure | ST-05; BO-02; C-160 | Recovery owner and closure evidence | ORG-06 |

## Recipe 44 completed example: operational readiness

| Area | Required condition | Episode B evidence | Status | Condition / owner |
|---|---|---|---|---|
| Operating ownership | Branch, regional, capability, object, and measure rights accepted | Signed RACI/decision-right record | Ready | None |
| Policy and controls | POL-01 approved and scenario-tested | Policy and observed tabletop | Ready | None |
| Information | Accepted R1 source status for BO-02 and confirmed BO-05 owner/source condition | BO-02 passes version/linkage audit; ORG-08 owns BO-05; its provisional inventory reservation source shows delayed updates in one branch | Ready with condition | BO-05 twice-daily reconciliation; no enterprise future-state authority claim for either source; ORG-08 / ORG-10 |
| Evidence design | Branch selection and minimum volume accepted | Three purposeful branches confirmed; minimum 100 eligible promises per branch and 450 aggregate over 90 days | Ready | Preserve lower volume as a confidence limitation; ORG-05 / ORG-14 |
| Roles and capacity | Exception route can respond within one shift | Peak-volume simulation shows rural escalation bottleneck | Ready with condition | Regional backup approver; ORG-05 |
| Measures | Definitions approved and parallel run reconciles | M-01/M-03/M-04 reconciled; M-05/M-06/M-08 baselined; M-07 audit method validated | Ready | None |
| Training and adoption | Dispatchers and managers pass scenarios | 91% complete; one shift remains | Not ready | Complete before branch activation; ORG-02 |
| Continuity / rollback | Branch can revert to prior practice without losing promise lineage | Tested rollback and record-retention procedure | Ready | None |

**DEC-003 — owner ORG-15:** The R1 Readiness Forum authorizes a staggered R1 start only after the remaining shift completes training. The BO-05 reconciliation and regional backup approver are accepted through the day-30 review; ORG-15 must then close, adapt, or explicitly renew each condition against E-009. No condition authorizes R2 or platform procurement.

---

# Episode C: Observe value and decide what follows

Episode C adds E-009 at day 30 and E-010 at day 90. Results are deliberately mixed. The case does not convert association into proof of causation.

## Recipe 43 completed example: value-realization trace

| Trace | Hypothesis | Measure | Day 30 | Day 90 | Interpretation |
|---|---|---|---:|---:|---|
| VR-01 | Confirmation or governed exception improves promise reliability | M-04 / M-01 | 84% / 89% | 92% / 93% | Feasibility thresholds reached by day 90, but launch period missed them |
| VR-02 | Better preparation reduces preventable rework | M-02 | 12% | 11% | Directionally improved but short of 8% target; coding dispute remains |
| VR-03 | Reliability can improve without margin transfer | M-03 | 30.8% | 31.2% | Day-30 guardrail breach recovered after work-mix review; Finance finds no sustained breach |
| VR-04 | Customer disruption does not increase as promise rules tighten | M-05 | 6.5 per 100 vs 6.2 pre-release | 5.6 per 100 | Within the approved day-30 tolerance and directionally improved by day 90 |
| VR-05 | The practice and its exception route are actually used | M-07 | 78% | 96% | Adoption threshold met after coaching and clearer exception authority |
| VR-06 | Formal exceptions preserve usable branch discretion | POL-01 one-shift exception criterion | 76% | 88% | Improved but missed 90%; rural escalation remains a constraint |
| VR-07 | Reliability is not purchased through hidden field burden | M-06 | -4.1% vs baseline | -2.0% vs baseline | Day-30 breach recovered within guardrail; manual checking remains burdensome |
| VR-08 | The bounded release remains within authorized cost and capacity | M-08 | $118,000 spent; $340,000 forecast; 5.8 FTE equivalent | $287,000; peak 5.8 FTE equivalent | Day-30 forecast required scope correction; final result stayed within the band |

**Evidence-volume and segmented finding:** E-010 contains 486 eligible promises: 176 metropolitan, 166 mixed-fleet, and 144 rural. The approved threshold of at least 100 per branch and 450 aggregate is met. Metropolitan promise adherence reaches 95%, the mixed-fleet branch reaches 94%, and the rural branch reaches 89%. The aggregate 93% result therefore cannot be treated as evidence of uniform repeatability.

**Attribution judgment:** the timing and adoption relationship support a contribution claim for POL-01, confirmation, and explicit exception rights. The three-branch design cannot isolate each intervention or prove enterprise causation. Seasonal demand and work mix remain plausible confounders.

## Day-30 review

- M-03 and M-06 breach their provisional guardrails.
- M-01, M-04, M-07, and the POL-01 exception criterion have not reached their thresholds.
- M-08 remains within its current spend limit, but the forecast exceeds the authorized band.
- The branch-exception backlog, not lack of dispatcher effort, is the strongest observed limiting condition.
- BO-05 source lag creates manual reconciliation work but has not yet established a platform requirement.

**DEC-004 — owner ORG-15; breach validation by ORG-07, ORG-12, and Delivery Management:** ORG-12 validates the M-03 result and the financial evidence for M-06 and M-08; ORG-07 validates the M-06 productivity breach; Delivery Management validates the M-08 forecast and the scope correction. Use ORG-15's delegated, one-interval remediation authority for the M-03 margin breach to continue R1 to the day-90 formal review. Apply the M-06 no-scale response while the productivity breach remains unresolved, and narrow one low-volume work type before the M-08 band is exceeded; neither response waives a guardrail or expands ORG-15's authority. Make no scope expansion or increase to the authorized band. Add a regional backup approver, correct BO-05 reconciliation, and review margin and workload weekly. Pause any branch if customer harm becomes severe; return to ORG-13 if the margin exception would extend beyond day 90 or before any funding or capacity boundary is exceeded.

## Day-90 scale, adapt, stop, and procurement decision

R1 demonstrates bounded feasibility: M-01 and M-03–M-08 meet their applicable R1 thresholds or guardrails by day 90. M-02 remains short of the strategic target, the POL-01 one-shift exception criterion remains below 90%, and the rural result exposes unresolved capacity and exception design. Manual confirmation burden identifies a candidate automation gap, not proof that the proposed platform is the correct response.

**DEC-005 — owner ORG-13:** Conclude R1 as feasible with material conditions. Authorize design and readiness work for R2, but do not activate twelve branches until regional exception capacity, BO-05 source remediation, repeat-visit coding, and segmented R2 exit criteria are approved. Preserve the option to reduce or stop R2 if those conditions cannot be met within the authorized capacity band.

**DEC-002 review disposition:** The procurement deferral remains in force. During R2, compare targeted integration, workflow automation, and platform alternatives against the measured residual gaps, total cost, adoption burden, and reversibility. Reopen DEC-002 only when its evidence conditions are met.

The result is neither “R1 succeeded, therefore scale” nor “technology is unnecessary.” It is a narrower institutional conclusion: the operating design is feasible, repeatability remains unproven, and the technology decision is better informed but still open.

## Continuing architecture and stopping rule

The business architect preserves the accepted IDs, definitions, evidence lineage, decisions, dissent, and review triggers. The Episode A recommendation is not rewritten using Episode C hindsight.

Stop extending this case analysis when the accountable forum can trace:

`O-* → M-* → VS/ST-* → C-* → BO-* → ORG-* → I/R/CP-* → readiness → realized evidence → DEC-*`

and can distinguish fact, provisional definition, inference, recommendation, accepted decision, and unresolved item. Reopen when a named trigger, new branch evidence, changed policy, operating failure, capacity conflict, or value result could alter a governed decision.

## How to use the case

1. Select the episode that matches the decision date; do not use later evidence prematurely.
2. Review the canonical backbone before opening a related work product.
3. Use the compact recipe examples to see how relationships persist across artifacts.
4. Replace fictional facts with sanitized, governed enterprise evidence and preserve source lineage.
5. Preserve unknowns, conflict, incentives, and local variation rather than making the record look complete.
6. Stop when the work materially improves the named decision.

## Boundaries

This case and its work products are educational practitioner aids. They do not replace executive accountability, organizational governance, authoritative enterprise models, formal investment approval, legal or regulatory review, financial validation, project or change management, solution design, requirements management, data modeling, records-management controls, or the judgment needed to tailor business architecture to a real institution.

Related guidance: https://stephenklahr.com/cookbook/