Ask what happens on Monday if the number moves
Last autumn I sat in a review of a customer service operations page in Power BI. Nineteen visuals, most of them fed from Dataverse case, queue, and SLA KPI instance tables, refreshed twice a day. I asked one question at every tile. If this number moves next week, what will you do on Monday that you would not otherwise do? The service manager had a clear answer for five tiles. For the rest, someone had asked for it once, or the column was there and dropping it in took thirty seconds.
That question is the whole test. A dashboard becomes a decision surface when every measure on it is tied to a decision a named person makes, at a value they can state, on a schedule they can describe. A page that fails the test is a report, and it belongs somewhere other than the screen a team lead opens before the morning huddle.
The tiles people are proudest of go first
Go tile by tile with the owner in the room and the page on the wall. For each one, ask who looks at it, how often, what value would make them act, and what the action is. Write the answers in four columns beside the page. No one gets to call a tile useful without filling in the last two columns. In that service review, seven of nineteen survived. The cutting took forty minutes. The arguing took the rest of the afternoon.
The first three to go were the ones the team showed to visitors. A rolling seven-day average handle time. A gauge of customer satisfaction against a target set two reorganisations ago. A donut of cases by channel. All three were correct. None of them had changed a rota, a queue assignment, or a coaching conversation. The team leads knew chat was busier than phone, and the satisfaction gauge had sat in amber for eleven months without anyone deciding what amber required of them.
Pushback arrives as a person rather than an argument. The director likes it. The regional lead asked for it in March. My answer is that the director can have a separate page, and the page that carries decisions stays small. Power BI makes adding a visual nearly free, so the discipline has to come from the review.
Put the threshold and the owner beside the number
A tile that survives still needs three things printed next to it, on the page rather than in a wiki. A one-sentence definition. The value at which someone acts. The name of the person who acts. Without those, two people read the same card and disagree about whether anything is wrong, and the meeting becomes a debate about what the number means.
Take cases due to breach SLA within four hours. The definition reads: any active case with a first response or resolution SLA KPI instance in the nearing non-compliance state, excluding cases on customer hold. The threshold reads: above twenty-five, the queue supervisor pulls two agents off email and tells the service manager before noon. The owner is the queue supervisor by name, with a named backup for leave. Power BI lets you write a description on every measure and a tooltip on every visual, and a small text box next to the card beats both. People read text boxes. They do not hover.
The definition is where Dataverse earns its share of the attention. Someone adds a new status reason for a pilot queue, and the measure quietly stops counting those cases. If the definition is written on the page, the mismatch shows up at the next review. If it lives only inside a DAX filter, the number drifts until it gets quoted to a customer. The argument over who gets to define revenue plays out on every operational page, and it is settled the same way, by someone owning the sentence.
A blank week has to say why it is blank
The worst hour I have spent in a dashboard review began with a week of zero resolved cases in one regional view. The director had already emailed the regional lead asking what had happened to the team. Nothing had happened to the team. A dataflow load from Dataverse had failed on Sunday night, the semantic model refreshed on schedule against the stale table, and the page showed Monday's timestamp over data from the previous week.
A blank period has at least two meanings. No work happened, or the source did not arrive. Support teams know this from the blank priority field that gets read as low priority. The page has to say which meaning applies without a phone call. That starts with a freshness stamp that reflects the last successful source load rather than the last model refresh, because those are different events and the refresh time is the one you get for free.
The model has to keep the distinction too. A measure that turns null into zero so the line looks tidy has thrown away the one signal that would have stopped that email. Leave the gap visible. Keep a known gaps note beside the visual, maintained by the owner, with the date of the failed load and who is fixing it. A page mixing settled and unsettled numbers needs the reconciliation status we argued for where a lake meets a ledger, so readers know which figures are final.
The workspace admin is not the owner
Power BI workspaces have admins and Dataverse tables have owners, and neither role means being answerable for what the page says. In the service review, the workspace admin was a BI developer who had built the page eighteen months earlier and since moved to finance. The manager who opened it every morning had never been asked to own it. Once she was, the definitions got written in an afternoon, because she was the only person who knew them.
The developer had done nothing wrong. He built to the analytics questions written at the start of the project, and then the project closed and the questions kept changing without him. It is the same gap that leaves automation owners losing the thread after a failed run. The work carries on and the accountable person has left the room.
Ownership here means three ordinary jobs. Keep the definition current when the source changes. Keep the known gaps note honest. Decide when a tile comes off the page. The last one matters most, because pages only grow. Six months after that review the page had gained two tiles, each with a decision written beside it, and lost one, because its threshold had never been crossed.
What I say in the next review
Open the page. Ask the owner to name the decision behind the first tile, who makes it, and at what value. Write the answer where everyone can see it. Refuse to let anyone defend a tile because it is accurate or because somebody once asked for it. Those two reasons account for most of the tiles nobody acts on.
Then ask about blanks. Pick any visual with a time axis and ask what it would show if tonight's load failed. If the answer is a zero, you have found the email that will go to the wrong person, and you have found it before it was sent.
Start with the page your operations lead opens first. If you are not sure which page that is, the workspace usage metrics will tell you. List its tiles in one column and beside each write the decision, the threshold, and the name. Any tile that leaves those columns blank comes off before anything goes on, and the page owner should be the one holding the marker.
