Role Cards for a Workforce Function

From WFM Labs

Part of the Planning Week chain · previous: Functional Organization Design for a Resource Optimization Center · next: Resizing a Workforce Function After an Acquisition Role cards for a workforce function are the method by which a planning room defines the roles of a workforce function one card at a time, each card carrying the role's rationale, responsibilities, skills, forum participation, node attribute, what it evolves into and the direction of its count, so that the function's catalog of roles is written down before anyone is assigned to one. A role card describes a role, not a job: one person may hold two roles, and one role may be held at several nodes. Role Evolution in the Resource Optimization Center carries the role map (what each role becomes as the function matures) and WFM Roles the practice definitions of the core families; this page carries the card and the catalog a room fills from them. The page produces the role card (T2, identifiers RC-nnn) and is worked in a session with Wiki:Packs/Organization Design and Role Cards (CP-WFM-014).

Role, not job

A job is a post on the org chart with a grade and a person; a role is a bundle of responsibilities the function needs held. The distinction matters in a merged function because the same responsibility is usually held under three titles, and the same title covers three responsibilities, and neither fact is visible until the roles are written independently of the posts. Writing the cards first lets the room see that a forecaster in one heritage and a planning analyst in another hold the same role, and that a scheduler in a third holds two. It also lets the count direction be stated as a direction (new, up, flat, down, retires as a title) without a number attached, which keeps the card from being read as a headcount decision, which it is not.

The card's shape is a working device older than this frame: the four fields it inherits — rationale, responsibilities, skills and forum participation — are the ones a person needs in order to know whether a role is theirs. The frame adds three fields the resource optimization center needs, described below. The reasoning behind the shape is the work-design finding that a role is motivating and holdable to the extent that its task identity, significance and autonomy are stated rather than inferred;[1] a card that cannot state a role's rationale has found a role that should not exist. Work-design research since then has widened the frame from the task to the relational and proactive content of a role, which is why the card carries forums and a node attribute beside responsibilities.[2]

The card

Field What it holds Why it is a separate field
ID RC-nnn, never reused every forum card, RACI row and charter cites it
Role the role's name in the function's own vocabulary one name per role; a synonym is a second card by mistake
Horizon the planning horizon the role works at: 12–36 months · annual · quarterly and monthly · weekly and daily · intraday and real time · any a role's horizon decides which forums it sits in and which decisions it is consulted on
Rationale why the role exists, in one sentence that would be false if the role were removed the test for a role that is a title rather than a need
Responsibilities three to six, each in the active voice with an object what the role is accountable for producing; matched to the RACI on Decision Rights by Planning Horizon
Skills the capabilities the role needs, named as capabilities rather than qualifications what the function must train or hire for; Role Evolution in the Resource Optimization Center lists the capabilities every existing role must learn
Forums the standing forums the role sits in, by name the placement forum, the council, the change-control board and budget season each need a known membership
Node attribute which nodes the role is held at (all; a hub; a service center; a partner) and whether the post is badged or partner-held the node is a place work can sit; a role held at a partner is the same role with a different custody rule
Evolves to what the role becomes at Level 4 and 5, cited from the role map the direction of the function's training investment
Count direction new · up · flat · down · retires as a title; never a number the honest statement of what automation does to the role, without a headcount attached

The catalog by horizon

The catalog is the role map cut by horizon, with the place each role sits in the chosen structure. The evolutions themselves are on the role map and are not redrawn here; the catalog adds the horizon, the node attribute and the seat, which the map does not carry. One row carries a declared change rather than a reading of the map: Integrated Global Resource Optimization Center and Role Evolution in the Resource Optimization Center both currently house continuity and crisis inside the center, and this chain proposes instead that the center keep the products while the roles sit with the continuity function — which is decision D-10, put to the room on Enterprise Interconnection Plan.

Horizon Role today (Level 2) Evolves to (per the role map) Node attribute Where it sits in a portfolio-facing structure
12–36 months capacity planner scenario architect and translator all nodes; the network design the portfolio planning seats, or the organization that holds long-range planning where it sits outside the function; simulation from the placement seat
annual and quarterly workforce management manager center leader and workforce strategist all the portfolio planning seats
monthly (the capacity cycle) forecaster, mid-term probabilistic forecaster all; per book the portfolio planning seats
weekly and daily forecaster, short-term; scheduler probabilistic forecaster; schedule designer badged and partner-held posts, transitional until automated short-term forecasting with the portfolio seats; scheduling under the standardization seat until the scheduling standard is live on one platform
intraday and real time real-time analyst automation orchestrator; agent overseer badged and partner-held, the same rule the real-time consolidation box, transferring to the placement seat at sunset
any reporting analyst workforce intelligence analyst all beside the definitions register's owner
any partner performance analyst node performance on one instrument (a product, not a role) the instrument sits in the center; the verdict with the node owner the placement seat
any continuity planner; crisis communications lead placement under duress; the crisis re-plan (products the center keeps; whether the roles leave with the continuity function or move into the center, as Role Evolution in the Resource Optimization Center describes, is decision D-10) the wire to continuity, not a team the placement seat, for the products
any methodology steward (added) unchanged; gains the engine's explainability records all the placement seat, or a named deputy beneath it
any automation analyst (added); operations research analyst as named all the placement seat and the analytics function

Two roles the catalog adds to the function

Neither role is new to the wiki. Role Evolution in the Resource Optimization Center already lists the automation analyst among the roles that are new, and The Automation Analyst is its own page; the methodology steward is the one this catalog introduces. What the catalog adds is both roles' place in a merged function's own structure — the horizon they work at, the node attribute, and the seat they sit under.

The methodology steward. The pattern it comes from is a process director who does not operate the process, one level up from the seats that do. The frame's version owns the registers (the objectives register, the constraint register, the definitions register, the counterfactual record) and chairs the standards committee, and it owns the method and never an outcome. The role exists because the registers need an owner who has nothing to gain from any particular placement; a steward who also owns a book will, in good faith, read the register in the book's favor. The steward's home is a consequence of the org decision: the placement seat, with a named deputy for the registers where the seat's span will not carry them.

The automation analyst. The role converts a process written down to an L2 step table into an agent specification, reading from the table and never filling in from memory; The Automation Analyst carries the conversion step by step and this page does not restate it. It appears on the catalog because the resizing method's third lever (handing written-down work to agent teams) has no owner without it, and because the acceptance gate's two entry criteria for automation (clear step ownership; the active voice) are what the analyst reads for.

Both roles are chosen against the survival test Role Evolution in the Resource Optimization Center applies to every role on the map — whether a role's complement to automation is worth paying for — and both pass it for the same reason: the steward's complement is arbitration and the analyst's is specification, and neither is codifiable in the first arc. The ironies-of-automation warning that page applies to modelers applies to these two as well, which is why both cards carry a responsibility to produce the answer and not only to check it.[3]

Partner performance as a competency in every role

The catalog carries no partner-management team and no third-party performance leader. Partner performance is a competency in every role: the forecaster reads a partner's committed capacity as supply, the scheduler publishes a schedule of record a partner staffs to, the real-time analyst steers across partner and badged pools on one protocol, and the placement seat compares every node on one instrument. The commercial functions that need comparison across suppliers stay central and commercial (Vendor Governance Placement holds where each belongs); the cards carry the operational relationship with a partner in the role that does the operational work. A card whose skills field omits partner performance describes a role for an estate with no partners.

Posts held by partners: transitional until automated

Some posts (schedulers, real-time analysts, some short-term forecasters) are held at a partner as a labor-hour arrangement inherited from a heritage. The cards state the posts as transitional until automated, with a named owner for the automation plan; the path is the one the function's own posts follow: decompose the work to L2, automate with the partner, and shift the post to build, oversee, exceptions and human-in-the-middle work. A card for a partner-held post carries the same role as its badged twin and a different custody line, which keeps the card from being read as a sourcing decision; that belongs to the gate.

How a room writes the cards

The cards are drafted before the week from the role map and the practice pages, and the room on Day 2 morning accepts, amends or strikes them. Three rules govern the session. The cards are written in the room's words, with ranges rather than points in any cell that carries a number. A card is accepted only with its forums filled, because the forum cards on Decision Rights by Planning Horizon are built from the roles that sit in them. And a card's count direction is stated once: the direction is the role map's, and a number, if ever needed, is an output of Resizing a Workforce Function After an Acquisition and never of this page. The automation analyst and the overseer are needed at the first agent handover and the cards for both are accepted on Day 2 even where the handover is a year away, because the agent ladder's alpha rung needs a named overseer to shadow.

Worked example

The function is a workforce planning function formed from three heritages, roughly 40–50 planners [E], at Level 2 (Foundational) as a band [A]. On Day 2 morning (Tue 21 Apr 2026), after D-03 chooses the portfolio-facing structure, the room accepts fourteen cards [C] drafted from the role map: nine evolutions, the steward, the automation analyst, the overseer, the operations research analyst and the portfolio planning seat as a role. RC-001, the methodology steward, is the first card accepted and the one the room amends most: the deputy line is added because the placement seat's span will not carry the registers as well. RC-004, the scheduler, is accepted with the node attribute "badged and partner-held; the partner-held posts transitional until automated, owner the standardization seat" and count direction "down; schedule-building retires as a title," with no number. The overseer's card names the migrating book's agent team as its first custody: the planning-loop team on that book is already at the pilot rung when the week opens and the scheduling and real-time teams at beta, so the card records a custody that exists rather than one a date will create. The cards go to the validation circuit, closing Fri 8 May 2026.

The artifact this page produces

Role card (T2), one card per role in the catalog. One filled example row:

ID Role Horizon Rationale Responsibilities Skills Forums Node attribute Evolves to Count direction
RC-001 Methodology steward any the method needs an owner who never owns an outcome owns the objectives, constraint and definitions registers and the counterfactual record; chairs the standards committee; runs the validation clause process standards; queueing arithmetic; evidence grading; writing the council; the change-control board; the placement forum (method) all unchanged; gains the engine's explainability records new

Produced in a working session with Wiki:Packs/Organization Design and Role Cards (CP-WFM-014); the filled set is part of blueprint v0.1.

What would change this

The page's central claim is that roles written independently of posts reveal overlaps and gaps that a title-based catalog hides. The observation that would overturn it is a merged function whose cards, once written, map one-to-one onto its inherited titles; the card would then be a documentation format and the catalog could be built from the org chart. The claim that partner performance is a competency rather than a team would be overturned by an estate in which the roles that carry it measurably neglect it relative to a dedicated team on the same instrument, over more than one contract cycle.

How this connects

Maturity Model Position

The card is level-agnostic; the catalog it produces is not. At Level 2 the cards describe the deterministic-by-hand roles and mark their direction; at Level 3 the automation analyst, the overseer and the orchestrator appear as cards with custody; the evolutions the cards point at are the Level 4 forms on the role map. The planning week writes the Level 2 catalog with every card's Level 4 destination filled, so the training plan and the count direction are decided together. Four scales on this wiki use the word "level"; Planning Week for a Workforce Function states which is which. This page uses the maturity levels.

See Also

References

  1. ↑ Hackman, J. R., & Oldham, G. R. (1976). "Motivation through the Design of Work: Test of a Theory". Organizational Behavior and Human Performance 16 (2), 250–279. doi:10.1016/0030-5073(76)90016-7.
  2. ↑ Grant, A. M., & Parker, S. K. (2009). "Redesigning Work Design Theories: The Rise of Relational and Proactive Perspectives". Academy of Management Annals 3 (1), 317–375. doi:10.1080/19416520903047327.
  3. ↑ Bainbridge, L. (1983). "Ironies of Automation". Automatica 19 (6), 775–779. doi:10.1016/0005-1098(83)90046-8.
Retrieved from "https://wiki.wfmlabs.org/w/index.php?title=Role_Cards_for_a_Workforce_Function&oldid=4725"