Power BI Report Design Checklist
Power BI Report Design Checklist
Try looking at your reporting solution as an end user. The report should be easy to navigate,
easy to understand, it should have a professional look and feel, and it should support faster
and better data driven decision making.
☐ 3. You clearly highlighted the existence of interactive elements and how they should be
used (e.g. buttons, tooltips, drill downs, drill throughs)
☐ 4. You have clearly defined areas in your report page for navigation, filters, charts etc
☐ 5. You have clear titles for your visuals/charts
☐ 6. Your users can take different journeys from the moment they open the report,
depending on the type of insights they need at that time, how granular they want to
go etc
7. These journeys are easy to follow, and your end user can go from a very high level
KPI to a more granular page like drill through easily
Design Effectiveness
☐ 1. You used the color scheme from your company/customer branding guidelines
☐ 2. You used the logo from your company/customer in all pages
☐ 3. You maximized the report page area, without making it look cluttered
☐ 4. You were careful with the choice of colors, you only used vibrant colors to highlight
information (exceptions apply depending on your company branding)
☐ 5. You made sure you had enough space between visuals/shapes so that your report
doesn’t look cluttered
☐ 6. You formatted your charts/visuals and got rid of everything that is redundant e.g.
titles of Y and X axis, dark visual borders, background color, Y axis (in case you
used labels instead)
☐ 7. You made use of design elements like stock images and icons to give your end
users visual cues and to enhance report design
☐ 8. You made use of buttons formatting features to make them more user friendly (on
hover effects etc)
☐ 9. You made use of formatting options like conditional formatting to give context to the
figures you have in your report
☐ 10. You were mindful of the text formatting (size, font, bold/italic)
☐ 11. You made sure your metrics naming on visuals/charts are ok (measures used show
on tooltips and legends, make sure you have good naming conventions!)