Power BI requirements gathering questions

AutoSpark

The synthetic requirements example used in the linked traceability matrix.

Questions before a Power BI report is designed

Ask which decision the report should support, how each measure is defined and which records can substantiate it. Resolve disagreements about dates, populations and ownership before treating a visual as the agreed requirement. Use a recent business example to test the answers.

Microsoft's BI solution planning guidance separates business design from technical validation. It includes metric definitions and source mappings. The questions below are an authored workshop aid, not a specification of Power BI capabilities or licensing.

Ask the business userAsk forRecord the unresolved point
What decision will you make after reading this?A recent decision and the information usedA chart request with no identified action
What does this measure include?A definition, population and worked calculationCompeting meanings of the same label
Which date belongs to the measure?Examples crossing a period boundaryOrder, invoice and payment dates conflated
How current must the information be for that decision?Decision timing and source availabilityDesired freshness not yet tested against the source
Who may inspect the underlying detail?An authorised access requirementAssumed permissions or unreviewed sensitive data
What should happen when a source is missing?A failure exampleWhether to suppress, label or hold the result

Synthetic workshop: “monthly sales”

A sales manager means orders accepted during the month. Finance means invoices issued during the month. Neither total is automatically wrong: the requested decision and definition differ.

Take a fictional order accepted on 30 September and invoiced on 2 October. Ask each person which month should include it and why. Record the proposed measures separately until the decision owner agrees the intended behaviour. Renaming a chart without resolving this boundary can hide the disagreement.

Do the same with cancellations and credit records. Keep an example that should be included and one that should be excluded. Confirm the source can distinguish them before committing to a calculation.

End the session with something testable

Read back each definition and its open questions. Assign a source check to a named owner. Once the definitions are agreed, write expected results for the sample records and link them to the requirements traceability matrix.

Technical design must still test the chosen connection, access and refresh behaviour in the actual environment. A requested refresh interval is a requirement to assess, not evidence that the platform or source will meet it.

Which measure definitions and source assumptions need agreement?

Resolve the decision, metric definitions and evidence gaps in a worked business session.

Your starting question: Which measure definitions and source assumptions need agreement?

Start by checking

  1. Inspect a decision and period-boundary example.
  2. Separate competing definitions of monthly sales.
  3. Assign source and technical checks.

Evidence to gather

  • Business definitions and sample source records.
  • Access requirements and source availability.

Not established yet

  • A requested refresh interval is feasible.
  • A product feature is configured correctly.

Discuss this investigation