# Build brilliant Power BI reports with a disciplined schematic: synthetic exercise worksheet

Curriculum reviewed: 2026-10-25. Use public or synthetic data only.
Do not include client evidence, credentials, private identifiers or raw receipts.

## Goal
A two-page synthetic report design, KPI rationale and verification evidence matrix.

## Outcomes
- Build a decision-led KPI hierarchy with governed polarity
- Choose among five page archetypes and appropriate native visuals
- Apply the brilliant-v1 frame, accessible theme and canvas workflow
- Distinguish layout, semantic-query and rendered-value verification

## Synthetic case
Describe a Sales report built from order headers and order lines. State which grain you intend and which independently established expectation you would compare.

## Review each lesson
### 1. Why most Power BI reports fail
Apply the 3-30-300 hierarchy to orientation, explanation and investigation.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

### 2. The brilliant-v1 frame and grid
Use the 1280 x 720 schematic, header, margins, gutters and deterministic placements.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

### 3. Choosing KPIs: outcome, drivers and guardrail
Build contextual KPI cards with valid comparisons, trends and explicit polarity.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

### 4. The five page archetypes
Give overview, trends, breakdown, exceptions and drillthrough distinct jobs.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

### 5. Picking the right visual
Use a selection matrix to match native visuals to questions and qualified fields.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

### 6. Colour, type and accessibility
Apply semantic colour, readable typography, contrast and keyboard review.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

### 7. Canvas backgrounds: generated and designer workflows
Compare preview generation with reviewed Marp, Figma and PowerPoint artwork.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

### 8. Anti-patterns and how the validator catches them
Separate geometry refusals from semantic, interaction and rendered-value evidence.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

## Failure case
Generated definitions exist but a required execution observation is missing. Explain why qualification cannot pass and name the next required observation. Do not fabricate a receipt or change a frozen expectation.

## Evidence table
| Claim | Expected observation | Available evidence | Missing/stale | Next owner/action |
| --- | --- | --- | --- | --- |
| | | | | |

## Limitations
This worksheet is a completion check, not live qualification, business acceptance or a professional award. Pro assessment and certification policy remain planned. Keep optional live results in customer-controlled custody.