Reality check Workday Position Management series
Strategy brief / 03 · For the CHRO

Your HR function is not failing.
Your HR
architecture is.

The Workday Position Management strategy brief for CHROs and senior HR leaders. 15-minute read. Built for executive-team distribution.

Author Tushar Makhija CEO, TeamOhana
For CHRO & senior HR Fast-growing tech, 500–10,000 employees
Format 5 arguments · 3 actions ~15-minute read
Edition May 2026 Reality Check series, No. 03
In this series
Brief · For the CHRO reading this
The argument is not against Workday. Workday is the right system of record. The argument is about what sits in front of it — and what is keeping your function operational instead of strategic.
Setup
Who this brief is for

A 15-minute read, structured for executive distribution.

This brief is for CHROs and senior HR leaders at fast-growing technology companies — 500 to 10,000 employees, running Workday HCM, growing headcount by more than 20% per year. If you are responsible for the strategic positioning of HR in your executive team, this brief names what is keeping your function operational instead of strategic.

Your HRBPs feel it every day. Your HRIS lead feels it. Your CFO sees the forecast variance. You see the strategic conversation your function is not getting invited to. Read this as you would read an HBR feature. Forward it to your executive team alongside the companion documents written for your CFO, HRIS lead, and TA leader.

01
Argument 01 · The structural problem

Your HR function is not failing.

Your HRBPs are reconciling spreadsheets instead of partnering. Your HRIS lead is patching integrations instead of building infrastructure. None of this is what you hired them to do.

The HRBPs you hired to be business partners are reconciling spreadsheets instead. The HRIS lead you hired to build strategic systems infrastructure is patching integrations instead. The TA leader you hired to be a strategic talent partner is fighting with finance about whose headcount number is right instead.

None of this is what these people want to be doing. None of this is what you hired them to do. And none of it is going to resolve on its own, because the underlying problem is structural.

The architecture was designed for a slower world

Workday HCM and Workday Position Management were designed for a slower world than the one your company operates in. Positions in that slower world were durable. Changes were rare. Audit-grade documentation was the default. Hiring managers tolerated forms because nothing else existed.

Your world is different. Positions are re-leveled, relocated, and re-scoped weekly. Hiring managers will not complete Workday forms because they have run their professional lives in Slack, Notion, and Linear for the last decade. The annual plan you approved in December is 30 to 50 percent wrong by April.

The system of record cannot keep up with the system of work, and the gap between them is now where your function loses two days a week.

— From the brief
02
Argument 02 · The cost

What it is costing the function.

Three categories of cost, each visible to a different person on your team. Drawn together, the magnitude is what your CFO needs to see.

The HRIS lead sees integration overhead and reconciliation labor. Failed hire syncs. Workday Studio implementation projects. The four to fourteen spreadsheets that run in parallel because nobody trusts the system. Sixty to eighty hours a month of reconciliation labor at a 1,500-person company, distributed across HR, TA, and FP&A.

The CFO sees forecast variance. Headcount-driven operating expense missing forecast by 15 to 25 percent quarter after quarter. The board notices. The audit committee notices. Public-market companies miss guidance over this category of error.

Your HRBPs feel everything. They are the connective tissue between hiring managers, recruiting, HR systems, and finance. Every gap in the system surfaces as work on their desks. They were hired to be business partners. They are functional reconciliation operators.

The annual cost, sized by your company
Company size
Annual cost · low
Annual cost · high
500 – 1,000 employees
$2.3M
$4.7M
1,000 – 2,500 employees
$5.1M
$13.2M
2,500 – 5,000 employees
$13.4M
$26.7M
5,000 – 10,000 employees
$22.6M
$42.4M

For a typical 1,500-person fast-growing tech company, that is $5.1M to $13.2M per year. The full methodology is in our companion CFO memo, which we recommend you forward to your finance partner alongside this brief.

03
Argument 03 · The opportunity cost

What it is costing the strategic conversation.

The dollar cost is what your CFO sees. The strategic opportunity cost is what your CEO will eventually ask you about.

There is a set of strategic initiatives that exists on every fast-growing tech company's HR roadmap, and that almost never ships. None of these initiatives are technically hard. All of them require the HR systems team to have time to build them. The HR systems team does not have time, because they are running the operational reconciliation that holds the existing infrastructure together.

The roadmap that almost never ships
On the plan ≥ 3 years

Skills inference & skills-based talent strategy

Every CHRO at our customer base has had this on their two-year plan for at least three years. It does not get built because the HRIS team is patching positions.

Business case unambiguous

Internal mobility infrastructure

Filling roles internally costs a fraction of external hiring and retains people. Most fast-growing tech companies have no real internal mobility infrastructure. Same reason.

Data infrastructure problem

Career frameworks that survive reality

A career framework that updates with the actual leveling decisions being made requires a data infrastructure most HR teams do not have.

Board-level question

AI-readiness audits

Boards are asking this now. Your CEO will ask it within the next year. The honest answer requires data about the composition of work that does not exist in any of your current systems.

The dollar cost is what your CFO sees. The strategic opportunity cost is what your CEO will eventually ask you about.

— From the brief
04
Argument 04 · The architectural fix

What changes for the function.

A decision layer in front of Workday. The work of headcount planning happens where it actually lives. Workday and the ATS stay in place.

Recruiting system
ATS
Greenhouse · Lever · Ashby
The new layer
Decision layer
TeamOhana
Headcount planning at the speed of work
System of record
Workday HCM
Position Management — unchanged
Plan of record
FP&A tool
Adaptive · Pigment · Anaplan

One decision layer. Every system stays. Workday remains the system of record. The ATS remains the recruiting system. A layer gets added on top — where the actual hiring conversation already happens.

What this means for the people you lead
Your HRIS leadThe person rebuilding integrations
Stops being the human API. Translation of Slack messages into Workday forms goes away. Reconciliation goes away. Integration repair work goes away. What replaces it is the strategic systems work the role was created for.
Your HRBPsThe connective tissue
Get back to being business partners. The half-week each HRBP currently spends on operational reconciliation returns to them. The conversation shifts from "did you fill out the form correctly" to "let's talk about how to sequence your hiring against your roadmap."
Your TA leaderFighting with finance
Stops fighting with finance. A single source of truth for hiring plan, open requisitions, target dates, and offer status replaces the three sources of truth they currently reconcile. TA conversations become about hiring strategy, not hiring operations.
Your hiring managersThe people avoiding Workday
Stop hating your function. The clunky Workday workflow they avoid gets replaced by a request flow that meets them in Slack. They engage with headcount planning as a real conversation instead of an administrative tax.
YouThe person reading this brief
Stop explaining why the data is wrong. The conversations with the CEO and CFO move from "the system is being updated" to "here is what the data is telling us about the business." That is the strategic register HR leadership has been trying to reach for fifteen years.
05
Argument 05 · For public & pre-IPO CHROs

The audit and compliance dimension.

A secondary argument — but a meaningful one for any CHRO whose company is public or preparing to go public.

Workday Position Management does not produce an audit-ready trail of position changes when the underlying conversations and approvals happen in Slack, email, and unrecorded meetings. The system records the change. The system does not record the reasoning behind the change. The reasoning is the audit-relevant material.

SOX exposure · IPO readiness

For public companies, this is a control weakness. For pre-IPO companies, it surfaces during the S-1.

Public-company CHROs are accountable for a category of risk Workday alone cannot close. Pre-IPO CHROs compound the readiness timeline if it is left in place.

$50K – $200K Per material weakness finding — and audit-committee attention is the bigger cost.
S-1 Where this exposure surfaces if you are preparing for IPO. It compounds the readiness timeline.

This is not the primary argument for the architectural change. It is a meaningful secondary argument for any CHRO whose company is public or preparing to go public.

What it takes to put the layer in
6–8 weeks 2–4 hrs HRIS admin time No consulting firm No Workday Studio developer No HR-team retraining Reversible

You can wait. The cost of waiting is the cost named earlier in this brief.

— From the brief
What to do next

Three concrete actions, in order of commitment.

Action 01

Forward this brief to your executive team

To your CFO with the companion cost memo. To your VP of People Ops or HRIS lead with the companion field guide. To your TA leader with the companion playbook. Each piece is written in the persona's specific register and gives them the argument they need from their own seat.

Open the companion field guide
Action 02

Run the diagnostic

A self-assessment worksheet that takes about 30 minutes for your HRIS lead to complete, and tells you exactly which of the five underlying failure modes is producing the most cost. We share it without requiring a sales conversation.

Run the 5-minute health check
Action 03

Book a 30-minute architecture review

A live conversation with a TeamOhana solutions architect about your specific Workday tenant, ATS, and FP&A stack. Bring your HRIS lead. Bring your FP&A partner. We require 30 minutes and the right people in the room.

Request the review
From the editor

If this brief resonated, we will come prepared.

This brief is one of four persona-specific assets in the Workday Position Management Reality Check series. The companion documents address the same architectural argument from the CFO, HRIS lead, and TA leader vantage points. We recommend reading them as a set when you're ready to bring the conversation to your executive team.

If you want to spend thirty minutes with us on what the architecture looks like in your specific Workday tenant — your ATS, your FP&A stack, your real cleanup queue — we will come prepared.

Tushar Makhija
Tushar Makhija CEO, TeamOhana