Skip to content
All insights

The record

When the dashboard misses the problem

A reported status tells you something about the work. It may not tell you whether the customer’s need was met. Why that distinction changes what businesses should monitor.

A status is an answer to a particular question

A closed request tells you that a workflow reached its closing step. An on-time task tells you that a recorded activity met its deadline. Both can be accurate while the underlying business problem remains unresolved.

The difficulty begins when the organization treats those measures as answers to a broader question. Did the work fulfill the agreement? Can the customer now do what they needed to do? Has the condition that caused the complaint actually changed?

Our view is that a dashboard should be a starting point for understanding those outcomes. When the evidence disagrees with the status, the disagreement deserves attention.

Activity can become a misleading measure

Slack’s 2023 State of Work research found that employees reported spending an average of 32% of their time on work intended to appear productive without contributing to company or team goals. The global survey covered more than 18,000 desk workers. That is a reported behavior, not a measure of every organization.

The finding is a reason to examine what a business rewards and reviews. If the visible measure is the number of requests closed, the organization may become good at closing requests without becoming equally good at resolving the issues behind them.

This does not require bad intentions. People usually work within the definitions and tools they are given. Improving the measurement means making the desired outcome explicit and connecting it to evidence that can actually establish it.

Sources: [1]

Compare the report with the experience it represents

Google’s Site Reliability Engineering guidance distinguishes the symptoms users experience from the internal causes engineers investigate. It combines observation of a service from the outside with information about how the service is operating internally.

For a broader business, we see a useful parallel. A work record describes an internal process. A customer’s report describes an experience. An agreement describes the outcome the business committed to provide. Comparing the three can expose a gap that none of them establishes alone.

If a customer continues reporting the same unmet requirement after a task is closed, the next step is to check what the completed work covered. The complaint and the closed task may concern different things. If they concern the same requirement, the business has a concrete reason to reopen the question of fulfillment.

Sources: [2]

Corroboration requires more than repeated wording

Three messages copied from one original complaint are not three independent confirmations. A useful assessment checks where each statement came from, what it refers to and whether it describes the same period of time.

The strongest explanation connects different kinds of evidence. The agreement establishes the requirement. The completion record establishes the work performed. A subsequent customer confirmation establishes whether the result met the need. Together, these can support a conclusion that is more precise than a general warning about account health.

Missing evidence should remain visible. The absence of a confirmation does not prove the customer is unhappy. It tells the business which part of the outcome has not yet been established.

Make the next step part of the finding

A useful finding should leave someone able to act. It identifies what remains unresolved, who can investigate it and which evidence would change the assessment. That might lead to more work, a corrected record or confirmation that the original obligation has already been met.

This is the standard we use when thinking about attention in Orcinta. A list of suspicious differences creates another queue to manage. A supported explanation of a consequential gap helps the responsible team decide what to do.

The business still needs its dashboards. It also needs a way to question what they imply, especially when the people experiencing the work are telling a different story.

A reported completion becomes useful when it can be connected to the outcome that matters.

Sources and further reading

  1. 1
    State of Work research, 2023

    Salesforce and Slack

  2. 2
    Monitoring Distributed Systems

    Google, Site Reliability Engineering

Essential

Always on

Remembers your cookie choice for 180 days so it can be respected on your next visit.

No analytics or advertising cookies are currently used on this website. Closing this window leaves your saved choice unchanged.