Leadership strategy readout
Purpose
Translate the touchpoint inventory into a practical view of current support commitments, carryover planning, and work that remains visible without funded capacity.
Why this matters
The portfolio makes risk, protected journeys, and current funding choices visible together so support can be sequenced responsibly.
Planned funded work 8 current funded touchpoints
Previously planned work carries forward when it remains funded in current data. Newly identified touchpoints join the plan once their support lane is confirmed as Funded.
Prior-period carryover 3 touchpoints
| Touchpoint | Current support context | Support lane |
|---|---|---|
| Careers website: External | Accessibility audit / remediation in progress | Funded |
| Time & attendance system | None active; awaiting team updates | Funded |
| AX Component Library | Foundation stabilization and direction setting | Funded |
Newly added funded touchpoints 5 touchpoints
| Touchpoint | Current support context | Support lane |
|---|---|---|
| Workplace incident and claims | New functionality | Funded |
| Careers app: External | Ownership clarification | Funded |
| Benefits portal | Enrollment support planning | Funded |
| Payroll portal | Risk watch; future change trigger | Funded |
| Enterprise intranet | Migration discovery | Funded |
Other planned work 11 touchpoints not currently funded
This includes 10 Baseline touchpoints and 1 proposed, unassigned touchpoint. They remain visible for planning, timing, and escalation context, but are not a funded commitment.
Evidence boundary: a leadership readout did exist as a separate strategy artifact. This page is a public-safe reframing of its strategy and planning treatment for a portfolio audience, not the original file and not a performance dashboard. Counts and planning treatment shown here are representative.