Guide section 22 of 31

Figma → Power BI Workflow

Business requirement
      ↓
Analytical question / decision
      ↓
Data availability + metric definitions
      ↓
Page archetype / template
      ↓
Figma design using company DS + Power BI-aware components
      ↓
Native component + interaction mapping
      ↓
Feasibility check
      ↓
Power BI implementation
      ↓
UX validation / business validation
      ↓
Reusable-pattern update

What Figma should specify

  • Page purpose and primary user question.
  • Canvas/page template and section hierarchy.
  • Component names and underlying Power BI visual/control.
  • Measures, dimensions and time grain used by each visual.
  • Filter scope, defaults, synced behavior and reset behavior.
  • Interactions between visuals.
  • Drill-down hierarchy and drillthrough destinations.
  • Tooltip content and whether it is standard or report-page tooltip.
  • Navigation, selected states and Back behavior.
  • Loading, empty/no-data, selected and filtered states where relevant.
  • Token/style mapping and any manual formatting exception.
  • Accessibility notes.
  • Responsive/mobile/embed and print/PDF requirements.
  • Any preview/custom visual caveat.

A Figma artifact is not 'ready' merely because it looks finished. It is ready when it is Power BI-feasible and implementable without reverse-engineering the intent.