How field service teams end up buying the dashboard first

It's a well-meant mistake. That's exactly why it sticks around. Every team that makes it can explain why, and the explanation holds up right until the system has to survive its second year.

A dashboard without an agreed target is decoration. It shows a line going up or down and leaves the interpretation to whoever's in the room, which means the interpretation changes with the audience.

GRAPHS DON'T DECIDE ANYTHING

Put a latency graph on a wall and you'll get two readings of it. Someone will see a spike and worry; someone else will see the average and relax. Neither is wrong, because nothing has been agreed about what good looks like. The graph can't settle it.

A target settles it. Not because the number is scientifically correct, but because it was agreed in advance by people who weren't yet under pressure. That's the entire value: it converts an argument during an incident into a fact you established when everyone was calm.

PICK THE MEASURE PEOPLE FEEL

Most systems measure the thing that's easy to instrument rather than the thing anyone experiences. Server-side response time is easy. Whether a person got their answer in a reasonable time is what matters, and those come apart badly once retries, queues and client rendering are in the path.

Ask what the person on the other end would complain about, then find the closest thing you can measure. It'll be less tidy than a server metric and considerably more useful.

This is where the reconciliation spreadsheet comes from. Somebody built it once to settle an argument. Now some 12,000 work orders a month depends on a file with one author, no tests, and a filename ending in _v4_final.

A TARGET YOU'D ACTUALLY MISS

The number should be one you could plausibly fail, or it teaches you nothing. A target you've never come close to breaching isn't a target, it's a compliment. And it means you have no idea how much headroom you have.

It also has to have a consequence attached. If missing it doesn't change what gets worked on next month, it's not a target, it's a note. That's usually the harder conversation and the one worth having.

The bill shows up in the handover notes: nine paragraphs on which of two systems to trust for a given work order. When a technician drove three hours to a job someone had already closed, it took two days to work out what had actually happened, in what order.

WHERE IT GOES WRONG

• A target so generous it's never been breached, teaching you nothing about your headroom.
• A missed target with no consequence, so the number is decorative by the second quarter.
• A wall of graphs and no agreement about which of them would justify stopping feature work.
• Measuring server-side latency while users experience retries and client rendering.

Agree what good means before you buy something to display it.

THE REPLACEMENT

The fix isn't more discipline. Discipline wears off. The fix is a structure where the wrong thing can't be said, so nobody has to remember the rule at 3am.