Planning Week for a Workforce Function
Part of the Planning Week chain · previous: none · next: Truth About Today
A planning week for a workforce function is four consecutive days, Day 1 to Day 4 — conventionally Monday to Thursday — in which the leadership of a workforce planning function answers the eight questions of its operating model together, in an order where nothing decided later reopens anything decided earlier, and walks out with a filled set of templates rather than a deck. It is operating model planning laid out as a chain of wiki pages: eight half-day blocks, each walking two to four pages, taking its decisions, running one working session on a Claude project pack, and producing a named artifact. This page is the entry. It says what the week is, what walks out on Day 4, and what to open first; every page in the chain links back here. The page produces the decision record, template T9 (D-01 to D-16), and the blueprint as the set of every filled template, worked in a session with Wiki:Packs/Executive Issue Register (CP-OPS-002 v1.1) and the thirteen other packs in the table below. It also carries two registers the rest of the chain points at rather than repeats: the artifact templates, below, and the wiki's four uses of the word "level".
Two words are defined here because the week uses both. A pack is a Claude project pack on Wiki:Packs: one instruction block and a few reference files a working session deploys in about two minutes. The service pack is the fifteen-section workbook each function owner takes home on Day 4, described on The Function Service Pack; an operating-model design calls that workbook the Global ROC Service Pack, and on this wiki "pack" without a qualifier means the Claude project pack alone.
Five minutes: what the week is, and is not
The week answers in one room, so that the answers agree, the eight questions Operating Model for Workforce Management sets out, one per component: strategy and principles, scope and placement, process execution, governance, roles and competencies, org structure, measures and scorecard, technology and data. That page states the questions; this one puts them on a clock. The week is not a reorganization, not a headcount exercise, and not a decision on where any body of work sits; those decisions stay with the node owners, the owners of the work placed at a node, and the week sets the rules they will use. A node is a place work can sit: a hub (in-country depth), a service center (badged arbitrage at scale), a partner (speed, market access, flex), or automated.
What walks out on Day 4 is a set of filled templates with permanent IDs, called blueprint v0.1: a function charter; a strategy on a page; the GRPI-T frame instantiated as five headlines and five sheets; a function catalog with process shells; an org option with its sunset conditions printed; role cards; the interconnection plan; a technology migration plan with its sub-plans; seven program charters, the agent program's among them; a roadmap with a seat per lane; and the decision record with every row marked taken, deferred or parked. Nothing on those pages is settled until the validation circuit, in which the teams who run the work correct the room, has run.
Open first: The Case for Operating Model Planning (why leaders do this together), Operating Model for Workforce Management (the ring, one question per component), and Truth About Today (how the current state is stated without blame). Those three are the pre-reads; nothing else is assumed read before Day 1.
The week as eight blocks
The blocks are half days. Each row names the pages walked in order, the decisions taken (generic wording; the full list is below), the pack used in the block's working session, and the artifact that walks out. Platforms are named by category throughout the chain: the long-term capacity engine, the short-term WFM engine (forecasting and scheduling), intraday automation, the Python analytics platform (the reporting platform's notebook component) and the reporting platform; no chain page names a product.
| Block | Pages walked | Decisions | Pack for the working session | Artifact that walks out |
|---|---|---|---|---|
| Day 1 morning — open; the truth about today; the strategy | this page (five minutes) → The Case for Operating Model Planning → Operating Model for Workforce Management → Truth About Today → Strategy on a Page → Operating Principles for Work Placement | D-01 ratify the strategy on a page | Wiki:Packs/Strategy on a Page (CP-WFM-011) |
the truth funnel in the room's words; the strategy on a page; twelve principle cards, each with "what will be different" |
| Day 1 afternoon — charter and goals | Function and Program Charters (the function charter) → Instantiating the GRPI-T Framework (the ordering rule; the Goals pillar) → WFM Goals | D-02 the goal frame | Wiki:Packs/Charter and Program Launch (CP-WFM-012) · Wiki:Packs/GRPI-T Instantiation (CP-WFM-013) |
the function charter v0.1 (CH-001); the goals sheet T1 by horizon and category; the Goals headline
|
| Day 2 morning — roles, organization, decision rights | Functional Organization Design for a Resource Optimization Center → Role Cards for a Workforce Function → Resizing a Workforce Function After an Acquisition → Decision Rights by Planning Horizon | D-03 the organization option · D-04 the sunset conditions · D-05 decision rights and the four forums | Wiki:Packs/Organization Design and Role Cards (CP-WFM-014) · CP-WFM-013 (the RACI) |
one org option with sunset conditions printed; the functional org chart as a transition state; role cards T2; the RACI by horizon T3; four forum cards; the Roles headline |
| Day 2 afternoon — processes and the Standard's shape | Anatomy of a ROC Standard → Process Shells for a Workforce Standard → Process Standardization Lifecycle → Process Decomposition (L0–L3) → two filled patterns: Three-Step Forecast Build and Incident Management for Contact Centers | D-06 the process architecture · D-07 "highly specified" defined once · D-08 one capacity-cycle calendar | Wiki:Packs/Process Decomposition (CP-OPS-001 v1.1) · Wiki:Packs/ROC Standard Authoring (CP-OPS-003) |
the function catalog with classes; L0 cards T4 as shells with "skeleton until" dates; the first-wave list; the standards committee's charter; the one calendar; the Processes headline |
| Day 3 morning — interconnections | Enterprise Interconnection Plan → Interconnected Workforce Management → Executive Issue Register (the register behind the door) → The Placement Gate | D-09 scope and interfaces · D-10 the continuity wire | CP-WFM-013 (interface cards) · Wiki:Packs/Executive Issue Register (CP-OPS-002 v1.1) |
the scope table; the interface plan T5 with the binding rows owned in the room; the intake door card — the six fields The Question Register and Knowledge Base defines, with the routes Enterprise Interconnection Plan sets, its live five plus the placement route that page adds; the interim protocol; the Interpersonal and Interconnected headline |
| Day 3 afternoon — technology and data | Technology Migration Plan for a Workforce Function → The Definitions Register → Migrating a Book of Business → the four sub-plans, ten minutes each: Placement Engine Build Path · Launching an Analytics Notebook Platform · Expanding Intraday Automation · Systems Administration for WFM Platforms | none of its own; the build order is presented as settled and feeds D-13 and D-14 | Wiki:Packs/Technology Plan (CP-WFM-016) · Wiki:Packs/Book Migration (CP-OPS-004) · Wiki:Packs/Placement Decision Engine Build (CP-WFM-008) · Wiki:Packs/Agent Capability Ontology (CP-WFM-002) |
component cards T6 by category; the build order dated; the definitions register v0; the book-migration runbook shell BM; four sub-plan shells SP; the integration-by-when table; the Technology headline |
| Day 4 morning — the Standard, the charters, the agent program | Anatomy of a ROC Standard (return) → The Function Service Pack → Function and Program Charters (the program charters) → AI Agent Program for a Resource Optimization Center → The Agent Team Ladder: Alpha to Production → A Roadmap Pattern for Agent Teams in WFM | D-11 issue the Standard v0.1 · D-12 the definitions register's owners and signatories · D-13 the first books · D-14 owners | CP-OPS-003 (front matter and §2) · CP-WFM-012 (program charters) · Wiki:Packs/Agent Program Readiness (CP-OPS-005) |
the Standard shell with an owner and a date per section and an expiry; seven program charters T7, the agent program's among them with its ladder cards AL — the rung each agent team is on, the rung the room sets next, and the clone onto a second book; the definitions register's owner and signatories |
| Day 4 afternoon — roadmap, timeline, landscape, close | Work Placement Landscape → The Two-Arc Roadmap → Transformation Timeline for a Workforce Function → this page (the close) → Open Office Hours for Next-Generation Workforce Planning | D-15 the first-quarter front-load · D-16 the validation circuit | Wiki:Packs/Two-Arc Roadmap (CP-WFM-015) · Wiki:Packs/Transformation Timeline (CP-WFM-017) · CP-OPS-002 v1.1 (the decision record and the readback) |
the landscape, current and end state; the roadmap T8 with a seat per lane and the front-load list; the transformation timeline TL, twelve dated tracks with their dependencies and sensitivities; the decision record T9; the validation circuit dated; blueprint v0.1; the service pack in every director's hands |
The order is the GRPI-T order, Goals then Roles then Processes then Interconnections then Technology, because a function designs top-down and, when something hurts, the cause is usually one pillar to the left. GRPI-T Framework carries the ordering rule and its origin; Instantiating the GRPI-T Framework carries the method for applying it live. The organization option gets a whole half day because it is the decision the week exists for.
The sixteen decisions, in order
The list is the room's; nothing later reopens anything earlier. Owners are seats (a post on the org chart with its scope and its sunset condition), never names. Every decision is recorded on the decision record with its outcome: taken, deferred with a date and an owner, or parked to the parking lot.
- D-01 Ratify the strategy on a page: vision, mission line, five intents with technology as an enabler and not a pillar, the twelve principles, the level target — Strategy on a Page
- D-02 The goal frame: four categories; weights per node with a body-of-work override; value as the unit; the quality score and the customer-experience index paired, never blended; targets by service tier, never by location — Instantiating the GRPI-T Framework
- D-03 The organization option, against six criteria, with the faces arithmetic written down — Functional Organization Design for a Resource Optimization Center
- D-04 The sunset conditions, printed on the chart, and where real time goes at sunset — Functional Organization Design for a Resource Optimization Center
- D-05 Decision rights by horizon with the first rule (method versus decision); declines recorded with their price as routine; the four forums with the placement forum as lock-and-decide — Decision Rights by Planning Horizon
- D-06 The process architecture: the function catalog; the seven-step lifecycle and its acceptance gate; the standards committee chartered with the queue; one constraint on the first wave — Process Standardization Lifecycle
- D-07 "Highly specified," defined once — Process Standardization Lifecycle
- D-08 One capacity-cycle calendar for every book, published a year ahead with an owner — Process Shells for a Workforce Standard
- D-09 Scope and interfaces: the scope table; the interface register with owners on both sides for the binding rows; the intake door as the single entry; the register as the interface; the weekly report derived — Enterprise Interconnection Plan
- D-10 The continuity wire: trigger and product, authority to move work, or both. Where the wire's authority is already settled above the function, this decision leaves the list and the count is fifteen — Enterprise Interconnection Plan
- D-11 Issue the Standard v0.1: owner, approvers, annual expiry, an owner and a date against every section — Anatomy of a ROC Standard
- D-12 The definitions register's ownership and signatories — The Definitions Register
- D-13 The first books: the platform instance's, and the next book the agent program clones onto — AI Agent Program for a Resource Optimization Center
- D-14 Owners: a seat against each program and each lane; the program office and who runs it — Function and Program Charters
- D-15 The first-quarter front-load with owners and dates; strike what cannot be staffed and say which quarter absorbs it — The Two-Arc Roadmap
- D-16 The validation circuit: who corrects the room's answers, by when; nothing is settled until it runs — this page
The nine settled premises the chain rests on (for example, that the function owns method and the node owner owns the decision) are not on the list; where a page relies on one it states it as a principle on Operating Principles for Work Placement, and reopening one needs new information.
The parking-lot rules
- Anything about an individual placement of work goes to the lot with the node owner's seat. The week sets the rules; the owners use them.
- Anything about a person, a grade or a name against a box goes to the lot and to the human-resources conversation, not to the room.
- Anything that needs a number the room does not have goes to the lot as a validation item with an owner and a date, named before the block ends.
- Anything that reopens a settled premise goes to the lot with the new information stated; without new information it stays settled.
- The lot is read at the close of each day. Every item leaves with an owner and a date, or is struck.
The close: readback, the circuit, the office
Each day closes with the decision record read back: a decision the room does not remember taking was not taken. Day 4 closes with three things. The templates are read back as blueprint v0.1, "for validation". Each function owner leaves with the service pack and the three-step rhythm on The Function Service Pack: validate it with the team, prepare the function's own version, execute the first transition state. And the validation circuit is named and dated (D-16): each director with their team, finance for the perimeter and the denominator, the partner-facing seat for the node taxonomy, human resources for the chart; two weeks is the usual length, and nothing on the pages is settled until it has run.
The program office, chartered at D-14, turns the sheets into the workspace ledgers the next working day and issues blueprint v0.1. Answers from the circuit are folded in as revision notes on the pages, never as new documents. Open Office Hours for Next-Generation Workforce Planning is the standing forum where the service packs are filled afterward; the week gives office hours a purpose and office hours give the service pack its content.
The decision record's discipline is borrowed from the register the function will run every week afterward: one row per decision, a permanent ID, the options and what changes if it goes the other way written before the decision rather than after, and a grade on any figure the row rests on. Writing the frame down before the decision is taken is what gives the room something to inspect; the decision-quality literature makes the parallel case that the person receiving a recommendation can install a quality control on it — a twelve-question checklist applied before the recommendation is approved.[1]
Running a shorter room
The eight blocks compress to a day and a half without changing their order: Day 1 is the first four blocks (strategy, goals, roles and organization, processes) with the organization option given the larger share of the afternoon, and Day 2 to about mid-afternoon is the remaining four (interconnections, technology, the Standard and the charters, the roadmap and the close). The day and a half is the minimum: below it the organization option is taken without its arithmetic and the charters become a read-through. What the shorter room gives up is the working sessions on the packs, which then run in office hours during the following two weeks with the same templates; the chain order, the sixteen decisions and the artifact list do not change.
The full chain
The chain is read in this order; each page carries a breadcrumb to its neighbors and back to this page. Where a title below is plain text rather than a link, the page is publishing this week. Pages 26 to 37 are the shelf the standards committee works from after the week; the room walks 26, 27 and 33 on Day 2 afternoon and returns to 26 on Day 4 morning.
- Truth About Today
- Strategy on a Page
- Operating Principles for Work Placement
- Decision Rights by Planning Horizon
- The Placement Gate
- Work Placement Landscape
- The Two-Arc Roadmap
- The Function Service Pack
- Function and Program Charters
- Instantiating the GRPI-T Framework
- Functional Organization Design for a Resource Optimization Center
- Role Cards for a Workforce Function
- Resizing a Workforce Function After an Acquisition
- Process Shells for a Workforce Standard
- Process Standardization Lifecycle
- Enterprise Interconnection Plan
- Technology Migration Plan for a Workforce Function
- The Definitions Register
- Migrating a Book of Business
- Placement Engine Build Path
- Launching an Analytics Notebook Platform
- Expanding Intraday Automation
- Systems Administration for WFM Platforms
- AI Agent Program for a Resource Optimization Center
- The Agent Team Ladder: Alpha to Production
- Anatomy of a ROC Standard
- Three-Step Forecast Build
- Forecast Lock Process
- Forecast Collision Calendar
- Event, Incident and Problem in Contact Centers
- Contact-Center Incident Severity Matrix
- Real-Time Cause and Effect Fishbone
- Incident Management for Contact Centers
- Post-Mortem and RCA for Workforce Operations
- Call-Sharing Models and Cost Allocation
- Vendor Change Control for Routing
- Activity-Code Consistency
The existing pages the chain walks without changing are The Case for Operating Model Planning, Operating Model for Workforce Management, GRPI-T Framework, WFM Goals, Process Decomposition (L0–L3), Interconnected Workforce Management, Executive Issue Register, A Roadmap Pattern for Agent Teams in WFM and Open Office Hours for Next-Generation Workforce Planning; the real-time command center whose operating environment the Standard's real-time sections describe is Resource Optimization Center (ROC).
The packs
Fourteen packs serve the week's working sessions, and a fifteenth writes the overview circulated before Day 1. Each is a Claude project pack in the pattern on Wiki:Packs: one instruction block, a few reference files, no installable skill.
| ID | Pack | Block | What the working session produces with it |
|---|---|---|---|
CP-WFM-011 |
Wiki:Packs/Strategy on a Page | Day 1 morning; Day 4 afternoon (landscape) | the truth funnel; the strategy on a page; twelve principle cards; the landscape table |
CP-WFM-012 |
Wiki:Packs/Charter and Program Launch | Day 1 afternoon; Day 4 morning | the function charter; seven program charters with first-ninety-days lists; the launch note |
CP-WFM-013 |
Wiki:Packs/GRPI-T Instantiation | Day 1 afternoon; Day 2 morning; Day 3 morning | five pillar headlines; the goals sheet; the RACI by horizon; interface cards; component cards |
CP-WFM-014 |
Wiki:Packs/Organization Design and Role Cards | Day 2 morning | the org options against six criteria; the transition chart with sunset conditions; role cards; the resizing note |
CP-OPS-001 v1.1 |
Wiki:Packs/Process Decomposition | Day 2 afternoon | L0 cards as shells; the function catalog; the first-wave list |
CP-OPS-003 |
Wiki:Packs/ROC Standard Authoring | Day 2 afternoon; Day 4 morning | the Standard's front matter with expiry; the §2 catalog with an owner and date per section; a §3 section in ten blocks |
CP-OPS-002 v1.1 |
Wiki:Packs/Executive Issue Register | Day 3 morning; Day 4 afternoon | the intake door card's routes, as Enterprise Interconnection Plan sets them; the decision record and the day-close readback |
CP-WFM-016 |
Wiki:Packs/Technology Plan | Day 3 afternoon | the build order dated; the definitions register v0; the integration-by-when table; four sub-plan shells |
CP-OPS-004 |
Wiki:Packs/Book Migration | Day 3 afternoon | the book-migration runbook: object inventory, measurement model before the phase, the phase sized as a range |
CP-WFM-008 |
Wiki:Packs/Placement Decision Engine Build | Day 3 afternoon (engine sub-plan); Day 3 morning (the gate) | the constraint register, the gate tests, supply cards and the recompute |
CP-WFM-002 |
Wiki:Packs/Agent Capability Ontology | Day 3 afternoon | the capability ontology on paper, the build order's first item beside the definitions register |
CP-OPS-005 |
Wiki:Packs/Agent Program Readiness | Day 4 morning | the agent program's charter; the readiness check per book; the ladder card; the clone checklist; the measures sheet |
CP-WFM-015 |
Wiki:Packs/Two-Arc Roadmap | Day 4 afternoon | the lane table over eight quarters; the front-load list with owners; the value timeline |
CP-WFM-017 |
Wiki:Packs/Transformation Timeline | Day 4 afternoon | the transformation timeline over five quarters with the tracks that do not fit drawn off its right edge; the track register; the sensitivity table |
CP-OPS-006 |
Wiki:Packs/Planning Week Overview | before Day 1, and each morning of the week | the overview an attendee reads instead of the chain: one paragraph per block, the pre-read assignment, and the time ledger when the week runs late |
The artifact templates
Every page in the chain produces one named artifact and says which pack fills it. The register of template IDs is kept here so that no page has to describe a template a neighbor owns, and so that the blueprint can be checked as a set.
| ID | Template | Page that carries it | Pack that fills it |
|---|---|---|---|
| TF | The truth funnel: situations, barriers, one question | Truth About Today | CP-WFM-011
|
| SG | The SOAP grid: vision, intents, dated outcomes, programs | Strategy on a Page | CP-WFM-011
|
| PC | Principle cards: focus, rule of the road, rationale, what will be different | Operating Principles for Work Placement | CP-WFM-011
|
| T1 | Goals sheet: horizon, category, measure, instrument, owner, paired with | Instantiating the GRPI-T Framework | CP-WFM-013
|
| T2 | Role card (RC-): rationale, responsibilities, skills, forums, node attribute, evolves to |
Role Cards for a Workforce Function | CP-WFM-014
|
| T3 | RACI by horizon: decision domain, the bodies, exactly one A per row | Decision Rights by Planning Horizon | CP-WFM-013
|
| T4 | Process L0 card as a shell (P-): identity filled, method block empty, "skeleton until" |
Process Shells for a Workforce Standard | CP-OPS-001 v1.1
|
| T5 | Interface card (I-): owners on both sides, flows, cadence, shared definition, state today |
Enterprise Interconnection Plan | CP-WFM-013
|
| T6 | Technology component card (TC-): component as a category, horizon, definitions it reads, integration and date |
Technology Migration Plan for a Workforce Function | CP-WFM-016
|
| T7 | Program charter (PG-): objective, scope in and out, owner as a seat, first 90 days, measures, lanes, arc |
Function and Program Charters; the agent program's row on AI Agent Program for a Resource Optimization Center | CP-WFM-012; CP-OPS-005
|
| T8 | Roadmap lane (L-): owner, programs, eight quarter cells, dependency step, value marker |
The Two-Arc Roadmap | CP-WFM-015
|
| T9 | Decision record (D-): options, recommendation, what changes if it goes the other way, outcome, owner of the consequence |
this page | CP-OPS-002 v1.1
|
| CH | Function charter (CH-): mission, vision, mandate, scope in and out, decision-rights summary, signatories, expiry |
Function and Program Charters | CP-WFM-012
|
| LT | The landscape table: four bands, node attributes, current state and end state as two rows | Work Placement Landscape | CP-WFM-011
|
| GO | The gate output page: six tests, five outcomes, the counterfactual recorded | The Placement Gate | CP-WFM-008
|
| RG | Definitions register entry: definition, version, instrument, resolution, pairing, signatories | The Definitions Register | CP-WFM-016
|
| BM | Book-migration runbook: object inventory, measurement model settled, delivered hours read, the phase as a range | Migrating a Book of Business | CP-OPS-004
|
| SP | Sub-plan shell (SP-): owner, first three deliverables, build-order step, measure, quarter |
Technology Migration Plan for a Workforce Function and its four sub-plan pages | CP-WFM-016
|
| RN | The resizing method: three levers in order, the size test, sunset conditions; headcount as an outcome, never an input | Resizing a Workforce Function After an Acquisition | CP-WFM-014; CP-OPS-005
|
| AL | Agent ladder card (AL-): book, team, rung, entered, exit evidence required and observed, catch rate, clone source |
The Agent Team Ladder: Alpha to Production | CP-OPS-005
|
| SD | The Standard front matter and the §2 function catalog, one row per function keyed by section number | Anatomy of a ROC Standard | CP-OPS-003
|
| SS | The ten-block standard section (S-n.n[.n]), one per function section |
the Series 3 section pages | CP-OPS-003
|
| TL | The transformation timeline: twelve named tracks as rows, quarters as columns, an off-chart column, plus the track register and the sensitivity table | Transformation Timeline for a Workforce Function | CP-WFM-017
|
| — | The service pack: the fifteen-section workbook, each section inheriting the week's enterprise answer | The Function Service Pack | the pack table above |
The filled set captured in the room is blueprint v0.1.
Worked example
The chain's pages share one example so that their numbers agree: a workforce planning function of a service organization formed from three heritages, roughly 40–50 planners [E] serving about a dozen books of business across voice, chat and email, with in-house and partner teams, two short-term WFM engine instances and one partner-held scheduling team, at maturity Level 2 as a band and not a point [A]. Its planning week runs Mon 20 Apr – Thu 23 Apr 2026, pre-reads sent Wed 15 Apr. The calendar is illustrative: it fixes the example's arithmetic so that the chain's pages agree with one another, and it is not a recommended date for any week.
On Day 1 afternoon the function charter CH-001 is drafted. On Day 2 morning D-03 is taken as a portfolio-facing structure with three portfolios — global multinational, small and midsize enterprise, and specialty — with work placement as a named function and one standardization seat, whose holder owns the forecasting, scheduling, real-time and placement standards and also leads the migration of the largest book; the sunset conditions are printed on the chart at D-04. On Day 4 morning the Standard v0.1 is issued with expiry Fri 30 Apr 2027 and the agent program's charter is accepted (PG-007 on Function and Program Charters); at D-13 the room takes the agent program's second book and the next rung for each of its three teams, which is the state The Agent Team Ladder: Alpha to Production carries. On Day 4 afternoon the first-quarter front-load is set to run to Tue 30 Jun 2026 with six foundations non-negotiable (the definitions register, the standards committee, the intake door, the ontology on paper, the agent team's second book, the platform instance charter), and the validation circuit is dated Fri 8 May 2026. Fifteen decisions are taken; D-10, the continuity wire, is deferred to the sponsor's leader with the date Fri 1 May 2026; one question about an individual placement is parked to its node owner.
The artifact this page produces
Decision record (T9), one row per decision. One filled example row:
| ID | Decision | Page | Options | Recommendation | What changes if it goes the other way | Outcome | Decided by | Date | Owner of the consequence | Record |
|---|---|---|---|---|---|---|---|---|---|---|
| D-13 | The first books: the platform instance's, and the book the agent program clones onto next | AI Agent Program for a Resource Optimization Center | a clean book · the migrating book, for each | a clean book for the instance; a second book with its own migration window for the agent program's clone, the first book already being run by the planning-loop team | the migrating book on the instance carries the migration's problems as the baseline; a clone onto a book whose definitions are not in the register stops at the checklist's first line | taken | the function's leader, in the room | Thu 23 Apr 2026 | the platform instance program's seat; the agent program's seat | the decisions ledger; the register row that cites the first book's published catch rate [C from the overseer's log] |
Produced in a working session with Wiki:Packs/Executive Issue Register (CP-OPS-002 v1.1); the filled set of every template in the register above, captured in the room, is blueprint v0.1.
What would change this
The page's claim is that eight half-day blocks in the GRPI-T order, with sixteen decisions where nothing later reopens anything earlier, produce a filled blueprint a function can validate and build from. A function that ran the same pages in a different order, or took the organization option on Day 1 morning, and reached a validated blueprint with fewer reopened decisions would weaken the ordering claim. A function whose validation circuit overturned a majority of the room's rows would show that the room's answers should be drafted by the teams first and ratified by leadership, which is the reverse of this chain. Neither observation exists at the time of writing; the chain records what the circuit corrects so that one day one might.
How this connects
- Next in the chain: Truth About Today — the first page walked on Day 1 morning after the two pre-reads
- Last in the chain: Activity-Code Consistency — the shelf's final page, whose breadcrumb returns here
- Defers to: The Case for Operating Model Planning (why the week is run) · Operating Model for Workforce Management (the eight questions) · GRPI-T Framework (the frame and its ordering rule) · Executive Issue Register (the register discipline the decision record borrows) · Open Office Hours for Next-Generation Workforce Planning (the forum after the week) · Wiki:Packs (what a pack is)
Maturity Model Position
A planning week is how a function at Level 2 on the WFM Labs Maturity Model™ writes down the answers that make Level 3 possible: a goal frame with trade-offs, processes documented to a standard, definitions with an owner. Its technology and agent blocks describe the route from Level 3 to Level 4. The week does not move a function up a level; it produces the artifacts whose use does, and the maturity finding it records is a band, never a point.
Four scales on this wiki use the word "level," and the chain states the difference once, here. The convention is the one the AI Agent Teams series set, and the chain adopts its wording unchanged: L0–L3 always means the documentation levels of Process Decomposition (L0–L3). It never means the process levels the Capacity Planning Cycle page writes as L1/L2/L3, the maturity Levels 1 to 5, or the L0–L3 leverage ladder of AI Leverage Maturity in WFM Teams; the series names each of those in full when it needs them. Every other page in the chain carries a one-line pointer back to this paragraph rather than repeating it.
Use this with Claude
Every working session in the week deploys one of the fourteen working-session packs in the table above, and the overview the room reads before Day 1 is written with Wiki:Packs/Planning Week Overview (CP-OPS-006); the pattern, and the two-minute deployment, are described on Wiki:Packs.
See Also
- The Case for Operating Model Planning — the five arguments for doing this together
- Operating Model for Workforce Management — the ring the week works around
- GRPI-T Framework — the order the blocks follow
- The Function Service Pack — what each function owner takes home
- Executive Issue Register — the intake door and the register the decision record borrows from
- Open Office Hours for Next-Generation Workforce Planning — where the service packs are filled afterward
- WFM Labs Maturity Model™ — the ladder the week's level target is stated on
- Wiki:Packs — the fifteen packs and the pattern
References
- ↑ Kahneman, D., Lovallo, D., & Sibony, O. (2011). "The Big Idea: Before You Make That Big Decision…". Harvard Business Review 89(6), 50–60, 137.
