Stop Measuring Clicks, Start Measuring Time

# A New Metrics Playbook for Enterprise UX

ENTERPRISE UX · 4 MIN READ

In 30 seconds

Measure time, not engagement.

Consumer-app “engagement” metrics are dangerously wrong for mandatory enterprise software. Good tools give users back their time.


01 · TIME ON TASK

Measure how fast a user gets in, finishes the job, and gets out—not session duration.


02 · USER ERROR RATE

Count costly mistakes, not clicks. High clicks often signal a confusing interface.


03 · TASK SUCCESS RATE

Could the user actually complete what they came to do? Yes or no.

I've spent the last few weeks trying to get our design team's playbook in order on our internal wiki. It's a soul-destroying task, mostly because you quickly realise that half of the 'rules' you've all been following are based on nothing more than outdated habits and imported nonsense.

And nowhere is this more obvious than in how we measure success.

Every month, the entire company gathers for the all-hands meeting, a ritual led from the very top. And every month, we are shown a series of charts. They all point, as they must, up and to the right. We all nod along as the latest meaningless metrics are paraded before us: page views per module, the general number of support tickets, and other figures that bear only a passing resemblance to actual user success.

It is a magnificent piece of corporate theatre. And it is almost completely useless.

This plague of "success theatre" is fuelled by a single, seductive, and utterly useless word: "engagement."

We are told to celebrate when users spend more time in our app. We are told to cheer when they click more things. This is the conventional wisdom, handed down from the consumer-app cathedrals of Silicon Valley. And for enterprise software, it is dangerously wrong.

Celebrating that an employee is 'engaging' more with your mandatory internal software is like a hammer manufacturer celebrating that it now takes twice as long to hammer in a nail. It's a sign that you have failed, spectacularly.

The user of a social media app is a customer. The user of enterprise software is an employee. They are a captive audience. They are not there to be "delighted" or "engaged." They are there to do a job, a job that is often stressful, complex, and time-sensitive. Our software is a tool, and the only measure of a good tool is how efficiently it gets the job done.

In the world of enterprise software, there is only one metric that truly matters: Time.

Every decision we make should be judged against a single, brutal question: does this give the user back their time, or does it steal more of it? If you want to build a metrics strategy that actually means something, you need to throw out the consumer playbook and start measuring what matters. Here’s a new one.

01 · THE ENTERPRISE METRICS PLAYBOOK

Three metrics that actually matter

01 · NOT SESSION DURATION

Measure Time on Task

Start measuring, with a stopwatch if you have to, how quickly they can get in, do the specific task they came to do, and get out. A 20% reduction is a real, quantifiable productivity gain.

02 · NOT CLICKS

Measure User Error Rate

An error in a stowage plan or an off-hire claim is a multi-million-pound problem. A high click count is often a symptom of confusion; a low error rate prevents costly failures.

03 · NOT ENGAGEMENT

Measure Task Success Rate

Could the user actually do the thing they came to do? Yes or no. If a Chief Officer gives up halfway through a safety compliance form, that is a 0% task success rate.

When you start measuring time, errors, and success, something magical happens. The conversation with your stakeholders changes. You are no longer having subjective arguments about the colour of a button. You are having objective, evidence-based discussions about efficiency, productivity, and risk. You are, in other words, finally speaking their language.

Let's stop celebrating engagement and start celebrating efficiency. Let's give our users back their most valuable asset. Their time.

CALL TO ACTION

What useless metric have you seen teams obsess over?

What's the most useless metric you've ever seen a team obsess over, and what should they have been measuring instead?