The courage to disappoint the dashboard
A useful measure becomes dangerous when defending the work requires hiding what it cannot see.
Public reading preview. Factual, interpretive, editorial and rights reviews remain pending.
A dashboard gives a meeting something to look at. The columns stay still while people explain themselves. A red number can ask for attention without saying a word. Work that has no column must arrive through a person, with all the hesitation and inconvenience that entails.
This creates a particular test of leadership. Can someone explain that the number improved while the work became worse, and expect to be heard?
Consider a hypothetical creative team using AI to help prepare product descriptions for a small independent retailer. The weekly report counts descriptions completed and time spent on each. Output rises. The shop owner is pleased: the team has time to improve material that used to remain unfinished.
One editor begins spending longer on a few objects. A handmade bowl has an irregular glaze that changes how it feels to hold. Another piece needs an explanation of why its visible repair is part of its history. The generated descriptions are smooth and broadly accurate. They make the objects sound interchangeable.
The editor wants to preserve the distinctions a customer would notice in the shop. Her slower work lowers the completion figure. At the review, she can defend that choice, quietly stop making it, or find a way to make the report look better without changing the underlying work. The dashboard has become part of the education the team receives about what matters here.
In the opening chapter of Understanding Media, Marshall McLuhan directs attention to how a medium changes the scale, pace, and pattern of human affairs. Applied to a work dashboard, the question is what its form encourages people to notice and repeat.
A measure does not have to be false to narrow the account. The completion count can be perfectly accurate. It simply cannot tell the meeting whether the descriptions preserve the character of the objects, help a buyer choose, or earn the shop's name. Those questions require a closer encounter with the work.
That encounter may confirm the editor's judgment. It may also reveal that she is polishing distinctions customers do not need while important work waits. An appeal to quality should not end scrutiny. It should give the team something specific to scrutinize beyond the number.
The leader's courage is therefore more demanding than dismissing metrics. It involves accepting a less flattering report long enough to examine what the report omits. It also involves making a decision after the examination. Otherwise every discussion of quality becomes an honorable reason to leave priorities unresolved.
AI can help the team produce options and compare what each description preserves. Increased capacity is valuable if the team uses some of it to make finer distinctions. The opportunity is to improve the work people came for, rather than allow the easiest count of completed work to define their ambition.
The practice
At your next review, choose one measure people care about. Ask for a concrete example in which doing the job well might make that number worse. Give the question a narrow scope. You are examining one reporting habit, not announcing that measurement has failed.
Put the example beside the dashboard. For the retailer, that means reading a generic description and a carefully distinguished version while looking at the actual object. Ask what a customer would need to understand, what the additional work costs, and whether a simpler change could preserve the important difference.
Write a short exception note. Record what the measure shows, what the example adds, and the decision the team will make. If slower work is justified, name where it belongs and where it does not. Keep the note with the review agenda so the next meeting inherits the reasoning instead of another unexplained exception.
Use the same measure for the next two reviews, with the exception note available. Notice whether people bring useful examples earlier, whether the team changes a priority, and whether the extra discussion improves a specific piece of work. Ask who is doing additional labor to supply what the dashboard omits. Their attention has a cost too.
Do not respond to every omission by adding another score. Sometimes a regular encounter with a piece of work is the better companion to measurement. The aim is a reporting surface that helps people attend to their purpose. A leader should be able to disappoint the dashboard while giving the work a more honest account.
Adapted from Nikos Acuña’s supplied manuscript. Prepared with AI assistance. Preview v1.0.
Final editorial approval pending. Sources are linked in the margin.