Put the actual numbers on the projector
The monthly review is on Thursday. On Tuesday afternoon somebody opens the board pack screen, screenshots it, crops the screenshot, pastes it into a slide, and repeats that for each of the cuts the meeting will want: actuals against plan, the lines that are behind, the same numbers by region. Wednesday, a correction lands. Thursday, the room is looking at a picture of Tuesday.
Then the inevitable question arrives. Somebody asks what the picture looks like without one region in it, or which owner the worst line belongs to, and the honest answer is that nobody can tell from a picture. So the meeting gets “I will follow up”, and the follow-up is another screenshot on Friday.
The deck is the grid
The grid above is a board pack, and the rail down its left has a control that presents it. Press it and the grid takes the whole screen, scaled up so the back of the room can read it, with the tool panel out of the way. The saved views on this grid are the slides, so the arrow keys, the space bar and the page keys step through them the way anybody in a meeting expects, and each step is the real grid re-sorting, re-filtering and regrouping in front of the room.
Two things follow from that, and they are the whole argument.
Nobody prepares anything. The views were built by the people who use this screen anyway, in the course of using it, and naming a view is the only extra work. On Thursday morning the deck is whatever the data says on Thursday morning.
Nothing on the screen is a picture. When somebody asks about one region, the answer is a filter away on the screen everyone is already looking at, and the totals move when you apply it. When somebody asks who owns the worst line, you point at the owner column, which is there because it was always there.
There is a second control that presents the grid exactly as it stands, without a deck, for the times when the conversation has already gone somewhere the slides do not cover. And a third that spotlights the rows you have selected, dimming everything else, so the room is looking at the lines being argued about rather than at all of them. Arm that one before you present: choose the rows with the tick boxes or by dragging across a block of cells, press the spotlight, then present, and the dimming appears with the presentation.
Press it on this page and the grid takes the viewport, which is why nothing here starts on its own. Escape ends it and gives the page back.
Live numbers survive the question
Meetings that run on live numbers spend less time relitigating whether the numbers are current, because everybody watched them being fetched. A stale screenshot cannot answer the follow-up; the live grid can. The awkward moment moves from “this is out of date, we will confirm later” to “let us look”, which takes about as long as the excuse would have.
If a column genuinely should not be on the projector, that is a different question with its own answer: redaction blurs the values and leaves the rest of the screen working. Sharing the real screen and hiding one column are not in tension.
Who else does this
A grid can be told to go full screen anywhere. The part that is unusual is that the saved views double as a slide deck, so the artefact you present is the same artefact you work in, and there is no export step between them. Where that is missing, the export step is where the staleness gets in: not because anybody was careless, but because a picture taken on Tuesday is a picture taken on Tuesday.
Your users get this because it ships in the grid. Nobody on your team builds a presentation mode, and nobody maintains the screenshot ritual that currently stands in for one.