Open Office Hours for Next-Generation Workforce Planning
Open office hours for next-generation workforce planning is a standing forum, held twice a month and open to everyone in a workforce function, where people bring a real problem from their own work and learn the skills the function is moving toward by solving it together. It has a standing agenda that anything brought on the day takes precedence over, no attendance list, and one rule of output: every session leaves something behind, a page, a notebook, or a template, so that what one person learned becomes something the function knows.
The forum exists because the skills of workforce planning are changing faster than any training catalog can follow. The working assumption here is that as routine work moves to agents, what stays is judgment, and judgment now needs tools it did not need before: a notebook rather than a spreadsheet, a model rather than a lookup, a range rather than a number. See Role Evolution in the Resource Optimization Center. Nobody acquires those tools by reading about them. They acquire them by watching someone apply them to a problem they recognize, trying it themselves, and then showing the next person. A function whose people learn these skills one at a time, each alone, has chosen the slowest way there is; the forum is the faster one.
What office hours are, and are not
Office hours are an open door with people on the other side of it who are working on the same shift in skills. Anyone can walk in with anything: a forecast that keeps missing, a report they rebuild by hand every week, a question about what a maturity level actually asks of their team, a notebook they cannot get to run.
They are not a status meeting, and nobody reports progress. They are not training, and there is no curriculum to complete. They are not a review, and nothing brought to office hours is graded. Attendance is not tracked, and nobody is missed.
Six tracks
Each track answers one question a person in the function will eventually have to answer for themselves. They map onto the climb described on the WFM Labs Maturity Model™.
| Track | The question it answers | Where it sits on the climb |
|---|---|---|
| Climbing the ladder | What does the next maturity level actually ask of my team, and what would I have to write down to hold it? | Foundational to progressive: goals balanced against each other, trade-offs documented, processes to a standard |
| Python and notebooks | How do I move an analysis from a spreadsheet into a notebook, and check that the notebook says what I think it says? | Progressive: interval-level analysis, correlation, the analyst who understands the model rather than asking for it |
| Automating the mundane | Which of my recurring tasks is written down well enough for an agent to run, and what do I do once it does? | Progressive to advanced: the step table becomes the specification, the overseer publishes the catch rate; see Process Decomposition (L0–L3) |
| Deterministic to probabilistic | How do I stop reporting one number and start reporting a range, and what does simulation let me ask that a formula cannot? | Advanced: scenario modeling informs targets; see Probabilistic Forecasting |
| Working with AI | How do I use an AI assistant on my own function's plan without letting it think for me? | Foundational upward, the habit starts before the tooling does: AI reads everything and thinks nothing; the answer is routed to a source or an engine; see AI Reads Everything and Thinks Nothing |
| One set of definitions | What does occupancy, handle time, shrinkage, contact, attrition or ramp mean in my estate, and why does my number differ from the next team's? | The foundation under every level; see Platform Migration as a Definitional Forcing Function |
A seventh slot, bring your problem, is always open and takes precedence over any track.
Three formats
- Show and tell. Someone who solved a problem walks through how, in fifteen minutes, with the notebook or template open. The room asks what they would do differently next time.
- Hands-on lab. Everyone brings the same kind of problem and works it live, with one person who has done it before moving around the room. Laptops open, nothing presented.
- Ask anything. No preparation. People bring what is on their desk that week, and the room works through as many as it can.
A session picks one format at the start based on who has turned up and what they have brought. A session may end up as some of each. All three work remotely; screen sharing replaces the open laptop.
Norms
- Bring a real problem. A made-up example teaches nothing. The forecast that actually missed, the report you actually rebuild.
- Show your notebook. Half-finished is fine. Nobody learns from a polished result; they learn from the third attempt that finally ran.
- No wrong questions. The person asking what a term means is doing the room a service, because three others did not know either.
- A range, not a number. Any estimate offered in the room is offered with its uncertainty. This is the habit the whole shift in skills depends on.
- Leave a page behind. Every session produces one artifact: a wiki page, a notebook in the shared repository, a template, or a one-paragraph note on what was tried and what happened. Someone in the room writes it, usually whoever brought the problem.
- Teach it next time. Whoever learned something this session is the first candidate to show it next session.
How office hours feed the service pack
Where a function's leadership has run an operating model planning session, each team receives a service pack: a set of templates in which the enterprise answers are inherited and the function-specific answers are the team's to complete. Office hours are where those templates get filled. A team that has to describe its processes to a documentation standard, define its own value measures, or draw its own placement worksheet brings that work to office hours, does it with people who have done it before, and leaves the completed section behind as the page for that session. The pack gives office hours a purpose; office hours give the pack its content.
The service pack's fifteen sections and the validate, prepare, execute rhythm are on The Function Service Pack; the four-day session that produces the enterprise answers each section inherits is Planning Week for a Workforce Function, whose close names office hours as the standing forum where the packs are filled in the two weeks of the validation circuit and after. A room that ran the week in a day and a half moves its working sessions here.
A starter calendar
Twelve sessions, two per track, is enough to establish the rhythm before the room starts setting its own topics.
| Session | Track | Suggested focus |
|---|---|---|
| 1 | One set of definitions | Pick one metric everyone uses and find every definition of it in the estate |
| 2 | Climbing the ladder | Read the next level's description for your function and list what you would have to write down |
| 3 | Python and notebooks | Rebuild one weekly spreadsheet as a notebook, with AI writing the first draft |
| 4 | Working with AI | Use an AI assistant to draft one section of your service pack, then check every claim against a source |
| 5 | Automating the mundane | Take one recurring task through the step table and decide whether an agent could run it |
| 6 | Deterministic to probabilistic | Take one number you report and turn it into a range with a stated reason |
| 7 | One set of definitions | Ramp: what "proficient" means for one work group, and how long it takes to get there |
| 8 | Climbing the ladder | Write the goal framework for your function: three or four categories and the trade-offs between them |
| 9 | Python and notebooks | Correlation and interval-level analysis on your own data |
| 10 | Working with AI | Answer-first reporting: one question in, one answer out, with the evidence attached |
| 11 | Automating the mundane | Run the first agent on a real task and publish its catch rate |
| 12 | Deterministic to probabilistic | A first simulation: what happens to placement if one cohort ramps slower than planned |
Hosting
Hosting rotates. The host's only jobs are to open the door, pick the format, keep the room on the problem in front of it, and make sure the page gets written afterward. The person best placed to host a given session is usually whoever left the page behind last time. Leadership attends as participants. The moment office hours become a place where people perform for their leaders, they stop working.
See Also
- Role Evolution in the Resource Optimization Center: the skills shift the forum serves
- The Case for Operating Model Planning: the session whose service packs office hours help complete
- WFM Labs Maturity Model™: the climb the six tracks map onto
- Process Decomposition (L0–L3): the standard behind automating the mundane
- Probabilistic Forecasting: the deterministic-to-probabilistic track
- AI Reads Everything and Thinks Nothing: the working-with-AI track
- Answer-First Reporting: the habit of returning the answer, not the search
- The Function Service Pack: the fifteen-section workbook each function owner completes here
- Planning Week for a Workforce Function: the week whose blueprint the service packs inherit from
