Report Layout Design in Power BI
Report layout is how you place KPIs, charts, slicers and white space so a busy shop owner finds the answer in seconds. Pretty colours cannot fix a muddy page.
Friends! Students pin twelve visuals and call it a dashboard. Why does the owner squint? Because nothing leads the eye. How? We design one FreshBasket executive page: audience questions first, KPI cards top-left, one trend, one breakdown, shared slicer strip, grid on. Less is more.
मित्रांनो! Students बारा visuals पिन करून त्याला dashboard म्हणतात. Owner का भुवया चढवतो? कारण डोळ्यांना मार्ग मिळत नाही. कसे? एक FreshBasket executive पेज: आधी प्रेक्षक आणि प्रश्न, KPI कार्ड वर-डावीकडे, एक trend, एक breakdown, समान स्लायसर पट्टी, grid चालू. कमी म्हणजे जास्त.
मित्रों! Students बारह visuals पिन करके उसे dashboard कहते हैं. Owner क्यों भौंहें चढ़ाता है? क्योंकि आँखों को रास्ता नहीं मिलता. कैसे? एक FreshBasket executive पेज: पहले दर्शक और सवाल, KPI कार्ड ऊपर-बाएँ, एक trend, एक breakdown, एक जैसी स्लाइसर्स पट्टी, grid चालू. कम यानी ज़्यादा.
Quick answer
Vertical path:
- Write who the page is for and three morning questions.
- Sketch cards on top, trend in the middle, detail below (Z-pattern).
- View → Gridlines and Snap to grid.
- Put slicers in the same strip on every page.
- Aim for about six to eight visuals — cut the rest.
- Read the page in ten seconds. If the headline number is slow to find, redesign.
Real example: one shop morning page
Questions:
- How much did we sell yesterday?
- Which city is soft?
- Are deliveries late?
Layout that answers them:
| Zone | Visual | Number the owner should see |
|---|---|---|
| Top-left card | Total Sales | 1160 |
| Top card | Orders | 4 |
| Top card | Late orders | 1 |
| Middle | Sales by month line | trend |
| Bottom | City bar | Mumbai 1000, Pune 160 |
| Left/top strip | City + Date slicers | filters |
What happens when Pune is selected on the slicer: cards drop to 160 sales and 2 orders. The layout did not change; the filter context did. Good layout makes that drop obvious.
What do I need before this guide?
Before and after (look at the tables first)
Before
आधी (Before)
पहले (Before)
After
नंतर (After)
बाद में (After)
Audience before pixels
- Who opens this — owner, city manager, or staff?
- What decision happens after they look?
- Which three KPIs matter for that decision?
- Phone or desktop? Plan mobile layout later if needed.
If you cannot answer those, stop dragging charts.
Z-pattern and grid
Z-pattern layout: KPI cards top-left, trend in the middle, detail table at the bottom.
Z-pattern layout: KPI कार्ड वर-डावीकडे, मध्ये trend, खाली detail टेबल.
Z-pattern layout: KPI कार्ड ऊपर-बाएँ, बीच में trend, नीचे detail टेबल.
Turn on gridlines and snap to grid. Same slicer strip on every page so readers do not hunt.
Gridlines आणि snap to grid चालू करा. प्रत्येक पेजवर सारखी स्लायसर पट्टी — वाचक शोधत फिरणार नाही.
Gridlines और snap to grid चालू करें. हर पेज पर एक जैसी स्लाइसर्स पट्टी — पाठक ढूँढता नहीं फिरेगा.
- Eyes start top-left. Put the hero KPI there.
- Move right across the KPI row.
- Drop to the trend, then to the detail.
- Gridlines + snap keep edges honest.
- Same slicer position on page 2 and page 3 — muscle memory.
Six to eight visuals per page is enough. Extra charts belong on the next page, not in the margins.
प्रति पेज सहा ते आठ visuals पुरे. अतिरिक्त charts पुढच्या पेजवर — margins मध्ये नाही.
प्रति पेज छह से आठ visuals काफ़ी. अतिरिक्त charts अगले पेज पर — margins में नहीं.
Why “less is more”: every extra visual steals attention and refresh time. A second page is cheaper than a crowded first page.
Mistakes and calm fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| Cannot find the KPI | Hero number not top-left | Move cards up |
| Slicers wander | Different layout per page | Shared strip |
| Rainbow page | Manual colours everywhere | Theme + few conditional rules |
| Looks fine to you only | Designed for the author | Test with a friend for ten seconds |
Ravindra Bagale's Tip
Interview line: “I design for three questions and a Z-pattern: KPIs top-left, then trend, then detail — about six to eight visuals.” Got it?
Ravindra Bagale's Tip – मराठी
Interview line: “मी तीन प्रश्नांसाठी आणि Z-pattern साठी design करतो: KPIs वर-डावीकडे, मग trend, मग detail — सुमारे सहा ते आठ visuals.” समजलं का?
Ravindra Bagale's Tip – हिंदी
Interview line: “मैं तीन सवालों और Z-pattern के लिए design करता हूँ: KPIs ऊपर-बाएँ, फिर trend, फिर detail — करीब छह से आठ visuals.” समझ में आया?
Practice task
- Write three questions for a shop owner.
- Sketch the page on paper.
- Build it with grid on.
- Remove one visual that does not answer a question.
Got it? Layout starts with the audience and three questions — not with twelve charts. Next: Power Query Applied Steps. Let us go ahead.
समजलं का? Layout प्रेक्षक आणि तीन प्रश्नांपासून सुरू होते — बारा charts पासून नाही. पुढे: Power Query Applied Steps. आता पुढे जाऊया.
समझ में आया? Layout दर्शक और तीन सवालों से शुरू होता है — बारह charts से नहीं. आगे: Power Query Applied Steps. अब आगे बढ़ते हैं.
Frequently asked questions
How many visuals per page?
About six to eight is a practical ceiling for reading and performance.
What is the Z-pattern?
Eyes move left-to-right on the top row, then down. Put the most important numbers top-left.
Theme or manual colours?
A report theme keeps pages consistent. Manual one-off colours drift across pages.
Mobile layout?
View → Mobile layout for phones. Desktop layout is not automatically good on a small screen.
Is a busy page “rich”?
No. Busy pages hide the decision. Rich means the right question is answered fast.
Course lessons?
Audience and questions, and layout, in the design principles chapter.