Shared systems and reusable patterns
| # | Touchpoints (4) | Connected surfaces | Leverage result | Support route | Evidence to collect | Next action |
|---|---|---|---|---|---|---|
| 1 | AX Component LibrarySystem-level touchpoint | Multiple employee and commerce products | Establish a stable shared foundation and clarify direction across consuming products. | Funded foundation support | Adoption context, product-flow exceptions, known component gaps. | Align priorities and ownership. |
| 2 | Enterprise intranetDomain: Corporate Communications · Shared communications platform | Corporate tools and internal content surfaces | Standardize navigation, content, and migration decisions. | Plan with redesign | Migration scope and key consuming workflows. | Identify migration patterns worth reviewing once. |
| 3 | Required workflow browserDomain: Field Operations · Required environment | Field-associate task flows | One constraint can affect every dependent workflow. | Pilot-stage monitoring | Whether the alternative route remains available through pilot close. | Watch until pilot ends in FY27 Q4. |
| 4 | Learning management systemDomain: Learning & Development · Required training | Training and learning surfaces | Scale accessible templates and content patterns. | Enablement | Repeated team questions and material reuse. | Package patterns in training and job aids. |
Key distinction: a system-level issue should be routed once to the accountable system owner; consuming products retain the local flow context rather than creating duplicate escalations. The leverage view organizes entered dependency and pattern context; people validate the owner, root cause, and action.