The Agentic Journey Map
The Agentic Journey Map is a series of pages laying out the route by which a workforce planning function — typically one assembled from several organizational heritages through merger, acquisition or regional consolidation — moves from unreconciled definitions to the execution of its own specified processes, and of the specified work it places, by AI agents. The route has eight stages in sequence. Each stage is a page, and each is mapped to the level of the WFM Labs Maturity Model at which it is typically undertaken. The map is a route, not a scorecard: a function can enter at whichever stage its definitions and documentation have reached, and the stages that follow are the ones that remain.
The premise beneath the whole route is that handing a process to an agent is a placement decision, not an AI initiative. An agentic capability is a node with unusual attributes, placed by the same machinery that places every other node, once the function can say — in one vocabulary — what the work is, who may do it, and what "done" means. The first four stages build that vocabulary and machinery. The last four use them.
The route
| Stage | Page | What the stage does | Maturity level |
|---|---|---|---|
| 1 | Reconcile the definitions — Inherited Sourcing Doctrine in Merged Service Estates · Headcount Reconciliation in Service Operations · Intent Normalization Before Work Placement · Platform Migration as a Definitional Forcing Function | Discover that the consolidated function carries several correct but unreconciled answers to every operational question — sourcing rules, headcount perimeters, intent taxonomies — and settle each with its own method, using the platform migration as the clock | Level 2 → 3 |
| 2 | Standardize before you automate — Standardize Before You Automate | Formalize, centralize and standardize six things: technology by planning horizon, process documentation, roles, the objective register, data definitions and interfaces. The platform executes the ontology and never defines it. The stage ends with the first agentic handover, not with a platform going live | Level 3 |
| 3 | Sort the work into three bands — Three Bands of Work | Classify every process as discretionary, overseen or specified by how completely it is documented and measured, using stakes and complexity as independent axes. The sort reveals how much of the function's "judgment" work is undocumented specified work | Level 3 → 4 |
| 4 | Take the first process through the gate — The Agentic Handover Gate | Pass one process through the five tests and run it agentically; the first handover forces every foundation to exist for at least one process | Level 4 |
| 5 | Establish identity and custody — Agent Identity and Custody | Give every agentic node an identity in the same system as people, an owner, a permission set derived from its step tables, an eligibility set, and a measured reputation, before it is delegated further work | Level 4 |
| 6 | Scale the overseer — The Agent Overseer | Make the overseen band a managed population: overseers who hold custody, run the catch-rate program and adjudicate exceptions, sized by exceptions and stakes, staffed inside the function for its own processes and contracted for supplier-delivered work | Level 4 → 5 |
| 7 | Consolidate, then automate fulfillment — Consolidate, Then Automate: Back-Office Fulfillment | Apply the bands and the gate to back-office fulfillment: consolidate under one process set, one view and one contract shape with contracted oversight, then automate | Level 4 → 5 |
| 8 | Re-size for the hardening residual — The Hardening Residual | Recognize that automation takes the easiest work first and leaves a harder residual, so every footprint is re-sized each cycle and the human population is reported as an output of the placement machinery rather than as a target | Level 5 |
How the stages depend on each other
The dependencies are strict in the first half and loose in the second. Stage 2 cannot begin until stage 1 has produced at least the definitions the platform migration needs; stage 3 reads the documentation standard stage 2 established; stage 4 cannot pass its first test without stage 3's sort. From stage 4 onward the stages are concurrent in practice: identity and custody (5) are established for the first agent as it passes the gate, the overseer (6) is filled for that first process, and fulfillment (7) can begin its consolidation phase as soon as the shared standard exists, regardless of how far the function's own handovers have progressed. Stage 8 is not a destination but a cadence: it begins with the first handover and never ends.
How the map relates to existing pages
The map is the sequential layer over three bodies of work the wiki already holds. The Observation Catalog supplies the field observations — on definitions, placement and measurement — that stages 1 to 3 respond to. The placement doctrine — The Workforce Broker, Placement Engine Architecture, Service Chain Decomposition and Node Sourcing, Comparing Delivery Arrangements — is the machinery stages 4 to 8 run on. And the Adaptive Concepts series, in particular Level 3: The Automation Layer, Level 4: Planning in Distributions and Level 5: Adaptive Orchestration, describes what a function looks like at each level the map's stages are mapped to. Agentic AI Workforce Planning and Conservation of Labor carry the supply-side and labor-displacement premises the route depends on.
See Also
- Three Bands of Work — the organizing principle of the route
- The Agentic Handover Gate — the mechanism at its center
- WFM Labs Maturity Model™ — the levels the stages are mapped to
- Observation Catalog — the observations the first stages answer
- Adaptive Concepts — the companion series, from first principles
- The Automation Analyst — the role stage 4 needs filled alongside the overseer
- Role Evolution in the Resource Optimization Center — how every role advances along the route
- Technology Journey from Level 2 to Level 5 — the technology path that runs beside the process-and-role route
- The Value Destruction Risk in Service Automation — the risk the route exists to avoid
