DATA GOBLINS REPORT CHECKLIST

Version X.X - Update-in-Progress, March 2024

Use the below interactive checklist to follow-up on your Power BI Report:

Click the question mark (?) for a link to a reference document. This will be learn.microsoft.com documentation; if none are available, this may be a Data Goblins article, or another blog post reference.

Layout & Design

Report follows the 3/30/300 rule of data design ?

Choose a good color palette ?

Make and use a Power BI theme .json ?

Add a title (landing) page and/or appendix, faq, etc.

Label report objects clearly/consistently (i.e. in selection pane)

Set default sort on visuals ?

Set chart axes to start at 0 (unless explicitly not desired) ?

Check that font is consistent (size, family, format)

Accessibility

Set visual layer order & tab order ?

View & test the report on different screens, browsers, contexts

Check accessibility of contrast, colours & fonts ?

Testing and Performance

Set and test all interactions (cross-filtering, slicers, etc.) ?

Test all filters; view the report with different filter combinations

Eliminate unnecessary or redundant visuals ?

Check if 'Apply' buttons are needed for Slicers & Filter pane ?

Document testing cases, queries, methods & results ?

Test report performance with the performance analyzer ?

User Experience (UX)

Add links for users to report issues or submit requests/ideas

Disable visual headers if no drilldown/drillthrough needed ?

Enable modern visual headers ?

Enable personalize visuals if needed & users can use it ?

Synchronize slicers where necessary ?

Set interactions between visuals ?

Report Handover

Identify who will support the report & how ?

Set up version control for the .pbix ?

Training & Adoption material / methods have been made/shared ?

Group visuals (and re-name groups) in the selection pane

Save custom themes, images and visual files ?

REPORT DOCUMENTATION CHECKLIST

Documentation varies from project-to-project and team-to-team, but below are some things you can consider documenting for your report.

Report Documentation

Basic Info.: Name, SPOC, Location, Workspaces...

Purpose: Business questions/problems the report addresses

User segments: Intended audience and devices used

User stories: specific questions/needs of users

Design & UX intent: How the design addresses the purpose

Complexity: atypical features, macguyvered visuals, custom visuals...

Field lists: Fields used in the report... ?

Manual interventions & justifications (if any)

REPORT TRAINING CHECKLIST

Documentation varies from project-to-project and team-to-team, but below are some things you can consider documenting for your report.

Report Business Users

Give user groups a personal walkthrough of the report

Explain the kind of business questions the report answers

How to reset to default ?

How to subscribe & use subscriptions (that it's not a replacement for interactive reports) ?

How & when to use which export format (if enabled)

How & when to use comments (if enabled) ?

Report Interactions: Slicers ?

Report Interactions: The Filter Pane ?

Report Interactions: Buttons ?

Visual Interactions: Cross-filtering & Cross-highlighting ?

Report Interactions: Drill down and up ?

Report Interactions: Drillthrough ?

Report Interactions: Focus Mode / Full-screen ?

Report Interactions: Show as Table ?

Report Interactions: Personal Bookmarks ?

A Goblin warning:

Implementing and adopting Power BI/Fabric successfully isn't a small, one-person job! It takes a team of complimentary skills. Read more: A Letter from Klonk.