Eight in ten Workday customers turned on Position Management for one reason: control. Control over who gets hired, where the money goes, and how the org changes over time. That was the promise. After studying hundreds of public conversations on r/workday, r/Workday_Community, r/FPandA, and practitioner forums, the picture that emerges is not the one anyone bought.
What operators describe is not a Workday failure. Workday is doing exactly what it was designed to do: hold the system of record. The breakdown is structural. The work of authorizing headcount — decisions about which roles are approved, funded, frozen, or active — has slipped out of Workday and into Slack, spreadsheets, and email. Workday gets the durable record. Everything in front of that record has gone informal.
This report synthesizes what we heard, organized into ten recurring failure themes and mapped to the people they hurt most: HRIS Leads, Finance, Talent, and the hiring managers stuck in the middle. We've kept the operator voice in their own words wherever possible. Their language is more honest than ours could ever be.
Position Management at scale doesn't have a configuration problem. It has an authorization problem. Workday holds the record. Something else has to hold the decision.
Public operator conversations across r/workday, r/Workday_Community, r/FPandA, and adjacent practitioner forums, captured and synthesized over the second half of 2025 and the first quarter of 2026. Threads were selected for substantive operator commentary, not vendor marketing or recruiter posts. Every quote was tagged against ten failure themes and seven personas. We made no attempt to soften the language.
Vendor research is full of survey data filtered through a sales motion. This is the opposite — written by the people doing the work, for an audience of their peers. When an HRIS lead vents on Reddit late on a Tuesday, you are reading what they actually believe.
Listed in order of frequency in the corpus, not severity. Each theme is followed by the verbatim language operators used and a short note on what it means underneath the surface complaint.
The HRIS team is in permanent repair mode. Stale positions, duplicates from managers who didn't know one already existed, broken history from inline edits, security tied to positions that should have been closed months ago. Cleanup is not a project. It is the job.
"HRIS teams describe being in continual repair mode — closing stale positions, correcting misclassified positions, untangling incorrect history. The work never ends because the upstream governance was never defined."
"Most of my ticket queue is position-related. Stale positions never closed, duplicates from managers who didn't know one existed, security tied to positions that shouldn't exist anymore. It's a full-time job."
"Inline title or org changes get implemented by editing the existing position rather than creating new positions where appropriate. Now the history is muddied and the position-level reporting breaks."
The cleanup work isn't a hygiene problem — it's the absence of an authorization layer upstream. Bad state enters Workday because nothing stops it from entering. The HRIS team becomes the control system by default, because no other control system exists.
Finance treats positions as budget line-items. HR treats them as organizational objects. Recruiting treats them as requisition feeders. Managers treat them as metadata in the way of just hiring. Same object, four interpretations. Analytics break. Reports don't tie. Everyone is right under their own definition.
"Stakeholders don't understand what a position is versus a job profile. Some teams expect job profiles to reflect individual seats. Others overuse positions as variant roles. The ontology is unclear, so analytics break."
"We debated position management versus job management for months. We chose position management for control. Two years in, we're still arguing about whether to use one position per seat or one position per role family. Nobody agrees."
The ontology argument is unresolvable inside Workday because Workday models a single object, but the business needs four different views of it. Without a layer that translates between those views, every cross-functional headcount conversation starts with a definitions debate.
Nobody owns position management. Or everyone does, which amounts to the same thing. Finance assumes HR. HR assumes HRIS. HRIS assumes Finance. The role exists in nobody's job description and on everybody's plate.
"Who owns position management at your company? We can't get a straight answer. HR thinks Finance, Finance thinks HR, HRIS thinks both. Six months later we still can't answer it cleanly."
The ownership question is unanswerable because the work spans three functions, and no single function has the mandate, the budget context, or the system access to do all of it. The structural answer is a coalition — Finance + Talent + HRIS — operating on a shared authorization record. Not an org chart fix. A system fix.
This is the one executives notice. Finance reports one headcount number. HR reports another. The ATS shows a third. The CEO asks a basic question and gets a two-day reconciliation project as an answer.
"Finance and HR present different headcount numbers in the same leadership meeting because they interpret position state differently. Both can defend their numbers. Neither is wrong. Neither matches the other."
"What counts as 'open'? Workday says X positions are open. The ATS says Y reqs are active. Finance says Z roles are funded. Each number is correct under its own definition. The board sees the discrepancy and asks why."
"Our CEO asks basic questions like 'how many approved but unfilled roles do we have?' and we spend two days reconciling before answering. The investment in Workday was supposed to solve this."
Each system is correct in its own definition of "open" or "current" or "funded." The systems disagree because the authorization state — the cross-system truth about whether a role is approved, funded, frozen, or filled — lives in none of them. The board sees the disagreement and loses trust in the underlying data.
The strongest signal that Workday isn't doing the job alone is what operators built next to it. Every team has its own tracker. In one customer environment we audited, fourteen separate spreadsheets were running simultaneously — each with its own version of the truth.
"We have Workday. We still maintain an Excel tracker for approved roles, backfills, hiring freezes, and reorganizations. Workday's view isn't trusted as the single source of truth because too much state lives elsewhere."
"FP&A maintains the headcount plan in Adaptive or a dedicated planning tool. Workday holds the positions. They never match. Reconciliation is a monthly project that consumes a full analyst's time."
"We're a Workday shop and we still built a Google Sheet to track approved heads, recruiting status, and start dates because Workday alone doesn't show the picture Finance needs."
Spreadsheets are a measurement of the gap, not the cause of it. They exist because Workday lacks the authorization state operators need. If you move that state into a layer designed for it, the spreadsheets have nothing left to track.
The req is operationally open in the ATS. Recruiting is sourcing. Finance doesn't know recruiting is sourcing. The hire happens before anyone reconciles whether the role was actually approved.
"Workday positions don't tell me if I should actually open this req. The position is technically there, but I can't tell if Finance has authorized it or if it's still pending budget review."
"The requisition is operationally open in the ATS, but financially ambiguous. Recruiting is sourcing. Finance doesn't know we're sourcing. The hire happens before anyone reconciles whether it was approved."
"Approval trails live in our ticketing system. Workday gets updated once the ticket is closed. By that time, the position is created, the req is open, and the candidate is in pipeline. Workday has no visibility into the rationale."
Authorization is conflated with operational state. A position can be technically created in Workday without ever being funded in the plan. The req goes live. Recruiting moves. The variance shows up at month-end. The control should have been at the approval, not at the reconciliation.
The Workday-to-ATS integration moves data. It does not move context. The ID transfers. The location transfers. Whether the role is a backfill or net-new, whether it's funded for this fiscal year, whether scenario A or B applies — none of that survives the trip.
"When Workday positions sync to the ATS, the field mapping is fine. ID transfers. Location transfers. What doesn't transfer is whether the position is a backfill or a net-new, whether it's funded for this fiscal year, whether scenario A or B applies."
"Finance approves a mid-year reforecast in Adaptive. The decision doesn't auto-propagate to Workday positions. HRIS gets a list and manually updates. By the time positions are updated, recruiting has moved on with the old assumptions."
Field-level integration is the floor, not the ceiling. The systems are technically connected and semantically incoherent. Workday Studio costs $30K–$50K to stand up and $5K–$10K a year to maintain. After all that, it still moves IDs, not intent.
Hiring managers do not complete the Workday requisition flow. They write Slack messages. Across every Workday customer we have listened to, the majority of requisitions are not initiated by the hiring manager directly. They are initiated by an HRBP, HRIS admin, or TA coordinator translating a Slack message into a Workday form.
"Managers view position management as administrative overhead. They prioritize speed to hire and local flexibility. They reuse positions in ways we didn't intend, change job profiles that Finance expected to stay distinct, and ask us to 'just fix it' after."
"I'm a manager. Why is opening a role so complicated? I have approved headcount in my budget. I just want to post the job. Why do I need to understand the difference between a position and a requisition?"
A typical Create Job Requisition flow has 12 to 18 required fields across 4 to 7 tabs. The hiring manager isn't a worse version of themselves inside Workday — they're responding rationally to a workflow that does not match the way they work. The fix is not better training. The fix is a workflow that meets the manager where they already are.
Workday's approval flow asks who approves the position. It does not ask whether the position fits the approved headcount plan, the budget envelope for this quarter, or the comp band that was originally signed off. Variance is discovered six months after the decisions that caused it.
"Workday's approval flow asks who approves the new position. It doesn't ask whether the position fits the approved headcount plan or the budget envelope for this quarter. Finance only finds out at month-end when actuals come in."
"Headcount cost variance hits the P&L six months after the decisions that caused it. By then the plan is so far gone we're rebuilding it from scratch. The control should have been at the approval, not the reconciliation."
"We approve a req at a certain comp band. Recruiting hires at a higher level because that's who applied. The position record doesn't flag the drift. Finance discovers it at month-end review. Repeat across 30 hires."
Headcount is 70 to 80% of operating expense at most technology companies. The single largest line in your P&L is being approved without a real-time check against the plan it's supposed to fit inside. Finance's job becomes variance explanation, not variance prevention. The control is on the wrong side of the decision.
Workday's business process framework is powerful but rigid. You can encode rich approvals. You cannot easily change them. Maintaining the logic as the org changes is a full-time job, so many teams choose simpler workflows and accept the governance gap.
"Workday's business process framework is powerful but complex. We can encode rich approvals, but maintaining the logic as the org changes is a full-time job. Many teams choose simpler, less robust workflows because the alternative is unsustainable."
"Conditional approvals like 'hire only if we hit revenue target X' have no native place in Workday. They live in leadership discussions and planning models. The position doesn't carry the condition. The recruiter doesn't see it."
Workday's strengths — auditable, governed, durable — are the same properties that make it the wrong place to hold authorization logic that changes weekly. Trying to force structural governance into BP configuration is what creates the HRIS overload. The authorization logic needs to live in a system built for change.
Here is the personalized version — six personas, the pain they describe in their own words, what's actually on their desk, and what they need to stop firefighting.
"I joined this company a year ago thinking I was going to do strategic HR. I spend half my week patching positions in Workday because someone changed a level in Greenhouse and the sync broke. I am not a strategic HR leader. I am a human cron job."
Bad data stopped before it enters Workday. Authorization logic in a layer designed for change. Workday left untouched as the system of record. No re-implementation. No new tab the hiring manager has to learn.
"Headcount cost variance hits the P&L six months after the decisions that caused it. By then the plan is so far gone we're rebuilding it from scratch. The control should have been at the approval, not the reconciliation."
Variance prevention, not variance explanation. Real-time budget impact at the moment of approval. One authoritative view of who is approved, open, hired, funded. Coexistence with Adaptive, Pigment, Anaplan — not replacement.
"Our credibility depends on the numbers matching Finance, and they don't. We're in permanent cleanup mode. I get blamed for data I don't own."
Shared authorization record with Finance, so the headcount conversation stops being adversarial. HRIS bandwidth recovered for the strategic systems work they were hired for. A clean source of truth that holds up in a board meeting.
"We start sourcing, the candidate gets to offer, and we discover the role was frozen three weeks ago. 35 open jobs. Every single one with a start date in the past. My recruiters lose trust in the requisition list."
A trustworthy authorized-roles list that feeds the ATS. Approval state visible inside the recruiter's tool. Backfill governance that is structured, not implied. Speed without the surprise.
"I'm a manager. Why is opening a role so complicated? I have approved headcount in my budget. I just want to post the job. Why do I need to understand the difference between a position and a requisition?"
A guided workflow that meets them in Slack, shows them what they have approved headcount for, and turns a sentence into an open req in days. Clear status: approved, pending, frozen. No new system to learn.
"Our CEO asks basic questions like 'how many approved but unfilled roles do we have?' and we spend two days reconciling before answering. The investment in Workday was supposed to solve this."
A default dashboard answer to the basic questions. Confidence that the numbers Finance sees, the numbers HR sees, and the numbers in the board deck are the same numbers.
The failure modes are uncomfortable to read. The aggregate cost is more uncomfortable. The integration spend is the obvious line. The expensive lines — variance, delayed hires, HRIS time stuck in operational triage — are the ones nobody bills directly.
Source: TeamOhana customer base; corroborated against Bersin, Gartner, and Forrester workforce planning analysis. Workday Studio integration costs ($30K–$50K initial, $5K–$10K annual) cross-referenced with Kinnect's public consultancy data.
A quick gut-check. If five or more of these answers make you wince, you are running the same pattern most Workday customers in your size range are running. The cost is real. The fix is not more Workday.
Workday is not the problem. Workday is the system of record. It should hold the durable, audited, governed truth about positions once decisions are made. That is what it was built for. The problem is that authorization — the decision-making layer in front of Workday — has nowhere to live. It lives in Slack, in spreadsheets, in email approval chains, in leadership conversations. By the time someone types the decision into Workday, the recruiter has been sourcing for a week, Finance is two cycles behind, and the manager has already moved on.
The structural fix is a layer in front of Workday that does seven things:
Approved, pending, frozen, funded — held as state, not implied from sync timing.
Backfill vs. net-new, scenario tag, comp band, funding context — carried with the position.
Variance prevented at the decision, not explained at month-end.
A guided way to open roles that are actually authorized — without a Workday tab.
Workday, the ATS, and the FP&A tool kept in agreement live — not in a Monday meeting.
Workday stays the system of record. Nothing gets re-implemented.
They model the plan. The authorization layer operationalizes the bridge between the plan and the position. The front door. Hiring managers, TA, HRBPs, and Finance transact in the front door. Workday gets the durable record.
TeamOhana sits above Workday (or whatever HRIS you're on), your ATS, and your FP&A tool, and owns the state that none of those systems were built to own.
Authorization happens upstream. Position cleanup stops being a job description.
Workday, ATS, FP&A reconcile continuously. The board sees one headcount answer.
The fourteen trackers have nothing left to track when authorization lives in a system designed for it.
Real-time budget impact at the moment of approval. No more six-month discovery.
Authorized roles flow into Greenhouse, Lever, or Ashby with the funding context intact.
Slack-native, guided to approved headcount, status visible, no Workday tab required.
No more translation work. No more cleanup tickets. The strategic role they were hired for.
No re-implementation. No data ownership conflict. No replacement narrative.
Manage headcount without the headache.
Not a generic demo. A discovery against your specific pattern. Which of the ten failure themes are running in your company, what the aggregate cost looks like, and which one you would solve first. We will walk your environment, surface the specific failure modes, and quantify the cost of the gap before pitching anything.
If TeamOhana isn't the right fit, you walk away with a structured map of where your headcount governance is leaking.
We map your specific failure modes against the ten themes in this report — before any pitch.
Book a callA scorecard that surfaces the specific failure patterns showing up in your environment. No demo required.
Start the health checkThis report draws on internal TeamOhana research artifacts and external corroboration from independent analysts.
The full operator quote corpus across r/workday, r/Workday_Community, r/FPandA, and adjacent practitioner forums. Every verbatim quote in this report is sourced here.
Source for the failure-mode framing, the cost stack, the front-door architecture, and the persona-tagged customer call quotes.
Long-form strategy memorandum on the failure modes and the design of a complementary authorization layer.
Workday Studio integration costs are corroborated by Kinnect (kinnectx.com), an independent Workday consultancy. Reconciliation labor and forecast accuracy ranges are cross-referenced against published analysis from Bersin, Gartner, and Forrester.
