The Cursor That's Already There

Turn on two-factor authentication in our CMS, log in, and the cursor is already sitting in the box waiting for your code. You don't have to click into it. You probably won't notice it's there at all. You'd notice straight away if it wasn't.

That's the whole thing. A cursor in the right place at the right moment, saving you a click and about half a second. On its own it's nothing. I'm writing several hundred words about it anyway, because it was never really about the cursor.

The half-second you'd never miss, until you do

Think about how often the opposite happens. You open a login screen and have to click into the email field before you can type a single character. A form asks for your details, then makes you go hunting for the next box. A two-factor page loads, the code is already on your phone, and the cursor is nowhere near where it needs to be, so you reach for the mouse, click, and go back to the keyboard.

None of that is a disaster. Each one costs you a moment and a small flicker of irritation. But you meet these moments dozens of times a day, across every tool you touch, and they add up. Not into anything you'd ever write down. Just a low background hum of friction that makes software feel like harder work than it should be.

Nobody puts it in the brief

No client has ever asked me to auto-focus a login field. It isn't the sort of thing that makes it into a specification. It's too small to name, and you only ever feel its absence, never its presence.

Which is exactly why it's a useful test. The things people remember to ask for get done by almost everyone. It's the things nobody asks for that separate software built with care from software assembled to a checklist. When you fix the bits no one will ever thank you for, you're doing it because you think it matters, not because someone is watching.

This is part of what I mean when I talk about what bespoke actually means. It isn't only a custom design on the front. It's having a say over every small decision behind it, right down to where the cursor lands.

Attention is an attitude, not a feature

You can't really retrofit this. You can't reach the end of a build, look at a long list of tiny frictions, and sand them all off in an afternoon. There are too many, and most stay invisible until someone hits them. The only way to get them right is to care about them as you go, on every screen, every form, every step.

So when I say it comes down to attitude and intent, that's what I mean. The cursor in the two-factor box isn't clever engineering. It's a sign that the person building the thing was thinking about the person using it. That instinct shows up everywhere or nowhere. You can't apply it to the screens that seem important and skip it on the rest, because you don't get to decide in advance which ones the user will care about.

It's the same instinct behind making it easy to say hello, just turned towards the people running the site rather than the people visiting it. Take the friction out of the path. Don't make someone work for something the software could have handled for them.

Why it's hard to buy off the shelf

Generic platforms struggle with this, and it isn't really their fault. A tool that has to serve a million businesses has to stay general. It smooths the big, common edges and leaves the small, specific ones alone, because your particular way of working is one of a thousand it's trying to cover at the same time. The result works. It rarely feels like it was built for the way you actually work.

When you build the thing yourself, for the people who will use it every day, you get to make the small calls. Where the cursor goes. Which action sits closest to hand. What happens the moment after you hit save. None of it is headline material. All of it is the difference between a tool you tolerate and one you barely have to think about.

I'm not going to pretend we get every one of these right. There's always another small friction we haven't spotted yet. But the intent is there, it's deliberate, and it runs through the whole thing rather than living in a feature list. The cursor is a small thing. The reason it's there isn't.

If you're using software that fights you on the small things every day, it's worth remembering it doesn't have to be like that. If you'd like to talk about what a tool built around the way you actually work might look like, get in touch.