The Steering Committee Still Reviews Screenshots

The steering committee pack arrives on Sunday night. It runs twenty slides, and half of them are screenshots of Power BI pages taken Friday afternoon. The app is live and the gateways are green, but the committee still manages from pictures.

Screenshots are not a temporary habit. They are the real operating system until someone changes the rules of the room.

Screenshots are a management choice

Teams blame risk aversion, projector anxiety, or “executives who like PowerPoint.” Those explanations are incomplete.

Screenshots win when the meeting needs a fixed artifact, when live filters feel unsafe in public, when commentary has nowhere to live in the app, or when the agenda still assumes a prepared pack.

This is a cousin of ask the model, don’t screenshot and Power BI is live, management cadence never changed. The technology can be ready while the committee ritual still refuses it.

A screenshot freezes context, which can be useful. It also freezes errors, stale filters, and last week’s as-of, and nobody notices until the argument starts. When the steering committee reviews pictures of a live system, you pay twice: once for the platform and once for the theater that ignores it.

Why the pack stays in screenshots

The agenda was never rewritten. Item three still says “review the slides,” not “open the certified app page.”

Leaders fear a live click that reveals a blank drillthrough or the wrong plant filter. Past failures taught caution, and caution became policy.

Commentary does not fit on the page. Screenshots get pasted into slides so the narrative can sit beside the picture, and the model never grows a place for decisions and owners.

Version control feels safer in a deck. “This is what we reviewed on the 12th” is easy with a PDF and harder when the live page moved overnight, unless you design a governed freeze.

Politics prefers prepared narratives. A live model answers follow-ups. A screenshot supports the story someone already wrote.

The costs of steering by screenshot

1. The committee and the model diverge. By Wednesday the live page has moved, but the decision was made on Friday’s picture. Reconciliation becomes a standing agenda item.

2. Accountability attaches to the slide author. The room asks who built the pack, not who owns the outcome, and management quality drops.

3. Follow-up questions leave the room. Screenshots do not drill, so the interesting question becomes an offline request and decision latency returns.

4. Filter mistakes fossilize. A wrong slicer in Friday’s capture becomes next week’s “official” number. Silent errors travel farther than live pages that can be corrected in place.

5. Analytics teams optimize for capture, not decisions. Pages get designed to look good as a rectangle on a slide, and grain and interaction lose to screenshot aesthetics.

6. Adoption metrics lie. Opens look fine while the management system still runs on PowerPoint. It is the same false green as export-heavy “adoption.”

7. Security theater appears. Sensitive pages get pasted into widely forwarded decks. Access controls on the app do not protect the screenshot chain.

8. You teach leaders the model is optional. Every successful screenshot meeting trains the organization to skip the product you funded.

How to fix it: change the committee artifact rules

1. Rewrite one recurring agenda item. Pick the operating review or the steering committee. Replace “review slides of KPIs” with “review page X in the app” or “review the governed pack generated from model Y.”

2. Decide where a freeze is legitimate. If the committee needs a fixed record, produce a scheduled paginated pack or a labeled snapshot from the same semantic model. Do not pretend random screenshots are that freeze.

3. Put commentary and owners next to the metric. Minutes, actions, and narrative need a home. If the only home is PowerPoint, screenshots will win forever.

4. Prove the live path once under real conditions. Use the same RLS, filters, and drill paths the chair will use. Fix blank pages and wrong defaults before you mandate live use. Treat the drillthrough that lands on a blank page as a prerequisite, not a later enhancement.

5. Ban unofficial captures as decision records. Screenshots are fine for illustration in email. They are not the system of record for steering decisions, and the charter should say so.

6. Make the default landing safe. The app should open on the right company, period, and page without a scavenger hunt. Leaders take screenshots when they fear live mis-clicks.

7. Align the pack with certified datasets. If the committee still pastes from three workspaces, fix the source map first. Screenshots of inconsistent models multiply the definition fight.

8. Time-box the transition. Run both for two meetings, then retire the old screenshot pack on a date, with the same discipline as how to retire a dashboard.

9. Measure success by decisions, not just fewer JPEGs. Did follow-ups stay in the model? Were owners assigned in the room? Did the next meeting start from the same numbers?

Screenshots versus governed packs

The need for a fixed committee record is legitimate. It does not require a collage of cropped tiles from Friday afternoon.

A governed pack has a known as-of, a known model, and a known distribution list. A screenshot chain has none of those. It only has convenience. If your committee cannot run fully live yet, build the governed pack first and retire the unofficial captures second. Banning screenshots while offering no freeze guarantees a quiet rebellion back to PowerPoint.

What the chair must signal

The chair sets the artifact rule. If the chair accepts screenshots as the decision record, no analytics roadmap will win.

Ask for one sentence in the charter: decisions are recorded against the certified app page or the governed pack, not against personal captures. Then enforce it for two cycles. Culture follows the gavel.

What good looks like

The steering committee opens a known app page or a governed pack with a clear as-of. Screenshots may still appear in narrative appendices, but they are not the authority. When someone asks “what changed since last month,” the room clicks instead of forwarding another chain of cropped tiles.

The analytics team stops formatting for capture and starts designing for the decision the agenda actually owns.

Executive takeaway

If the steering committee still reviews screenshots, Power BI is a content library for PowerPoint, not a management system. Change the artifact rules, offer a governed freeze when you need one, and make the live path safe. Then stop paying for a platform the room only visits long enough to take a picture.

Want help moving one executive forum off screenshot packs? Book a session with Alluvium. We will map the agenda, the freeze requirement, and the page that should replace the Sunday night deck. To check the model behind that page, request a free Model Health check.