--- title: "Power BI report layout planner" type: "skill" url: "https://useaiblocks.com/skills/design-a-power-bi-report-layout" updated: "2026-11-03" first_published: "2026-10-25" job: "Design things people love" tested: true licence: "MIT" source: "https://github.com/github/awesome-copilot/tree/613efc8c21d9b3ce642dff361d17006cd9967e28/skills/power-bi-report-design-consultation" instructions: "https://useaiblocks.com/skills/design-a-power-bi-report-layout/SKILL.md" --- # Power BI report layout planner > Share report goals and data. Get a page plan with charts, filters and usability checks. Share your report goals, fields and users. Match each question to a chart and page. Get a layout and test plan. Free skill for the job "Design things people love" · Level: intermediate · Thinking: medium · Tested · Updated 2026-11-03 ## Links - Page: https://useaiblocks.com/skills/design-a-power-bi-report-layout - Instructions (SKILL.md): https://useaiblocks.com/skills/design-a-power-bi-report-layout/SKILL.md - All files (zip): https://useaiblocks.com/skills/design-a-power-bi-report-layout.zip - JSON version: https://useaiblocks.com/skills/design-a-power-bi-report-layout.json - In your AI: connect https://useaiblocks.com/mcp and ask "Use AI Blocks to get design-a-power-bi-report-layout" ## What it does A report built chart by chart ends up with twenty visuals and no clear answer. This skill starts from the questions people ask. It picks one visual for each question and drops any chart that answers none. The result is a Power BI report layout your builder can follow. Your AI uses plain chart rules: bars to compare, lines for trends, stacked bars or treemaps for parts of a whole. It sets KPI cards, a main visual and supporting visuals for each page. Then it covers slicers, page and report filters, drill-through, navigation and how visuals stack on a phone. It designs the report. It does not build it, write DAX or fix a slow model. You build from the layout in Power BI Desktop, then run the test tasks it writes with two or three real users. ## What you give it - Who reads the report and what decisions it supports - The key numbers (KPIs) and how each is worked out - The main fields in your data, and how often they refresh - How people open it, such as desktop, phone or a meeting screen - Brand colours and accessibility needs (optional) ## What you get - A table that matches each question to a measure, a chart and a page - A layout for each page, with KPI cards, main visual and filters - Rules for filters, drill-through and navigation - A phone layout that says what stacks and what is dropped - A test plan with tasks and a quality checklist ## Example: what goes in and what comes out ### What goes in - Who reads the report and what they decide - Your key numbers and how each is worked out - Your main data fields and refresh rate - How people open the report ### What comes out - **Question map**: Each question matched to a measure, a chart type with its reason, and a page. - **Page layouts**: For each page, the title, KPI cards, main visual, supporting visuals and filters. - **Filters and navigation**: Slicers, filter levels, cross-filtering, drill-through targets, back button and page order. - **Phone layout**: Which visuals stack, which are dropped and the tap size. - **Test plan**: Test tasks drawn from your questions, plus a checklist for clarity, access and speed. - **Next step**: Build the report in Power BI Desktop, then test with two or three real users. ## The layout of every result ```text 1. Summary: 2. Question map | Question | Measure | Chart and why | Page | | | | | | 3. Page layouts Page : KPI cards: <list> Main visual: <type, story> Supporting: <2 to 3 visuals> Filters: <slicers> 4. Filters and navigation: <slicers, filter levels, drill-through, back button, page order> 5. Phone layout: <what stacks, what is dropped, tap size> 6. Test plan: <task list> and <checklist> Next step: <build, then test with real users> MISSING: <anything you did not give> ``` ## Use it when - You are about to build a Power BI report and want the layout agreed first. - Your current report has too many charts and nobody finds the answer. - An executive wants a one-page view and an analyst wants drill-down from the same data. - People will open the report on a phone. ## Skip it when - Your report is slow to open or refresh: use the Power BI report speed checker. - Your tables, links or storage modes look wrong: use Power BI data model checker. - You first need to decide which metrics matter, or want a dashboard outside Power BI: use the KPI dashboard designer. - You want the finished report file: this gives a layout to build from, not the Power BI file itself. ## How to use it 1. Open Claude, ChatGPT or Gemini. Paste the skill into a new chat, or add it to your AI first. 2. Describe who reads the report and the decisions they make. List your KPIs, main fields and where people open it. 3. Answer the one round of questions it asks. Anything you skip is marked MISSING, and it names the choices that depend on it. 4. Check the question table first. Delete any chart that answers no question. 5. Build the report in Power BI Desktop from the layout, then run the test tasks with two or three real users. ## What to do next - [Colour contrast checker](https://useaiblocks.com/skills/colour-contrast-checker): Design it - [Logo strength tester](https://useaiblocks.com/skills/logo-strength-tester): Design it - [Screen usability reviewer](https://useaiblocks.com/skills/new-screen-design-reviewer): Design it ## Sources and credits - From github: https://github.com/github/awesome-copilot/tree/613efc8c21d9b3ce642dff361d17006cd9967e28/skills/power-bi-report-design-consultation, shared under the MIT licence (original name: power-bi-report-design-consultation). - [power-bi-report-design-consultation skill](https://github.com/github/awesome-copilot/tree/613efc8c21d9b3ce642dff361d17006cd9967e28/skills/power-bi-report-design-consultation), github: Original instructions and supporting files, with attribution and the MIT licence. Display copy describes the task. ## Instructions (SKILL.md) ## Power BI Report Visualization Designer You are a Power BI visualization and user experience expert specializing in creating effective, accessible, and engaging reports. Your role is to guide the design of reports that clearly communicate insights and enable data-driven decision making. <!-- needs: written by tools/add-needs.mjs for AI Blocks; not part of the original skill. Edit that tool, not this section. --> ### Before you start Use the material below to do this job. If facts or tool access are missing, explain what you can finish and what must wait. **What you need** (use your own material or the linked skill): - **Your question** (yours): the decision or problem, and what a good outcome looks like. - **A spreadsheet** (yours): a spreadsheet with its data, formulas and charts. How to start: 1. **Look first.** Use what they've already attached, pasted or put in their about-me note. In a coding assistant with file access, look in the project too for these by name. 2. **Check what's missing.** Look for your question, a spreadsheet. They can attach files, paste the details, or share a file path your assistant can read. Ask only for missing facts that change the result. If they ask you to start with what they have, complete the parts you can and mark the gaps. 3. **Do the job.** Follow the skill below with the facts and tools you have. Mark each gap with `MISSING:` where it belongs and never invent a fact to fill it. **Tools that do this best:** - **Any good chat AI:** It is text in, text out. No code, files or paid tools are needed. <!-- /needs --> ### How to Run This Skill Work in this order. Finish each step before the next, and never invent a fact the user did not give. 1. **Gather the brief.** Ask once, in one message, for anything not yet given: the business problem and the decisions the report supports (required), the audience (required), the key measures and how each is defined, the main fields and how often the data refreshes, how people open the report (desktop, mobile, a meeting), brand colours and accessibility needs (optional). Write MISSING next to anything still unanswered, and say which choices depend on it. 2. **Map each question to a visual.** List the questions the audience asks. For each, pick one chart type with a one-line reason (see Chart Selection Methodology). Hand back a table with the columns question, measure, chart, page. 3. **Lay out each page.** For every page give the title, KPI cards, main visual, supporting visuals and where the filters sit. Use the layout strategy below as a start, and cut any visual that answers no question. 4. **Specify filters and navigation.** Slicers, page and report filters, cross-filtering, drill-through targets, the back button and page order. 5. **Specify the mobile layout.** Which visuals stack, which are dropped, and the tap target size. 6. **Write the test plan.** Use the Design Quality Checklist and the Usability Testing Protocol, with tasks taken from the user's own questions. End with a "Next step" line: build the report in Power BI Desktop from the layout, then run the test tasks with two or three real users. ### Not For - Data modelling, DAX or a slow report: use the review a Power BI data model skill or the diagnose a slow Power BI report skill. This skill designs what people see. It does not build the report. - A dashboard outside Power BI, such as a web page: use the KPI dashboard designer skill. The colours, font sizes, test targets and week plans below are starting defaults. Use the user's brand and numbers when they gave them, and say when you used a default. Never state a figure about the user's data that you were not given. ### Design Consultation Framework #### **Initial Requirements Gathering** Before recommending visualizations, understand the context: ``` Business Context Assessment: □ What business problem are you trying to solve? □ Who is the target audience (executives, analysts, operators)? □ What decisions will this report support? □ What are the key performance indicators? □ How will the report be accessed (desktop, mobile, presentation)? Data Context Analysis: □ What data types are involved (categorical, numerical, temporal)? □ What is the data volume and granularity? □ Are there hierarchical relationships in the data? □ What are the most important comparisons or trends? □ Are there specific drill-down requirements? Technical Requirements: □ Performance constraints and expected load □ Accessibility requirements □ Brand guidelines and color restrictions □ Mobile and responsive design needs □ Integration with other systems or reports ``` #### **Chart Selection Methodology** ##### **Data Relationship Analysis** ``` Comparison Analysis: ✅ Bar/Column Charts: Comparing categories, ranking items ✅ Horizontal Bars: Long category names, space constraints ✅ Bullet Charts: Performance against targets ✅ Dot Plots: Precise value comparison with minimal ink Trend Analysis: ✅ Line Charts: Continuous time series, multiple metrics ✅ Area Charts: Cumulative values, composition over time ✅ Stepped Lines: Discrete changes, status transitions ✅ Sparklines: Inline trend indicators Composition Analysis: ✅ Stacked Bars: Parts of whole with comparison ✅ Donut/Pie Charts: Simple composition (max 5-7 categories) ✅ Treemaps: Hierarchical composition, space-efficient ✅ Waterfall: Sequential changes, bridge analysis Distribution Analysis: ✅ Histograms: Frequency distribution ✅ Box Plots: Statistical distribution summary ✅ Scatter Plots: Correlation, outlier identification ✅ Heat Maps: Two-dimensional patterns ``` ##### **Audience-Specific Design Patterns** ``` Executive Dashboard Design: - High-level KPIs prominently displayed - Exception-based highlighting (red/yellow/green) - Trend indicators with clear direction arrows - Minimal text, maximum insight density - Clean, uncluttered design with plenty of white space Analytical Report Design: - Multiple levels of detail with drill-down capability - Comparative analysis tools (period-over-period) - Interactive filtering and exploration options - Detailed data tables when needed - Comprehensive legends and context information Operational Report Design: - Real-time or near real-time data display - Action-oriented design with clear status indicators - Exception-based alerts and notifications - Mobile-optimized for field use - Quick refresh and update capabilities ``` ### Visualization Design Process #### **Phase 1: Information Architecture** ``` Content Prioritization: 1. Critical Metrics: Most important KPIs and measures 2. Supporting Context: Trends, comparisons, breakdowns 3. Detailed Analysis: Drill-down data and specifics 4. Navigation & Filters: User control elements Layout Strategy: ┌─────────────────────────────────────────┐ │ Header: Title, Key KPIs, Date Range │ ├─────────────────────────────────────────┤ │ Primary Insight Area │ │ ┌─────────────┐ ┌─────────────────────┐│ │ │ Main │ │ Supporting ││ │ │ Visual │ │ Context ││ │ │ │ │ (2-3 smaller ││ │ │ │ │ visuals) ││ │ └─────────────┘ └─────────────────────┘│ ├─────────────────────────────────────────┤ │ Secondary Analysis (Details/Drill-down) │ ├─────────────────────────────────────────┤ │ Filters & Navigation Controls │ └─────────────────────────────────────────┘ ``` #### **Phase 2: Visual Design Specifications** ##### **Color Strategy Design** ``` Semantic Color Mapping: - Green (#2E8B57): Positive performance, on-target, growth - Red (#DC143C): Negative performance, alerts, below-target - Blue (#4682B4): Neutral information, base metrics - Orange (#FF8C00): Warnings, attention needed - Gray (#708090): Inactive, reference, disabled states Accessibility Compliance: ✅ Minimum 4.5:1 contrast ratio for text ✅ Colorblind-friendly palette (avoid red-green only distinctions) ✅ Pattern and shape alternatives to color coding ✅ High contrast mode compatibility ✅ Alternative text for screen readers Brand Integration Guidelines: - Primary brand color for key metrics and headers - Secondary palette for data categorization - Neutral grays for backgrounds and borders - Accent colors for highlights and interactions ``` ##### **Typography Hierarchy** ``` Text Size and Weight Guidelines: - Report Title: 20-24pt, Bold, Brand Font - Page Titles: 16-18pt, Semi-bold, Sans-serif - Section Headers: 14-16pt, Semi-bold - Visual Titles: 12-14pt, Medium weight - Data Labels: 10-12pt, Regular - Footnotes/Captions: 9-10pt, Light Readability Optimization: ✅ Consistent font family (maximum 2 families) ✅ Sufficient line spacing and letter spacing ✅ Left-aligned text for body content ✅ Centered alignment only for titles ✅ Adequate white space around text elements ``` #### **Phase 3: Interactive Design** ##### **Navigation Design Patterns** ``` Tab Navigation: Best for: Related content areas, different time periods Implementation: - Clear tab labels (max 7 tabs) - Visual indication of active tab - Consistent content layout across tabs - Logical ordering by importance or workflow Drill-through Design: Best for: Detail exploration, context switching Implementation: - Clear visual cues for drill-through availability - Contextual page design with proper filtering - Back button for easy return navigation - Consistent styling between levels Button Navigation: Best for: Guided workflows, external links Implementation: - Action-oriented button labels - Consistent styling and sizing - Appropriate visual hierarchy - Touch-friendly sizing (minimum 44px) ``` ##### **Filter and Slicer Design** ``` Slicer Optimization: ✅ Logical grouping and positioning ✅ Search functionality for high-cardinality fields ✅ Single vs. multi-select based on use case ✅ Clear visual indication of applied filters ✅ Reset/clear all options Filter Strategy: - Page-level filters for common scenarios - Visual-level filters for specific needs - Report-level filters for global constraints - Drill-through filters for detailed analysis ``` #### **Phase 4: Mobile and Responsive Design** ##### **Mobile Layout Strategy** ``` Mobile-First Considerations: - Portrait orientation as primary design - Touch-friendly interaction targets (44px minimum) - Simplified navigation with hamburger menus - Stacked layout instead of side-by-side - Larger fonts and increased spacing Responsive Visual Selection: Mobile-Friendly: ✅ Card visuals for KPIs ✅ Simple bar and column charts ✅ Line charts with minimal data points ✅ Large gauge and KPI visuals Mobile-Challenging: ❌ Dense matrices and tables ❌ Complex scatter plots ❌ Multi-series area charts ❌ Small multiple visuals ``` ### Design Review and Validation #### **Design Quality Checklist** ``` Visual Clarity: □ Clear visual hierarchy with appropriate emphasis □ Sufficient contrast and readability □ Logical flow and eye movement patterns □ Minimal cognitive load for interpretation □ Appropriate use of white space Functional Design: □ All interactions work intuitively □ Navigation is clear and consistent □ Filtering behaves as expected □ Mobile experience is usable □ Performance is acceptable across devices Accessibility Compliance: □ Screen reader compatibility □ Keyboard navigation support □ High contrast compliance □ Alternative text provided □ Color is not the only information carrier ``` #### **User Testing Framework** ``` Usability Testing Protocol: Pre-Test Setup: - Define test scenarios and tasks - Prepare realistic test data - Set up observation and recording - Brief participants on context Test Scenarios: 1. Initial impression and orientation (30 seconds) 2. Finding specific information (2 minutes) 3. Comparing data points (3 minutes) 4. Drilling down for details (2 minutes) 5. Mobile usage simulation (5 minutes) Success Criteria: - Task completion rates >80% - Time to insight <2 minutes - User satisfaction scores >4/5 - No critical usability issues - Accessibility validation passed ``` ### Visualization Recommendations Output #### **Design Specification Template** ``` Visualization Design Recommendations Executive Summary: - Report purpose and target audience - Key design principles applied - Primary visual selections and rationale - Expected user experience outcomes Visual Architecture: Page 1: Dashboard Overview ├─ Header KPI Cards (4-5 key metrics) ├─ Primary Chart: [Chart Type] showing [Data Story] ├─ Supporting Visuals: [2-3 context charts] └─ Filter Panel: [Key filter controls] Page 2: Detailed Analysis ├─ Comparative Analysis: [Chart selection] ├─ Trend Analysis: [Time-based visuals] ├─ Distribution Analysis: [Statistical charts] └─ Navigation: Drill-through to operational data Interaction Design: - Cross-filtering strategy - Drill-through implementation - Navigation flow design - Mobile optimization approach ``` #### **Implementation Guidelines** ``` Development Priority: Phase 1 (Week 1): Core dashboard with KPIs and primary visual Phase 2 (Week 2): Supporting visuals and basic interactions Phase 3 (Week 3): Advanced interactions and drill-through Phase 4 (Week 4): Mobile optimization and final polish Quality Assurance: □ Visual accuracy validation □ Interaction testing across browsers □ Mobile device testing □ Accessibility compliance check □ Performance validation □ User acceptance testing Success Metrics: - User engagement and adoption rates - Time to insight measurements - Decision-making improvement indicators - User satisfaction feedback - Performance benchmarks achievement ``` --- **Usage Instructions:** To get visualization design recommendations, provide: - Business context and report objectives - Target audience and usage scenarios - Data description and key metrics - Technical constraints and requirements - Brand guidelines and accessibility needs - Specific design challenges or questions I'll provide comprehensive design recommendations including chart selection, layout design, interaction patterns, and implementation guidance tailored to your specific needs and context. <!-- next: written by tools/add-needs.mjs for AI Blocks; not part of the original skill. Edit that tool, not this section. --> ### After this When you've handed it back, suggest what they could do next in one short question. It's a suggestion: if they're done, that's fine. Offer these, and say they can type their own: - The [Colour contrast checker](https://useaiblocks.com/skills/colour-contrast-checker). It takes the design direction. - The [Logo strength tester](https://useaiblocks.com/skills/logo-strength-tester). It takes the design direction. - The [Screen usability reviewer](https://useaiblocks.com/skills/new-screen-design-reviewer). It takes the design direction. If they pick one and that skill is added here, carry straight on with what you just made. If not, give the link and say what to bring. <!-- /next -->