On UI

I've been building out a set of systems for a pest control owner lately, and he's been loving the progress. But the most useful thing he gave me wasn't a compliment. It was a pattern.

Every single request he made, every one, was really the same request wearing different clothes: make me click less.

The theme hiding in every request

Here's a concrete example. The old way: go into the calendar, book the appointment, leave the calendar, open the documents section, dig around, and finally send the contract. Four features and a dozen clicks to do one obvious thing.

What he actually wanted: sitting right there on the appointment, hit a button, send the contract, the estimate, or the invoice. Done. Don't make me travel across the whole app to do the thing that's obviously related to the thing I'm already looking at.

Once I saw it in one request, I saw it in all of them. The entire wishlist boiled down to a single principle: fewer clicks, less thinking.

Technology for its own sake is a waste

You know me. I love this stuff. I love building. But technology for the sake of technology is silly. The entire point of software is to make someone's life easier, and here's the irony that trips up a lot of builders: the way you make their life easier is by making them use your software less.

Less clicking. Less thinking. Less time staring at your screen. Every click you remove is a small gift you're handing the person on the other end.

The three-second rule

There's a stat I love: advertising copy written at a fifth-grade reading level outperforms the fancy stuff. Simple wins. Clear wins.

The software version comes from Yu-kai Chou, who wrote Actionable Gamification: if a user looks at your interface and can't tell what to do within three seconds, it's not good enough. Not "they'll figure it out eventually." Not good enough. Three seconds, or you go back and simplify.

That's a brutal standard, and it should be. Your user shouldn't need a manual. They shouldn't need a tour. They should glance at the screen and just know.

Overkill is bad UI too

Here's the flip side, and it recently handed me a free sales pitch. We started offering domain hosting at Hyppo, and the second I lined it up against the big registrars, the difference was almost funny.

On GoDaddy or Squarespace, you get hit with a text message code every single time you want to change a DNS record. Sometimes three separate verifications just to log in. It's friction dressed up as protection, and it's miserable to actually use.

So when I walk a client through moving their domain over to us, I don't even have to sell it. Their old registrar's terrible UI does the selling for me. I just ask one question: "Do you want to stop getting thirty text messages every time you need to touch a DNS record?" Then, "and we'll do it at half the price as a bonus." That's the whole pitch. The friction they've been putting up with closes the deal.

That's the same lesson in reverse. Overkill is its own kind of bad UI. Making someone jump through five hoops to do one simple thing isn't safer or smarter, it's just annoying, and eventually it sends them looking for the exit.

We build for the person, not the demo

So when we build systems, we build them with the actual end user in mind, and we design them to take the fewest clicks and the least time possible. Because here's the truth most of software doesn't want to admit: your users don't want to look at your software.

They want to run their business. They want to go home and have dinner with their family. They do not want to troubleshoot thirty bugs or hunt for the one thing they need buried behind three hundred windows. The best compliment your software can get is that they barely noticed using it.

Good UI isn't about how much it can do. It's about how little it asks of the person using it. Make them click less. Make them think less. Give them their time back. That's the whole job.

Want software people actually enjoy using?

Built for the end user, fewest clicks, zero clutter. That's what we do at HyppoAI.

Build it right