MUKESH.OSPower BI

Power BI

Power BI Dashboard Builder

A reference layout showing how a Power BI report is composed around a decision — what belongs above the fold, what belongs one click away, and what should never be on the page at all.

Portfolio demonstration — illustrative figures, real structure

The problem

Reports were being built dataset-first: every column that existed became a visual. Pages took thirty seconds to read and answered no particular question.

Who reads it

The BI team building reports, and the business owners who sign off on them before publication.

Decision it drives

Whether a report is ready to publish. A page that cannot state its question, its audience and its refresh contract does not ship.

Report pages8one question per page, no exceptions
Measures in model24defined centrally, reused everywhere
Model size312 MBafter column pruning and encoding
Refresh window4.2 minincremental, off-peak schedule

Report render time before and after modelling

Seconds to first interaction, by page. Lower is better.

12s9s6s3s0s
OverviewRevenueDeliveryPeopleQualityDetail
Before: direct query, no modelAfter: star schema, aggregations

Most of the gain came from the model, not from the visuals. Removing high-cardinality columns and pre-aggregating did more than any visual-level tuning.

Page composition rules

Applied to every page before sign-off.

LayerWhat goes hereLimit
Above the foldThe answer: three to five measures against targetMax 5 visuals
SupportingThe trend and the breakdown that explains the answerMax 3 visuals
One click awayDrill-through to the record level for anyone who challenges a numberUnlimited
Not on the pageAnything nobody has asked a question aboutRemoved

The last row is the one that matters. Most report bloat is additive: nobody ever takes a visual away.

How it was built

The parts that carry over to a production deployment.

Model first

Star schema with conformed date and organisation dimensions. Report authors never write a measure against a raw fact table.

Aggregations

Pre-aggregated tables for the summary pages, with detail resolved on drill-through only, which is what pulled render time under three seconds.

Governed measures

A single measures table with descriptions and format strings, so a measure means the same thing in every report that consumes it.

Publication contract

Each page carries its question, audience, refresh cadence and owner in metadata. Missing metadata blocks the deployment pipeline.

Power BIDAXPower QueryAggregationsDrill-throughDeployment pipelines