A number is not a decision

There’s often a panel like this:

“Daily sales: 2,400 ₼.”

The number looks right. The layout is tidy. The chart is green.

A little later the manager writes in WhatsApp:

“How did today go?”

That question is already a warning.

If the report has a number, but nobody can make a concrete decision with it, there is no management on the screen — only a total.

Why does this happen?

Reports often answer “what is easy to sum?”

Business asks “who will do what with this number?”

Those are not the same question.

The sales total can be correct. Closing a shift may still need zone, open balances, payment mix, or cancellations. If the number doesn’t show them, the manager asks people again.

Then the system looks like it’s working.

In reality the decision still lives in chats and memory.

Common wrong measures

The mix-up usually arrives in familiar words:

• “Completed orders” — the status is done, but not all money may be in the till.
• “Guest count” — that is not occupancy or revenue.
• “Payment count” — that is not the till total; partial payments and refunds are different.

Each can be useful in the right place. The problem is reading a “good day” from an answer to the wrong question.

One question first

Before a report, I usually ask:

“Who decides what with this number?”

The answer should be short.

• Can we close the shift?
• Which zone still has capacity?
• Who will collect the open balance?
• Can we send today’s total to the owner?

When the question is clear, the metric is clear. When it isn’t, people will keep asking each other — no matter how pretty the dashboard is.

Takeaway

Having a number in the system is not management.

Management is when the number answers a concrete question.

Write the question first.

Then the report.