Back to Blog

How we work

A number behind a key is a number nobody looks at twice

By Maria Catalina Kovacs · 28 October 2026 · 4 min read

A number you have to go and unlock is a number you look at in the first week and never again.

We built a page that shows how many people read what we write. It was correct, it worked, and for weeks it was opened about as often as a filing cabinet. Nothing was broken. That is what makes it worth writing about.

The page was fine

Counts per day. A chart. Which article, which link people arrived through. Everything you would want, and all of it accurate.

It sat behind a key, which was the correct decision. The numbers are ours and a public counter invites somebody to make it interesting.

And then it was barely used.

Not because anybody disliked it. Because the key was typed once, on a laptop, and the person who wanted the numbers is almost never at that laptop. She is on a phone, between other things, and that phone had never been given the key. By the time it mattered there were several keys and no memory of which was which.

A number you have to go and unlock is a number you look at in the first week and never again.

The fix we built first, which was wrong

The obvious engineering answer is to remove the typing. So that is what we built.

A signed link, carried in a notification. Tap it on any device and the numbers open with nothing to enter. The signature is checked by the function that made it, it expires after a fortnight so an old notification is not a permanent door, and the payload is namespaced so a link minted for one purpose cannot be presented for another.

It is a nice piece of work. It took about an hour. It was still the wrong answer, and it would have stayed wrong no matter how well it was built.

Because it solved the stated problem, which was the typing, and left the real one untouched: the numbers were on a page nobody had any habit of opening. We had made it easier to arrive somewhere nobody was going.

The fix that worked, which took ten minutes

The question was never how do we remove the key.

The question was: which screen is this person already on, every day, without being reminded?

There was one. The page where comments are read and approved gets opened daily, because a comment is a person waiting for an answer and that is a pull nothing else has. The key for it is already on the phone.

So the numbers were put at the foot of that page. Three days, each with its date written out in full, each showing the change against the day before, and a line underneath saying exactly what is being counted. The morning notification was pointed at that page instead of the other one.

Ten minutes. No new page, no new key, no new habit to form. It is now read every day, because it is sitting under something that was already being read every day.

Why this keeps happening

This is not a story about analytics and it is not a story about one page. It is a thing software people do constantly, and we did it with an hour of good engineering to show for it.

We built the correct thing, confirmed it was correct, and were then quietly surprised that it was not used. When something is correct and unused, the instinct is to make it easier to reach. That instinct produces links, shortcuts, reminders and eventually notifications nagging somebody toward a destination they have no reason to visit.

The useful question is not whether the thing works. It is:

Correct and unused is not a discoverability problem. It is usually a place problem, and the fix is not a better route. It is a different destination.

  • <b>Where is this person already standing</b>, every day, without being asked?
  • <b>What already pulls them there?</b> Something waiting for them, something unfinished, something with a person on the other end of it.
  • <b>Can this live there instead?</b> Almost always yes, and almost always for a fraction of the effort of building somewhere new.

What it costs to get this wrong

Nothing dramatic, which is exactly why it survives.

A correct, unused page does not fail. It does not raise an error or appear in a log. It sits there being right, and the organisation quietly concludes that nobody wanted the information, when what actually happened is that it was put somewhere nobody goes.

That conclusion is expensive, because the next thing that gets built is a better version of the same page, in the same place.

Nothing here describes our infrastructure beyond the shape of the idea: no addresses, no identifiers, no names of anything that holds a credential.

A measurement nobody looks at is not a measurement. Before building the dashboard, find out which screen the person is already on, and put it there instead. It is almost always a smaller job than the one you were about to do, and it is the only version that gets read.

MK!

Maria Catalina Kovacs

There is no tracking on this site. No analytics, no cookies, nothing recording where you went or how long you stayed.

But I would like to know if something here was worth your time. If it was, press the heart. It tells me nothing about you. It is a number going up, and it is what tells me to keep writing.

Share this article

XLinkedIn

If you want more of this, I am on X. @Queendemetriak