Ask the Model. Don’t Screenshot the Dashboard

Screenshots age in an hour. A trusted model answers the next question without a new file.

The slide deck, the chat image, and the PDF of a tile are how mid-market companies pretend they distributed insight. What they distributed was a moment. The next question still needs a person, a new export, and another picture.

Screenshot culture is not a definition problem

We already wrote the rule that questions in plain English only work on agreed measures: conversational analytics without a trusted model is just chat. Definitions come first. Chat on fog is still fog.

This piece is about the habit that survives even after definitions exist. People still snip the page, paste it into a deck, and email the crop. Then they argue about a jpeg from Tuesday while the model moved on Wednesday.

The fix is not a nicer Q&A box. The problem is a distribution system that treats analytics as a picture. A picture cannot filter, take a follow-up, or show the measure description. It can only age.

Adoption means people use the product, not that captures circulate. If nobody opens the dashboard, the workaround is often exactly this: one person opens it and everyone else lives on the snip.

Why the snip feels faster, and why it isn’t

A screenshot is immediate. There is no license question, no “I can’t find the workspace,” and no fear of breaking a filter. For a one-hour meeting it feels kind.

Then the meeting produces a question like “Is freight in this?” The owner of the snip is not in the thread and the file is a picture. Someone files a ticket, someone builds a new page, and someone sends a new picture. You did not save time. You turned the next click into a project.

A trusted model with access, grain, and named measures lets the same person, or the next one, ask without a new artifact. That can be a filter on a live page, a connected Excel slice, or a question in the analytics interface your tenant already has, pointed only at the certified product. The interface is not the point. The point is no new file.

Do not start with a demo of talking to a messy estate. The semantic model is the product, so ask that.

The costs of running the company on captures

1. Every follow-up is a rebuild. Leadership’s second question should be a slice. In screenshot culture it becomes a request, analysts become print shops, and the backlog fills with “same page, different crop.”

2. Stale pictures become unofficial actuals. A board pre-read with Tuesday’s snip sits next to Wednesday’s refresh. Directors notice the drift, or they don’t, which is worse. Timing is part of a definition and a jpeg has none. The pack version of this problem is your board pack is late. The cultural version is that you mailed a still.

3. Security and grain leak. Screenshots ignore row-level rules. They travel to inboxes that should not see the plant, the customer, or the margin. A live model can restrict access and a picture cannot. Dashboard sprawl already taxes you, and snips are sprawl that never shows up in usage metrics.

4. Definitions cannot travel with the number. The measure sentence, the refresh stamp, and the steward all fall away, and recipients argue about pixels. Measures nobody can explain have their own post. Screenshots guarantee the explanation stays behind.

5. You train the organization not to look. Why learn the workspace if the slide arrives anyway? License seats sit idle, and the few people who can open the model become bottlenecks and photographers.

6. You cannot ask the next question in the same channel. Chat, email, and decks become the analytics interface. They are terrible at lineage and excellent at multiplying files.

If your executive communication is a stack of captures, you already know the cost in hours and in meetings that went the wrong way.

What not to do

Do not ban screenshots with a poster. People will snip from home. Give them a live path that is easier than the snip for the questions that matter.

Do not paste more tiles into email as a “fix.” That is still a still.

Do not spin up a second analytics layer so you can keep screenshots and also “ask.” Keep one certified model as the one place questions are allowed to hit, and keep the sandbox out of executive channels.

Do not confuse a recorded video of a dashboard with access. Video ages too.

If you have not listed the questions you want answered, you will end up conversing about everything. Pick the standing questions first, with a strategy roadmap if you need one.

How to fix it

1. List the questions that should never become a jpeg. These are the ones that hit every ELT: margin by plant, cash versus plan, fill rate, throughput. If those still travel as pictures, you have a distribution failure, not a curiosity failure.

2. Point people at the certified model, not a capture of last week’s page. Set up access, row rules, and labeled measures. The live page is the default attachment. A screenshot is an exception with an expiry date, if you allow it at all.

3. Make follow-ups cheap. Filters, drill, bookmarks, and connected Excel should cover the next question without a developer. If they don’t, the model is missing grain or a measure, and a nicer screenshot will not help.

4. Stamp every official view with an as-of time and the measure name. When someone does need a still for a plane or a binder, the still must carry that contract. Unlabeled pictures stay unofficial.

5. Move executive conversation onto the product. Standing reviews open the report or a thin app, not a slide of a report. Commentary can live in the pack. Actuals stay live or tied to refresh, never to a snip.

6. Retire the photographer role. If an analyst spends the week exporting tiles for other people’s decks, that is the process to kill. Teach requesters to open the certified page. If they lack access, that is a governance ticket, not a reason to print. A Power BI Quickstart can put one executive question on a model people are allowed to query, so you can stop mailing the crop.

Excel is still a fine consumer when a grid or a statement is the right shape, as long as it stays connected. The boundary is the same as in Excel vs Power BI. A pasted picture of a pivot is still a picture.

What good looks like

The CEO asks a follow-up in the meeting and someone filters. Nobody says “I’ll send a new screenshot after.”

Pre-reads link to the certified view with a refresh time. Directors who need to work offline get a stamped pack, not a crop from Slack.

Analysts spend their time on new measures and exceptions instead of photography.

Screenshots still happen, but they are not how the company remembers the number.

Get started

If the last decision was made on a picture of a tile, you asked the jpeg. Ask the model.

Want to find which executive questions still travel as captures? Book a session. We will name the certified product those questions should hit and the one screenshot habit to kill first. Or start with a free Model Health check.