23. Report and Dashboard Design Principles
23.2 Layout
Quick answer: the short, self-contained version of this lesson is the guide Power BI Report Layout Design.
- Z-pattern / F-pattern: people read from top-left to right, then down. Place the most important KPIs (cards) at the top-left/top row, trends in the middle, details at the bottom.
- Overview → detail: summary page first, then deeper pages (by city, dark store, product, customer), then detail tables via drill through.
- Grid and alignment: use View › Gridlines and Snap to grid; keep equal spacing between visuals; align edges.
- Less is more: roughly 6–8 visuals per page is a practical upper limit for readability (and performance).
- Consistency: same position for slicers and titles on every page; same colour for the same meaning.
- Whitespace: empty space is not wasted – it helps the eye separate groups.
HeaderReport title · date range · logo · navigation buttons
About this data: This table uses columns: Wrong result, Reason, Correction. Values shown are the lesson examples already on this page (not a new dataset). | |||
KPI cardTotal Sales | KPI cardTotal Orders | KPI cardAOV (₹) | KPI cardAvg Delivery Time |
TrendLine chart: Sales vs Sales LY by month | ComparisonBar chart: Sales by Category | ||
GeographyMap or bar: Orders by City | DetailMatrix: Dark Stores with KPIs | ||
Kagdavar layout aadhi kadhun bagha – mag Power BI madhe banvayla khup vel vachto.
Ravindra Bagale's Tip
A common layout mistake is scattering visuals without alignment, so the eye doesn't know where to start. Put the most important KPIs at the top-left, align everything to a grid, and keep consistent gaps. Use View › Gridlines and Snap to grid. Remember this rule.
Ravindra Bagale's Tip – मराठी
Layout मधली एक common चूक म्हणजे alignment शिवाय visuals इकडे-तिकडे ठेवणं, त्यामुळे डोळ्यांना कुठून सुरुवात करायची ते कळत नाही. सगळ्यात महत्त्वाचे KPIs वर डावीकडे ठेवा, सगळं grid ला align करा, आणि अंतरं सारखी ठेवा. View › Gridlines आणि Snap to grid वापरा. हा नियम लक्षात ठेवा.
Ravindra Bagale's Tip – हिंदी
Layout की एक common गलती है बिना alignment के visuals इधर-उधर बिखेर देना, जिससे आँख को पता नहीं चलता कि कहाँ से शुरू करे. सबसे ज़रूरी KPIs ऊपर बाईं ओर रखो, सब कुछ grid पर align करो, और gaps एक जैसे रखो. View › Gridlines और Snap to grid इस्तेमाल करो. यह नियम याद रखो.
What "important" means on this page
Top-left is not a design fashion. It is where the eye lands, so it is where the decision KPI goes. If total orders sits there, you have told the reader that volume is the point, even if your mouth says "we care about speed". Put % delivered under 10 minutes in that corner when the question is lateness. Put the volume card somewhere small, or on the next page, and label it as context.
Figure 23.1, just above, is a generic sales sketch. It teaches position: header, cards, then comparison. Total Orders is on that sketch because a sales question cares about volume. When the question is which store is late, keep the positions and change the card. The picture under this section is that change.
The overview-to-detail path is the same idea in pages. Page one names the city that is off the promise. The next page names the store. Drill-through names the orders. A reader who can jump straight to a 40-column table will, and will miss the name. Do not make the table the front door.
"Less is more" is a business rule wearing a design coat. Every extra visual is another number that can outshout Gangapur. Six to eight visuals is already a lot for a Monday read. If you cannot point at one of them and say which decision it changes, it is not neutral. It is noise.
Whitespace is where the groups become visible: the promise cards together, the city comparison together, the "not for this meeting" list somewhere that is not fighting the cards. Alignment is how Shraddha knows the third card is the same kind of thing as the first. A page of tilted, uneven boxes feels unfinished because the reader cannot tell what you decided.
Draw the question as the title. Draw three cards. Draw one comparison. Write the numbers from a tiny fictional table in pencil, including one number you are refusing to put on the page. If the pencil sketch already answers the question, the build will. If the pencil sketch needs twelve charts, the question is still too wide.
Sample layout — fictional data. Same Nashik week as section 23.7. The left page leads with 50 orders. The right page leads with Gangapur at 4 of 6 delivered orders inside 10 minutes.
Read the two pages as a manager, not as a designer. On the left, College Road wins, because 12 orders is the sort of number that survives a messy page. Gangapur and Kothrud are the same visual size as everyone else. The business gets no name before lunch. On the right, the title is the question Shraddha is paid to answer. The first card is 66.7% (4 of 6) at Gangapur. The missed-delivery count is 2, so she does not hire a team for a flood that is not there. Cancellation is 12.5% (1 of 8), so she does not ignore a lost order just because the time card moved. Total orders is absent on purpose. College Road's 12 is still true. It is just not the decision.
The right-hand page is not a copy of a product screen. There is no ribbon and no menu of icons. It is a layout: title, three numbers, one comparison, one action line. Build that. The clicks that place a card are already in Modules 14 and 22. They do not choose the number.
Fix common mistakes
| Wrong result | Reason | Correction |
|---|---|---|
| Eye jumps around the page | KPIs scattered | KPI cards in the top row, left to right |
| Visuals misaligned | Dragged by hand | Format › Align / Distribute |
Practise independently
Practice task
Sketch a layout on paper: 4 KPI cards (Sales ₹2,100, Orders 8, AOV ₹300, Cancel 12.5%) and two charts.
Practice file (fictional): visuals_orders_apr_may_2026.csv
Hints
- Top row cards, chart row below.
Solution
Row 1: four cards; Row 2: Sales by City bar (Pune 850, Nashik 800, Kolhapur 450) and Sales by Month column (Apr 900, May 1,200).
Revision card