Operations / Field guide
Build an operations dashboard around exceptions
A wall of green metrics can hide one order that needs action today. Design the view around who must do what next.
2XD Studio · · 2 min read
Start with a morning decision
Ask a dispatcher what makes them open the CRM, a spreadsheet, and a shared inbox before nine. A useful answer is concrete: identify orders due today with no assigned driver. Define exactly what due today means and which system is authoritative for the assignment.
Make each row actionable
Show the order reference, deadline, current owner, last update, and a link to the record. Distinguish a missing assignment from an unavailable source. A disconnected dispatch feed should produce a source warning, not a list claiming that every driver is absent.
Close the loop after intervention
Let the owner acknowledge or resolve an item and record the time. Decide when an item should reopen; a changed delivery date may invalidate yesterday's decision. Review the queue after a week and remove alerts that never lead to a meaningful action. A shorter, trusted queue is easier to operate than a comprehensive list nobody checks.
Audit the empty state
An empty queue can mean every order is assigned or that the feed never ran. Display a last-success marker and the number of source records examined. Test a normal empty day alongside a failed import. The first should let the dispatcher move on; the second should direct someone to the connection that needs attention.
Reader questions
Should the dashboard automatically fix exceptions?
Start by proving that the exceptions are real. Then consider narrowly scoped actions with clear evidence and approval rules.
What is a useful success measure?
Count overdue unresolved items and time to ownership, alongside the rate of incorrectly flagged records.