Many teams have a report that arrives every Friday. It contains figures, coloured cells and a few paragraphs about what happened. People skim it, file it away and ask for another update on Monday.
The problem is not necessarily the spreadsheet. It may be that nobody has agreed what decision the report should support.
A useful weekly snapshot is not a smaller version of every system the team uses. It is a short account of what matters now, what has changed and where someone needs to act.
Start with the next decision
Before adding a metric, ask what someone will do differently after seeing it. A team handling customer requests might need to decide whether to redistribute work. A small retailer might need to know whether one delayed delivery requires a customer update.
These are different questions. They need different evidence. If a number cannot help answer a current question, it probably does not belong in the weekly view.
Write the question at the top in ordinary language: Are urgent requests being handled on time? Is a supplier delay likely to affect customers? Does someone need help with a growing queue?
Choose a few signals, not a wall of numbers
For each question, select the smallest measure that makes the situation visible. For a support queue, this could be the number of requests waiting beyond an agreed response window, not every activity count from the week.
Avoid creating a precise-looking percentage when the underlying records are incomplete or the sample is tiny. A simple count with a note about what it includes may be more trustworthy.
Keep the definition stable for long enough to see a pattern. If 'open' means one thing this week and another next week, the comparison will mislead.
Show change alongside context
A number by itself is rarely a plan. If six requests were delayed, readers need to know whether that is unusual, whether a temporary absence explains it and whether the delays affect anything important.
A brief line can provide more value than a chart: 'Six requests passed the agreed window; four are waiting for supplier information. We expect two replies tomorrow.'
State what is known and what is still uncertain. This helps people respond without turning an incomplete update into a confident prediction.
Leave room for the exception
Not every important issue appears in a trend. One access problem, missing approval or unhappy customer may deserve attention even when the overall numbers look fine.
Add a small section for exceptions that need a decision. Describe the consequence and the next sensible step rather than using the report to assign blame.
Keep customer names and personal information out of shared summaries unless access and a clear business need justify including them.
End with an owner and a next check
A short report should make the next conversation easier. If action is needed, name the person responsible, the next step and when the team will review the result.
Sometimes the right decision is to do nothing yet. Record that too, along with what would trigger a reconsideration. Otherwise the same discussion may restart each week.
Remove what nobody uses
After a month, ask which parts changed a decision, which merely repeated information available elsewhere and which were misunderstood.
Retire unnecessary fields. The report should become lighter as the team learns, not larger because every past request for a number was treated as permanent.
Good reporting is a small form of care for people's attention. It gives colleagues enough context to act, without asking them to study a dashboard before doing their actual work.