Not another dashboard: turning answers into decisions

Almost every feedback tool comes with a dashboard. Charts, filters, a score over time, a word cloud. On the day it launches, everyone looks at it. A month later, nobody does.

That’s not because people don’t care about feedback. It’s because a dashboard asks them to do the hardest part themselves: work out what the numbers mean and what to do about them. Busy people don’t have time for that, so the dashboard waits, and the insights wait with it.

What people actually need

The person running a restaurant, a housing team or a department doesn’t need more data. They need answers to three questions:

1. What changed?
2. Why?
3. What should I do about it?

If you can answer those three in a few sentences, you’ve done more than most dashboards ever will.

That’s it. Four lines, read in half a minute, and the next step is clear.

Let people speak for themselves

The “why” is where most summaries go wrong. It’s tempting to turn everything into neat categories: service, price, atmosphere. But “service” doesn’t tell you whether people are unhappy about unfriendly staff or about waiting. Their own words do.

A good summary groups answers into themes, says how often each theme comes up and shows a few of the actual answers behind it. That way the reader can trust the summary, and check it if they want to.

Make recommendations small and concrete

“Improve service” is not a recommendation. “Add an extra server on Fridays between 8 and 10 PM” is. A good recommendation is:

• Specific enough that someone can do it next week.
• Small enough that it doesn’t need a project plan.
• Testable, so next week’s numbers show whether it helped.

Not every week needs a recommendation. Sometimes the honest answer is “nothing changed, keep going”. That’s useful too.

Compare, don’t just count

A single score over time tells you little. The same score by location, team or product tells you a lot. If one location drops while the others stay the same, you know where to look. If everything drops at once, the cause is probably something you changed for everyone.

Send it to where people already are

The best place for this summary is not a separate tool with a separate login. It’s the inbox, on a fixed day, at a time when people plan their week. Monday morning works well. The point is that the insight comes to the person, instead of the person having to go looking for it.

Close the loop internally

A recommendation only helps if someone acts on it. Make it clear who does what, and by when. Then use next week’s message to show whether it worked. Over time, this builds a habit: every week, one small decision based on what people actually said.

Start without any charts

Next time you collect feedback, try this before you build anything: write the summary as three lines. What changed, why, and what you’d do. If you can’t write those lines, more charts won’t help. If you can, you may not need the charts at all.

That’s how Voisana reports back: not with another dashboard, but with a short message that tells you what to do. You can see an example on our homepage.