Sharing a dashboard without sharing everything

A dashboard built for one person and opened once a month is a report. A dashboard the team sees daily changes behaviour.

The second is far more valuable and carries a question the first never raises: who should see which numbers.

Build the board for a person, not for the data

A board holding everything the system knows is a database with colours, and nobody reads it twice.

A board answering the three questions one role asks each morning gets opened every day, which is the only measure that matters.

Different roles need different boards

A supervisor wants today's jobs and who is on them. An owner wants the month against the target and the money outstanding.

One board serving both serves neither, and building a second one costs far less than the confusion of a shared compromise.

Permissions belong to the data, not the dashboard

A widget showing revenue by staff member is fine for a manager and not for the team, and the widget cannot tell the difference.

Where the underlying records already restrict by role, the board inherits that automatically, and that is the arrangement to trust.

Say what each number counts

A tile reading Jobs could mean this week, this month, open, or completed, and two people reading it differently make opposing decisions.

A label naming the period and the filter removes that, and it costs a few words on the widget.

A dashboard is a prompt, not a report

The useful numbers are the ones somebody can act on today: overdue invoices, jobs without a person, quotes awaiting a reply.

Our guide to what to measure covers choosing those rather than the figures that merely look impressive.

Showing targets changes what people do

A number without a target is information. The same number beside what it should be is a prompt, and the difference in behaviour is immediate.

That also means a badly chosen target moves the team in the wrong direction quickly, so the choice deserves care.

Sharing a figure invites a conversation about it

A team seeing a metric will ask how the system works it out, and the question is usually a good one.

A business that cannot explain its own numbers plainly has a measurement problem the dashboard has just made visible.

Individual numbers need handling with care

A board ranking staff by output can motivate a strong team and demoralise a struggling one, and the context decides which.

Showing the team's total, with individual figures visible to that person and their manager, usually gets the benefit without the damage.

A stale board loses its authority

A dashboard showing last month because a data source broke teaches people to distrust every number on it.

A visible timestamp, and somebody who owns the board, is what keeps it trusted rather than quietly ignored.

Put the board where people already are

A dashboard behind three clicks gets opened on the first day and forgotten by the second week.

The landing screen, a phone home screen or a screen on a wall are where a shared board actually gets read.

Retire boards nobody opens

Dashboards accumulate, and a list of fifteen makes the two useful ones harder to find.

Opening counts answer which are which, and removing the rest is an improvement rather than a loss.

What to change first

• Each board answers the questions one role asks each morning
• Roles that ask different questions get different boards
• A board shows only what record level permissions already allow
• Every tile names the period and the filter behind it
• Numbers people can act on today take the prominent space
• Individual performance figures stay with the person and their manager
• A timestamp and a named owner keep the board trusted