# I have a dashboard but still don't know where we stand. Why?

Because a dashboard can only show what someone wrote down. A number is true if it was written, and you can trust it if you can open it back to its records.

Published: 2026-10-12  
Canonical: https://felesh.ai/blog/i-have-a-dashboard-but-still-dont-know-where-we-stand-why

## The short answer

You have a dashboard, with tidy figures and clean charts, and you still cannot say where the business stands. That is not a failure of your judgement. It is usually a problem with what sits underneath the dashboard.

A dashboard draws a picture of the records behind it. If the work was never written down, the picture is a neat drawing of gaps. A number is true only if it was written. It is trustworthy when you can open it and see the records it came from.

## Why does a dashboard show numbers you cannot rely on?

Most dashboards fail in the same few ways.

The first is thin writing. A call happened, a promise was made, a customer asked for something, and none of it reached the record. The dashboard counts what was typed. It cannot count what stayed in your head or on the back of an envelope.

The second is loose words. One person marks a job as finished when the work is done. Another marks it finished when the invoice goes out. The chart adds them together as if they meant the same thing.

The third is age. A figure sits on the screen and nobody can say when it was last true.

The fourth is the one that does the most harm. You cannot open the number. It says a figure, you doubt it, and there is nowhere to click through to the customers and conversations behind it. So you argue with it from memory, and memory usually wins.

## What makes a number worth trusting?

Four plain things.

It was written by someone, at the time, about something that happened. It carries a date. It means the same thing every time it is counted. And it opens to its records, so that when it looks wrong you can see why.

The last point matters most. A number you can open is one you can correct. A number you cannot open is one you either believe or ignore. Neither is a good way to run the work.

Notice that none of this is about the chart. A better-looking dashboard on the same thin records gives you the same doubt in a nicer font.

## What does this look like at a year-end review?

Picture the review. You sit down to look back over the year's work, and you open the dashboard. One figure looks low. Customers you remember promising things to do not seem to be in it. You start to say so, and realise you cannot prove it either way.

So the review turns into reconstruction. You scroll through your inbox. You ask the people you work with what they remember. You piece the year together from fragments, and by the end the dashboard has been quietly set aside. You are back to going by feel, which is where you started.

The dashboard did not cause this. The year simply was not written down in a form it could count.

## How does Felesh keep the numbers honest?

Felesh begins with the writing, because that is where the numbers come from. Here is how it goes in an ordinary week.

1. A conversation ends. You type one sentence about what happened.
2. Felesh drafts a note, the promise with its date if you said one, and the next step. Each draft shows its reason and waits for your yes. You will see it as a "Review draft".
3. A task is added directly. There is no approval step for tasks.
4. Later, you ask a question in your own words, such as which promises to customers are still open. Felesh answers from your own records.

That last step is why the earlier ones matter. Felesh has no figures of its own. It does not bring numbers in from somewhere else, and it does not estimate. When you ask, it answers from what was written on Felesh, and what was written is what you put there or said yes to.

Felesh has [dashboards](/features#dashboards) that read your own records, and any number opens the records behind it.

So the answer to "where do we stand?" is no longer a chart you have to believe. It is a reply built from notes, promises and tasks that exist in your records.

## What if some of the work happens somewhere Felesh cannot see?

Then it will not be in the answer, and it is better to know that than to find out at year end.

Felesh knows what is done on Felesh. It knows the files you import: contacts and companies can be brought in from one Excel or CSV file, and you see the column mapping and the rows before anything is saved. It knows what you upload or teach it, such as documents and written instructions.

It does not read your mail or your drives, and it does not connect to other tools. If a conversation happened over a channel you never typed up, there is no record of it, and no question can recover it.

That sounds like a limit, and it is one. It also keeps every answer honest. A reply from Felesh can be traced to something that was written on Felesh. Nothing arrives from a source you cannot see.

## How do you check a number before you rely on it?

Whatever you use, ask four things of any figure.

Who wrote the thing it counts, and when? Does the word it counts mean the same each time? Can you open it and see the records behind it? And what work is missing because it never reached the record?

If you can answer all four, trust the number. If you cannot answer the last one, treat the number as a floor, not a total.

One more point on what the numbers are about. They should describe the work: a quiet customer, a promise that has gone past its date, a job waiting on a reply. They should not be a way of watching the people doing the work. A figure that follows the work helps everyone. A figure that follows a person turns the records into something people stop writing in, and then the numbers fail again.

## Where to start

Pick one conversation this week and type one sentence about what happened, then ask Felesh a question about it later in your own words. To see how the records and the questions fit together, read about dashboards and asking.