Strategic Framing &
Decision Architecture
Illustrative work product / Decision brief 01
Integration sequence
& operating continuity
A structured decision on purchasing integration following an acquisition.
01The decision to be made
Which integration sequence captures purchasing benefits while protecting customer continuity, and who has authority to approve the trade-offs?
Determine the first transition scope, the service conditions required to proceed, and the exception and escalation rights. Defer irreversible supplier changes until the supporting evidence has been reviewed.
Proposed course
Stage the integration. Make the conditions explicit.
Begin with a bounded purchasing category where supplier readiness and customer-service safeguards can be demonstrated. Expand only after the agreed operating review. Maintain exceptions where evidence supports continuity risk, with a named approver and expiry or review date.
02Situation and evidence discipline
Scenario premise: A sponsor has acquired a complementary business. Shared systems and centralized purchasing form part of the integration plan. Milestones are slipping, and leadership initially attributes the delay to management resistance.
| Evidence category | What the brief records |
|---|---|
| Assumed for this illustration | Integration milestones have slipped. Operating leaders have raised service and supplier-continuity concerns. The plan anticipates purchasing benefits. |
| Unverified interpretation | Management resistance is the principal cause of delay. This is a hypothesis to examine, not an established finding. |
| Evidence required | Milestone and approval logs; service performance by customer; supplier readiness and capacity; contract constraints; purchasing baseline; transition costs; current authority limits. |
| Economic uncertainty | No quantified savings, transition-cost estimate, or customer exposure has been supplied. Financial attractiveness remains to be validated. |
03Read the situation through five lenses
| Lens | Decision implication |
|---|---|
| Reality | Trace the delay to specific unmet prerequisites and approvals. Distinguish operating constraints from unsupported objections. |
| Interests | The sponsor seeks value realization; operations carries service risk; procurement must deliver consolidation. Test these working hypotheses directly with the participants. |
| Power | Identify who owns the timetable, approves exceptions, controls resources, and can pause a transition. Resolve responsibility without authority. |
| Framing | Evaluate integration sequence and acceptable exposure rather than treating the entire issue as a demand for compliance. |
| Consequence | Consider disruption, deferred savings, transition cost, and the effect of exceptions on future integration. Link each choice to reviewable commitments. |
04Compare the available courses
| Course | Potential advantage | Principal exposure | Condition for selection |
|---|---|---|---|
| Accelerate full integration | Earlier access to purchasing benefits if execution succeeds. | Service disruption, rushed supplier qualification, and limited reversibility. | Readiness and continuity safeguards verified across the full scope. |
| Stage integration Proposed | Tests readiness while progressing toward the thesis. | Some benefits arrive later; parallel processes add complexity. | A bounded category can proceed safely and its economics justify transition costs. |
| Pause pending resolution | Preserves continuity while critical uncertainty is resolved. | Deferred benefits and a risk that temporary delay becomes indefinite. | No safe initial scope exists; a time-bound evidence plan has an accountable owner. |
The proposed course is conditional. If the evidence does not support a safe and economically viable first stage, pause and reassess.
05Assign decision rights and commitments
| Accountable role | Required commitment | Timing or gate | Evidence of completion |
|---|---|---|---|
| CEO / decision sponsor | Approve scope, delegated authority, and escalation rules. | Before the first supplier commitment. | Signed decision record and explicit authority limits. |
| Finance lead | Validate net benefits, costs, and downside exposure. | Before approval of each stage. | Reviewed economics and sensitivity assumptions. |
| Operations lead | Define customer-service safeguards and fallback arrangements. | Before transition authorization. | Baseline measures, thresholds, and recovery plan. |
| Procurement lead | Confirm supplier readiness and contractual constraints. | Before changing purchase commitments. | Qualification record and documented constraints. |
| Integration lead | Maintain the decision register and escalate unresolved dependencies. | Weekly through the initial stage. | Owner, due date, status, and escalation for each open decision. |
Roles and cadence are illustrative. Actual authority and reporting arrangements must be agreed with the client.
06Monitor the decision, not just the timetable
- Service continuity: Track agreed fulfillment and reliability measures against the pre-transition baseline. Set numerical thresholds before launch.
- Economic realization: Compare verified purchasing benefits with transition and parallel-running costs.
- Decision flow: Review overdue approvals, unresolved exceptions, and dependencies without an accountable owner.
- Commitment completion: Check delivery against named owners and agreed deadlines.
Revisit the course when: service safeguards are breached, supplier readiness changes, the economic case deteriorates materially, or required authority remains unresolved. The designated decision owner determines whether to pause, amend, or expand the stage under the agreed governance.
07Record the conclusion
Proposed decision: Authorize a staged integration only after the readiness, service, economic, and authority conditions above are satisfied.
Open items before approval: Category selection; quantified economic case; service thresholds; exception authority; transition review date.
Approval status: Pending. In a live engagement, the record would capture the decision owner, approval date, accepted trade-offs, and next review.
This fictional example demonstrates the structure of a Courtier work product. Scenario premises, roles, and proposed actions are illustrative; it makes no claim about realized results.