Learnings from Lou Downe's book, Good Services: How to design services that work.
What is a service?
A service is simply someone trying to get something done.
The most important thing to remember is that only the user can determine what the service is. Users show up with a specific need, and it is our job to take care of the messy details behind the scenes so they easily get what or where they need to be. We have to care more about the people on the other end of the screen, making their day a little easier, than the pixels on the screen itself.
The best services are the ones you do not notice
People often say that good design is invisible, but that is not quite right. It is more accurate to say that when a service works perfectly, people simply are not looking at the design because they are focused on the task they set out to do.
What makes a good service is not a matter of personal taste. A service either works or it does not. The ultimate compliment from a user is the phrase, "I expected that to be a lot harder."
When we nail the basics and remove the friction, the tech and design fades into the background and life gets a little bit easier.
Three core principles that feel most relatable
These three principles stand out because they are easy to relate to, but often difficult to get right in practice.
Name the task, not the technology
Users look for what they think they need rather than what we have decided they need. This means we should name services using a solid understanding of the words the user uses. We should describe the task at hand and avoid internal acronyms or marketing promises.
For example, instead of saying "5000 mAh battery capacity", we should sell the benefit by saying "Stay connected for 24 hours". When the name reflects what the user is trying to do, it becomes findable and understandable for someone with no prior knowledge.
Decisions need space and visibility
It is a common mistake to think that fewer steps always make a better service. In reality, the number of steps in a journey should match the number of decisions a user has to make. People need space to think, especially when the stakes are high.
By breaking things down, you give users control. A well-placed pause is not a barrier, it gives the user the space to feel confident about their choice before moving forward.
There is a delicate balance between working in a familiar way, and breaking out of this to set a better way of working.
There is no such thing as a normal user
We cannot just build for the best-case scenario. We have to design for the user who is juggling a thousand other things while trying to use our service. We should design for a full spectrum of needs. This means considering people with physical or cognitive disabilities as well as those in short-term difficult circumstances.
When you design for the edge cases, you end up making the service better for everyone. And if someone is not eligible for your service, do not just ignore them. Give them a clear, intentional dead end with directions on what to do next.
95% of service design projects are about fixing the basics.
Why this matters for businesses
A seamless service is a successful one.
When we work in isolation, we end up handing our users a disjointed experience where the left hand does not know what the right is doing. That confusion is not just frustrating for the customer, it is expensive.
Bad services cost more in customer support because users are forced to ask for help when they cannot find or understand the solution.
Bad services cost more in support and lost trust.
At the end of the day, if your service is confusing or opaque, you lose the one thing you cannot buy: trust.
Efficiency does not come from building flashy new features. It comes from fixing the basics so you can stop wasting time solving the same avoidable problems over and over again.
A good service is consistent throughout.