Strategy on a Page

From WFM Labs

Part of the Planning Week chain · previous: Truth About Today · next: Operating Principles for Work Placement Strategy on a Page is a one-page grid of four rows, vision, strategic intents, dated business outcomes and programs, with a mission line above it, on which a workforce function writes what it is, where it is going, what will be true by when, and what will build it. It matters because a strategy that fits on one page can be ratified in one act and read by everyone the function serves, and because the roadmap is the same page sorted into lanes and quarters, so the strategy and the plan cannot drift apart. The page produces the SOAP grid (SG) and is worked in a session with Wiki:Packs/Strategy on a Page (CP-WFM-011); it is ratified as decision D-01 on Day 1 morning of a planning week.

The grid

The grid is the familiar strategy on a page: one grid, four rows, filled live in the room, and the shortest bridge from an aspiration to a roadmap. One row is added above it. A shared service has to say what it is before it says what it aspires to, because its authority is the most contested thing about it; so a mission line precedes the vision.

Row What it holds Test it must pass
Mission What the function is, in one sentence: what it owns and what it does not Names the method the function owns and the decision it does not own
Vision Where it is going, in a phrase short enough for a wall, chosen from candidates The billboard test and the argument test on Right Work, Right Capability, Right Location
Strategic intents Five pillars, each the how in one line Every later program sits under exactly one
Business outcomes Dated, one column per intent, the completion event for each arc A completion event is observable; a date is a quarter
Programs The delivery vehicles, color-coded by the quarter they start Every outcome has at least one program under it; every program has a charter (Function and Program Charters)

The grid is filled top to bottom, and each row constrains the one beneath it. A program with no outcome above it is a project looking for a strategy; an outcome with no intent above it is a target looking for a reason. The discipline is the one strategy maps impose, in which every measure hangs from an objective and every objective from a theme,[1] and it is the reason the page can be ratified in one act rather than five.

Mission and vision

The mission line for a global ROC, the shared service that owns the methodology for forecasting, scheduling, real-time steering and work placement across every node, has a generic form:

A shared service that owns the methodology by which work is forecast, scheduled, steered in real time and placed across every node, so that the owners of the work can decide with computed and explained options.

Two words in it are the governance settlement and are not removed when a room shortens it: methodology, which is what the function owns, and owners of the work decide, which is what it does not. Every later decision-rights question on Decision Rights by Planning Horizon is settled by those two words.

The vision is chosen from candidates. Five is the working number: enough that the room sees a choice was made, few enough to compare on one slide. A candidate earns its place if it passes the billboard test (read alone, it says what the function is building) and the argument test (when a proposal arrives, the vision supplies the reply). Right Work, Right Capability, Right Location is the vision statement a session typically starts from and carries the two tests; this page does not restate the argument. The other candidates stay visible so the choice is a record, not an assumption.

The five intents

Five pillars, each a how in one line. Technology is deliberately not among them. The lesson of estates that bought tools for good reasons, each with its own definitions, is that tools are not yet an ecosystem (Technology Journey from Level 2 to Level 5); technology serves all five intents and has its own build order on Technology Migration Plan for a Workforce Function, but it is not a pillar the strategy stands on.

Intent The how, in one line Serves
1 Data and comparability One definition, one core, one instrument; comparisons only at matched tenure, node, channel and case mix Every other intent; the inputs to the placement gate
2 Process and automation Every process written to a documentation standard; the capacity cycle run on one calendar; specified components automated with an overseer and a catch rate The climb from Level 2 to 3, then 3 to 4
3 Placement and sourcing Work sits where objectives and constraints say, at every horizon; a partner is a node whose every block carries one supply-seat use The placement function
4 Governance and roles The function owns the method, the node owner owns the decision; one placement forum, one change-control board; roles evolve and new job classes open Decision rights that survive a reorganization
5 Value and measurement Value is the unit, with two inputs never blended; the quality score and the CX index paired; targets by service tier, never by location The scorecard; the case to the commercial function

Five is not a magic number, but fewer than five collapses data into process or governance into value, and more than five produces intents no one can hold in their head. Where a room proposes a sixth, the test is whether it is a how or a what; a what is an outcome and belongs in the row below.

Dated outcomes

One column per intent, two rows of dates: the completion event of Arc 1 and of Arc 2, the two arcs being Arc 1 consolidate and standardize (Level 2 to 3 by hand) and Arc 2 automate (Level 3 to 4 by engine). An outcome is written as an observable event, a sentence that will be true or false on a date, never as a percentage improvement, because a percentage needs an instrument the estate may not yet have. Each cell is the star of the corresponding roadmap lane (The Two-Arc Roadmap); the words in the cell and the words on the star are identical by rule.

The quarter is the unit of dating. A month is too fine for a completion event that depends on other owners, and a year is too coarse to sequence. Every date on the page is a proposal until the validation circuit has run, and the artifact carries the note in its footer.

Programs

The bottom row holds the delivery vehicles, color-coded by the quarter they start. A strategy names artifacts and a roadmap names lanes; neither names the vehicles that build them, which is why the programs are proposed on this page and chartered on Function and Program Charters. Seven is a working number for a function of this kind; the worked example's seven are below. Each program sits under the intent it delivers, and a program that delivers to two intents sits under the one whose outcome it completes.

The roadmap is the second view

The roadmap on The Two-Arc Roadmap is not a second document. It is this page sorted differently: intents become groups of lanes, outcomes become the stars at the end of each lane, programs become the bars, and the quarter colors become the columns. The rule is that roadmap and strategy on a page are one thing in two views, and the test is mechanical.

On this page On the roadmap The check
An intent A group of lanes Every lane belongs to one intent
A dated outcome The star at the end of a lane The star's words are the cell's words
A program A bar, starting in its quarter A bar's color is its start quarter's color
The mission and vision The arc band above the quarters The arcs are named on both

Where a check fails, the two views have drifted, and the page is corrected before the roadmap, because the page is the one the room ratified. The reason to keep the two views rather than one document is that a leader reads the page and a program owner reads the roadmap, and the same content in the form each reader needs is what keeps the strategy from being re-litigated at every use. The classic warning about strategic planning, that formal planning drives out strategic thinking when the plan becomes the strategy,[2] is answered here by keeping the thinking on one page and the plan as its sort order. The page is a rule that keeps producing a destination, not the destination (Build the Rule, Not the Destination); Strategic Workforce Planning covers the long-horizon activity the page directs.

Ratifying it: decision D-01

The room ratifies the page as one act: the vision as chosen, the mission line with its two words kept, the five intents with technology not a pillar, the twelve principles on Operating Principles for Work Placement, and the level target (Level 3 Progressive by the Arc 1 star, Level 4 Advanced by the Arc 2 star). Amendments to wording and dates are recorded; the room does not vote five times. Three principles are named as load-bearing, and striking one of them is the only live argument on the page; the next page says which three and why. The decision is recorded on the decision record (T9) with the truth funnel from Truth About Today attached as the current state it answers. A strategy needs a diagnosis, a guiding policy and coherent action to be a strategy at all;[3] the funnel is the diagnosis, the principles the guiding policy, and the programs the coherent action, and D-01 ratifies all three at once.

Worked example

The chain's worked example function (three heritages, roughly 40–50 planners [E], about a dozen books, two short-term WFM engine instances, one partner-held scheduling team) ratified its page on Day 1 morning, Mon 20 Apr 2026, with the vision "One global ROC: right work, right capability, right location" chosen from five candidates, the mission line as written above, and the five intents unchanged. Its arcs run eight quarters from the week: Arc 1 from Q2 2026 to Q1 2027 (star quarter Q1 2027, ending Wed 31 Mar 2027), Arc 2 from Q2 2027 to Q1 2028 (star quarter Q1 2028, ending Fri 31 Mar 2028). Its seven programs, PG-001 to PG-007: the definitions register; the capability ontology, on paper then as a platform; the long-term capacity engine extended into simulation; the migration (the worked example's phased servicing-platform migration, as the forcing function); a short-term WFM engine instance built to the Standard; the program office; and the agent program (PG-007, chartered on AI Agent Program for a Resource Optimization Center). Two amendments were recorded: the Arc 1 outcome under intent 1 was reworded from "one instrument" to "one instrument across all nodes, first matched-tenure comparison run," and the level target's Arc 2 date was marked as depending on D-13. The page carries the footer "all dates proposals until the validation circuit closes Fri 8 May 2026."

The artifact this page produces

The SOAP grid (SG), one page, four rows plus the mission line. The decision record for D-01 points at it. One filled example cell from the outcomes row:

Intent Arc 1 star (Q1 2027) Arc 2 star (Q1 2028) Program(s) beneath
1 Data and comparability one question, one answer: one instrument across all nodes; the first matched-tenure comparison run every output carries its evidence: governed metric records with lineage in every report PG-001 the definitions register; PG-004 the migration as forcing function

Produced in a working session with Wiki:Packs/Strategy on a Page (CP-WFM-011); the filled set is part of blueprint v0.1.

What would change this

The page's claim is that one grid, ratified in one act and sorted into a roadmap, holds a strategy stable across the two arcs. The observation that would overturn it is a roadmap that, by the second quarter, carries lanes or stars with no cell on the page, or cells with no lane, and a room that corrects the roadmap rather than the page. That would show the page had become a poster and the roadmap the strategy, which is the failure the two-view rule exists to prevent; the remedy would be to ratify the roadmap directly and retire the grid.

How this connects

Maturity Model Position

A written strategy with dated outcomes is what separates a Level 2 Foundational function from a Level 3 Progressive one on the WFM Labs Maturity Model™; the page is a Level 2 to Level 3 artifact (Level 2: Structured Workforce Management, Level 3: The Automation Layer). Its Arc 2 outcomes describe Level 4 Advanced (Level 4: Planning in Distributions), which the page targets but does not claim. 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 1–5.

See Also

References

  1. ↑ Kaplan, R. S., & Norton, D. P. (2000). "Having Trouble with Your Strategy? Then Map It". Harvard Business Review 78(5), 167–176.
  2. ↑ Mintzberg, H. (1994). "The Fall and Rise of Strategic Planning". Harvard Business Review 72(1), 107–114.
  3. ↑ Rumelt, R. P. (2011). Good Strategy Bad Strategy: The Difference and Why It Matters. New York: Crown Business. Chapter 5, "The Kernel of Good Strategy". ISBN 978-0-307-88623-1.
Retrieved from "https://wiki.wfmlabs.org/w/index.php?title=Strategy_on_a_Page&oldid=4714"