Guide section 51 of 55
What a designer should hand over
Do not hand over only a screenshot. For every page, specify:
| Area | What to specify |
|---|---|
| Purpose | The question the page answers |
| Data | Measures, dimensions, hierarchy, targets, comparison periods |
| Components | Figma component → native Power BI component, for each element |
| Filters | Filter, default, scope, single/multi-select, search, sync behavior, reset behavior |
| Interactions | Per visual pair: filter, highlight or none |
| Drill | The hierarchy used |
| Drillthrough | Source page, destination page, carried context, return path |
| Sorting | Default sort column and direction |
| States | Normal, selected, filtered, no data, empty result, unavailable/error |
| Accessibility | Alt-text intent, tab order, semantic status, labels |
| Technical mapping | Native / native + configuration / theme controlled / DAX-dependent / bookmark-dependent / field-parameter based / custom visual |
Interaction specification example:
Visual A select Department ↓ Visual B cross-filter Visual C cross-highlight KPI D no interaction