Chrono Log

← The Log

Jun 27 2026 · 1 min read · Evidence

How to build reports that help people make decisions

Start reporting work with the decision it should support, then choose the numbers, systems, and definitions needed to make that decision easier.

Reporting work usually starts with the tool. What can the CRM show? What can the booking system export? What can we filter by: date, city, channel, or rep? Reasonable questions, but none of them is the first one.

The first question is what decision the report is supposed to make easier.

Here is the difference in practice. “Sales by city, last twelve months” is a clean-looking chart that changes nothing on its own. Turn it into a decision and it earns its place: “Which two cities are growing fast enough that we should add capacity before summer?” Same underlying data. One is a wall decoration; the other tells someone what to do on Monday.

When a report does not connect to a decision, it becomes one more thing to check. And the failure is often not the report itself. Sometimes the question was never clear. Sometimes the answer is split across three tools. Sometimes two systems use the same word differently: one counts a quote as a sale, another counts only paid work. A dashboard can look polished and still leave you unsure what to do.

Try this today. List the three reports you open most. For each, finish this sentence: “This report helps us decide ___,” and name what you would do differently if the answer were trustworthy. Any report where you cannot finish the sentence is not earning its place. Tie it to a real decision, or stop opening it.

A good report does not only show what happened. It makes the next decision easier to make.

Always expect friction.

Chrono Log

One idea you can use, in about a minute.

New notes from real operating work, sent as they are written.