Operating Model for Workforce Management
An operating model for workforce management is the set of answers to eight questions about how a workforce function is built and run: what principles drive it, what it owns and where work sits, how it operates, who decides, what roles and skills it needs, how it is organized, how it measures success, and what technology and data support it. Written down together, the eight answers are the operating model. Any one of them alone is a policy.
The eight-component form follows the common target-operating-model pattern, in which a ring of components is shown at the start of every working session so the room always knows which question it is answering. Two changes distinguish the workforce version described here. Scope and placement replaces the older "constructs" component, because the defining question for a modern workforce function is where work should sit. And sourcing, which the older method treated as an implication with its own principles, is not a component at all: it runs through every one of the eight.
The eight components
| Component | The question it answers | What the answer looks like |
|---|---|---|
| Strategy and principles | What principles drive our decisions? | A strategy on a page and a short set of principle cards, each with a rationale and a statement of what will be different |
| Scope and placement | What does the function own, and where does work sit? | A scope line (what is owned, what is wired to, what belongs to operations) and a placement landscape showing bodies of work by node, current state and end state |
| Process execution | How do we operate? | A level-one process cycle, a documentation standard for each process, and a lifecycle for taking a process from undocumented to standardized to automated |
| Governance | Who decides? | A decision-rights matrix by planning horizon and a small number of forums with a stated scope, cadence and membership |
| Roles and competencies | What roles, skills and behaviors? | A role catalog with one card per role, distinguishing roles from jobs, and a view of how roles evolve as routine work moves to automation |
| Org structure | How are we organized? | The structure for the next transition state, not the end state, with the reasoning for staging |
| Measures and scorecard | How do we measure success? | A category pyramid with the unit of value at the apex, gauge groups beneath, and a checklist any new measure must pass |
| Technology and data | What supports all of it? | One data core and one set of definitions, with the tools as spokes, and a build order that puts the ontology on paper before any platform |
Sourcing runs through every component
An outsourced or captive supply base is not a ninth component. It appears inside each of the eight:
- in principles, as rules that apply to every node rather than to the in-house estate alone;
- in placement, as nodes the work can sit in;
- in governance, as a party with decision rights on daily performance for its own node;
- in roles, as a competency every functional role carries rather than a separate vendor-management team;
- in org structure, as oversight inside each functional team rather than a vendor-management box on the chart;
- in process, as the same process applied at another node with a node attribute, not a bolted-on "third-party" variant;
- in measures, as one instrument across every node so that comparisons mean something;
- in technology, as supply cards the placement engine reads.
The reason is practical. Where vendor management is run as a separate stream, the other components tend to be designed for the in-house estate and then patched for the vendor. The patches accumulate into a second, weaker operating model. Designing the vendor into each component from the start produces one model, and the vendor's output becomes a natural function of the organization design rather than an exception to it.
Using the ring
The ring is a navigation device. It is shown once at the start of an alignment session to set the map, and again at the head of each section with the current component highlighted. Every component is then worked in the same four beats: a definition (what the component is), the truth about today (current state, stated without blame), a proposal with options where options genuinely exist, and a template the room fills in live. The filled templates are the deliverable; a deck that describes an operating model without the room having filled anything in is not yet an operating model.
In a planning week the ring is walked over eight half-day blocks, Day 1 to Day 4, one or two components per block, in the order the GRPI-T Framework gives. The mapping from component to block to page:
| Component | Block | Page that produces the template |
|---|---|---|
| Strategy and principles | Day 1 morning | Strategy on a Page · Operating Principles for Work Placement |
| Measures and scorecard | Day 1 afternoon | Instantiating the GRPI-T Framework (the goals sheet) |
| Roles and competencies | Day 2 morning | Role Cards for a Workforce Function |
| Org structure | Day 2 morning | Functional Organization Design for a Resource Optimization Center |
| Governance | Day 2 morning | Decision Rights by Planning Horizon |
| Process execution | Day 2 afternoon | Process Shells for a Workforce Standard · Process Standardization Lifecycle |
| Scope and placement | Day 3 morning; Day 4 afternoon | Enterprise Interconnection Plan (scope) · Work Placement Landscape (placement) |
| Technology and data | Day 3 afternoon | Technology Migration Plan for a Workforce Function |
The ring on this page is the eight-component operating-model ring. Integrated Global Resource Optimization Center draws a different object also called a ring — the three functions of an integrated center with its peers wired around them — and the two are not the same thing.
Relationship to maturity
The eight answers change as a function climbs the WFM Labs Maturity Model™. At the foundational level most components are answered by inheritance from whatever structure the organization arrived with. At the progressive level each has a written answer and an owner. At the advanced level the answers are connected: the scorecard reads the definitions, the governance forums consume the placement engine's output, and the roles have shifted toward oversight. The ring does not change; the quality of the eight answers does.
Use this with Claude
A ready-to-deploy instruction set and reference files for the first component, the truth funnel, the strategy on a page and the principle cards, are at Wiki:Packs/Strategy on a Page (CP-WFM-011). The other components' packs are listed on Planning Week for a Workforce Function.
See Also
- The Case for Operating Model Planning: why leaders answer the eight questions together, and what the team receives
- Right Work, Right Capability, Right Location: the vision statement the model serves
- Integrated Global Resource Optimization Center: the coordination point at the center of the ring
- GRPI-T Framework: the diagnostic that the components map onto
- Vendor Governance Placement: governance with the vendor inside it
- Role Evolution in the Resource Optimization Center: the roles component over time
- Placement Engine Architecture: the technology and placement components together
- Planning Week for a Workforce Function: the ring walked over four days as a chain of pages, decisions, packs and artifacts
- Strategy on a Page: the first component's artifact
- Operating Principles for Work Placement: the principle cards, twelve, each with what will be different
- Instantiating the GRPI-T Framework: the order the eight components are worked in
