Operations · 8 steps · 6–9 months
Shared Services Migration
Consolidate transactional work into a shared services center.
When to use
When 3+ business units run duplicate back-office processes.
Playbooks
Translate analysis into implementation steps.
What this page is for
Implementation playbooks
Each playbook is a step-by-step implementation guide. It tells you when to use it, what you need, what it produces, and the risks to manage.
Implementation plan — derived from active scenario
Workstreams generated from the selected scenario's design choices. Each row is editable once the scenario backend lands; today this is the recommended structure.
| Workstream | Action | Owner | Timeline | Priority | Dependency | Status |
|---|---|---|---|---|---|---|
| Governance | Re-tier governance — light-touch for low-risk pods, tight for high-risk | Alex Morgan | Wk 1-4 | P1 | — | Not started |
| Capability | Stand up two GTM pods (Customer Acquisition, Order & Fulfillment) as proof points | Priya Shah | Wk 2-8 | P1 | Governance re-tier | Not started |
| Roles | Clarify decision rights for pricing, segmentation, campaign prioritization | Marcus Lee | Wk 3-6 | P1 | — | Not started |
| Shared Services | Move repeatable GTM reporting into shared services or automation | Hana Suzuki | Wk 6-12 | P2 | Capability pods live | Not started |
| AI | Pilot AI scoring on lead qualification — 1 pod, 1 quarter | Marcus Lee | Wk 4-12 | P2 | — | Not started |
| Change | Move 12% of FTEs into a redeployment pool funded by AI Augmentation lift | James O'Reilly | Wk 8-16 | P2 | AI pilot results | Not started |
| KPIs | Define top-of-funnel + cycle-time scorecards reviewed weekly at GTM forum | Alex Morgan | Wk 2-4 | P3 | — | Not started |
- 1Filter playbooks by category to find the right starting point.
- 2Click a card to expand its inputs, outputs, and risks before launching.
- 3Click 'Use this playbook' to open the stepped walkthrough.