Functional Organization Design for a Resource Optimization Center

Part of the Planning Week chain · previous: Instantiating the GRPI-T Framework · next: Role Cards for a Workforce Function Functional organization design for a resource optimization center is the method by which a planning room chooses the structure of a workforce function under one leader: six criteria written down before any chart is drawn, three archetypal options tested against them, placement drawn as a named function in every option, and the chosen chart issued as a transition state with its sunset conditions printed on it. ROC Organization Models carries the four shapes and the hybrid consolidated estates tend to adopt; this page is the design method on top of it, not a fifth model. The page produces the org options table and the transition chart with sunset conditions, and is worked in a session with Wiki:Packs/Organization Design and Role Cards (CP-WFM-014).

A method, not a model

The structure of a planning function is a maturity ceiling rather than a background condition: the Progressive form needs a formal goal frame, interval-level reporting and documented trade-offs, each owned somewhere, and a structure organized by inherited entity, region or reporting line has several places where each could live and none where it must. The ceiling is not the people; it is the absence of a function-shaped slot. The design method's job is to create the slots, and its governing sentence is same people, clearer structure: the room built the current structure through several heritages, and it was the right answer for each business at the time it was built.

ROC Organization Models sets the models against the classical structural choices and the grouping trade-off; this page adds only what a room needs to decide in one morning: the criteria, the options, and the printed sunset conditions.

The six criteria

The criteria come first, so that the room argues with the criteria rather than with the chart. Each is a thing to write down, not a preference to hold. Criteria 2 and 3 are the two tests ROC Organization Models sets out, carried here unchanged; criteria 1, 4, 5 and 6 are what a room needs beside them to leave with a chart.

#	Criterion	What the room writes down
1	The faces arithmetic	Two counts per option: how many counterparts each business leader sees, and how many counterparts each department (finance, recruiting, technology) sees for the same question (the arithmetic is on ROC Organization Models; the counts come from the interface register)
2	The pooling test	The share of the estate's work that is place-bound (regulation, data residency, an on-soil promise) against the share servable from anywhere, at the constraint set expected at the end of the horizon; that language constraints may decay while regulatory and data-residency constraints do not is the working assumption ROC Organization Models records for the pooling test, to be tested estate by estate, and the eligibility constraint it rests on is on Sourcing Design Axes: Node and Client Ownership
3	The size test	How large the human organization needs to be at all, stated as a direction and a dependency (the interior optimum sizes the human population, and that question is upstream of every structural one); never a headcount (Resizing a Workforce Function After an Acquisition)
4	Converge or ratify	Whether the option produces one method and one source of truth, or ratifies the inherited ones under a new set of titles
5	Sunset conditions	For every seat or assignment that exists to consolidate, the condition under which it ends, in a sentence a stranger could test
6	Spans	Whether each leader's span is defensible for the coordination load: leaders over multi-time-zone, multi-partner coordination carry small spans by design, and no source validates a total leader count from the size of the function

On the sixth criterion the evidence is specific and limited: span and performance are related curvilinearly, and the diversification of function, time and space a leader coordinates conditions the optimum, so multi-time-zone, multi-partner coordination supports a leader layer over a flat structure. No source ties a leader count to the size of a shared service.

Three options against the criteria

Three archetypal options are enough. Every one of them sits under one leader, plans against the same demand taxonomy (how demand is segmented for planning and how people are organized are different objects), and draws placement as its own block. The structure below is presented as the function leader's proposal, with the alternatives considered beside it; the criteria are what the room argues with.

	A. Global functional	B. Portfolio-facing, with a standardization seat (the proposal)	C. Functional with regional delivery
Organized by	the stages of the planning cycle: long-range capacity · forecasting · scheduling · real time · placement; reporting and administration as a supporting function	two layers on two axes: a thin leader-facing layer of portfolio planning seats over an execution layer by horizon and function. Three portfolios in the first year: global multinational, small and midsize enterprise, and specialty (a regional and specialized-services portfolio); beside them a placement seat and a standardization seat	the functional blocks of A, each with regional cells; a standalone block for a regulated segment
1 Faces	departments: one counterpart per kind of question. Business leaders: several, one per stage	business leaders: one face each. Departments: one counterpart per question in the execution layer. Both counts are one, which is the point of the hybrid	business leaders: one per region. Global departments: one per region, and reconcile
2 Pooling	pools across the whole estate; regional presence only where the test demands it	pools in the execution layer; the portfolio layer is re-pointed, not rebuilt, when a book moves	regionalizes around constraints that may decay; pooling limited to a region
3 Size	sized once, by function	sized by function in the execution layer; the portfolio layer is small and cheap to re-point	sized per region, so the same capability is bought several times
4 Converge or ratify	converges	converges in the execution layer; the portfolio layer carries the leader relationship and no method of its own	ratifies regions
5 Sunset conditions	none needed; nothing is transitional	the standardization seat's migration assignment is time-boxed and printed; any real-time consolidation box carries a condition and a destination	none
6 Spans	five or six function seats under one leader	three portfolio seats, a placement seat, a standardization seat, and any partner-contracts manager beneath placement	function seats plus regional leads: the largest count
Where placement sits	its own block	its own seat, absorbing real-time operations at sunset	its own block, with regional cells
When it is right	the fallback if the room rejects a matrix inside the function	when leaders need one counterpart and the estate must converge on one method at the same time	rarely at the planning layer; regional presence belongs in the execution layer

Option B carries a known long-run risk the room should hear before it votes: the three-box shape (partner, shared service, center of expertise) resolves tensions in the short term and fragments accountability over time unless something other than the seats holds the whole. The shape is the shared-services pattern human-resources functions have run for three decades. The holders are named two sections below; a room that cannot name all three has not yet chosen B.

Placement as a named function

Every option draws placement as its own block; its existence is a consequence of the function catalog (placement is a function in the integrated center's ring), not a room decision. The placement function is the concept that work sits where objectives and constraints say, at every horizon; the placement engine is the machinery (constraints define the feasible set, scores rank inside it, the owner decides). The engine needs an owner for the constraint register and the gate, and the registers (objectives, constraints, definitions, the counterfactual record, the executive issue register) need a steward who owns the method and never an outcome; the placement seat is where both live. Debates about placement are usually debates about whether the node owner (the owner of the body of work placed at a node, never the operator of the node) keeps the decision; that is settled as a principle on Operating Principles for Work Placement and expressed as the first rule of Decision Rights by Planning Horizon.

A standards owner who carries a migration

The standardization seat in option B owns the forecasting, scheduling, real-time and placement standards and also leads the migration of the largest book of business onto the function's platform. The pairing is deliberate: the migration is the forcing function that makes standardization happen on a date (Platform Migration as a Definitional Forcing Function), and the standard's owner is best placed to refuse a shortcut that would fork it. Its risk is that the migration comes to own the standard: a deadline amends a definition; an inherited configuration becomes the instance's default. Three holders that are neither the seat nor the migration prevent it.

Holder	What it holds	How the migration reaches it
One platform configuration	the activity-code set, the skill and pool dictionary, the lock calendar, configured once to the standard	the migrating book is configured to the instance; the instance is never reconfigured to the book. A book that cannot be configured to the standard has found a definition the register must settle first
One definitions register	the versioned definitions every report and platform reads (The Definitions Register)	a migration may propose a definition; only the register's change control (propose · review · version · adopt) can adopt it, with the register's signatories
One change-control board	routing, platform configuration, contract changes and the migration schedule; chaired by the placement seat, with the standardization seat as a member, not the chair	the migration's phases are change-control items on the board's calendar; a phase that needs an amendment to the standard waits for the standards committee's acceptance gate (Process Standardization Lifecycle) like any other change

Three consequences follow. What is time-boxed is the migration assignment, not the seat: when the last phase is accepted, the seat keeps the standards, and the chart prints that as the assignment's sunset condition. The standard's owner, approvers and expiry sit in its own front matter (Anatomy of a ROC Standard) and do not move with the migration's dates. And the seat reports the migration to the board and the standard to the council, so a slip in one cannot be traded for a concession in the other.

Sunset conditions and where real time goes

A transitional seat without a printed sunset condition becomes permanent, which is how a merged function becomes the residue of its heritages rather than a design. Every consolidation seat or assignment therefore carries, on the chart, a testable condition (when one scheduling standard is live on one platform; when the real-time protocol and the automation layer are live; when the migration's last phase is accepted) and a destination for its work. Decision D-04 asks the room to print the conditions and to say where real-time operations report at sunset: to the placement seat (recommended, because real time is the horizon at which the engine acts) or to the portfolios (which re-fragments the method by book). The conditions are re-read at every validation circuit.

Where long-range capacity planning sits

Long-range capacity planning may sit in another organization, most often beside the function that owns the annual operating plan. The method treats that horizon as an interface to be hardwired (an owner on both sides, a cadence on the capacity cycle's calendar, shared definitions) rather than as a defect, so that the plan of record the function schedules against is the one the other organization signed; Enterprise Interconnection Plan carries it as a first-class row of the register, and the chart shows it as a wire, not a dotted line.

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) the room writes the six criteria on the wall, computes the faces arithmetic for each option (A: each business leader sees five planners, one per stage; B: one; C: one per region [C]), and takes D-03: the portfolio-facing structure, with three portfolio seats (global multinational · small and midsize enterprise · specialty), a placement seat, and a standardization seat whose migration assignment is time-boxed to the largest book's final phase. D-04 is taken in the same block: real-time operations transfer to the placement seat at sunset; the conditions are printed on the chart. One question, where an individual body of work should sit, is parked to the node owner as a gate question. The chart, the criteria and the conditions go to the validation circuit, which closes Fri 8 May 2026.

The artifact this page produces

The org options table (one column per option, one row per criterion, as above) and the transition chart with sunset conditions, one row per seat or assignment. One filled example row of the chart's table:

Seat or assignment	Owns	Faces	Sunset condition	Work goes to
Standardization seat: the migration assignment	the migration of the largest book onto the instance, phase by phase, as change-control items	the change-control board; the migrating book's node owner	when the last phase is accepted at the board and the book runs on the standard configuration	the seat keeps the four standards; the assignment ends

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 method's central claim is that a portfolio-facing structure converges on one method only if the standard is held by a platform configuration, a definitions register and a change-control board rather than by the seats. The observation that would overturn it is a merged function that ran the three-box shape for two annual cycles with no such holders and still reports one method, one configuration and one register; the holders would then be overhead. The pairing of standard and migration would be overturned by a migration whose final configuration differs from the standard's, adopted without a register version.

How this connects

• Previous in the chain: Instantiating the GRPI-T Framework — the Roles pillar starts here
• Next in the chain: Role Cards for a Workforce Function — the seats become cards
• Defers to: ROC Organization Models (the four models, the faces arithmetic, the two tests, the hybrid of record) · WFM Organizational Models (the forms and their reporting lines) · WFM Center of Excellence CoE Design · Building a WFM Team (sizing rules of thumb, not restated) · Team Size, Span of Control, and Dunbar's Number (span evidence at team level) · Role Evolution in the Resource Optimization Center
• Feeds: Resizing a Workforce Function After an Acquisition · Decision Rights by Planning Horizon · Enterprise Interconnection Plan · Systems Administration for WFM Platforms (the platform configuration as a holder of the standard)

Maturity Model Position

The functional slot is the Level 3 form, because one methodology and clean platform ownership are what the automation layer needs; the two-layer hybrid is the Level 4 form, when placement genuinely moves and leaders need one counterpart for a scored proposal. A function at Level 2 uses this page to build the Level 3 execution layer first and the thin leader layer over it. 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

• Planning Week for a Workforce Function
• ROC Organization Models
• The Workforce Broker
• Integrated Global Resource Optimization Center
• Inherited Sourcing Doctrine in Merged Service Estates