peopletechguide.com

Tag: workday implementation

  • Understanding Workday Organizations Clearly

    One of the most common questions from new Workday users and even some project stakeholders is, “Aren’t all organizations in Workday basically the same?” On the surface, everything looks like “an org” with a name and hierarchy. But once you start configuring security, routing approvals, or building reports, the differences between Workday organization types become critical.

    Thinking of all orgs as interchangeable often leads to messy designs, confusing security, and reports that never quite reconcile. A clearer mental model of Workday organizations helps HR, Finance, and Workday admins design a tenant that is easier to use and maintain.

    What Workday Means by “Organization”

    In Workday, “organization” is a generic term for several different structures that group people, positions, or financial elements in specific ways. Each type of organization exists for a defined purpose: some drive staffing, some drive cost allocation, and others drive reporting or security.

    For example, supervisory organizations represent who manages whom, but cost centers represent where costs are tracked and reported. Both are “orgs” in Workday, yet they answer completely different questions for the business. Treating them as the same quickly causes problems in both configuration and reporting.

    Key Workday Organization Types and Their Roles

    While each tenant has its own configuration, a few core organization types show up in almost every Workday implementation. Understanding the “why” behind each type is more important than memorizing every configuration option.

    • Supervisory organizations focus on management and staffing.
      They answer: “Who manages this worker?” and “Which team does this position belong to?” These orgs shape your supervisory hierarchy and drive staffing models and approvals.
    • Cost centers focus on financial responsibility.
      They answer: “Where should this worker’s costs be tracked?” and “Which department owns this spend?” Cost centers are critical for reporting labor costs and enabling Finance visibility.
    • Company (or legal entities) focus on legal and financial structure.
      They answer: “Which legal entity employs this worker?” and “Which company is responsible for this transaction?” Companies are important for regulatory, tax, and financial reporting.
    • Regions, locations, or custom organizations often focus on grouping for reporting or process routing.
      They answer: “Which geography or business line does this worker belong to?” or “Which group should see this dashboard or approval?”

    Each type has its own configuration screens, reference IDs, and impact areas in Workday. Calling all of these simply “orgs” hides the fact that each one exists for a slightly different reason and is used in different parts of the system.

    Why It Matters to Stop Treating All Orgs as Equal

    When project teams or business users treat all organizations as interchangeable, a few predictable issues appear over time:

    • Confusing security and access.
      Security designed on the wrong org type can give the wrong users access to data, or force admins to maintain endless exceptions.
    • Approvals that don’t match the real world.
      Routing approvals on the wrong structure (e.g., cost center when you really mean manager) leads to frustration and delays.
    • Reports that never align.
      If HR reports use supervisory orgs while Finance reports rely on cost centers, and users don’t understand the difference, data disputes become a regular occurrence.

    Changing how people think about Workday organizations is often the first step to cleaning up an implementation. It is much easier to improve configuration and reporting when everyone shares a common understanding of what each org type represents.

    A Simple Mental Model for Workday Organizations

    To help non-technical stakeholders, it can be useful to translate Workday organizations into everyday language:

    • Supervisory organizations: “Teams and managers.”
    • Cost centers: “Where the money is tracked.”
    • Companies: “Legal employers or entities.”
    • Additional orgs: “Ways we group people for routing or reporting.”

    This simple language reduces jargon and makes it easier for HR and Finance leaders to participate in design decisions. When they understand the purpose behind each org type, they give better input on how approval chains, financial ownership, or reporting structures should be set up.

    Practical Tips for HR, Finance, and Admins

    If you are trying to simplify Workday for your HR and Finance teams, use these principles when talking about organizations:

    • Always name the org type explicitly.
      Instead of saying “update the org,” say “update the supervisory org” or “update the cost center.”
    • Tie each org type to business questions.
      Explain which questions are answered by supervisory orgs and which by cost centers or companies.
    • Use visuals and examples.
      Simple diagrams that show a worker with a manager, cost center, and company help users see that one person can belong to multiple organization structures at once.
    • Align training and documentation.
      Ensure your guides and training materials consistently use the same terminology and explanations; this builds confidence in your users.

    Bringing It Back to Simplifying Workday

    At its core, Workday is powerful because it lets you slice and group your workforce in many different ways. That power becomes complexity when everyone calls everything “an org” and stops distinguishing the purpose of each structure.

    By teaching your HR and Finance teams the differences between Workday organization types, you reduce confusion and empower them to make smarter decisions about configuration, reporting, and workflows. The goal is not to turn everyone into an architect, but to give them enough understanding to use Workday with clarity and confidence.

  • 10 Common Workday Implementation Pitfalls

    Workday implementations fail (or succeed) based on decisions made in the first few weeks, not the last few. Most implementation pitfalls are predictable: scope creep, poor data migration, over-customization, inadequate testing and weak change management. The organizations that succeed do not avoid complexity—they design for it from day one with clear principles, strong governance and disciplined execution.​

    Here are 10 common pitfalls and the smart design practices that prevent them.

    Pitfall 1: Poorly defined scope and vague objectives

    The problem: Projects start without clear goals, success metrics or boundaries, leading to scope creep, misaligned expectations and cost overruns.​

    Smart design fix:

    • Define measurable objectives tied to business outcomes (for example, “reduce hire-to-pay cycle by 30%”, “eliminate 10 legacy HR systems”).​
    • Document in-scope vs out-of-scope features, modules and integrations in a signed project charter.​
    • Establish a change control process from day one so new requests are evaluated, not just added.​

    Clear scope prevents the “everything to everyone” trap.​

    Pitfall 2: Weak project governance and leadership

    The problem: When accountability is unclear, decisions stall, issues escalate slowly and the project drifts.​

    Smart design fix:

    • Establish a steering committee with executive sponsorship, clear decision rights and regular cadence.​
    • Assign a dedicated process owner for each major area (HR, Finance, Payroll, Security) with authority to make design decisions.​
    • Use a RACI matrix to clarify who is Responsible, Accountable, Consulted and Informed for key deliverables.​

    Strong governance turns “we’ll figure it out later” into structured decision-making.​

    Pitfall 3: Over-customization and ignoring Workday best practices

    The problem: Teams recreate legacy processes in Workday instead of adopting modern, cloud-native patterns, leading to complexity and technical debt.​

    Smart design fix:

    • Start with delivered Workday functionality and only customize where there is a compelling business case.​
    • Challenge “we’ve always done it this way” thinking; Workday’s best practices exist for a reason.​
    • Document every customization: why it was needed, alternatives considered and long-term maintenance plan.​

    The goal is not zero customization—it is intentional customization.​

    Pitfall 4: Poor data migration planning and execution

    The problem: Data migration is treated as a one-time technical task instead of a strategic initiative, resulting in incomplete, inaccurate or duplicate data at go-live.​

    Smart design fix:

    • Start data cleansing in the source systems months before migration, not during load testing.​
    • Run multiple mock data loads in sandbox environments to validate mapping, transformation and load processes.​
    • Define data quality gates: minimum thresholds for completeness, accuracy and consistency before go-live.​
    • Plan for post-go-live cleanup but minimize it by getting data right before launch.​

    Good data migration is boring and methodical—that is why it works.​

    Pitfall 5: Insufficient or unrealistic testing

    The problem: Testing is compressed, skipped or limited to happy-path scenarios, so critical issues emerge only in production.​

    Smart design fix:

    • Plan for structured test phases: unit testing, integration testing, user acceptance testing (UAT) and end-to-end regression.​
    • Test edge cases and exceptions, not just standard scenarios (for example, retroactive hires, org changes mid-process, high-value transactions).​​
    • Include cross-module testing: HR → Payroll → Finance, Procurement → Projects → GL.​
    • Build a regression suite to retest after every release and configuration change.​

    Testing is not optional; it is risk mitigation.​

    Pitfall 6: Inadequate training and change management

    The problem: Users are “thrown into” Workday with minimal training, leading to low adoption, errors and workarounds.​

    Smart design fix:

    • Develop a comprehensive training strategy with role-based curricula, in-app guidance, job aids and live sessions.​
    • Start change management early: communicate the “why” of Workday, involve users in design and celebrate quick wins.​
    • Use champions and super users in each business area to provide peer support and feedback.​
    • Plan for ongoing training and support post-go-live, not just a one-time event.​

    Technology adoption is a people problem, not a configuration problem.​

    Pitfall 7: Ignoring integrations until late in the project

    The problem: Integration design is deferred, leading to rushed builds, data mismatches and post-go-live failures.​

    Smart design fix:

    • Inventory all required integrations (payroll, benefits, time, ERP, CRM) in the planning phase.​
    • Design integration architecture early: EIB vs Core Connector vs custom, data flows, frequency and error handling.​
    • Test integrations early and often, not just at the end.​
    • Build in monitoring and alerting so integration failures are caught immediately.​

    Integrations are not “nice to have” tasks; they are critical path.​

    Pitfall 8: Failing to plan for scalability and growth

    The problem: Designs work for current state but break when the organization grows, acquires companies or enters new markets.​

    Smart design fix:

    • Design the Foundation Data Model (FDM) to accommodate future growth: additional companies, countries, business units and Worktags.​
    • Avoid hard-coding assumptions (for example, “we only operate in the US”) that limit flexibility.​
    • Plan for multi-tenant or multi-org scenarios if acquisitions are likely.​
    • Test designs with “what if” scenarios: double headcount, add 10 new locations, acquire a competitor.​

    Good design accommodates change without rework.​

    Pitfall 9: Poor documentation and knowledge transfer

    The problem: Configuration decisions are made but not documented, so when the implementation team leaves, no one understands how or why the tenant was built.​

    Smart design fix:

    • Document design decisions, not just settings: what was decided, why, alternatives considered and implications.​
    • Maintain configuration workbooks and architectural diagrams that evolve throughout the project.​
    • Conduct knowledge transfer sessions with internal teams before the implementation partner exits.​
    • Create a runbook for key processes, integrations and troubleshooting.​

    Documentation is insurance against institutional memory loss.​

    Pitfall 10: No post-go-live stabilization or optimization plan

    The problem: Organizations treat go-live as the finish line, not the starting line, leading to unresolved issues, poor user experience and eroding trust.​

    Smart design fix:

    • Plan for a 90-day stabilization period with dedicated support, issue tracking and rapid resolution.​
    • Schedule tenant health assessments at 6, 12 and 24 months post-go-live to identify optimization opportunities.​
    • Establish ongoing governance and AMS (Application Management Services) to maintain tenant health long-term.​
    • Treat Workday as a continuous improvement journey, not a one-time project.​

    Go-live is the beginning of value realization, not the end of the project.​

    Avoiding these 10 common pitfalls is not about having a perfect plan; it is about having the right design principles, governance discipline and execution rigor from day one. Organizations that succeed with Workday treat implementation as a transformation program—not a software installation—and build in the structures, processes and culture to sustain success long after the consultants leave.

  • Workday Position Management

    “We’re implementing Workday Position Management next quarter. Any advice?”

    I get this question at least once a month from HR leaders embarking on Workday implementations.

    My honest answer? Position Management works beautifully when configured correctly. When configured poorly, it becomes the most complained-about feature in your entire Workday tenant.

    Last year, I joined a client project three months after their Workday go-live. The HR Operations team was drowning in position management tickets:

    “Why can’t I fill this position?”

    “The system says this position is filled, but the worker terminated two weeks ago.”

    “I need to create 50 new positions for our expansion, but it takes 45 minutes per position.”

    “Position data doesn’t match our headcount reports.”

    “Why do I need a position AND a job? They’re the same thing!”

    Their Position Management implementation had all the classic problems. Five thousand positions. Three thousand active workers. Dozens of unfillable positions. No clear ownership. Inconsistent data quality. And an HR team that had completely lost trust in the system.

    We spent six weeks systematically fixing the root causes. By the end, position management went from their most hated feature to a strategic workforce planning tool that executives actually used.

    This guide will show you the seven fixes that transformed their implementation and have since worked across dozens of other Workday tenants. These are not theoretical best practices from Workday Community. These are battle-tested solutions to the specific problems that make people hate Position Management.

    Why Position Management Gets So Much Hate

    Before we dive into fixes, you need to understand why Position Management creates so much frustration.

    The Fundamental Misunderstanding

    Most organizations implement Position Management because they think they need it for budgeting or headcount planning.

    They are partially right. Position Management can support those use cases. But that is not what Position Management actually does.

    Position Management is a workforce structure management tool that maintains a parallel organizational structure based on positions rather than workers.​

    When you enable Position Management in Workday, you are making a fundamental architectural decision: Your organizational structure will be built on positions first, workers second.

    Without Position Management, your organizational structure looks like this:

    • Worker → Job → Supervisory Organization → Cost Center

    With Position Management, your organizational structure looks like this:

    • Position → Worker → Job → Supervisory Organization → Cost Center

    That extra layer creates the complexity that frustrates everyone.

    The Three Core Complaints

    Every Position Management complaint falls into one of three categories:

    Complaint 1: “It’s too much work”

    Creating positions is more work than just hiring workers directly into jobs. Managing position changes is more work than managing worker job changes. Every organizational change now requires updating positions first, then workers.

    Complaint 2: “The data doesn’t match reality”

    Positions show as filled when workers have terminated. Positions show as vacant when workers are actively working. Position budgets don’t match actual headcount. Position titles don’t match what people actually do.

    Complaint 3: “Nobody understands it”

    Hiring managers do not understand the difference between a position and a job. Finance does not understand why budget is allocated to positions that have no workers. HR does not understand when to create new positions versus reusing existing vacant positions.

    All three complaints stem from the same root cause: Position Management was implemented without clear business rules and governance.

    The fixes I am about to show you establish those rules and governance.

    Fix 1: Define Clear Position Creation Rules (Or Stop Creating Positions Entirely)

    This is the most important fix. Get this wrong and everything else fails.

    The Problem

    Most organizations have no clear rules for when to create a new position versus reusing an existing vacant position.​

    The result? Managers create new positions for every hire because it is easier than searching for vacant positions to reuse. Three years later, you have 8,000 positions for 3,000 workers.

    Your position-to-worker ratio should rarely exceed 1.5:1 (1.5 positions for every 1 worker). When you hit 2:1 or 3:1, your position data has become meaningless.​

    The Fix: Establish Position Creation Governance

    Implement one of these three position creation strategies based on your organizational needs:

    Strategy 1: Strict Position Control (Best for stable, hierarchical organizations)

    New positions can only be created through:

    • Annual budgeting process (Finance approves all position budget)
    • Formal headcount planning (HR Ops creates positions in batches)
    • Executive approval for unbudgeted positions

    When to use this: Large enterprises with formal budgeting processes, government organizations, healthcare systems with strict FTE budgeting.

    Position-to-worker ratio target: 1.1:1 to 1.3:1

    Strategy 2: Manager-Initiated with Approval (Best for growing organizations)

    Managers can create positions through a business process that requires:

    • Business justification
    • Budget code assignment
    • HR Operations approval
    • Finance approval for new budget allocation

    When to use this: Mid-sized companies with active hiring, organizations in growth mode, companies with distributed HR.

    Position-to-worker ratio target: 1.3:1 to 1.5:1

    Strategy 3: Just-in-Time Position Creation (Best for dynamic organizations)

    Positions are created automatically during the hiring process:

    • Requisition approval creates the position
    • Position is filled immediately upon hire
    • Position closes automatically when worker terminates

    When to use this: High-growth startups, project-based organizations, consulting firms with rapid hiring cycles.

    Position-to-worker ratio target: 1.0:1 to 1.2:1

    Implementation Guidance

    Step 1: Audit your current state

    Calculate your current position-to-worker ratio:

    • Total positions ÷ Total active workers = Ratio

    If your ratio exceeds 2:1, you have a data quality crisis that needs immediate cleanup before implementing governance.

    Step 2: Choose your strategy

    Select the strategy that matches your culture. Do not choose Strategy 1 (Strict Position Control) if your organization values manager autonomy. Do not choose Strategy 3 (Just-in-Time) if you need position budget before hiring approval.

    Step 3: Document the rules

    Create a position management policy document that answers:

    • Who can create positions?
    • What approval is required?
    • When should positions be created (before requisition? during hiring? after offer acceptance)?
    • How are vacant positions reused?
    • When are positions closed or inactivated?

    Step 4: Train your stakeholders

    Position creation rules mean nothing if managers, recruiters, and HR do not understand them. Include position management in:

    • New manager onboarding
    • Recruiter training
    • HR operations procedures
    • Finance budgeting processes

    Step 5: Enforce through business process configuration

    Configure your Workday business processes to enforce your rules:

    • Remove position creation from manager self-service if using Strict Position Control
    • Add approval steps to position creation if using Manager-Initiated
    • Auto-create positions from requisition approval if using Just-in-Time

    Do not rely on training and documentation alone. Configure Workday to make the wrong behavior impossible.

    Expected Impact

    Clear position creation rules reduce position proliferation by 60% to 80% within the first year.​

    One client reduced their position-to-worker ratio from 2.7:1 to 1.4:1 over 18 months by implementing Manager-Initiated position creation with HR approval.

    Fix 2: Implement Position Lifecycle Automation

    Manual position lifecycle management creates the data quality problems that make everyone hate Position Management.

    The Problem

    In most implementations, positions remain in “Filled” status after workers terminate. They remain in “Vacant” status after workers are hired. They accumulate in “On Hold” or “Frozen” statuses with no clear owner responsible for cleanup.​

    Finance allocates budget to positions showing as “Vacant” that have been filled for six months. HR Operations sees positions showing as “Filled” when the incumbent terminated three months ago.

    Nobody trusts position data because position status never reflects reality.

    The Fix: Automate Position Status Updates

    Configure Workday to automatically update position status based on worker events:

    Automation 1: Position Fills on Hire

    When a worker is hired into a position:

    • Position status changes from “Vacant” to “Filled”
    • Position availability changes from “Available” to “Unavailable”
    • Position filled date updates to hire date
    • Position worker relationship is established

    Workday configuration: Enable “Update Position on Hire” in your Hire business process.

    Automation 2: Position Vacates on Termination

    When a worker terminates from a position:

    • Position status changes from “Filled” to “Vacant”
    • Position availability changes from “Unavailable” to “Available” (if the position should remain open)
    • Position vacant date updates to termination date
    • Position worker relationship is ended

    Workday configuration: Enable “Update Position on Termination” in your Terminate Employee business process.

    Automation 3: Position Status Updates on Worker Job Change

    When a worker moves to a new position:

    • Old position status changes from “Filled” to “Vacant”
    • New position status changes from “Vacant” to “Filled”
    • Old position becomes available for backfill
    • New position becomes unavailable

    Workday configuration: Enable “Update Position on Job Change” in your Job Change business process.

    Automation 4: Position Freezes on Elimination

    When a position is eliminated:

    • Position status changes to “Frozen” or “Eliminated”
    • Position availability changes to “Unavailable”
    • Position budget can be reallocated
    • Position cannot be filled without unfreezing

    Workday configuration: Create “Eliminate Position” business process with automatic status update.

    Position Availability Logic

    Position status and position availability are different fields that control different behaviors:

    Position Status (informational):

    • Vacant
    • Filled
    • Frozen
    • Eliminated

    Position Availability (controls hiring):

    • Available (can be filled through hiring)
    • Unavailable (cannot be filled)

    Your automation should update both fields appropriately.

    Example logic:

    • Filled position = Status “Filled”, Availability “Unavailable”
    • Vacant position approved for hire = Status “Vacant”, Availability “Available”
    • Vacant position on hiring freeze = Status “Vacant”, Availability “Unavailable”
    • Eliminated position = Status “Eliminated”, Availability “Unavailable”

    Expected Impact

    Lifecycle automation eliminates 90% of position status data quality issues.​

    One client had 450 positions with incorrect status before automation. Six months after implementing lifecycle automation, they had 12 positions with incorrect status (all explained by complex job sharing scenarios that required manual management).

    Fix 3: Solve the Position Title Confusion

    Position titles are one of the most frustrating aspects of Position Management for managers and workers.

    The Problem

    Workers are confused when their position title does not match their job title. Managers are confused when they see “Senior Software Engineer – Position 00347” on organizational charts instead of just “Senior Software Engineer.”

    The root cause: Workday displays position ID and position title in many places where users expect to see job title.​

    Example of the confusion:

    • Worker name: Sarah Chen
    • Job: Senior Software Engineer
    • Position: Senior Software Engineer – Position 00347

    Sarah sees “Senior Software Engineer – Position 00347” on her worker profile, organizational charts, and business cards. She reasonably asks: “Why does my title have a position number in it?”

    The Fix: Standardize Position Titling Convention

    Implement one of these three position titling strategies:

    Strategy 1: Position Title Matches Job Title (Simplest)

    Every position’s title exactly matches its job title.

    Example:

    • Job: Senior Software Engineer
    • Position Title: Senior Software Engineer
    • Position ID: P-12847 (used for internal tracking only)

    When to use this: Organizations where positions represent generic roles, not unique positions.

    Pros: Workers see familiar job titles everywhere. No confusion.

    Cons: Cannot distinguish between multiple positions with the same job title. Difficult to track specific positions for budgeting.

    Strategy 2: Position Title Includes Location or Department (Balanced)

    Position title includes job title plus identifying information.

    Example:

    • Job: Senior Software Engineer
    • Position Title: Senior Software Engineer – Product Engineering
    • Position ID: P-12847

    When to use this: Organizations that need to distinguish between positions in different locations or departments.

    Pros: Clear identification of specific positions. Still readable and makes sense to workers.

    Cons: Position titles become long. Requires consistent naming convention enforcement.

    Strategy 3: Position Title Uses Descriptive Unique Identifier (Most Control)

    Position title is completely unique and descriptive.

    Example:

    • Job: Senior Software Engineer
    • Position Title: Lead Engineer – Payment Processing Platform
    • Position ID: P-12847

    When to use this: Organizations with highly specialized positions where each position has unique responsibilities.

    Pros: Maximum clarity about what each specific position does. Useful for succession planning and workforce planning.

    Cons: Most complex to manage. Position titles may not align with external market titles. Requires significant governance.

    Display Configuration

    After choosing your titling strategy, configure what displays in common views:

    Worker Profile: Display job title, not position title.

    Organizational Charts: Display job title, not position title (unless position title is strategy 3 with descriptive information).

    Headcount Reports: Include both job title and position ID (for HR and Finance), but default display to job title.

    Position Budget Reports: Display position title and position ID (for Finance).

    Expected Impact

    Standardized position titling reduces position-related confusion tickets by 50% to 70%.​

    One client implemented Strategy 2 (job title plus department) and saw position titling questions drop from 30 tickets per month to 8 tickets per month.

    Fix 4: Build Position Forecasting and Planning Tools

    Position Management only creates value when it enables better workforce planning. Most organizations implement positions but never build planning tools.

    The Problem

    Organizations implement Position Management to support headcount planning and budget forecasting. Then they discover Workday does not automatically provide planning tools just because you enabled positions.​

    Finance wants to see position budget versus actual spend. HR wants to forecast hiring needs based on vacant positions. Executives want to see position fill rates and time-to-fill by department.

    Without these reports and dashboards, Position Management becomes a compliance requirement that creates work without providing value.

    The Fix: Create Position Planning Reports and Dashboards

    Build these five essential position management reports:

    Report 1: Position Budget vs. Actual Headcount

    Purpose: Finance needs to reconcile position budget with actual headcount and spending.

    Key fields:

    • Supervisory Organization
    • Position ID
    • Position Title
    • Position Status (Filled, Vacant, Frozen)
    • Position Budget FTE
    • Worker Name (if filled)
    • Worker Annual Salary
    • Budget Variance (Position Budget minus Actual Salary)

    Frequency: Monthly

    Primary audience: Finance, HR Operations

    Report 2: Vacant Position Analysis

    Purpose: HR needs to prioritize filling critical vacant positions and identify positions that should be eliminated.

    Key fields:

    • Position ID
    • Position Title
    • Supervisory Organization
    • Position Vacant Date
    • Days Vacant
    • Position Budget
    • Requisition Status (if open requisition exists)
    • Last Worker Name (who previously held the position)
    • Last Worker Termination Date

    Frequency: Weekly

    Primary audience: HR Operations, Hiring Managers, Recruiters

    Report 3: Position Fill Rate Dashboard

    Purpose: Executives need to monitor hiring effectiveness and workforce planning.

    Key metrics:

    • Total Positions
    • Filled Positions
    • Vacant Positions
    • Fill Rate Percentage (Filled ÷ Total)
    • Average Days to Fill
    • Fill Rate by Department
    • Fill Rate Trend over Last 12 Months

    Frequency: Monthly

    Primary audience: CHRO, CFO, Department Heads

    Report 4: Position Lifecycle Audit

    Purpose: HR Operations needs to identify data quality issues and positions stuck in wrong status.

    Key fields:

    • Position ID
    • Position Title
    • Position Status
    • Position Availability
    • Worker Name (if status is “Filled”)
    • Data Quality Flag (e.g., “Status shows Filled but no worker assigned”)

    Frequency: Weekly

    Primary audience: HR Operations, Workday Administrators

    Report 5: Position Forecasting by Department

    Purpose: Department heads need to forecast hiring needs and budget requirements.

    Key fields:

    • Supervisory Organization
    • Total Positions (current)
    • Filled Positions (current)
    • Vacant Approved Positions (ready to hire)
    • Vacant Unapproved Positions (not ready to hire)
    • Frozen/Eliminated Positions
    • Forecasted New Positions (from planning process)
    • Total Forecasted Headcount (12 months forward)

    Frequency: Quarterly

    Primary audience: Department Heads, Finance, HR Business Partners

    Dashboards and Visualizations

    Reports alone are not enough. Create executive dashboards using Workday’s discovery boards or external visualization tools:

    Executive Workforce Dashboard:

    • Fill rate trend line
    • Vacant positions by department (bar chart)
    • Average days to fill by department
    • Headcount actual vs budget (variance analysis)

    HR Operations Dashboard:

    • Positions vacant over 90 days
    • Positions with data quality issues
    • Requisitions without positions
    • Recent position changes log

    Department Manager Dashboard:

    • My team’s positions (filled and vacant)
    • My vacant positions awaiting requisition
    • My team’s budget vs actual
    • Hiring pipeline status

    Expected Impact

    Position planning tools increase Position Management value perception by 80% or more.​

    One client’s CFO went from saying “Position Management just creates extra work” to “Position Management is our single source of truth for workforce budgeting” after implementing these five reports and two executive dashboards.

    Fix 5: Integrate Position Management with Recruiting

    The disconnect between Position Management and Recruiting creates operational friction that frustrates everyone.

    The Problem

    In many implementations, Position Management and Recruiting operate as separate processes:

    • HR creates positions
    • Weeks later, someone creates a requisition
    • The requisition is not clearly linked to the position
    • The position is filled through hiring, but the requisition status does not update
    • Nobody knows which vacant positions have active recruiting efforts

    Managers ask: “Which of my vacant positions are we actively recruiting for?”

    Recruiters ask: “Which positions do I need to create requisitions for?”

    HR asks: “Why do we have 200 vacant positions but only 80 open requisitions?”

    The Fix: Tightly Integrate Position and Requisition Workflows

    Implement one of these two integration strategies:

    Integration Strategy 1: Position-First Workflow

    Positions must exist before requisitions can be created.

    Process flow:

    1. Manager or HR creates position (or reuses vacant position)
    2. Position status = “Vacant”
    3. Position availability = “Available”
    4. Manager creates requisition linked to the position
    5. Requisition approval process completes
    6. Recruiting begins
    7. Candidate hired into the position
    8. Position status automatically updates to “Filled”
    9. Requisition status automatically updates to “Filled”

    Workday configuration:

    • Make position selection required on Create Requisition business process
    • Enable automatic position update on Hire
    • Create report showing positions available but without requisitions

    When to use this: Organizations using Strict Position Control or Manager-Initiated strategies (Fix 1). Organizations with formal budgeting where positions represent budget allocation.

    Integration Strategy 2: Requisition-First Workflow

    Requisitions can be created first, and positions are created automatically.

    Process flow:

    1. Manager creates requisition with job and organization
    2. Requisition approval process completes
    3. System automatically creates position linked to requisition
    4. Position status = “Vacant”
    5. Position availability = “Available”
    6. Recruiting begins
    7. Candidate hired into the position
    8. Position status automatically updates to “Filled”
    9. Requisition status automatically updates to “Filled”

    Workday configuration:

    • Enable automatic position creation on Requisition approval
    • Configure position naming convention for auto-created positions
    • Enable automatic position update on Hire

    When to use this: Organizations using Just-in-Time position creation strategy (Fix 1). High-growth companies where hiring speed is critical.

    Position-Requisition Status Synchronization

    Regardless of which integration strategy you choose, implement status synchronization:

    When requisition is approved:

    • Linked position availability updates to “Available”

    When requisition is on hold:

    • Linked position availability updates to “Unavailable”

    When requisition is filled:

    • Linked position status updates to “Filled”
    • Linked position availability updates to “Unavailable”

    When requisition is cancelled:

    • Linked position availability updates to “Unavailable” (if position should be frozen)
    • Or remains “Available” (if position should be filled through a new requisition)

    Reporting Integration

    Create reports that show the position-requisition relationship:

    Vacant Positions Without Requisitions Report:

    Shows positions approved for hiring but no active recruiting effort. HR Operations uses this to prompt managers to create requisitions or inactivate unnecessary positions.

    Requisitions Without Positions Report:

    Shows requisitions approved but not linked to positions. Finance uses this to identify potential budget disconnects.

    Expected Impact

    Position-recruiting integration reduces time-to-fill by 20% to 30% by eliminating administrative delays.​

    One client reduced their average time-to-fill from 67 days to 48 days primarily by eliminating the lag between position approval and requisition creation through requisition-first integration.

    Fix 6: Solve the Job vs. Position Confusion

    The most common Position Management complaint is: “Why do I need a position AND a job? They seem like the same thing.”

    The Problem

    Most people do not understand the difference between a job and a position in Workday.

    The technical definitions do not help:

    Workday documentation says:

    • Job: A generic role (like “Software Engineer”)
    • Position: A specific instance of a job (like “Software Engineer position in the Product team”)

    That explanation makes sense to Workday consultants. It makes no sense to hiring managers.

    The confusion creates practical problems:

    Managers do not know whether to change the job or the position when responsibilities change.

    HR does not know whether to create a new position or change the position’s job when a role evolves.

    Finance does not understand why budget is allocated to positions but compensation is tied to jobs.

    The Fix: Create Clear Guidance on Job vs. Position

    Develop simple, practical guidance that non-HR people can understand:

    Simple Explanation:

    Job = What you do (your role, responsibilities, job level)
    Position = Where you do it (which team, which budget, which headcount slot)

    Examples that clarify:

    Scenario 1: Two people doing the same work in different locations

    Sarah and David are both Senior Software Engineers (same job) on different teams (different positions).

    • Sarah: Job = “Senior Software Engineer”, Position = “SSE – Product Team”
    • David: Job = “Senior Software Engineer”, Position = “SSE – Platform Team”

    Same job. Different positions. Different managers. Different budgets.

    Scenario 2: A promotion

    Sarah gets promoted from Senior Software Engineer to Staff Software Engineer.

    What changes?

    • Her job changes (Senior to Staff)
    • Her position might stay the same (still “SSE – Product Team” position, but now we need to rename it)
    • Or she might move to a different position (new “Staff Engineer – Product Team” position)

    Scenario 3: A transfer

    David transfers from the Platform Team to the Product Team.

    What changes?

    • His job stays the same (still Senior Software Engineer)
    • His position changes (from “SSE – Platform Team” to “SSE – Product Team”)

    Practical Decision Rules

    Give managers these decision rules:

    When to change the job:

    • Promotion or demotion (job level changes)
    • Significant responsibility change that affects market pay (accountant becomes senior accountant)
    • Role type changes (individual contributor becomes manager)

    When to change the position:

    • Worker transfers to a different team
    • Worker moves to a different location
    • Worker’s budget allocation changes to a different cost center
    • Organizational restructure moves the position to a different reporting line

    When to create a new position:

    • Headcount increase approved (new budget allocation)
    • Organizational expansion (new team, new location)
    • Backfill approval for a departed worker (if using position reuse strategy)

    When to change both job and position:

    • Promotion with transfer (worker promoted and moves to new team)
    • Role change with team change (individual contributor becomes manager in a different organization)

    Training Materials

    Create visual decision trees that managers can reference:

    Decision Tree: Do I need to change the job, position, or both?

    Start: Something about this worker’s role is changing.

    Question 1: Are their responsibilities or job level changing?

    • Yes → Job change needed
    • No → Continue to Question 2

    Question 2: Are they moving to a different team, location, or reporting line?

    • Yes → Position change needed
    • No → Continue to Question 3

    Question 3: Is their budget allocation or cost center changing?

    • Yes → Position change needed
    • No → No job or position change needed (might be compensation change, org assignment change, or other worker data change)

    Expected Impact

    Clear job versus position guidance reduces manager confusion tickets by 60% to 80%.​

    One client created a 2-page visual guide on job versus position and included it in manager onboarding. Position-related manager questions dropped from 45 tickets per quarter to 12 tickets per quarter.

    Fix 7: Implement Position Data Quality Audits

    Even with all the fixes above, position data quality degrades over time without active monitoring.

    The Problem

    Position data quality problems accumulate silently:

    • Positions showing as filled when workers terminated months ago
    • Positions showing as vacant when workers are actively working
    • Duplicate positions for the same role and team
    • Position titles that do not match job titles
    • Positions with outdated budget allocations
    • Frozen positions that should be eliminated
    • Eliminated positions that should be reopened

    Nobody notices until Finance runs a budget report that shows 200 vacant positions with budget allocation when HR knows they only have 80 approved openings.

    The Fix: Quarterly Position Data Quality Audits

    Implement a recurring quarterly audit process:

    Audit Checkpoint 1: Position Status Accuracy

    Data quality check: Position status matches actual worker assignment.

    Query logic:

    • Positions with status “Filled” but no worker assigned
    • Positions with status “Vacant” but worker is assigned
    • Positions with worker assigned but status is “Frozen” or “Eliminated”

    Resolution:

    • Update position status to match reality
    • Investigate why automation failed (Fix 2 may need adjustment)
    • Identify positions that require manual status management (job sharing, complex scenarios)

    Audit Checkpoint 2: Position-to-Worker Ratio

    Data quality check: Position-to-worker ratio remains within target range.

    Query logic:

    • Total positions ÷ Total active workers
    • Position-to-worker ratio by department
    • Departments with ratios exceeding 2:1

    Resolution:

    • Identify departments with position proliferation problems
    • Work with department heads to eliminate unnecessary positions
    • Review position creation governance (Fix 1) if ratio is increasing

    Target: Position-to-worker ratio should remain between 1.1:1 and 1.5:1 depending on your strategy from Fix 1.

    Audit Checkpoint 3: Vacant Position Aging

    Data quality check: Vacant positions are actively managed or eliminated.

    Query logic:

    • Positions vacant for more than 180 days
    • Positions vacant without open requisitions
    • Positions with status “Frozen” for more than 365 days

    Resolution:

    • Contact department heads about positions vacant over 180 days
    • Eliminate positions with no hiring plan
    • Unfreeze positions approved for hiring or permanently eliminate positions no longer needed

    Audit Checkpoint 4: Position Budget Alignment

    Data quality check: Position budget matches organizational budget allocation.

    Query logic:

    • Positions with no budget allocation
    • Positions with budget allocation but status “Eliminated”
    • Total position budget versus total organizational budget (should match)

    Resolution:

    • Update position budget to match approved headcount budget
    • Reallocate budget from eliminated positions
    • Investigate discrepancies between position budget total and organizational budget

    Audit Checkpoint 5: Position Naming Consistency

    Data quality check: Position titles follow your established convention from Fix 3.

    Query logic:

    • Positions with titles not matching job titles (if using Strategy 1 from Fix 3)
    • Positions with generic titles like “Position 1” or “New Position”
    • Positions with titles containing “copy” or “test”

    Resolution:

    • Rename positions to match your titling convention
    • Train HR Operations on proper position creation
    • Consider implementing position name validation in business process configuration

    Audit Reporting and Accountability

    Create a quarterly Position Data Quality Scorecard:

    Metrics to track:

    • Total positions
    • Position-to-worker ratio
    • Positions with status accuracy issues (count and percentage)
    • Positions vacant over 180 days (count and percentage)
    • Positions with budget alignment issues (count and percentage)
    • Position data quality score (percentage of positions with zero issues)

    Accountability:

    • Assign HR Operations ownership for overall position data quality
    • Assign department heads ownership for their department’s positions
    • Report scorecard to CHRO and CFO quarterly
    • Set improvement targets (e.g., 95% data quality score)

    Expected Impact

    Quarterly audits maintain position data quality above 95% accuracy.​

    One client started with 72% position data quality (28% of positions had at least one data issue). After four quarterly audits with clear accountability and remediation, they reached 96% position data quality.

    Implementation Roadmap: Rolling Out These 7 Fixes

    You cannot implement all seven fixes simultaneously. Here is a realistic implementation roadmap:

    Quarter 1: Foundation (Fixes 1, 2, 3)

    Month 1: Fix 1 – Position Creation Governance

    • Audit current position-to-worker ratio
    • Choose position creation strategy
    • Document position creation rules
    • Configure business process enforcement

    Month 2: Fix 2 – Position Lifecycle Automation

    • Enable automatic position updates on hire, termination, job change
    • Test automation with representative scenarios
    • Train HR Operations on new automation
    • Monitor for edge cases requiring manual intervention

    Month 3: Fix 3 – Position Title Standardization

    • Choose position titling strategy
    • Rename existing positions to match strategy (may require batch update)
    • Configure display preferences
    • Train stakeholders on new conventions

    Expected outcome: Position creation is controlled, position status reflects reality, position titles make sense to workers.

    Quarter 2: Value Creation (Fixes 4, 5)

    Month 4: Fix 4 – Position Planning Reports (Part 1)

    • Build Report 1 (Position Budget vs. Actual)
    • Build Report 2 (Vacant Position Analysis)
    • Train Finance and HR on new reports

    Month 5: Fix 4 – Position Planning Reports (Part 2)

    • Build Report 3 (Position Fill Rate Dashboard)
    • Build Report 4 (Position Lifecycle Audit)
    • Build Report 5 (Position Forecasting)
    • Create executive dashboards

    Month 6: Fix 5 – Recruiting Integration

    • Choose position-requisition integration strategy
    • Configure business processes for integration
    • Enable status synchronization
    • Build integration reports
    • Train recruiters and hiring managers

    Expected outcome: Position Management delivers tangible value through planning insights and recruiting efficiency.

    Quarter 3: Sustainability (Fixes 6, 7)

    Month 7: Fix 6 – Job vs. Position Guidance

    • Develop simple explanations and decision rules
    • Create visual decision trees
    • Build training materials
    • Deliver training to managers

    Month 8: Fix 7 – Data Quality Audits (Setup)

    • Build audit reports for all five checkpoints
    • Create Position Data Quality Scorecard
    • Assign accountability
    • Set baseline metrics and targets

    Month 9: Fix 7 – Data Quality Audits (First Execution)

    • Run first quarterly audit
    • Remediate identified issues
    • Refine audit queries based on findings
    • Establish recurring quarterly schedule

    Expected outcome: Stakeholders understand Position Management, data quality is maintained systematically.

    Ongoing: Continuous Improvement

    Quarterly activities:

    • Run position data quality audit
    • Review position-to-worker ratio trends
    • Assess position planning report usage
    • Gather stakeholder feedback
    • Refine processes based on learnings

    Annual activities:

    • Comprehensive review of position creation governance
    • Position title convention review and updates
    • Position budget alignment with annual planning
    • Position Management training refresher for all stakeholders

    Common Objections (And How to Respond)

    When you propose these fixes, you will encounter objections. Here is how to respond:

    Objection 1: “This is too much governance. We need flexibility.”

    Response: Position Management without governance creates chaos, not flexibility. You currently have 6,000 positions for 2,500 workers. That is not flexibility; that is data that nobody trusts. These fixes give you disciplined flexibility with accountability.

    Objection 2: “We don’t have time to implement all this.”

    Response: You are already spending time managing position chaos. Last quarter, your HR Operations team spent 120 hours investigating position data quality issues and answering manager questions. These fixes automate 80% of that work. You are not adding work; you are replacing chaotic reactive work with structured proactive work.

    Objection 3: “Our organization is too complex for simple rules.”

    Response: Every organization thinks they are too complex for simple rules. Then they implement simple rules and discover 90% of scenarios fit the rules perfectly. You can handle the other 10% as exceptions. Start simple. Add complexity only when genuinely needed.

    Objection 4: “Finance will never agree to change the budgeting process.”

    Response: Finance wants position data they can trust more than they want to maintain the current process. Show your CFO the current position-to-worker ratio and ask if they trust position budget numbers. They will support process changes that improve data quality.

    Objection 5: “We already tried to fix Position Management and it didn’t work.”

    Response: Most Position Management fixes fail because they address symptoms instead of root causes. These seven fixes address root causes systematically. Also, previous failures often occurred because fixes were implemented without stakeholder buy-in. This roadmap builds buy-in through phased implementation with visible results.

    Measuring Success: Key Metrics

    Track these metrics to demonstrate improvement:

    Operational Efficiency Metrics:

    • Position-related HR tickets per month (target: 75% reduction)
    • Time spent on position data quality remediation (target: 80% reduction)
    • Position creation to approval time (target: 50% reduction)

    Data Quality Metrics:

    • Position-to-worker ratio (target: 1.1:1 to 1.5:1)
    • Position data quality score (target: 95%+)
    • Positions with status accuracy issues (target: less than 5%)

    Business Value Metrics:

    • Finance confidence in position budget data (survey-based, target: 8/10 or higher)
    • Manager understanding of position concepts (survey-based, target: 7/10 or higher)
    • Position planning report usage (target: 80% of eligible users accessing monthly)

    Recruiting Efficiency Metrics:

    • Average days to fill (target: 20-30% reduction)
    • Time from position approval to requisition creation (target: less than 5 days)
    • Percentage of vacant positions with active requisitions (target: 90%+)

    Conclusion: From Most Hated to Strategic Asset

    Position Management gets a bad reputation because most organizations implement it poorly.

    They enable the feature, create positions, and expect value to appear automatically. When chaos ensues, they blame Position Management.

    But Position Management is not the problem. Lack of governance, automation, and planning tools is the problem.

    The seven fixes in this guide transform Position Management from a compliance burden into a strategic workforce planning capability:

    Fix 1 controls position proliferation through clear creation rules.

    Fix 2 ensures position data reflects reality through lifecycle automation.

    Fix 3 eliminates title confusion through standardized conventions.

    Fix 4 delivers business value through planning reports and dashboards.

    Fix 5 improves recruiting efficiency through tight integration.

    Fix 6 reduces stakeholder confusion through clear guidance.

    Fix 7 maintains data quality through systematic audits.

    Implement these fixes systematically over three quarters, and Position Management will go from your most complained-about feature to a trusted strategic asset that Finance, HR, and executives actually use.

    Tell Me Your Experience

    What is your biggest Position Management frustration? Which of these seven fixes would have the most impact in your organization?

    Have you successfully implemented Position Management? What worked for you?

    Share your experiences in the comments below. We learn best from each other’s real-world challenges.

  • Designing Your Workday HCM Foundation

    Designing Your Workday HCM Foundation

    Designing your Workday HCM foundation is one of the most important decisions you will ever make in a tenant. Once you go live with supervisory orgs, positions, job profiles and cost centers, reversing bad design is painful, political and expensive. A clean foundation, on the other hand, makes every downstream process easier: hiring, transfers, security, reporting, integrations and even future modules like Time Tracking or Learning.​

    Start with a clear operating model

    Before touching configuration, clarify how the business actually operates. In Workday terms, this means understanding who manages whom, how cost is tracked, how HR wants to report headcount and how finance wants to see labor cost. You will use those answers to decide the shape of supervisory orgs, whether you go position or job management, and which worktags (like cost centers) become mandatory.​

    Workday supervisory organizations represent management relationships and operational structure, not legal entities. Companies and entities represent legal and accounting structure, while cost centers and other worktags represent how cost is tracked and reported. Separating these concepts early prevents you from overloading supervisory orgs with finance responsibilities they were never designed to carry.​

    Designing supervisory orgs that do not collapse

    A common mistake is to copy the HR org chart directly into Workday as dozens or hundreds of tiny supervisory orgs. That usually creates reporting complexity, security noise and constant maintenance whenever someone changes manager. A better pattern is to design supervisory orgs around stable management units: departments, teams or business units that change less frequently than individual manager assignments.​

    When designing supervisory orgs, ask:

    • Can this org survive manager changes without needing to be restructured every week?
    • Does this level of granularity help reporting and security, or just create clutter?
    • Is there a clear business purpose for this org beyond “we have a manager”?

    Aim for a hierarchy that can support real-world approvals, headcount reporting and security boundaries, but is still simple enough that new HRIS analysts can navigate it confidently.​

    Positions vs jobs: choose consciously

    Workday supports position management and job management, and the choice is foundational. Position management is best when you need rigorous headcount control, budget-to-position matching and clear tracking of vacancies. Job management is lighter and works well in fluid environments where individual seats are less important than overall staffing levels.​

    For position management, design patterns include:

    • Use positions anywhere headcount is tightly controlled, such as regulated functions or centralized operations.​
    • Give positions meaningful, consistent titles that align with job profiles and not personal names.
    • Avoid creating “temporary” positions for one-off cases; these often become long-term clutter.

    For job management, ensure you still have clear job profiles with compensation grades and worktags so that reporting and security do not depend on free-text job titles.​

    Job profiles as your talent backbone

    Job profiles are the backbone of how Workday sees roles, qualifications, compensation and, in some tenants, learning and talent. Poorly designed job profiles lead to reporting chaos: dozens of variations for the same role, unclear grade mappings and confusing job histories for workers.​

    Strong job profile design usually includes:

    • A consistent naming pattern (e.g., “Analyst, HR Operations” instead of many variations).
    • Clear classification into job families and job profiles that align with how HR and talent teams think about roles.​
    • Linkage to compensation grades and grade profiles so that pay ranges are consistent across markets.​

    When job profiles are clean, you can deploy performance, learning and career frameworks more easily, because everything hangs off a small number of well-maintained roles rather than hundreds of one-off titles.​

    Cost centers and worktags: think like finance

    Cost centers and other worktags are how finance sees the world in Workday Financials, and even in HCM-only tenants they drive a lot of reporting. HR often underestimates how important it is to design cost centers that match finance’s management reporting rather than HR’s internal labels.​

    Good practices include:

    • Keep cost centers relatively stable and align them to budget owners or P&L responsibility.​
    • Avoid duplicating cost centers just to represent small team differences; use supervisory orgs, locations or custom organizations for that.​
    • Ensure default cost centers are set correctly at the position, worker or org level so payroll and financial postings are accurate without manual fixes.​

    When cost centers and worktags are clean, you can produce reliable reports like headcount by cost center, labor cost by business unit and budget versus actual staff cost with minimal reconciliation.​

    Putting it all together in real processes

    The real test of your HCM foundation is not whether it looks neat in the configuration pages, but whether everyday processes run smoothly. When HR creates a new position, it should be obvious which supervisory org to use, which job profile to select and which cost center should default. When a manager initiates a transfer, the path through supervisory orgs and cost centers should be clear, and reporting should show the move without gaps or duplicates.​

    Think through core processes end to end:

    • Hire to retire: are orgs, positions and cost centers stable across promotions, transfers and international moves?​
    • Security: can you grant HR partners and managers access based on supervisory orgs and cost centers without dozens of exceptions?​
    • Reporting: can HR and finance quickly answer questions about headcount, vacancies and cost without manual spreadsheets?​

    When these scenarios work, you know the foundation is serving the business rather than the other way around.

    Design for the next three years, not three months

    Finally, design your Workday HCM foundation with a three-year horizon. Most organizations will go through reorganizations, new business lines and possibly new geographies in that time. Build supervisory org structures, position rules, job profiles and cost center hierarchies that can absorb that change without needing a full rebuild.​

    Document your design principles and decisions, not just your configuration. Future HRIS analysts, Workday consultants and auditors should be able to understand why the tenant looks the way it does. That documentation is part of the foundation, just as much as the orgs and positions themselves.​

    A strong Workday HCM foundation does not happen by accident. It is the result of deliberate choices about how to represent your organization, control headcount, classify roles and track cost. When you get those basics right, everything from security to payroll to analytics becomes simpler, more reliable and much easier to scale.

  • Making Workday Fields Work For You

    Making Workday Fields Work For You

    Workday Gives You Many Fields. The Question Is: Which Ones Matter?

    One of the first surprises for new Workday project teams is just how many fields are available in the system. For almost any object—workers, positions, jobs, organizations, transactions—Workday provides a large set of standard fields plus the option to add custom ones. It can feel like standing in front of a giant buffet: everything looks useful, and it is tempting to take a bit of everything.

    But in daily use, the opposite is true. HR and Finance users do not want every possible field. They want the right fields, in the right places, with clear labels and obvious value. When every screen is full of optional fields that no one understands, Workday starts to feel heavy and complicated instead of helpful.

    The Risk of “Collect Everything” Thinking

    During implementation, it is common for project teams to hear requests like:

    • “Let’s capture this field, we might need it later.”
    • “Legal might ask for this data one day.”
    • “Our legacy system had this field, so we should bring it over.”

    Individually, each request sounds reasonable. Together, they create:

    • Crowded data entry pages where users scroll past dozens of fields they never touch.
    • Inconsistent data because some fields are optional and rarely filled in correctly.
    • Confusing reports that include fields no one knows how to interpret or trust.

    Instead of being a clean, focused system, Workday becomes a mirror of every “just in case” decision made during implementation.

    A Better Question: What Decisions Will This Field Support?

    A more effective way to choose which fields to use is to start from decisions, not from the system’s capabilities. For each field you are considering, ask:

    • Which business decision does this field help us make?
    • Who will use this data, and how often?
    • What happens if we do not capture it?
    • Can we get this information from another trusted source instead?

    If a field does not clearly support a decision, a process, or a legal requirement, you should question whether it is worth adding to every screen, task, and report.

    Designing Workday Pages for Real Users

    Remember that most HR and Finance users interact with Workday through specific tasks and pages, not through configuration screens. Page layout, field order, and visual clarity matter as much as which fields are technically available.

    When designing pages:

    • Prioritize essential fields at the top.
      Make sure the fields that must be filled in for a process to work are clearly visible and easy to understand.
    • Group related fields together.
      Keep job-related fields, compensation fields, and organizational fields grouped so they make sense in context.
    • Hide or collapse rarely used fields.
      If a field is only relevant in special cases, consider collapsing it into an expandable section or removing it from most users’ view.
    • Use clear labels and help text.
      If a field is not self-explanatory, add short help text that describes when and how it should be used.

    The goal is to make Workday tasks feel quick and focused, not like filling out endless forms.

    Balancing Standard and Custom Fields

    Workday standard fields cover a wide range of typical HR and Finance needs. However, every organization has unique data requirements, which is where custom fields come in. The danger is adding custom fields for every request without thinking about long-term maintenance.

    To balance standard and custom fields:

    • Use standard fields whenever they reasonably fit.
      Standard fields are more likely to be supported in delivered reports, updates, and integrations.
    • Create custom fields only when there is a clear, ongoing use case.
      For example, tracking a specific internal classification that truly matters for reporting or compliance.
    • Review custom fields regularly.
      Remove or retire fields that are no longer used or that have been replaced by better structures.

    This reduces clutter and helps keep your data model understandable for both current and future admins.

    Field Governance: Small Rules, Big Impact

    You do not need a complex governance framework to manage fields effectively. A few simple rules can dramatically improve your Workday experience:

    • Approval for new fields.
      Require a short justification (what decision it supports, who will use it) before adding new custom fields.
    • Clear ownership.
      Assign an owner for important fields, especially those that drive reporting and compliance.
    • Standards for naming and help text.
      Use consistent naming patterns and simple language so users can quickly understand what each field means.
    • Periodic cleanup.
      Schedule regular reviews to identify fields that are unused or duplicated and decide whether to hide, retire, or consolidate them.

    These practices turn field management from a one-time implementation activity into an ongoing, controlled process.

    Helping HR and Finance See the Value in Fields

    Fields are not just boxes to fill in; they are commitments of time and attention from HR, Finance, and other business users. To get buy-in, show them how fields connect to outcomes they care about:

    • Better headcount or cost reports.
    • Faster approvals and fewer errors.
    • More reliable analytics for planning and budgeting.
    • Easier compliance and audit reporting.

    When users understand why a field exists and how it is used, they are more likely to enter accurate data and less likely to complain about “yet another thing to fill in.”

    Simplifying Workday by Designing Fields Intentionally

    Workday’s flexibility is powerful, but without intentional design, that flexibility can become noise. Instead of asking, “How many fields does Workday give us?” the better questions are:

    • Which fields do our HR and Finance teams actually need on screen?
    • Which fields support critical decisions and reporting?
    • How can we keep pages clean, consistent, and easy to use?

    By choosing, designing, and governing fields carefully, you turn Workday from a complex data collection tool into a clear, focused system that truly supports your people and processes. That is a key part of simplifying Workday for HR and Finance.