peopletechguide.com

Tag: workday analytics

  • Workday Reports: Advanced vs. Matrix vs. Composite Guide

    You open a reporting request from your CFO:

    “I need headcount by department, broken down by location and job level, with month-over-month trends and turnover rates.”

    You stare at the request. Should you build an Advanced Report? A Matrix Report? A Composite Report? Or maybe three separate reports?

    This is where most Workday professionals get stuck. They know how to build reports technically, but they don’t know which report type to use when. So they default to Advanced Reports for everything, then spend hours manipulating data in Excel to get the view they actually need.

    Here’s the truth: choosing the wrong report type doesn’t just waste time. It creates slow, unmaintainable reports that confuse users and break during updates.

    This guide teaches you how to choose the right report type for every scenario. You’ll learn what each report type does, when to use it, and how to build it correctly with real-world examples.

    The Three Report Types: What They Actually Do

    Advanced Reports: The List Builder

    What It Is:
    An Advanced Report displays data from a single business object as a list of rows. Think of it as a detailed table where each row represents one record.

    Structure:

    • One row per record (employee, position, transaction, event)
    • Multiple columns showing different fields
    • Can include filters, prompts, sorting, and grouping
    • Can include subtotals and aggregations

    Visual Example:

    Employee NameHire DateDepartmentLocationJob TitleAnnual Salary
    Sarah Johnson2022-03-15EngineeringSan FranciscoSenior Engineer$125,000
    Mike Chen2023-01-10SalesNew YorkAccount Executive$95,000
    Emily Davis2021-06-20HRChicagoHR Business Partner$105,000

    Best For:

    • Employee lists (active headcount, new hires, terminations)
    • Transaction logs (compensation changes, job changes, time off)
    • Detailed records for audits, integrations, or EIB loads
    • Reports that answer: “Show me all [records] where [criteria]”

    Not Good For:

    • Pivoting data across multiple dimensions
    • Showing trends over time periods
    • Combining data from multiple business objects

    Matrix Reports: The Pivot Table

    What It Is:
    A Matrix Report summarizes numeric data across rows and columns. It’s Workday’s version of an Excel pivot table or crosstab.

    Structure:

    • Rows define one dimension (e.g., Department)
    • Columns define another dimension (e.g., Location or Time Period)
    • Cells show aggregated metrics (count, sum, average)
    • Interactive drilling (click to see detail records)

    Visual Example:

    Headcount by Department and Location

    DepartmentSan FranciscoNew YorkChicagoTotal
    Engineering4512865
    Sales10381563
    HR581225
    Total605835153

    Best For:

    • Summarizing data across two dimensions
    • Headcount analysis (by org, location, job level)
    • Trend analysis over time (monthly, quarterly, yearly)
    • Financial rollups (cost by department and account)
    • Reports that answer: “Show me [metric] broken down by [dimension 1] and [dimension 2]”

    Not Good For:

    • Showing raw transaction details
    • Combining multiple unrelated metrics
    • Reports with more than two grouping dimensions

    Composite Reports: The Dashboard Builder

    What It Is:
    A Composite Report combines multiple Matrix Reports into a single unified report. It’s how you build executive dashboards and scorecards.

    Structure:

    • Multiple sub-reports (each is a Matrix Report)
    • Each sub-report can have different data sources
    • Aligned by common dimension (department, location, time period)
    • Metrics calculated across sub-reports at the composite level

    Visual Example:

    HR Scorecard by Department

    Sub-Report 1: Headcount Trend

    DepartmentJan 2025Feb 2025Mar 2025
    Engineering606365
    Sales586163

    Sub-Report 2: New Hires

    DepartmentJan 2025Feb 2025Mar 2025
    Engineering543
    Sales354

    Sub-Report 3: Terminations

    DepartmentJan 2025Feb 2025Mar 2025
    Engineering211
    Sales022

    Composite Calculation: Turnover Rate

    DepartmentJan 2025Feb 2025Mar 2025
    Engineering3.3%1.6%1.5%
    Sales0%3.3%3.2%

    Best For:

    • Executive dashboards (HR scorecard, Finance KPIs)
    • Multi-metric analysis aligned by common dimension
    • Combining HCM + Finance data
    • Reports that answer: “Show me 4-5 related metrics side-by-side”

    Not Good For:

    • Simple lists or single-metric analysis
    • Ad-hoc analysis (too complex for quick requests)
    • Reports without a common aligning dimension

    Decision Framework: Which Report Type Should I Use?

    Use this flowchart to decide:

    Question 1: Do I need multiple related metrics from different data sources?

    • Yes → Use Composite Report
    • No → Go to Question 2

    Question 2: Do I need to aggregate/summarize data across dimensions?

    • Yes → Use Matrix Report
    • No → Go to Question 3

    Question 3: Do I need a detailed list of records?

    • Yes → Use Advanced Report

    Real-World Scenario Examples

    Scenario 1: “Show me all employees who were hired in the last 90 days”

    Report Type: Advanced Report

    Why: You need a list of individual employee records. No aggregation needed.

    Data Source: Workers

    Columns: Employee Name, Employee ID, Hire Date, Department, Manager, Location

    Filter: Hire Date is within the last 90 days

    Scenario 2: “Show me headcount by department and location”

    Report Type: Matrix Report

    Why: You need to aggregate (count employees) across two dimensions (department and location).

    Data Source: Workers

    Rows: Department (grouping)

    Columns: Location (grouping)

    Measure: Count of Workers

    Scenario 3: “Show me monthly headcount, new hires, terminations, and turnover rate by department”

    Report Type: Composite Report

    Why: You need multiple related metrics (4 different calculations) aligned by common dimensions (department and month).

    Sub-Report 1 (Matrix): Headcount by Department and Month

    Sub-Report 2 (Matrix): New Hires by Department and Month

    Sub-Report 3 (Matrix): Terminations by Department and Month

    Composite Calculation: Turnover Rate = (Terminations ÷ Average Headcount) × 100

    Building Your First Advanced Report

    Let’s build a practical Advanced Report: New Hires in Last 90 Days

    Step 1: Create the Report

    1. Search for Create Custom Report
    2. Report Type: Advanced
    3. Data Source: Workers
    4. Report Name: New Hires – Last 90 Days
    5. Click OK

    Step 2: Add Columns

    Click Add in the Columns section to add fields:

    Column 1: Worker (displays employee name)

    Column 2: Employee ID

    Column 3: Hire Date

    Column 4: Primary Position

    Column 5: Worker’s Manager (manager name)

    Column 6: Location

    Column 7: Cost Center

    Column 8: Time Type (Full-Time, Part-Time)

    Pro Tip: Rename column labels for clarity. “Worker” → “Employee Name”, “Worker’s Manager” → “Manager”

    Step 3: Add Filter

    Click Filter tab.

    Filter Condition: Hire Date is within the last 90 days

    Configuration:

    • Field: Hire Date
    • Operator: Is Within
    • Value: Last 90 days (Workday calculates dynamically)

    Alternative: Use Prompt instead of hard-coded filter to let users choose the date range at runtime.

    Step 4: Add Sorting

    Click Sort tab.

    Primary Sort: Hire Date (descending – newest hires first)

    Secondary Sort: Worker (ascending – alphabetical within same hire date)

    Step 5: Add Grouping (Optional)

    Click Sort tab, scroll to Grouping.

    Group By: Department

    This groups all new hires by their department, with subtotals showing count per department.

    Enable: Summarize Detail Rows (checkbox)

    Result: Report shows:

    • Engineering: 12 new hires
      • Sarah Johnson – 2025-03-15
      • Mike Chen – 2025-03-10
      • …
    • Sales: 8 new hires
      • Emily Davis – 2025-03-20
      • …

    Step 6: Test and Share

    Click OK to save and run the report.

    Validate:

    • Do all employees shown have hire dates within last 90 days?
    • Are columns displaying correctly?
    • Is sorting working as expected?

    Share the Report:

    1. Click Share icon
    2. Select users or security groups
    3. Grant View permission
    4. Save

    Building Your First Matrix Report

    Let’s build: Headcount by Department and Location

    Step 1: Create the Report

    1. Search for Create Custom Report
    2. Report Type: Matrix
    3. Data Source: Workers
    4. Report Name: Headcount by Department and Location
    5. Click OK

    Step 2: Configure Rows

    Rows Axis: Department (Supervisory Organization)

    This defines what appears down the left side of your matrix.

    Row Field: Organization > Name (displays department names)

    Sort: Ascending (alphabetical order)

    Step 3: Configure Columns

    Columns Axis: Location

    This defines what appears across the top of your matrix.

    Column Field: Location > Name (displays location names like “San Francisco”, “New York”)

    Sort: Ascending (alphabetical order)

    Step 4: Configure Measure

    Measure: What you’re counting or summing in each cell.

    Metric: Count of Workers

    Aggregation Method: Count (default for counting records)

    Alternative measures:

    • Sum of Annual Salary (for compensation analysis)
    • Average of Tenure (for tenure analysis)

    Step 5: Add Filter (Optional)

    Click Filter tab.

    Filter: Worker Status = Active

    This excludes terminated employees from the headcount.

    Step 6: Enable Drilling

    Drilling lets users click a cell to see the detail records.

    Configuration: Enabled by default in Matrix Reports

    How It Works:
    User clicks cell showing “45 employees in Engineering – San Francisco”
    → Workday displays list of those 45 employees with details

    Step 7: Add Prompts (Optional)

    Prompts let users filter the report at runtime.

    Add Prompt: As of Date

    Use Case: Users can run the report “as of December 31, 2024” to see historical headcount.

    Configuration:

    1. Click Prompts tab
    2. Add As of Date prompt
    3. Default value: Today (report defaults to current headcount)
    4. Users can override to see historical data

    Step 8: Test and Visualize

    Click OK to save and run.

    Validate:

    • Do row totals match expected headcount per department?
    • Do column totals match expected headcount per location?
    • Does grand total match total active headcount?

    Add Chart Visualization:

    1. Click Add Chart
    2. Chart Type: Stacked Bar Chart
    3. X-Axis: Department
    4. Y-Axis: Headcount
    5. Stack By: Location (different colors for each location)

    Result: Visual chart showing headcount distribution across departments and locations.

    Building Your First Composite Report

    Let’s build: HR Monthly Scorecard (Headcount, Hires, Terms, Turnover)

    Step 1: Build the Matrix Sub-Reports First

    You need to create each Matrix Report separately before combining them.

    Sub-Report 1: Monthly Headcount by Department

    1. Create Matrix Report
    2. Data Source: Workers (Snapshot-based for historical data)
    3. Rows: Department
    4. Columns: Month (from Period Reporting Calendar)
    5. Measure: Count of Workers
    6. Filter: Worker Status = Active (at snapshot date)
    7. Save As: Headcount by Department – Monthly

    Sub-Report 2: New Hires by Department and Month

    1. Create Matrix Report
    2. Data Source: Hire Employee Event
    3. Rows: Position > Organization (Department)
    4. Columns: Event Date > Month
    5. Measure: Count of Events
    6. Save As: New Hires by Department – Monthly

    Sub-Report 3: Terminations by Department and Month

    1. Create Matrix Report
    2. Data Source: Terminate Employee Event
    3. Rows: Position > Organization (Department)
    4. Columns: Event Date > Month
    5. Measure: Count of Events
    6. Save As: Terminations by Department – Monthly

    Step 2: Create the Composite Report

    1. Search for Create Custom Report
    2. Report Type: Composite
    3. Report Name: HR Monthly Scorecard
    4. Click OK

    Step 3: Add Sub-Reports

    Click Add Sub-Report for each Matrix Report you created.

    Sub-Report 1: Headcount by Department – Monthly

    Sub-Report 2: New Hires by Department – Monthly

    Sub-Report 3: Terminations by Department – Monthly

    Step 4: Align Sub-Reports

    Alignment ensures data from different sub-reports lines up correctly.

    Align By:

    • Rows: Department (common dimension across all sub-reports)
    • Columns: Month (common time dimension)

    Result: All three metrics display side-by-side for each department and month.

    Step 5: Add Composite Calculations

    Composite Calculations perform math across sub-reports.

    Calculation: Turnover Rate

    Formula: (Terminations ÷ Average Headcount) × 100

    Configuration:

    1. Click Add Calculation
    2. Calculation Name: Turnover Rate
    3. Formula Type: Custom
    4. Formula:text(Sub-Report[Terminations].Measure / ((Sub-Report[Headcount].Measure + Sub-Report[Headcount].Measure.PriorPeriod) / 2)) * 100

    What This Does:

    • Divides terminations by average headcount (current month + prior month ÷ 2)
    • Multiplies by 100 to get percentage
    • Displays as new row in the composite report

    Calculation: Net Headcount Change

    Formula: Hires – Terminations

    Configuration:

    textSub-Report[New Hires].Measure - Sub-Report[Terminations].Measure

    Step 6: Format the Report

    Add Section Headers:

    • Section 1: Headcount Metrics
    • Section 2: Movement Metrics
    • Section 3: Turnover Analysis

    Conditional Formatting:

    • Turnover Rate > 5%: Red (concerning)
    • Turnover Rate 3-5%: Yellow (monitor)
    • Turnover Rate < 3%: Green (healthy)

    Number Formatting:

    • Headcount: Whole numbers (no decimals)
    • Turnover Rate: One decimal place with % symbol (e.g., 3.2%)

    Step 7: Test and Validate

    Run the composite report.

    Validation Checks:

    • Do headcount numbers match your HRIS records?
    • Do new hires + terminations align with HR transaction logs?
    • Does turnover calculation make sense? (formula working correctly?)
    • Are all departments showing data? (check for alignment issues)

    Common Issues:

    • Misaligned departments: Sub-reports use different organization hierarchies. Standardize to Supervisory Organizations.
    • Missing time periods: One sub-report has data for January, another doesn’t. Add zero-value handling.

    Advanced Techniques: Calculated Fields

    Calculated Fields let you create custom formulas and logic within reports.

    When to Use Calculated Fields

    Scenario 1: Custom Tenure Calculation

    Need: Show employee tenure in “Years.Months” format (e.g., 3.5 years = 3 years, 6 months)

    Advanced Report Column: Tenure (Calculated Field)

    Formula:

    textDATEDIFF(Hire Date, Today, "years") + "." + MOD(DATEDIFF(Hire Date, Today, "months"), 12)

    Result: Employee hired March 1, 2022 shows “3.9” (3 years, 9 months as of Dec 2025)

    Scenario 2: Compensation Ratio (Compa-Ratio)

    Need: Compare employee salary to midpoint of their pay grade

    Matrix Report Measure: Compa-Ratio (Calculated Field)

    Formula:

    text(Annual Salary / Compensation Grade Midpoint) * 100

    Result: Employee earning $90K in grade with $100K midpoint shows 90% (below midpoint)

    Scenario 3: Conditional Text Labels

    Need: Tag employees as “New Hire”, “Tenured”, or “Long-Term” based on tenure

    Advanced Report Column: Tenure Category (Calculated Field)

    Formula:

    textIF(Tenure < 1, "New Hire",
   IF(Tenure >= 1 AND Tenure < 5, "Tenured",
      "Long-Term"))

    Result:

    • Employee with 6 months tenure: “New Hire”
    • Employee with 3 years tenure: “Tenured”
    • Employee with 8 years tenure: “Long-Term”

    Creating a Calculated Field

    1. From your Custom Report editor, click Columns tab
    2. Click Add > Calculated Field
    3. Field Name: Tenure Category
    4. Field Type: Text (or Number, Date, depending on formula output)
    5. Formula: Enter your formula using Workday formula syntax
    6. Available Functions:
      • DATEDIFF (date arithmetic)
      • IF/THEN/ELSE (conditional logic)
      • SUM, AVG, COUNT (aggregations – Matrix only)
      • CONCAT (text concatenation)
      • ROUND, CEILING, FLOOR (number formatting)
    7. Click Validate to check formula syntax
    8. Click OK to save

    Report Performance Optimization

    Why Report Performance Matters

    Slow reports frustrate users, time out during scheduled runs, and consume system resources.

    Performance Best Practices

    1. Filter Early, Filter Often

    Bad: Pull all 50,000 workers, then filter in Excel

    Good: Filter to active workers in last 6 months (reduces dataset to 2,000 records)

    How:

    • Add Worker Status = Active filter
    • Add date range filters (Hire Date, As of Date)
    • Use Prompts to let users narrow scope

    2. Limit Columns in Advanced Reports

    Bad: Include 40 fields “just in case”

    Good: Include only fields users actually need (10-15 columns max)

    Why: Each column adds processing time and data retrieval overhead.

    3. Use Summarize Detail Rows in Advanced Reports

    Scenario: You need totals by department, not every individual employee.

    Solution: Enable Summarize Detail Rows in Sort tab

    Result: Report aggregates data automatically (like a Matrix), runs faster than full detail list.

    4. Avoid Cross-Business Object Relationships When Possible

    Bad: Advanced Report pulling from Workers + Positions + Compensation + Benefits (4 objects)

    Good: Use Matrix Report with single business object, or Composite to separate concerns

    Why: Cross-object joins slow down queries significantly.

    5. Schedule Large Reports to Run Off-Hours

    Scenario: Monthly headcount report with 3 years of historical data (slow)

    Solution:

    1. Navigate to Edit Custom Report
    2. Configure Schedule
    3. Run at 2:00 AM when system load is low
    4. Deliver via email or save to shared folder

    6. Use Data Sources Wisely

    For Historical Trending: Use Snapshot-based Data Sources (Workers – Snapshot) instead of live Workers object

    Why: Snapshots are pre-aggregated and optimized for time-series analysis.

    Common Mistakes and How to Avoid Them

    Mistake 1: Using Advanced Report When Matrix Is Better

    Scenario: Request is “Show me headcount by department”

    What People Do: Build Advanced Report listing all employees, export to Excel, create pivot table

    What They Should Do: Build Matrix Report with Department as Row, Count of Workers as Measure

    Impact: 10 minutes in Excel becomes 30 seconds in Workday.

    Mistake 2: Too Many Calculated Fields in One Report

    Problem: Report has 15 calculated fields with nested IF statements and cross-field references.

    Impact: Report takes 5 minutes to run, times out in production.

    Solution:

    • Move complex calculations to Business Object Calculated Fields (reusable across reports)
    • Simplify formulas (break complex logic into multiple simpler fields)
    • Use Composite Reports to separate calculations across sub-reports

    Mistake 3: Not Sharing Reports with Appropriate Security

    Problem: You built a great report, but users can’t find it or don’t have permission to run it.

    Solution:

    • Share report with Security Groups (not individual users)
    • Grant appropriate permissions:
      • View: Users can run and view results
      • Modify: Users can edit the report definition (usually admins only)
    • Add report to relevant Dashboard or Report Category for discoverability

    Mistake 4: Hard-Coding Filters Instead of Using Prompts

    Problem: Report filters to “Hire Date between Jan 1, 2025 and March 31, 2025” (hard-coded)

    Impact: Report is useful for Q1 2025 only. Next quarter, you have to edit and update the report.

    Solution: Use Prompts

    • Add Start Date prompt
    • Add End Date prompt
    • Users can run report for any date range without editing definition

    Mistake 5: No Testing with Large Data Sets

    Problem: Report works great in test tenant with 100 employees. In production with 50,000 employees, it times out.

    Solution:

    • Test in Sandbox with production-like data volumes
    • Run performance checks before deploying
    • Add filters to limit data scope if needed

    Real-World Report Examples

    Example 1: Compensation Analysis Report (Advanced)

    Business Need: HR needs list of all employees with compensation below market midpoint for their pay grade.

    Report Type: Advanced Report

    Data Source: Workers

    Columns:

    • Employee Name
    • Employee ID
    • Job Profile
    • Compensation Grade
    • Annual Salary
    • Compensation Grade Midpoint (reference field)
    • Compa-Ratio (calculated: Salary ÷ Midpoint × 100)
    • Variance from Midpoint (calculated: Salary – Midpoint)

    Filter:

    • Worker Status = Active
    • Compa-Ratio < 90% (below market)

    Sorting: Compa-Ratio ascending (lowest paid first)

    Use Case: Annual compensation review to identify underpaid employees.

    Example 2: Termination Trend Analysis (Matrix)

    Business Need: Leadership wants to see termination trends over the past 12 months by department.

    Report Type: Matrix Report

    Data Source: Terminate Employee Event

    Rows: Organization (Department)

    Columns: Event Date > Month

    Measure: Count of Terminations

    Filter: Event Date is within the last 12 months

    Chart: Line chart showing termination trend by department

    Use Case: Monthly leadership review to identify retention issues.

    Example 3: Executive HR Dashboard (Composite)

    Business Need: CEO wants single-page HR scorecard showing headcount, hiring, turnover, and diversity metrics.

    Report Type: Composite Report

    Sub-Reports:

    1. Headcount Trend (Matrix)

    • Rows: Time Period (Month)
    • Measure: Count of Active Workers

    2. Hiring by Source (Matrix)

    • Rows: Recruiting Source
    • Measure: Count of Hires

    3. Turnover Rate (Matrix)

    • Rows: Department
    • Columns: Month
    • Measure: Termination Count
    • Composite Calculation: Turnover % = (Terms ÷ Avg Headcount) × 100

    4. Diversity Metrics (Matrix)

    • Rows: Gender
    • Columns: Job Level
    • Measure: Count of Workers

    Alignment: By Time Period (Month)

    Use Case: Monthly executive briefing, CEO board presentation.

    Your Report Type Cheat Sheet

    QuestionReport TypeExample
    Need a list of individual records?Advanced“Show me all new hires in Q1”
    Need to aggregate across 1-2 dimensions?Matrix“Headcount by dept and location”
    Need to combine multiple metrics?Composite“HR scorecard: headcount, hires, terms, turnover”
    Need detailed transaction history?Advanced“All compensation changes in 2024”
    Need trend analysis over time?Matrix“Monthly hiring trend by department”
    Need pivot table / crosstab?Matrix“Average salary by job level and location”
    Need executive dashboard with 4-5 KPIs?Composite“Finance scorecard: budget, actuals, variance, forecast”
    Need to export for integration/EIB?Advanced“All active workers with full demographic data”
    Need drillable interactive analysis?Matrix“Headcount by org (click to see employees)”

    What You’ve Learned

    You now understand:

    ✅ The three core Workday report types and when to use each

    ✅ How to build Advanced Reports for detailed lists and transaction logs

    ✅ How to build Matrix Reports for aggregations, pivots, and trends

    ✅ How to build Composite Reports for multi-metric dashboards

    ✅ How to use Calculated Fields for custom formulas and logic

    ✅ Performance optimization techniques to keep reports fast

    ✅ Common mistakes to avoid and best practices to follow

    The difference between a junior and senior Workday professional isn’t knowing how to build reports—it’s knowing which report type to build for each business need.

    Choose wisely. Build efficiently. Deliver insights, not just data.

  • Designing a Trusted Reporting Layer in Workday

    Why a “reporting layer” matters

    A trusted reporting layer in Workday is less about flashy dashboards and more about shared logic: one set of calculated fields and patterns that HR and Finance reuse across hundreds of reports, scorecards and integrations. Without this layer, each report writer re‑implements logic (tenure, FTE, headcount, comp metrics, margins), leading to conflicting numbers and low trust.​

    Calculated fields are the engine of that layer: they turn raw Workday data into analytics‑ready metrics without custom code.​

    Governance basics for calculated fields

    Before patterns, there needs to be discipline. Key governance practices:

    • Create global fields only when reusable
      • Use tenant‑wide calculated fields for metrics you know will appear in many reports (tenure, age, FTE, total comp, margin).​
      • Keep one‑off logic as report‑specific calculated fields to avoid polluting the global namespace.​
    • Name and document clearly
      • Use descriptive names like HR_Tenure_Years, FIN_Project_Gross_Margin_Pct, and store purpose, formula and owner in a simple catalog.​
    • Keep formulas as simple as possible
      • Break complex logic into smaller helper fields instead of one giant IF/CASE chain; this improves maintainability and performance.​

    This governance is what turns calculated fields from “sprawl” into a coherent reporting layer.​

    Core HR calculated field patterns

    These HR patterns appear in almost every serious tenant; making them global and standard is what builds trust.

    1. Tenure and service metrics
      • Fields like “Tenure in Years”, “Tenure Band” (0–1, 1–3, 3–5, 5+), and “Service Date for Benefits” based on hire/rehire dates and worker history.​
      • Used for attrition analysis, promotion eligibility, benefits, and career-path analytics.
    2. Headcount and FTE flags
      • Boolean fields like “Is Headcount”, “Is Active Employee”, “Is Contingent Worker”, and numeric “FTE Value” derived from standard hours and job data.​
      • These underpin headcount, FTE, and span-of-control reporting across HR and Finance.
    3. Demographic and cohort bucketing
      • Age buckets, generation labels, service bands, job‑level buckets using IF/CASE logic on age, service and job profile.​
      • These fuel diversity, equity and inclusion dashboards and workforce planning views.
    4. Compensation rollups
      • “Annualized Base Pay”, “Total Target Cash”, “Total Rewards Value” that aggregate multiple comp components with date‑aware logic.​

    Standardizing these HR fields ensures everyone slices workforce data on the same definitions.​

    Core Finance calculated field patterns

    For Finance, calculated fields often sit on journals, ledger, spend, revenue and project business objects.

    1. Normalized amount and currency
      • Fields that convert transaction or ledger amounts into a single reporting currency using rate tables, so analytics do not re‑implement conversion.​
    2. Account and Worktag groupings
      • Text fields that map detailed accounts/Worktags into reporting buckets (“Opex vs COGS vs Capex”, “Travel vs Marketing vs IT”) for P&L and cost analytics.​
    3. Margin and profitability metrics
      • Project or contract‑level gross margin %, contribution margin, and variance metrics built from revenue and cost measures.​
    4. Period‑aware flags
      • “Is Current Month”, “Is QTD”, “Is YTD” booleans based on accounting date to simplify time-bucket reporting.​

    These fields let you reuse Finance logic across GL reports, revenue dashboards, project views and even Prism datasets.​

    Reusable expression patterns that work everywhere

    Across HR and Finance, a handful of formula types show up repeatedly:

    • Date difference and banding
      • Use date difference to derive age, tenure, time-in-role, then wrap in IF/CASE logic for buckets.​
    • Lookup Related Value instead of nested IFs
      • Pull attributes (for example, region, cost bucket, leadership area) from related objects rather than hard‑coding lists.​
    • Boolean flags as building blocks
      • Create small true/false fields (is active, is restricted country, is bonus eligible) and reuse them instead of re‑expressing logic.​
    • Aggregate‑then‑derive patterns
      • Aggregate transaction-level data (sum, count, average) by worker, project, cost center, then derive ratios or scores from those aggregates.​

    These patterns keep formulas clear and reusable, which is essential for a trusted layer.​

    Performance and scalability considerations

    A reporting layer that times out is not trusted. Performance patterns:

    • Use report-level fields for one-offs
      • If logic is needed in a single heavy report, keep it report-specific to avoid cluttering tenant‑wide fields and indexes.​​
    • Evaluate at extract and avoid over-broad data sources
      • For large datasets, choose “evaluate at extract” and avoid “All Workers” or giant data sources where narrower ones exist.​
    • Refactor expensive CFs
      • Replace repeated date arithmetic or nested IF chains with pre‑computed helper fields; watch run-times and simplify hot spots.​
    • Regular clean-up and catalog reviews
      • Use reports to find unused or duplicate calculated fields and retire them on a schedule.​

    Designing for performance is as important as getting the math right if you want leaders to rely on Workday for analytics.​

    A well‑designed reporting layer in Workday is ultimately a library of governed, reusable calculated fields shared between HR and Finance. When you standardize patterns for tenure, headcount, compensation, margins, buckets and time windows—then manage them like a product—Workday stops being a collection of one‑off reports and becomes a consistent analytics platform everyone can trust.

  • Discovery Boards That Executives Actually Use

    I built my first Workday Discovery Board with genuine excitement.

    It had everything: KPI cards showing headcount trends, a beautiful waterfall chart displaying hiring pipeline, color-coded heat maps showing turnover by department, and interactive drill-downs into every metric.

    I spent three days perfecting it. The visualizations were stunning. The data was accurate. The interactivity was smooth.

    I shared it with the CFO.

    She opened it once. Never looked at it again.

    Two weeks later, I found her reviewing a spreadsheet someone had exported from a basic Workday report. The spreadsheet had pivot tables and ugly charts, but she used it every Monday morning.

    That is when I learned the hard lesson: Beautiful dashboards mean nothing if executives do not actually use them.

    Over the past five years, I have built Discovery Boards across dozens of Workday tenants. I have watched executives ignore gorgeous dashboards while repeatedly asking for the same basic reports via email.

    But I have also seen Discovery Boards become indispensable tools that executives check daily before their first meeting.

    The difference is not the visualization quality or the data complexity. The difference is understanding what executives actually need versus what we think they need.

    This guide will show you how to build Discovery Boards that executives actually use, based on real implementations where adoption exceeded 80%.

    Why Most Discovery Boards Fail

    Before we discuss what works, understand why most Discovery Boards fail.

    The Three Failure Patterns

    Failure Pattern 1: The Dashboard Museum

    You build a comprehensive Discovery Board with 15 sheets, 47 visualizations, and every possible metric the executive might need.

    The executive opens it once, gets overwhelmed by the sheer volume of information, and never returns.

    They go back to asking their assistant to pull specific numbers via email because it is faster than hunting through your 15-sheet dashboard.​

    Failure Pattern 2: The Beautiful But Useless Dashboard

    You create stunning visualizations with perfect color schemes, elegant transitions, and impressive interactivity.

    The executive looks at it and says: “This is beautiful. But I still cannot answer my question: Which departments are over budget on contractor spend?”

    Your dashboard shows aggregate metrics and trends. It does not answer their specific decision-making questions.

    Failure Pattern 3: The Stale Data Problem

    You build a Discovery Board that requires manual data refresh or uses data sources that update weekly.

    The executive checks it Monday morning to prepare for their leadership meeting. The data is from last Thursday. They make a comment based on your dashboard. Someone corrects them with more recent data.

    They never trust your dashboard again.

    The Root Cause

    All three failures stem from the same problem: You built the dashboard for yourself, not for the executive.

    You built what you thought was impressive. What demonstrated your Workday skills. What showcased Discovery Board capabilities.

    You did not build what the executive actually needs to make decisions on Tuesday morning.

    Understanding What Executives Actually Need

    Executives do not need dashboards. They need answers to specific recurring questions.

    The Five Executive Question Types

    Every executive question falls into one of five categories:

    Question Type 1: Status Check (“Where are we right now?”)

    Examples:

    • What is our current headcount?
    • How many open positions do we have?
    • What is our month-to-date spending versus budget?

    What they need: One number. Current state. Updated in real-time or near real-time.

    What they do NOT need: Historical trends, departmental breakdowns, year-over-year comparisons (unless they specifically ask).

    Question Type 2: Trend Detection (“Are we moving in the right direction?”)

    Examples:

    • Is turnover increasing or decreasing?
    • Are we filling positions faster or slower than last quarter?
    • Is our compensation spend trending toward budget or exceeding it?

    What they need: Simple directional indicator (up, down, flat). Trend line over relevant time period (usually last 3-6 months).

    What they do NOT need: Statistical significance tests, detailed breakdowns, multiple trend lines on the same chart.

    Question Type 3: Problem Identification (“Where are the issues?”)

    Examples:

    • Which departments have the highest turnover?
    • Which roles are hardest to fill?
    • Where are we overspending on contractors?

    What they need: Ranked list. Top 5 or top 10. Clear identification of where to focus attention.

    What they do NOT need: Complete list of all departments, roles, or cost centers. They want to know the problems, not the successes.

    Question Type 4: Comparison (“How do we compare?”)

    Examples:

    • Which department has the highest span of control?
    • How does Q4 hiring compare to Q3?
    • Which business unit is most efficient on cost per hire?

    What they need: Side-by-side comparison. Clear winner/loser identification. Context for whether the difference matters.

    What they do NOT need: Every possible comparison. Just the comparisons that drive decisions.

    Question Type 5: Deep Dive (“Tell me more about this specific thing”)

    Examples:

    • Show me everyone who terminated in Engineering last quarter.
    • Break down contractor spend by hiring manager.
    • What is driving the turnover spike in the Dallas office?

    What they need: Drill-down capability from summary to detail. Ability to filter and explore.

    What they do NOT need: This level of detail on the main dashboard. This is where interactive drill-through becomes valuable.

    The Executive Attention Span Reality

    Executives spend an average of 90 seconds on a dashboard before moving to their next task.

    If your Discovery Board cannot answer their primary question in 90 seconds, they will not use it.

    This means:

    • One primary insight per sheet (not 10 vizzes per sheet)​
    • Three to five sheets maximum (not 15 sheets)
    • Clear hierarchy of information (most important at top left)
    • Minimal scrolling (fits on one screen without vertical scroll)

    The Discovery Board Framework That Actually Works

    Here is the framework that consistently achieves 80% or higher executive adoption.

    The One-Page, Five-Number Rule

    Your Discovery Board should answer five specific questions on one visible page (no scrolling required).

    Not five categories of questions. Five actual questions the executive asks repeatedly.

    Example: CHRO Discovery Board

    Question 1: What is our current headcount?
    Visualization: KPI card showing total headcount with trend indicator​

    Question 2: Are we filling positions faster or slower?
    Visualization: KPI card showing average days to fill with month-over-month comparison

    Question 3: Which departments have the highest turnover?
    Visualization: Horizontal bar chart showing top 5 departments by turnover rate​

    Question 4: How is our diversity representation trending?
    Visualization: Line chart showing diversity percentage over last 12 months​

    Question 5: Where are we overspending on contractors?
    Visualization: Heat map showing contractor spend by department with budget comparison​

    Five numbers. One page. Answers the five questions the CHRO asks every Monday morning.

    The Three-Sheet Maximum

    If you need more than five metrics, use sheets (tabs) to organize by decision type, not by data category.​

    Sheet 1: “At a Glance”

    • Five most important metrics
    • What the executive checks first thing Monday morning
    • KPI cards and simple bar charts only

    Sheet 2: “Problem Areas”

    • Metrics highlighting issues requiring attention
    • Top 5 departments with highest turnover
    • Positions open longer than 90 days
    • Budget variances exceeding 10%

    Sheet 3: “Details” (Optional)

    • Drill-down capability for executives who want to explore
    • Interactive filters for department, location, time period
    • Detailed tables with worker-level data

    Most executives never go past Sheet 1. That is fine. Sheet 1 solves 90% of their needs.

    The Data Source Strategy

    Discovery Boards only support indexed data sources.​

    This is actually good news. It forces you to use performant data sources that load quickly.

    High-Performance Data Sources for Executive Dashboards:

    • Workers (indexed, fast)
    • Positions (indexed if Position Management enabled)
    • Organizations (indexed, fast)
    • Compensation (indexed for current compensation)
    • Recruiting (indexed for active requisitions)

    Data Sources to Avoid:

    • Worker History (not indexed, slow for large datasets)
    • All Benefit Elections (not indexed unless using current elections filter)
    • Custom data sources without indexing

    If your executive needs historical trend data, use Workday Prism Analytics for pre-aggregated data instead of pulling raw historical transactions in Discovery Boards.​

    The Refresh Strategy

    Executives need current data, not yesterday’s data.

    Real-time data sources: Workers, Positions, Organizations update in real-time in Discovery Boards. These are safe for executive dashboards.

    Daily refresh data sources: Compensation, recruiting data may have slight delays. Document this clearly: “Data refreshed daily at 2 AM.”

    Manual refresh data sources: If you are using Prism Analytics or custom data sources, document the refresh schedule prominently: “Turnover data refreshed weekly on Mondays.”

    If the executive makes a decision based on stale data and gets corrected in a meeting, they will never trust your dashboard again.

    The Mobile-First Design

    Executives check dashboards on their phones more often than on their laptops.

    This means:

    • Visualizations must be readable on mobile screens
    • KPI cards work better than complex charts
    • Horizontal bar charts work better than vertical bar charts (easier to read on narrow screens)
    • Avoid tiny fonts and detailed tables

    Test your Discovery Board on a mobile device before sharing with executives. If you cannot read it easily on your phone, they will not use it.

    The Five Discovery Boards Executives Actually Use

    Based on implementations with 80% or higher adoption, here are five Discovery Board templates that consistently succeed.

    Discovery Board 1: Executive Headcount Dashboard (CHRO/CFO)

    Primary Purpose: Answer “Where is our headcount versus budget?”

    Sheet 1: Headcount at a Glance

    Metric 1: Total Headcount

    • Visualization: KPI card​
    • Shows: Current headcount with trend indicator (up/down from last month)
    • Data source: Workers (Active Status equals Active)

    Metric 2: Open Positions

    • Visualization: KPI card
    • Shows: Count of vacant positions with availability equals available
    • Data source: Positions (if Position Management enabled) or Requisitions

    Metric 3: Headcount vs Budget

    • Visualization: KPI card showing variance
    • Shows: Current headcount minus budgeted headcount, percentage variance
    • Data source: Workers + Budget data (may require Prism if budget in external system)

    Metric 4: Headcount by Department

    • Visualization: Horizontal bar chart​
    • Shows: Top 10 departments by headcount
    • Interactivity: Click to drill into department details

    Metric 5: Hiring Pipeline

    • Visualization: Waterfall chart​
    • Shows: Requisitions by status (Approved, Interviewing, Offer Extended, etc.)
    • Data source: Requisitions

    Sheet 2: Problem Areas

    Metric 6: Positions Open Over 90 Days

    • Visualization: Table
    • Shows: Position ID, Title, Department, Days Open, Recruiter
    • Data source: Positions or Requisitions with date filter

    Metric 7: Departments Over Budget

    • Visualization: Horizontal bar chart showing variance percentage
    • Shows: Departments where actual headcount exceeds budget by more than 10%

    Usage pattern: CHRO checks Sheet 1 every Monday morning before leadership meeting. CFO checks Metric 3 (Headcount vs Budget) daily during month-end close.

    Key success factor: Budget data integration. If budget lives in external system, use Prism to bring it into Workday for comparison.​

    Discovery Board 2: Turnover Analysis Dashboard (CHRO/HR Operations)

    Primary Purpose: Answer “Where are we losing people and why?”

    Sheet 1: Turnover at a Glance

    Metric 1: Monthly Turnover Rate

    • Visualization: KPI card
    • Shows: Turnover percentage for current month with comparison to previous month
    • Calculation: (Terminations this month ÷ Average headcount this month) × 100

    Metric 2: Voluntary vs Involuntary Turnover

    • Visualization: Two KPI cards side by side
    • Shows: Voluntary turnover rate and involuntary turnover rate separately
    • Critical distinction: Executives care more about voluntary turnover

    Metric 3: Turnover Trend

    • Visualization: Line chart​
    • Shows: Monthly turnover rate over last 12 months
    • Helps answer: Are we improving or declining?

    Metric 4: Turnover by Department

    • Visualization: Horizontal bar chart
    • Shows: Top 5 departments by turnover rate (not count, rate matters)
    • Sorted: Highest to lowest

    Metric 5: Turnover by Tenure

    • Visualization: Bar chart
    • Shows: Turnover distribution by tenure bands (0-6 months, 6-12 months, 1-2 years, 2-5 years, 5+ years)
    • Insight: High turnover in 0-6 months indicates onboarding problems

    Sheet 2: Termination Details

    Metric 6: Recent Terminations

    • Visualization: Table
    • Shows: Worker Name, Job, Department, Termination Date, Termination Reason, Manager
    • Filter: Last 30 days
    • Purpose: Drill-down for executives who want specifics

    Usage pattern: CHRO checks Sheet 1 weekly. HR Ops uses Sheet 2 daily for exit interview preparation.

    Key success factor: Accurate termination reason coding. If termination reasons are inconsistent or generic, the dashboard provides no actionable insight.

    Discovery Board 3: Recruiting Efficiency Dashboard (CHRO/VP Talent Acquisition)

    Primary Purpose: Answer “How effective is our recruiting process?”

    Sheet 1: Recruiting Efficiency

    Metric 1: Average Days to Fill

    • Visualization: KPI card
    • Shows: Average days from requisition approval to hire date, with trend indicator
    • Data source: Requisitions (Status equals Filled, effective date filter for recent hires)

    Metric 2: Open Requisitions

    • Visualization: KPI card
    • Shows: Count of requisitions with status equals Open
    • Context: Shows recruiting workload

    Metric 3: Hiring Pipeline by Stage

    • Visualization: Waterfall chart or horizontal bar chart​
    • Shows: Count of candidates by recruiting stage (Sourcing, Screening, Interviewing, Offer, etc.)
    • Insight: Identifies bottlenecks in recruiting process

    Metric 4: Requisitions by Age

    • Visualization: Bar chart
    • Shows: Count of open requisitions by age bands (0-30 days, 31-60 days, 61-90 days, 90+ days)
    • Insight: Identifies aging requisitions needing attention

    Metric 5: Time to Fill by Department

    • Visualization: Horizontal bar chart
    • Shows: Average days to fill by department
    • Sorted: Longest to shortest
    • Insight: Identifies departments with recruiting challenges

    Sheet 2: Problem Requisitions

    Metric 6: Requisitions Open Over 90 Days

    • Visualization: Table
    • Shows: Requisition ID, Job, Department, Hiring Manager, Days Open, Recruiter, Candidate Count
    • Purpose: Action list for recruiting leadership

    Usage pattern: VP Talent Acquisition checks Sheet 1 every Monday morning. Recruiting Ops uses Sheet 2 to prioritize aging requisitions.

    Key success factor: Accurate requisition status updates. If recruiters do not update candidate stages promptly, pipeline metrics are meaningless.

    Discovery Board 4: Compensation Analysis Dashboard (CHRO/CFO/Compensation Manager)

    Primary Purpose: Answer “Are we paying competitively and within budget?”

    Sheet 1: Compensation Overview

    Metric 1: Total Compensation Spend

    • Visualization: KPI card
    • Shows: Total annual compensation (base salary + bonuses) with budget comparison
    • Data source: Workers with current compensation

    Metric 2: Average Base Salary

    • Visualization: KPI card
    • Shows: Average base salary across organization with year-over-year comparison
    • Context: Helps track compensation inflation

    Metric 3: Compensation by Department

    • Visualization: Horizontal bar chart
    • Shows: Average compensation by department
    • Insight: Identifies compensation disparities across organization

    Metric 4: Compa-Ratio Distribution

    • Visualization: Bar chart or histogram
    • Shows: Count of workers by compa-ratio bands (Below 0.85, 0.85-0.95, 0.95-1.05, 1.05-1.15, Above 1.15)
    • Insight: Identifies workers paid below or above market range

    Metric 5: Compensation Spend vs Budget

    • Visualization: Waterfall chart showing variance​
    • Shows: Budgeted compensation, actual compensation, variance by category (base, bonus, equity)

    Sheet 2: Compensation Outliers

    Metric 6: Workers Below Market (Compa-Ratio Below 0.85)

    • Visualization: Table
    • Shows: Worker Name, Job, Department, Base Salary, Market Midpoint, Compa-Ratio
    • Purpose: Identifies retention risks

    Metric 7: Workers Above Market (Compa-Ratio Above 1.15)

    • Visualization: Table
    • Shows: Worker Name, Job, Department, Base Salary, Market Midpoint, Compa-Ratio
    • Purpose: Identifies budget optimization opportunities

    Usage pattern: CFO checks Metric 1 and Metric 5 weekly during budget cycles. CHRO checks Metric 4 monthly for equity analysis.

    Key success factor: Accurate job profile to compensation grade mappings. If jobs are not properly mapped to compensation grades, compa-ratio is meaningless.

    Discovery Board 5: Diversity & Inclusion Dashboard (CHRO/Chief Diversity Officer)

    Primary Purpose: Answer “How is our diversity representation changing?”

    Sheet 1: Diversity Overview

    Metric 1: Overall Diversity Representation

    • Visualization: KPI card showing percentage
    • Shows: Percentage of workforce from underrepresented groups with trend indicator
    • Definition: Clearly define what “underrepresented” means for your organization

    Metric 2: Diversity Trend

    • Visualization: Line chart​
    • Shows: Diversity representation percentage over last 24 months
    • Insight: Are we improving or declining?

    Metric 3: Diversity by Department

    • Visualization: Horizontal bar chart
    • Shows: Diversity representation percentage by department
    • Sorted: Lowest to highest (highlights departments needing attention)

    Metric 4: Diversity by Job Level

    • Visualization: Bar chart
    • Shows: Diversity representation by job level (Individual Contributor, Manager, Director, VP, Executive)
    • Insight: Pipeline representation at leadership levels

    Metric 5: Hiring Diversity

    • Visualization: KPI card
    • Shows: Percentage of new hires from underrepresented groups in last 90 days
    • Context: Leading indicator of future representation

    Sheet 2: Diversity Deep Dive

    Metric 6: Pay Equity Analysis

    • Visualization: Scatter plot​
    • Shows: Compensation by gender/ethnicity within same job profile
    • Purpose: Identify potential pay equity issues
    • Note: Use Workday’s delivered Pay Equity Discovery Board template as starting point​

    Usage pattern: Chief Diversity Officer checks Sheet 1 monthly for board reporting. CHRO checks Metric 5 (Hiring Diversity) monthly to validate recruiting effectiveness.

    Key success factor: Data quality and privacy. Diversity data must be accurate and voluntarily provided. Dashboard must comply with privacy regulations in your regions.

    Building Your Discovery Board: Step-by-Step

    Here is the practical implementation process.

    Step 1: Identify the Five Questions (30 minutes)

    Schedule a 30-minute meeting with the executive.

    Ask: “What are the five questions you find yourself asking repeatedly about [headcount/turnover/recruiting/compensation]?”

    Do not ask: “What metrics do you want to see?”

    Do not ask: “What would you like on a dashboard?”

    Ask about questions. Get specific questions. Write them down verbatim.

    If the executive says: “I want to know about turnover,” that is not specific enough.

    Probe: “When you think about turnover, what specific question are you trying to answer? Is it ‘Which departments have the highest turnover?’ or ‘Is turnover increasing or decreasing?’ or something else?”

    Get five specific questions. Write them down. Confirm understanding.

    Step 2: Design on Paper First (15 minutes)

    Do not open Workday yet.

    On paper or whiteboard, sketch how you would answer each of the five questions.

    For each question, choose the simplest visualization that answers it:

    • Status check question: KPI card
    • Trend question: Line chart
    • Problem identification question: Bar chart (sorted, top 5 or top 10)
    • Comparison question: Bar chart or table
    • Deep dive question: Table with filters

    Arrange the five visualizations on your paper. Most important (Question 1) goes top left. Least important (Question 5) goes bottom right.

    Show this sketch to the executive. Get confirmation before building anything.

    Step 3: Build in Workday Drive (60-90 minutes)

    Access Discovery Boards through Workday Drive.​​

    Create new Discovery Board:

    1. Click your profile menu
    2. Select Drive
    3. Click Add New
    4. Select Discovery Board​

    Build Sheet 1:

    1. Name the sheet clearly: “Headcount at a Glance” (not “Sheet 1”)
    2. Add your first visualization (drag data source, choose viz type)
    3. Configure the visualization to answer Question 1 specifically
    4. Repeat for visualizations 2-5
    5. Arrange visualizations to fit on one screen (no scrolling)

    Visualization best practices:

    • Use KPI cards for single numbers​
    • Use horizontal bar charts for rankings​
    • Use line charts for trends over time​
    • Enable drill-by and show details for interactivity​
    • Configure data labels for clarity

    Performance considerations:

    • Limit to 10 vizzes per sheet​
    • Use indexed data sources only​
    • Avoid complex calculations in visualizations
    • Test load time (should load in under 5 seconds)

    Step 4: Configure Security and Sharing

    Discovery Boards use Workday Drive sharing model.​

    Share with executives:

    1. Click Share button​
    2. Add executive as viewer (not editor unless they need to modify)
    3. Consider sharing with security group if multiple executives need access
    4. Discovery Boards respect Workday security model for data access​

    Important: Test security by viewing as the executive’s persona. Ensure they see the data you intend them to see.

    Step 5: Test with Executive (15 minutes)

    Schedule a brief screen share with the executive.

    Walk through the Discovery Board. For each visualization, explicitly state which question it answers.

    Ask: “Does this answer your question [restate their original question]?”

    If yes, move to next visualization.

    If no, ask: “What is missing?” or “What would make this more useful?”

    Take notes. Make adjustments.

    Step 6: Document and Train (30 minutes)

    Create a one-page guide:

    • How to access the Discovery Board (link to Drive location)
    • What each visualization shows
    • When data is refreshed
    • Who to contact with questions

    Send this guide with your initial share of the Discovery Board.

    Step 7: Monitor Adoption (Ongoing)

    Track whether the executive actually uses the Discovery Board:

    • Check view count in Drive (shows how often it is accessed)
    • Ask for feedback after two weeks: “Are you finding the dashboard useful?”
    • Watch for whether the executive still asks for the same data via email (if yes, the dashboard is not meeting their needs)

    If adoption is low, schedule a follow-up to understand why.

    Common Mistakes and How to Fix Them

    Mistake 1: Too Many Visualizations

    Symptom: Executive opens dashboard, looks overwhelmed, closes it.

    Fix: Remove visualizations. You need fewer metrics, not more. Start with three visualizations. Add more only if executive explicitly requests them.

    Mistake 2: Wrong Visualization Type

    Symptom: Executive says “I cannot tell what this is showing me.”

    Fix: Simplify visualization type. KPI cards and bar charts are almost always better than scatter plots, bubble charts, or complex combo charts.

    Mistake 3: No Clear Question Answered

    Symptom: Executive says “This is interesting, but I still need to [pull report/ask assistant for data].”

    Fix: Your dashboard is not answering their actual question. Go back to Step 1. Re-identify the specific question. Rebuild visualization to answer that question directly.

    Mistake 4: Data Does Not Match Other Reports

    Symptom: Executive says “This shows 523 workers, but the HR report shows 541. Which is right?”

    Fix: Document data source and filters explicitly. Add text box on dashboard explaining: “Active workers as of [date], excluding contractors and leave of absence.” Ensure definition matches other reports.

    Mistake 5: Stale Data

    Symptom: Executive makes comment based on dashboard. Gets corrected with newer data in meeting. Stops using dashboard.

    Fix: Document refresh schedule prominently. If data is not real-time, consider whether Discovery Board is right tool or if scheduled report would be better.

    When NOT to Use Discovery Boards

    Discovery Boards are not always the right solution.

    Use traditional reports instead when:

    • Executive needs data exported to Excel for manipulation
    • Executive needs detailed worker-level data (hundreds of rows)
    • Executive needs data that requires complex calculations not supported in Discovery Boards
    • Data security requirements are complex (Discovery Boards inherit Workday security but have limited customization)

    Use Workday Prism Analytics instead when:

    • Data comes from multiple systems (Workday + external data)
    • Historical trend analysis requires years of data
    • Advanced analytics or predictive modeling needed
    • Data volumes exceed Discovery Board performance capabilities​

    Measuring Success

    Track these metrics to evaluate Discovery Board adoption:

    Adoption metrics:

    • View count per week (from Drive analytics)
    • Number of executives actively using (viewed in last 7 days)
    • Reduction in ad-hoc report requests on same topics

    Value metrics:

    • Time saved on manual reporting (hours per week)
    • Executive satisfaction survey (1-10 scale: “Does this dashboard help you make better decisions?”)
    • Decision-making speed (time from question to answer reduced)

    Target benchmarks:

    • 80% of intended executives view dashboard weekly
    • 60% reduction in ad-hoc report requests on dashboard topics
    • Executive satisfaction score 8 or higher (out of 10)

    Conclusion: Less Is More

    The best Discovery Boards are not the most comprehensive. They are not the most visually impressive. They are not the ones that showcase every Discovery Board feature.

    The best Discovery Boards answer five specific questions on one page in 90 seconds.

    Start small. Five metrics. One page. One specific executive.

    Get that working. Get adoption above 80%. Get the executive checking it every Monday morning.

    Then build the next one.

    Your goal is not to build impressive dashboards. Your goal is to build dashboards that get used.

    Tell Me Your Experience

    What Discovery Boards have you built that executives actually use? What made them successful?

    What Discovery Boards did you build that nobody uses? What went wrong?

    Share your experiences in the comments. We learn best from each other’s real-world successes and failures.

  • Build a Trustworthy Workday Reporting Layer

    Why Workday Reporting Feels Harder Than It Should

    Workday’s reporting engine is powerful, but many tenants experience the same frustrations:

    • Opening a custom report reveals a long list of cryptic calculated fields.
    • Similar reports show slightly different numbers for the same metric.
    • HR and Finance keep exporting to Excel because they don’t fully trust Workday.​

    The problem usually isn’t the tool itself. It’s the absence of a deliberate reporting architecture. Reports have been built ad hoc, one request at a time, often by different people, with no shared standards. Over time, this creates a fragile, confusing reporting layer that is hard to maintain and even harder to trust.

    A better path is to treat reporting as its own design problem: build a clean layer on top of Workday’s data, with clear rules about sources, fields, security, and ownership.

    Start With a Small, Well-Defined Reporting Catalog

    Instead of hundreds of overlapping reports, aim for a small catalog of core reports that the business can rely on.

    Practical steps:

    • Identify the key recurring questions HR and Finance ask (headcount, movement, attrition, cost, recruiting funnel, etc.).
    • Map each question to one primary report or dashboard that should be considered the “source of truth”.
    • De-duplicate existing reports that try to answer the same question in slightly different ways.​

    This doesn’t mean you never build new reports; it means new reports fit into a structure instead of adding to chaos. People know which report to use for which decision, and you stop seeing multiple versions of “headcount” or “attrition” competing with each other.

    Use Core Data Sources and Delivered Reports Wisely

    Not all reports should start from scratch. Workday provides rich delivered data sources and standard reports that can be extended or reused.​

    Good practices include:

    • Prefer delivered data sources that are designed and maintained by Workday for core areas like workers, organisations, time, and financials.
    • Use standard reports as reference patterns: see how they join data and which filters they use.
    • Only build highly customised data sources when you have a clear, recurring need that standard ones cannot cover.

    Choosing the right data source and pattern up front makes reports simpler, faster, and more consistent. It also lowers the need for excessive calculated fields and complex logic later.

    Minimise and Simplify Calculated Fields

    Calculated fields are one of Workday’s superpowers—but also one of the easiest ways to create a messy reporting layer.​

    To keep them under control:

    • Use calculated fields only when necessary and document their purpose.
    • Prefer reusable, general calculated fields over one-off fields created inside a single report.
    • Avoid chaining long sequences of calculated fields where one depends on another several layers deep—this makes debugging difficult and can impact performance.

    The goal is a small, understandable library of calculations that everyone on the Workday team recognises and can support, rather than a new custom field for every request.

    Keep Report Design Lean and Focused

    A trustworthy reporting layer is not just about data accuracy; it’s also about usability and performance.

    Design reports to:

    • Answer a specific business question with a focused set of columns and filters.
    • Load quickly by limiting unnecessary fields and avoiding overly broad datasets.
    • Use prompts so users can control date ranges, organisations, or populations without requesting new reports.​

    For deeper analysis, it’s often better to start from a lean summary report and allow drill‑through than to build a single “everything” report with 100+ columns.

    Align Security With Reporting From the Start

    Security and reporting are tightly linked: a report that shows the right numbers to the wrong people is just as untrustworthy as a report with incorrect data.

    Key principles:

    • Design reports with role-based access in mind: HR, HRBPs, managers, Finance, executives, etc.
    • Ensure that report data respects existing domain security, supervisory org boundaries, and field-level restrictions.
    • Test how reports behave for different roles, not just for admins or HRIS users.​

    When security is aligned properly, business users stop asking for shadow exports “just to be safe” and start using Workday as their primary source.

    Establish Ownership, Standards, and Maintenance

    A clean reporting layer needs clear ownership and simple governance:

    • Assign owners (often HRIS, reporting, or analytics leads) for key reports and metric definitions.
    • Create lightweight standards for naming, filters, prompts, and layout.
    • Maintain a simple report catalog that explains what each core report is for, who owns it, and who should use it.​

    You don’t need heavy bureaucracy. A few shared conventions and a visible owner for each important report are enough to prevent the reporting layer from drifting into confusion again.

    Collaborate Across HR, Finance, and IT

    Workday reporting sits at the intersection of HR, Finance, and technology. A strong reporting layer is usually built by a cross-functional effort rather than by one team working alone.​

    Helpful collaboration patterns:

    • Regularly review key reports and metrics with HR and Finance stakeholders.
    • Agree on definitions (for example, what counts as headcount, turnover, internal move) and reflect these in report logic.
    • Align reporting priorities with broader analytics and planning initiatives.

    This alignment reduces the risk of each function building its own spreadsheets and unofficial metrics outside Workday.

    Do All of This Before You Reach for Prism

    Workday Prism Analytics and external BI tools are valuable when you truly need to blend multiple data sources at scale or build advanced analytics. But they don’t fix a messy core reporting layer inside Workday.​

    Before you invest in more tools:

    • Make sure your Workday core reporting is clean, governed, and trusted.
    • Use standard Workday reporting capabilities for the majority of operational and management needs.
    • Then, layer Prism or external BI where there is a clear, justified use case.

    A solid in‑tenant reporting layer reduces the amount of complexity you need to push into other platforms and keeps Workday at the centre of your HR and Finance data story.

    The Payoff: Trust and Time Back for Everyone

    A clean, trustworthy reporting layer changes how the organisation works:

    • Executives stop arguing over which report is correct and start making decisions.
    • Auditors and compliance teams find consistent answers quickly.
    • HR and Finance stop rebuilding the same extracts in Excel every month.
    • The Workday team spends less time firefighting report issues and more time improving analytics.​

    You don’t need Prism or a full data warehouse to get there. You need a thoughtful design for how reports are built, secured, owned, and used.

    Done well, Workday becomes the place where everyone from HR to Finance to leadership can go to get numbers they trust.

  • Stop Overusing Workday Composite Reports

    Stop Overusing Workday Composite Reports

    Composite Reports Everywhere: A Hidden Workday Problem

    If you’ve spent time in a mature Workday tenant, you have probably seen it: a library full of Composite Reports that are slow to run, hard to edit, and understood by only one or two people. Any time someone asks for a new slice of data, the default response seems to be, “Let’s build a Composite.”

    This pattern is common, especially in environments where reporting was treated as a “technical” activity instead of a core part of how HR and Finance work. Composite Reports absolutely have their place. But overusing them creates complexity, performance issues, and a real dependency on a small group of “report wizards.”

    The real skill in Workday reporting is not knowing how to build the most complex report. It is knowing which report type is the simplest, most sustainable way to answer a business question.

    A Quick Reminder: Workday Report Types in Plain Language

    Workday provides several report types, each suited to different needs.​

    • Simple reports
      Great for straightforward lists with basic filters. Think of them as quick views or ad-hoc extracts.​
    • Advanced reports
      Flexible, support calculated fields, joins, and richer filtering. Most custom reporting needs can be handled here.​
    • Matrix reports
      Excellent when you want cross-tab views—rows and columns—for comparisons such as headcount by location and time.​
    • Composite reports
      Designed for complex scenarios: combining multiple report results, multiple time periods, or different business objects into a single output.​

    Composite Reports are not “better” than other types; they are just more specialized. Treating them as the default option is like using a chainsaw to cut paper.

    Why Teams Overuse Composite Reports

    There are several reasons why Composite Reports become overused in Workday tenants:

    • Misunderstanding of report types.
      Many admins and analysts learn Composite Reports early and assume they are the “advanced” or “professional” choice for all complex needs.​
    • Copy-paste reporting culture.
      Instead of improving existing advanced or matrix reports, teams clone an old Composite and keep adding logic.​
    • Pressure to deliver quickly.
      When deadlines are tight, it can feel faster to “just throw everything into one Composite” rather than step back and design a simpler solution.
    • Lack of reporting strategy.
      Without clear guidelines on which report type to use when, every new request becomes a one-off decision.

    Over time, this leads to a reporting landscape that is powerful, but fragile: if the one person who understands all the Composite Reports leaves, the organization feels stuck.

    When a Composite Report Is the Right Choice

    Composite Reports are valuable when:

    • You truly need to combine multiple report results or data sources that are not easy to join in a single advanced report.
    • You must compare data across multiple time periods in one output.
    • You need more control over layout, formatting, or multi-section outputs than other report types provide.​

    Examples include:

    • Year-end audit reports that combine time, time off, and leave data into one view.
    • Complex financial statements that compare plan vs actual across multiple structures.
    • Executive-ready outputs where you want multiple sections, subreports, and formatted layouts.​

    In these cases, a Composite Report can save time and reduce manual work in Excel by bringing everything into one place.

    When Composite Reports Are Overkill

    However, many real-world reporting needs do not require a Composite. For example:

    • A monthly headcount trend by location or cost center.
    • A list of employees with a specific status and a few key attributes.
    • A time-off summary by department for a given period.​

    In these cases, an advanced report, sometimes combined with a calculated field or a matrix view, is usually enough. Overusing Composite Reports here can cause:

    • Performance issues.
      Composite Reports often run slower, especially when they reference multiple subreports and large datasets.​
    • Maintenance headaches.
      Debugging a problem inside a Composite with multiple subreports is much harder than fixing a single advanced report.
    • Lower adoption.
      If reports are slow, brittle, or confusingly named, HR and Finance users will avoid them and export data to spreadsheets instead.​

    A good rule of thumb: if an advanced or matrix report can answer the question, use that first.

    A Simple Decision Framework for Report Types

    To reduce Composite Report overuse, introduce a simple decision framework for your reporting team:

    1. Start with the question.
      What business question are we trying to answer? Who is the audience—HR, Finance, leadership?
    2. Try standard reports first.
      Check whether Workday already delivers a standard report that can be slightly filtered or adjusted.​
    3. Use advanced reports for most custom needs.
      If standard reports are not enough, design an advanced report with clear prompts, calculated fields, and security alignment.​
    4. Use matrix reports for comparisons.
      When the main value is comparing categories (e.g., departments vs months), consider a matrix report.​
    5. Reserve Composite for true multi-source or multi-period complexity.
      Only move to Composite when you genuinely need to combine multiple reports or time slices in ways other report types cannot handle.​

    This framework alone will prevent many unnecessary Composite Reports from being built.

    Designing Reports HR and Finance Will Actually Use

    Regardless of report type, the way your reports are designed determines whether HR and Finance teams will trust and use them:

    • Use prompts instead of hard-coded filters.
      Allow users to change date ranges, organizations, and other parameters without editing the report definition.​
    • Name reports clearly and consistently.
      Avoid names like “Composite_Report_3_Final_v2”. Use patterns such as “Headcount – Monthly Trend” or “Time Off Summary – By Department”.​
    • Align security early.
      Ensure the right people can run the report without raising access tickets every time.​
    • Document the logic.
      For any complex report, especially Composites, keep a brief design note describing inputs, filters, and key calculations.

    These practices make your reporting layer simpler and more resilient, even as your tenant grows in complexity.

    Cleaning Up an Existing Composite-Heavy Environment

    If your Workday tenant already has “Composite everywhere syndrome,” you can still improve things gradually:

    • Inventory existing reports.
      Identify Composite Reports in use and understand which ones are truly needed.​
    • Find candidates for simplification.
      Look for Composites that could be replaced by one or two advanced or matrix reports.
    • Refactor slowly, starting with high-impact reports.
      Focus first on the slowest, most frequently used reports; redesign them using simpler types where possible.
    • Educate your reporting community.
      Share your report type guidelines and run short sessions for HR, Finance, and admins on “choosing the right report type.”

    Over time, this reduces technical debt and makes it easier for new team members to manage Workday reporting.

    Composite Reports as Part of a Balanced Reporting Strategy

    Composite Reports are not the villain. They are a powerful tool in the Workday reporting toolbox. The problem is when they are treated as the only tool, or as a shortcut for every complex question.

    The goal is a balanced reporting strategy where:

    • Standard, simple, and advanced reports handle most day-to-day needs.
    • Matrix reports provide clear comparisons for HR and Finance leaders.
    • Composite Reports are reserved for genuinely complex, multi-source, or formatted outputs.

    When your team chooses report types intentionally, Workday reporting becomes faster, more maintainable, and more trusted. That’s a key step in simplifying Workday for HR and Finance.

  • You’re Using Workday Dashboards Wrong

    You’re Using Workday Dashboards Wrong

    Are You Using Workday Dashboards the Wrong Way?

    Workday dashboards are one of the most visible parts of your analytics experience. Leaders log in, see tiles and charts, and quickly decide whether they trust the system or not. Yet in many tenants, dashboards are treated as a dumping ground for every “important” report rather than as carefully designed decision tools.

    If your Workday dashboards are slow, cluttered, or ignored by HR and Finance leaders, the issue is rarely technical. It’s usually a design and intent problem: too many reports, not enough focus, and no clear story.

    Dashboards Are Not Just “Report Collections”

    A common pattern looks like this: a stakeholder asks for a dashboard, the team gathers a list of “key reports,” and all of them are added to a single page. Over time, more and more tiles appear, each corresponding to another custom report. Soon:

    • No one remembers which tile is truly important.
    • Different tiles show similar data with slight variations.
    • Performance slows because too many complex reports load at once.
    • Leaders stop clicking into details because they feel overwhelmed.

    In other words, the dashboard becomes a cluttered homepage instead of an analytical cockpit.

    A true Workday dashboard should be designed around a set of questions and decisions, not around a list of reports you happen to have.

    Start with Questions, Not Charts

    The most effective dashboards begin with a simple question: “What decisions does this person need to make, and how often?”

    For example, an HR leader might need to answer:

    • Are we on track with headcount and hiring?
    • Where are we seeing higher turnover or absenteeism?
    • Which departments need attention this month?

    A Finance leader might ask:

    • How are labour costs trending vs budget?
    • Which cost centres or companies need a closer look?
    • Where are there anomalies in overtime or allowances?

    Once you have the questions, you can design dashboard sections and tiles that align directly to those decisions instead of randomly combining reports.

    Designing Dashboards for Specific Roles

    Many Workday tenants have generic “HR Dashboard” or “Finance Dashboard” pages that try to serve everyone at once. A more effective approach is to build dashboards tailored to roles:

    • HR Director Dashboard – strategic view of headcount, hiring, turnover, and critical risks.
    • HR Operations Dashboard – focus on transactions, backlogs, SLA compliance, and data quality.
    • Finance Leader Dashboard – focus on labour costs, budget vs actuals, and key variances.
    • Talent Acquisition Dashboard – focus on pipeline health, time-to-fill, and recruiter performance.

    Each dashboard should contain a small number of high-value tiles, not every report you’ve ever built. This makes it easier for each role to understand what they are seeing and act on it.

    Less Is More: Curate Your Tiles

    A Workday dashboard with 6–10 well-designed tiles is usually more effective than one with 25 tiles. When curating content:

    • Prioritise metrics over raw lists.
      Use charts, KPIs, and summaries for the main view, and let users drill into detailed reports when needed.
    • Group related tiles.
      For example, group headcount, hires, and exits together, or labour cost and overtime together, so the story is clear.
    • Remove low-value tiles.
      If a tile is rarely opened or no longer used for decisions, retire it. Dashboards should evolve, not accumulate clutter.
    • Align with how often decisions are made.
      Monthly or quarterly metrics do not need daily prominence; daily operational metrics might.

    This curation step is often skipped but is critical for adoption: people are more likely to use a dashboard that respects their time and attention.

    Make Dashboards Actionable, Not Just Interesting

    Pretty charts that no one acts on do not justify the effort. For each tile or visual, ask:

    • What action could someone take based on this?
    • Does the dashboard make it easy to take that next step?

    Some practical tactics to increase actionability:

    • Link from tiles to relevant tasks or reports.
      For example, a tile showing “Open Requisitions Past SLA” should link directly to a detailed report where recruiters can triage them.
    • Use prompts and filters intelligently.
      Allow users to quickly switch organization, time period, or population without rebuilding the report.
    • Highlight thresholds and exceptions.
      Use visual cues (e.g., colours, bands, or markers) to show when a metric is outside the desired range.

    The goal is for leaders to move from “interesting chart” to “I know exactly what to do next” in as few clicks as possible.

    Performance and Maintenance: The Hidden Costs of Bad Dashboards

    Overloaded dashboards do more than just annoy users—they strain your system and your reporting team.

    • Performance issues
      Dashboards that load many complex advanced or composite reports at once can become slow, causing timeouts or long waits. Users quickly give up and export data to spreadsheets instead.
    • Maintenance overhead
      Each tile points to a report. When you need to change logic or fields, you may have to update multiple reports and tiles across several dashboards. Without a clear design, this becomes error-prone.
    • Version confusion
      Multiple tiles showing similar metrics using different report versions create disputes. Stakeholders argue about which tile is “correct” instead of focusing on the insight.

    Investing in a clean dashboard design now saves time and frustration later.

    A Practical Framework to Redesign Your Dashboards

    If you suspect your Workday dashboards are “report dumps,” you can redesign them with a simple framework:

    1. Pick one audience per dashboard.
      Decide exactly who this dashboard is for and what decisions they make.
    2. List their top 5–10 questions.
      Work with real users to understand what they truly need to see and how often.
    3. Map each question to 1–2 visuals.
      Choose charts, KPIs, or tables that answer each question directly.
    4. Limit total tiles and group them.
      Aim for a clean layout with logical sections and minimal scrolling.
    5. Connect tiles to actions.
      Ensure users can click through to more detailed reports or relevant tasks from key tiles.
    6. Measure usage and iterate.
      Monitor which tiles are used, gather feedback, and adjust periodically.

    This approach turns dashboards from static collections into living tools that improve over time.

    Educating HR and Finance on “Good Dashboard Use”

    Finally, dashboard success is not just about design; it is about user behaviour. Help HR and Finance leaders understand:

    • Which dashboard is “the source of truth” for a given topic.
    • How often they should review it (daily, weekly, monthly).
    • What actions they are expected to take based on what they see.
    • Where to go if they have questions or feedback on metrics.

    Short enablement sessions, quick Loom-style walkthroughs, or written guides can go a long way in increasing adoption and trust.

    When users see dashboards as trustworthy, focused tools rather than confusing walls of charts, they will log in more often—and rely on Workday rather than offline spreadsheets.

  • The Workday HR Reporting Playbook

    The Workday HR Reporting Playbook

    Every Workday tenant reaches the same point: the delivered reports are not enough, spreadsheets are multiplying, and leaders want real‑time answers to tough HR questions. Workday’s reporting stack – from Simple to Composite Reports, powered by Calculated Fields – is designed to solve exactly that, if you treat it like a reporting architecture instead of a random collection of custom reports.​

    This playbook walks through when to use each report type and which Calculated Fields almost every HR tenant should build.

    Know your Workday report types

    Workday offers multiple custom report types, each built on a Business Object such as Worker, Position, Organization or Job Application.​

    At a minimum, understand these:

    • Simple Reports
      • Best for basic lists on a single business object (for example, workers with key fields).
      • Limited filtering and no advanced joins, but quick to build and great for operational lists.​
    • Advanced Reports
      • Your main workhorse for HR analytics.
      • Support complex filters, multiple prompts, sub‑filters and usage of most Calculated Fields.​
    • Matrix Reports
      • Pivot‑style reports with row and column groupings, aggregations and charts.
      • Great for headcount by org, diversity metrics, or comp by grade and location.​
    • Composite Reports
      • Bring together multiple Matrix (and related) reports into one output for multi‑period or multi‑subject analytics.
      • Ideal for dashboards, trend analysis and cross‑domain insights (for example, headcount + turnover + internal movement).​​

    The rule of thumb:

    • Start with Simple for quick, one‑object lists.
    • Move to Advanced for “real” HR reporting.
    • Use Matrix when you want to slice and aggregate.
    • Use Composite when you want to tell a story across time or subject areas.​

    Design a layered reporting approach

    Instead of dozens of one‑off reports, design a layered approach:

    • Operational layer (Simple / Advanced)
      • Examples: “Active Workers”, “Open Positions”, “Pending Hires”, “Workers on Leave”.
      • Used daily by HR operations and HRBPs.​
    • Analytics layer (Advanced / Matrix)
      • Examples: “Headcount and FTE by Org”, “Turnover by Manager and Tenure”, “Comp by Grade and Gender”.​
    • Executive layer (Composite + Dashboards)
      • Executive dashboards built on Composite Reports combining key metrics and trends.
      • Examples: Workforce overview, diversity scorecard, HC cost and movement.​​

    By reusing the same core datasets as sub‑reports (Advanced/Matrix) inside Composite Reports, you keep logic consistent and easier to maintain.​

    Calculated Fields: your secret reporting weapon

    Calculated Fields (CFs) are where Workday reporting becomes powerful. They let you transform, derive and combine data without code.​​

    Common types include:

    • Date Calculations – tenure, age, days since event.
    • Text Fields – concatenated names, formatted IDs.
    • Boolean / Conditional – true/false flags like “Is Terminated?”, “Is Manager?”, “Is High Risk?”.
    • Lookup and Related Object – pull attributes from related business objects (for example, worker’s manager’s organization).
    • Aggregations – counts, sums, minima/maxima across related data.​​

    Think of Calculated Fields as your reusable logic library: build once and use across reports, dashboards and even integrations.​

    Essential HR calculated fields every tenant should have

    While specifics vary, most HR tenants benefit from a core set of Calculated Fields on the Worker and related objects. Examples:​

    • Worker Tenure
      • Business case: segment turnover, eligibility, and recognition.
      • CF type: Date difference between Hire Date (or Original Hire) and Current Date, expressed in years/months.
    • Age and Age Band
      • Business case: workforce demographics and eligibility (for certain benefits or policies).
      • CF type: Date difference between Birth Date and Current Date, plus a conditional field assigning bands (e.g., “<30”, “30–39”, etc.).
    • Headcount Flag
      • Business case: define what counts as “headcount” in your reports.
      • CF type: Boolean that returns “True” only for Active, non‑contingent workers meeting your criteria.
    • Termination Risk Window
      • Business case: track leavers by tenure or after certain events.
      • CF type: Conditional on Termination Date minus Hire Date or last event.
    • Manager Chain Attributes (for example, “Top‑Level Organization”, “Level‑2 Manager Name”)
      • Business case: slice reports cleanly by different leadership levels.
      • CF type: Related Business Object / Lookup fields walking up the supervisory hierarchy.
    • Diversity Attributes (normalized)
      • Business case: DEI reporting with consistent categories.
      • CF type: Text or Conditional to map raw demographic fields into standard buckets used in analytics.

    Each of these can be reused in Advanced, Matrix and Composite reports, which avoids re‑implementing logic in filters or Excel.​

    From Simple to Composite: practical HR examples

    To make the progression tangible, consider a common HR need: headcount and turnover by organization over time.

    • Step 1 – Simple Report
      • Build a “Workers – Current Snapshot” Simple report listing Active workers with org, job and location.​
    • Step 2 – Advanced Reports
      • Create an Advanced report “Headcount by Org and Month” using Effective Date prompts and your Headcount Flag CF.
      • Create another Advanced report “Terminations by Org and Month” using the terminations data source and a tenure CF.​
    • Step 3 – Matrix Reports
      • Convert each into a Matrix report to group by Org (rows) and Month (columns), with counts as measures.​
    • Step 4 – Composite Report
      • Build a Composite report that combines the two matrix reports into a single output with headcount, terms and turnover rate.
      • Use formatting and sections so leaders see a clean summary plus drill‑downs.​​

    Now you have a reusable HR analytics asset instead of ad‑hoc Excel snapshots. The same pattern works for internal mobility, learning impact or compensation analytics.​

    Security and performance: silent success factors

    Two often overlooked aspects of reporting success are report security and performance.

    • Report/Data Source Security
      • Ensure report writers have the right Report Writer and domain permissions, but limit access to sensitive data.​
      • Use Workday security to ensure managers see only their teams; avoid hard‑coding security filters into reports where possible.
    • Performance
      • Avoid unnecessary fields and prompts; each join and CF can add load time.
      • Use prompts for date ranges and organizations to reduce dataset size for big reports.
      • Where possible, reuse CFs instead of building “report‑specific” ones that duplicate logic.​

    Good security and performance make reports usable in real life – otherwise, people will export data and go back to spreadsheets.

    Building your HR reporting playbook

    Treat Workday reporting like a product with its own playbook:

    • Document core reports (Simple, Advanced, Matrix, Composite) and their purpose: who uses them, how often, for what decisions.​
    • Maintain a Calculated Field catalog with ownership, description and examples. This prevents duplication and confusion.​
    • Provide basic training for HRBPs and analysts on report types, prompts and how to export responsibly instead of rebuilding Excel every time.​​

    When you design HR reporting in Workday as an intentional architecture – moving from Simple to Composite reports, powered by a curated set of Calculated Fields – your tenant stops being just a transaction system and becomes a true analytics platform for people decisions.