A login is not a briefing
A dashboard is a place to look. A briefing is a document someone can finish. If the reader will not open the BI tool, a link is not the report.
Write as if they will read it on a phone between meetings. If the first paragraph does not name the change, they will never click through.
Five places a dashboard dies in an inbox
Start with what changed, in words. Then say whether that is good, bad, or mixed. The chart can sit underneath.
A usable briefing usually includes:
- What changed this period
- Where the change came from
- What you recommend next
- What is still unknown
- Who owns the next check
- Where to look if they want more
- When the next briefing lands
A screenshot of a dashboard is not a briefing. It still asks the reader to do the work you already did.
Screenshot theater
After the opening, explain the cause in one paragraph. Filters, segments, and date pickers belong in the tool. The briefing belongs in a document.
Then name the action. Hold spend. Refresh a campaign. Recheck a source. A dashboard without a next step is a place to wander, not a memo.
Keep the live view available. Do not make it the only way to understand what happened.
The phone test
If the reader was not in the working session, they still need the same three answers. Write as if they will never log in.
- The question they actually asked
- The change they can see without a login
- The source behind that change
- The action you want this week
- The link, if they still want the live view
Do not paste a gallery of tiles. The briefing has to survive a phone, a missing seat, and a dead login.
When the live data will keep moving, say what was true at send time, and when you will send again.
Make the live link optional
A concise briefing helps people act without a login. It may include the period, the change, the cause, and the ask.
Write it so it can be forwarded. That is the whole job.
What operators forget
Have a teammate comment before it goes out. Ask whether the opening can be forwarded, and whether the dashboard link is optional.
Useful questions include:
- Could someone act without opening the tool?
- Is the first paragraph a story or a caption?
- Did we paste a screenshot instead of writing the change?
- What would we cut if this had to be one page?
- Is the live link optional or required?
- What should stay in the tool for people who still want to dig?
Create space for honest feedback without defending the dashboard. Capture the cuts that would make the briefing finishable.
Working file versus send file
The version you send should read like a document. The live dashboard can keep the extra filters, the caveats, and the unfinished questions.
Lock the send version, then document lessons that should change the next briefing.
Assign ownership for those changes. A lesson that stays in a thread rarely changes the next send.
Same questions. New period.
Keep the same three questions. Change only the period. A new layout every week is how a briefing turns back into a dashboard tour.
Lock the send version before the numbers refresh again. A briefing dated after the meeting is already a recap.
Agree on what can be forwarded before the briefing leaves your desk.
If there is no action, it is not a briefing
End with one decision. Keep looking where the story is already working, and say what to ignore until the next send.
If you keep one live link, put it after:
- The sentence they can finish without a login
- The filter they should not have to reconstruct
- The owner of the next check
- The date the live view can wait until
- What stays in the tool for people who still want to dig
Some readers need a document they can finish. Others still want the live view. The briefing should stand alone either way.
Monday, not whenever the chart looks ready
When a follow-up is needed, connect it to the change you just named. Do not wait until someone asks why the chart moved.
If they still need the live view, put the link after the ask. The briefing has to stand if the login fails, the seat is missing, or they are on a phone.
Give them enough time to decide without requiring a login.
Comment before it leaves
Name who owns the next send. A dashboard ping has no owner. A briefing does.
Schedule the next send around a real event: a launch, a budget cycle, a weekly close. A relevant briefing is more useful than another dashboard ping.
Do not invent a new layout each week
Do not wait for the chart to look finished. Send Monday with what was true at close. The live tool can keep moving.
Use the follow-up to review what moved, answer remaining questions, and name any required change. That shows continued ownership without turning every send into a live walkthrough.
Confirm they finished it
Archive superseded drafts, confirm the final briefing, close open questions, and record the send in writing.
Keep the last send. When someone asks what they were told, you should be able to open the document, not reconstruct a dashboard state.
Inbox first
A dashboard is a place to look. A briefing is the thing people finish. Done well, it becomes the bridge between the numbers and a decision they can stand behind.
Teams that write the story first spend less time walking people through filters and more time answering the question they actually asked.