15.3 Discovery Boards

15.3 Discovery Boards

Quick Summary: Discovery Boards are Workday’s interactive visual analytics experience for exploring summarized data—especially Matrix report outputs—as charts, graphs, and related visuals. You create visuals, drive them with prompts, and apply filters so leaders can slice headcount and workforce metrics without exporting everything to a spreadsheet.

Task T67 closes the “presentation” side of Report Writer for HCM Core. After you can build Advanced reports (T57–T64), schedule them (T65), and design Matrix summaries (T66), Discovery Boards answer: how do business users explore the story visually?

What a Discovery Board Is

Purpose

A Discovery Board is a configurable analytics surface that presents interactive visuals built from Workday reporting data—classically Matrix report data sources. Consumers open the board, answer prompts, apply filters, and drill into visuals to understand patterns (headcount by org and job family, attrition slices, hiring funnels where data allows, and similar HCM stories).

Exam definition to memorize: Discovery Boards surface Matrix report data as interactive charts and visuals on a configurable analytics board—with prompts and filters, and often drillable paths into detail.

What Discovery Boards are not

Creating a Discovery Board Visual

High-level create flow

1. Prepare the data foundation — usually a well-designed Matrix report (row/column groupings, clean measures, sensible filters).
2. Open / create Discovery Board experience available in the tenant for authorized users.
3. Select the data / matrix source that feeds the visual.
4. Choose a visualization type (bar, column, pie, line, scorecard-style tiles—as offered in product).
5. Map dimensions and measures — what sits on axes, what is colored/sliced, what number is shown.
6. Arrange the board — multiple visuals can tell a multi-angle story (headcount + average tenure + openings).
7. Add prompts and filters for runtime control.
8. Validate with a realistic role account (Manager vs HR Partner vs CHRO see different populations).

 Matrix report (summarized HCM data)
        │
        ▼
 Discovery Board
   ├── Visual A: Headcount by Region (bar)
   ├── Visual B: Headcount by Job Family (pie)
   ├── Prompts: As of Date, Company
   └── Filters: Worker Type, Location Hierarchy
        │
        ▼
 Interactive exploration + drill to detail

Configuration scenario: Contoso people analytics builds a Matrix of active headcount by Region × Job Family Group. They create a Discovery Board with a stacked bar for regions and a pie for job family mix, both reading the same matrix foundation. HRBPs open the board Monday morning instead of waiting for a static PDF.

Design tips that show up as exam judgment calls

• Prefer clear measures — “Count of Active Workers” beats an unexplained calculated blob.
• Limit dimension explosion — boards with hundreds of tiny slices are unreadable.
• Align with matrix grain — do not expect a board to invent a measure the matrix never aggregated.
• Plan drill — if leaders will ask “who is in this bar?,” detail drill paths must exist on the underlying design.
• Name for business language — “Q3 Active Headcount Explorer,” not “RPT_MX_472_final_v9.”

Using Prompts on Discovery Boards

Why prompts matter

A prompt captures a runtime value from the consumer—Company, Supervisory Organization, as-of date, Region, Job Family Group—and uses it to scope the data. The same board definition serves many audiences without cloning a board per org.

Prompts on Discovery Boards follow the same reporting idea you learned for custom reports (T63): one definition, many parameter values. They are not the Scheduling Report task, not ownership transfer, and not a way to lock the report from edits.

Prompt vs schedule criteria (keep them straight)

Exam trap: “Primary purpose of a custom prompt” is still runtime filter/parameter input—whether on a report or experienced through a board—not scheduling, not PDF export, not edit locking.

Built-in vs custom prompt mindset

You already distinguish built-in prompts (delivered with certain data sources, often effective date / organization context) from custom prompts authors add. On boards, the practical exam skill is: identify that the board can be driven by prompts so consumers do not need a new matrix per company.

Applying Filters on Discovery Boards

Filters refine the live view

Filters on a Discovery Board further restrict which instances or categories appear during exploration. Examples:

• Worker Type = Employee (exclude contingent)
• Location Hierarchy under EMEA
• Exempt status
• Specific Cost Center hierarchy nodes

Filters work with prompts: a prompt might set Company = Acme US, while a filter temporarily hides contingent workers for a leadership conversation.

Filter design hygiene

1. Put always-true exclusions on the report/matrix definition so no consumer forgets them.
2. Expose audience-variable dimensions as prompts.
3. Leave ad-hoc exploration to board filters.
4. Remember security still filters rows—a board filter cannot reveal data the runner’s domains hide.

Configuration scenario: Northwind’s Discovery Board prompts for Region. During a store-ops review, the analyst applies a board filter Job Family = Store Associate to focus the charts. The underlying matrix still enforces Active workers only. A store manager with constrained security never sees other regions’ bars even if they try to clear filters.

Discovery Boards in the HCM Analytics Stack

 Advanced report          Matrix report           Discovery Board
 (detail lists)    →     (summaries)      →     (visual exploration)
        │                      │                        │
        └──────── schedules, sharing, domain security ──┘

Security and Sharing Reminders

Discovery Boards do not create a parallel security universe:

• Domain security still governs field and data visibility.
• Sharing / access still governs who can open the board or its source reports.
• Runner security still wins over “the designer could see everything.”
• Constrained roles still see only their population—empty charts can be correct, not broken.

Exam scenario: “User opens a board shared by an admin but sees fewer regions.” → Expected if the user’s constrained HR Partner scope is smaller. Sharing is not a data grant.

Common Confusions Table

Study Links

• T66: Build matrix rows/columns/measures first; boards visualize that work.
• T63: Prompt literacy transfers directly to board prompts.
• T64: Sharing and ownership affect who maintains source reports behind boards.
• T65: Some organizations still schedule source reports even when leaders primarily use boards.
• T69: Heavy visuals on slow matrices feel “broken”—performance is part of board success.

When a stem mentions interactive charts, visual dashboard, or Discovery Board with prompts and filters, choose Discovery Board—not Reorg, not Tenant Setup, not a security group.