Business Intelligence with Power BI

L10 · Report Design

Practice — Medium · Solution

The rescue, resolved

  • The split: attainment belongs with your Performance/Vs-Target page; the heat grid and scatter belong with Specialty (or Detail); employee count by region is a new question entirely ("how is headcount distributed?") — a stub page, honestly labeled, possibly cut altogether if nobody asked the question. "Q3 Overview" was four questions in a trench coat, and the four resolve into existing homes plus one honest orphan.
  • Hierarchy: whichever page you kept leads with its answer, not the company's name — the logo took the bottom corner and lost nothing.
  • Typical timings: the mess takes ~10 minutes; the rescue 25–40. That asymmetry is the honest price of "later" — and this rescue was easy mode, with the original builder (you) still in the room. Inherited messes cost the archaeology too.

Reflection answers

  • Most students report nearly aligning or alt-texting the scatter — which the split then moved to another page, where its size, neighbors, and tab position all changed. Polish applied before structure is polish applied twice. The pass's order exists because its steps invalidate each other's premature work in exactly one direction.
  • Ratios of 1:3 or 1:4 are typical — and the rescue's cost grows with distance from the original build (context decays, intent is forgotten). "Design later" is a loan whose interest compounds; the design pass at build time is the cheap version of itself.