Insights
Ask the Model. Don’t Screenshot the Dashboard.
Screenshots age in an hour. A trusted model answers the next question without a new file.
Screenshots age in an hour. A trusted model answers the next question without a new file.
The slide deck, the chat image, the PDF of a tile—those are how mid-market companies pretend they distributed insight. They distributed 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 English only work on agreed measures: conversational analytics without a trusted model is just chat. That piece is definitions first. Do not skip it. Chat on fog is still fog.
This piece is the habit that survives even when definitions exist. People still snip the page. They paste it into a deck. They email a crop. They argue about a jpeg from Tuesday while the model moved Wednesday.
That is not “we need a nicer Q&A box.” That is a distribution system that treats analytics as a picture.
Pictures cannot filter. Pictures cannot take a follow-up. Pictures cannot show the measure description. They can only age.
Adoption looks like usage of the product, not circulation of captures. If nobody opens the dashboard, the workaround is often this: one person opens it, everyone else lives on the snip.
Why the snip feels faster—and why it isn’t
A screenshot is immediate. No license question. No “I can’t find the workspace.” No fear of breaking a filter. For a one-hour meeting, it feels kind.
Then the meeting produces a question. “What if we drop that customer.” “Show the other plant.” “Is freight in this.” The owner of the snip is not in the thread. The file is a picture. Someone files a ticket. Someone builds a new page. Someone sends a new picture.
You did not save time. You deferred the next click into a project.
A trusted model with access, grain, and named measures lets the same person—or the next person—ask without a new artifact. That can be a filter on a live page. It can be a connected Excel slice. It can be 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 microphone is another brochure. The semantic model is the product. Ask that.
The costs of running the company on captures
-
Every follow-up is a rebuild. Leadership’s second question should be a slice. In screenshot culture it is a request. Analysts become print shops. The backlog is full of “same page, different crop.”
-
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 a definition. A jpeg has none. The pack version of the clock is your board pack is late. The cultural version is this: you mailed a still.
-
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. A picture cannot. Governance already taxes you when sprawl is the inventory: dashboard sprawl. Snips are sprawl that will not even show up in usage metrics.
-
Definitions cannot travel with the number. The measure sentence, the refresh stamp, the steward—gone. Recipients argue the pixels. Unexplained KPIs have their own post. Screenshots guarantee the explanation stays behind.
-
You train the organization not to look. Why learn the workspace if the slide arrives anyway? License seats sit idle. The few people who can open the model become bottlenecks and photographers.
-
You cannot ask the next question in the same channel. Chat, email, and decks become the analytics UI. They are terrible at lineage. They are excellent at multiplying files. The program looks busy. It is a photocopier.
No client story. No made-up savings. If your exec comms are a stack of captures, you already know the cost in hours and in wrong rooms.
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.” One certified model. One place questions are allowed to hit. Sandbox stays mute in executive channels.
Do not confuse a recorded video of a dashboard with access. Video ages too.
If the questions you want to ask are not even listed, you will converse about everything. Pick the standing questions. Strategy first if you have to: roadmap.
How to fix it
-
List the questions that should never become a jpeg. 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.
-
Point people at the certified model, not at a capture of last week’s page. Access, row rules, labeled measures. The live page is the default attachment. A screenshot is an exception with an expiry—if you even allow it.
-
Make follow-ups cheap. Filters, drill, bookmarks, connected Excel. The next question must not require a developer. If it does, the model is missing grain or a measure, not a nicer screenshot.
-
Stamp every official view with as-of and measure name. When someone does need a still—for a plane, for a binder—the still must carry the contract. Unlabeled pictures stay unofficial.
-
Move exec conversation onto the product. Standing reviews open the report or a thin app. They do not open a slide of a report. Commentary can live in the pack. Actuals stay live or refresh-bound, not snip-bound.
-
Retire the photographer role. If an analyst’s week is exporting tiles for other people’s decks, that is the process to kill. Teach the 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 exec question on a model people are actually allowed to query—then stop mailing the crop.
Excel remains a consumer when a grid or a statement is the right shape. Connected. The boundary stays 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. 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 offline get a stamped pack, not a crop from Slack.
Analysts spend time on new measures and exceptions, not on photography.
Screenshots still happen. They are not how the company remembers the number.
You still have dashboards. You stopped treating them as posters.
Get started
If the last decision was made on a picture of a tile, you asked the jpeg. Ask the model.
Need a 30-minute look at which executive questions still travel as captures? Contact Alluvium. We will name the certified product those questions should hit, and the one screenshot habit to kill first.
Next step
Book a Session
Need a clearer finance or executive reporting stack? Book a Session.