Instantiating the GRPI-T Framework

Part of the Planning Week chain · previous: Function and Program Charters · next: Functional Organization Design for a Resource Optimization Center Instantiating the GRPI-T Framework is the method by which a planning room turns the five pillars of the GRPI-T frame (Goals, Roles, Processes, Interpersonal and Interconnected, Technology) into five filled sheets, each carrying a one-sentence headline, a named owner and a template, in one fixed order across the four days of a planning week. The frame is an instrument for diagnosing a workforce function; instantiating it is the act of writing down, for one function, what each pillar is and what it must become, so that the function's standard, its programs and its roadmap are all built on the same five statements. The page produces the goals sheet (T1) and the five pillar headlines, and is worked in a session with Wiki:Packs/GRPI-T Instantiation (CP-WFM-013); the sheets for the other four pillars are produced on the chain pages that carry them and are named below.

What "instantiated" means

A pillar is instantiated when three things exist for it: a headline, one sentence that states what the pillar is today and what it becomes by the expiry of the function's standard, carrying an evidence grade in the sense of Data Synthesis Before Decision (Established, Inferred, Asserted or Open); a sheet, the filled template for the pillar, with an identifier on every row; and an owner, a seat (a post on the org chart: a director-graded or manager-graded box with its scope and its sunset condition) that holds the sheet after the week and brings it to the validation circuit. A headline without a sheet is a slogan; a sheet without an owner is a document no one will reopen.

Instantiation is not scoring. The GRPI-T Framework page carries the rules by which the maturity diagnostic reads the five pillars, and this page does not restate them; a room that has not run the diagnostic can still instantiate the frame, because the sheets describe what the function will do, not what level it holds. The frame uses the maturity levels by canonical name (Initial, Foundational, Progressive, Advanced, Pioneering), and this page uses them only in the column of the goals sheet that records where a measure belongs.

The frame's origin explains why the order is not negotiable, and GRPI-T Framework carries that origin in full: the first four pillars are a priority ordering with the interpersonal layer last, and the fifth comes from the reading of organizational change in which task, structure, people and technology move together. The consequence for a room is the only part this page adds: a room that fills the technology sheet first specifies a platform for roles it has not defined against goals it has not ordered, which is why the order below is fixed and why the facilitation rule that follows works in one direction.

The order across the week, and the rule applied live

The five pillars are walked in their own order, one per half-day block, so that each sheet is filled with the sheets to its left already on the wall.

Block	Pillar	Sheet filled (template)	Chain page that carries it	Decision taken in the block
Day 1 afternoon	Goals	Goals sheet (T1)	this page	D-02 the goal frame
Day 2 morning	Roles	Role cards (T2); RACI by horizon (T3); the org option and its sunset conditions	Functional Organization Design for a Resource Optimization Center · Role Cards for a Workforce Function · Decision Rights by Planning Horizon	D-03, D-04, D-05
Day 2 afternoon	Processes	Process L0 cards as shells (T4); the function catalog	Process Shells for a Workforce Standard · Process Standardization Lifecycle	D-06, D-07, D-08
Day 3 morning	Interpersonal and Interconnected	Interface cards (T5); the scope table; the intake door	Enterprise Interconnection Plan · The Placement Gate	D-09, D-10
Day 3 afternoon	Technology	Technology component cards (T6); the build order	Technology Migration Plan for a Workforce Function	none of its own
Day 4 morning	all five, read back	the five headlines as the standard's §1	Anatomy of a ROC Standard	D-11

The "one pillar to the left" rule is the frame's ordering rule used as a facilitation move. When a sheet will not fill, the facilitator does not press on the sheet; the room turns to the pillar to its left and asks what is missing there. The symptoms are recognizable.

What happens in the room	Where to look	What is usually missing
A role card cannot state what the role is accountable for	Goals	No agreed ordering of objectives, so accountability has nothing to attach to
The catalog argues about which function owns a process	Roles	No owner for the definitions the process depends on
An interface card cannot name what flows across it	Processes	The process that would produce the flow is not written down, so the flow has no cadence
The technology sheet lists a platform before a definition	Interpersonal and Interconnected	The interface that would carry the definition (usually technology or finance) has no owner on the function's side

The rule turns GRPI-T Framework's summary of the original insight — that dysfunction almost always traces to misalignment in one of the layers above the one where it is felt — into a question the facilitator can ask in the moment.

The Goals pillar: the sheet

Goal-setting capability is itself a dimension of maturity. A function at Level 2 (Foundational) typically holds several metrics that are not balanced against each other: a service level, an adherence figure, a shrinkage figure, each with a target and none with a stated trade-off. A function at Level 3 (Progressive) holds a formal goal frame across a small number of categories with the trade-offs written down. That distinction matters beyond reporting: a placement engine consumes objectives with weights, not a list of siloed targets, so reaching the Progressive form on goals is the precondition for placement rather than a reporting improvement. The goals sheet is how the room writes the frame down. The practice page WFM Goals carries five goal categories (service quality, efficiency, employee experience, customer experience, compliance) and the trade-off triangle among them; the planning sheet collapses those to four categories, customer experience, cost, employee experience, and risk (flexibility counted as a risk objective), and holds compliance as a constraint rather than a goal, because a constraint excludes and a goal is weighed.

The sheet's rules, each of which is a line the room ratifies as decision D-02:

• The horizon is the row. Placement runs at every horizon (12–36 months, annual, quarterly and monthly, weekly and daily, intraday and real time, and intake events at any horizon) with a different object at each, so the goal the function holds differs by horizon even within one category.
• Goals, not targets. A goal is a sentence stating what good looks like. A target is a number, and a number appears on the sheet only where a source carries it and the instrument can detect the difference it asks for; a target set before its instrument exists is an aspiration recorded as a fact.
• Weights per node, with a body-of-work override. 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. A back-office node may weight cost heavily and experience lightly; a synchronous voice node carries both. Where one body of work needs different weights from its node, the override is recorded in the constraint register, not on the sheet.
• Value as the unit; two sides, never blended. The quality score and the customer-experience index are paired on the sheet and never averaged; the pairing rule and its reason are on Quality Score and Customer Experience Index.
• Targets by service tier, never by location. A service tier is the tier of service the offer sells a client; a node's location is a consequence of placement, and a target that varies by location has silently decided placement.
• The level column. Each measure is placed at the level where it belongs on the ladder, not where the estate is; the column tells the room which measures are Arc 1 (by hand) and which are Arc 2 (by engine).

The sheet carries a seven-question check on any new measure: who owns it, what decision it changes, what instrument produces it, at what resolution, how it is gamed, what it is paired with, and when it expires. The check is older than this frame; goal-setting research has held for decades that specific goals with feedback outperform vague ones, and that a goal whose attainment cannot be observed does not function as a goal at all. The pairing rule has the same lineage as the balanced scorecard's insistence that financial and non-financial measures be read together rather than reduced to one.

The headline per pillar

A headline has a fixed shape: the pillar today, in one clause; the pillar at the standard's expiry, in one clause; the grade. It is written by the room, in the room's words, after the sheet is filled, and it is the sentence the function's standard prints in its scope section and the launch page reads back on Day 4. The grade is on the first clause, which is a claim about the current state; the second clause is a commitment and carries no grade. Headlines are written non-accusatorially: a current state formed from several heritages is several correct answers placed side by side, and the headline says what exists and what it becomes, never what was neglected.

Two rules keep headlines honest. A headline never states a maturity level as a point; where a level is mentioned it is a band. And the Interpersonal half of the fourth pillar gets its own clause, because a function assessed only on its interfaces has left the relationships unassessed, and the sheet should say so as Open rather than omit it.

Worked example

The function is a workforce planning function formed from three heritages, roughly 40–50 planners [E], serving about a dozen books of business, at Level 2 (Foundational) as a band, not a point [A]. Its planning week runs Mon 20 Apr – Thu 23 Apr 2026. On Day 1 afternoon (Mon 20 Apr) the room fills the goals sheet and takes D-02: four categories; weights per node with the override in the constraint register; value as the unit; the quality score and the customer-experience index paired; targets by service tier. The first row written is G-001, below. The Goals headline recorded: "Goals exist per metric and are not weighed against each other (Established); by Fri 30 Apr 2027 the function holds one goal frame across four categories with the trade-offs written on the sheet." On Day 2 morning the role cards will not fill for the placement seat until the room returns to G-004, the annual objectives row, and agrees who reorders it; the "one pillar to the left" rule is applied once, and recorded. On Day 4 morning (Thu 23 Apr) the five headlines are read back as §1 of the standard, issued as v0.1 with expiry Fri 30 Apr 2027, and the validation circuit corrects them by Fri 8 May 2026.

The artifact this page produces

Goals sheet (T1), one row per goal. One filled example row:

ID	Horizon	Category	Goal	Measure	Instrument today	Level	Owner (shared or ROC)	Paired with
G-001	Quarterly / monthly	CX	the customer-experience index held at parity across nodes at matched tenure	CX index by node, matched tenure	index designed; live at one node [E]	3	shared: node owner and the global ROC	cost per unit of value; the quality score (never blended)

The five pillar headlines are recorded on the same sheet as five untabled lines, one per pillar, each with its grade. Produced in a working session with Wiki:Packs/GRPI-T Instantiation (CP-WFM-013); the filled set is part of blueprint v0.1.

What would change this

The page's central claim is that the five sheets must be filled in the frame's order because a sheet that will not fill is diagnosed one pillar to the left. The observation that would overturn it is a room that fills the technology and interface sheets first, without an agreed objective ordering, and whose sheets survive the validation circuit unchanged: if the platform and interface commitments made on Day 3 do not have to be reopened when the goals are ordered later, the ordering rule is a preference rather than a dependency, and the week could be run in any order that suits the calendar.

How this connects

• Previous in the chain: Function and Program Charters — the function charter drafted in the same block; its measures are the goals sheet's apex rows
• Next in the chain: Functional Organization Design for a Resource Optimization Center — the Roles pillar begins with the structure
• Defers to: GRPI-T Framework (the pillars, the ordering rule and the diagnostic's scoring rules) · Future WFM Operating Standard (the five pillars as practice, level by level) · WFM Goals (the goal categories, the trade-off triangle, cascading) · WFM Roles and WFM Processes (the practice pages the Roles and Processes sheets rest on) · Interpersonal Relationships and Interconnected Workforce Management (the two halves of the fourth pillar) · Technology (the fifth pillar as practice) · Quality Score and Customer Experience Index (the pairing rule)
• Feeds: Decision Rights by Planning Horizon (the RACI is the Roles sheet's second half) · Process Shells for a Workforce Standard (the Processes sheet) · Enterprise Interconnection Plan (the Interconnected sheet) · Technology Migration Plan for a Workforce Function (the Technology sheet) · Role Cards for a Workforce Function

Maturity Model Position

The method belongs to the climb from Level 2 to Level 3: it is how a function whose goals are siloed and whose interfaces are personal writes down the frame that Level 3 requires, by hand and in one week. The goals sheet's level column reaches into Level 4 for the measures an engine will carry, and marks them as such so the room does not commit to instruments it cannot yet run. 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
• GRPI-T Framework
• The Maturity Diagnostic and Pathways
• Operating Model for Workforce Management
• Instrumenting the Objective Before Building the Model