There's a moment that happens in poorly designed IT self-service where someone gives up. You can almost see it. They're in the portal, looking for a password reset or trying to request software access, and something about the interface or the flow makes them decide it's faster to just email IT directly. And they're probably right. So they do. And IT gets the ticket anyway, and the self-service portal sits there unused, and everyone pretends it was a good investment.
The organizations that have actually cracked this do something that sounds obvious but apparently isn't: they design for the moment right before someone gives up.
Take password resets as an example, since it's the most common thing people try to do in self-service. A good implementation doesn't make you answer three security questions from a list you set up six years ago and have completely forgotten. It just sends you a link to your email, you click it, you pick a new password, done. Ninety seconds. The person trying to reset their password isn't interested in security theater. They want their password reset. The system that respects this gets used.
Same logic applies across the board. Request new software? You fill out a form that's actually as simple as the form looks, not a form with hidden fields that appear based on answers to previous fields, creating a choose-your-own-adventure of bureaucratic confusion. Request access to a resource? The system either gives it to you immediately (because it can), or tells you exactly who needs to approve it and how long it'll take (because clarity beats mystery). When something requires human review, the portal doesn't just vanish your request into the void. You can see where it is, who's looking at it, what's holding it up.
The successful ones also get the basics right in ways that seem small until you're not doing them. They're actually fast. Not theoretically fast, but genuinely fast. Load times matter. Search that works matters. The ability to find what you need without clicking through six layers of categorization matters. Teams integration matters too. If people can do something directly through Teams without switching to a separate portal, they will, and the organizations that have enabled that have basically solved their engagement problem.
What's interesting is how much of this comes down to actual thoughtfulness rather than money. Some of the most clunky self-service systems are expensive enterprise platforms. Some of the most fluid ones are built by smaller teams who just treated the end user experience as non-negotiable. That's not to say money doesn't help, but it's not the main variable.
The thing that separates working self-service from the other kind is that last detail: respecting people's time. If someone is using your self-service portal, they're already trying to help themselves. They're not choosing difficulty. They just want to move forward. The portals that understand this get used not because they're mandatory, but because they're actually quicker and less annoying than the alternative.
That's the whole game. Everything else is just execution.