The Waiter Who Served Clarity: Onboarding as a Product Decision
A great feature nobody discovers is a wasted feature. The difference between shipping and success is often one well-placed nudge.
I was at a self-service restaurant the other day and noticed something interesting. There was a waiter whose only job was to tell people it is self-service. At first it felt unnecessary, until I saw how many customers were confused. He was not serving food. He was serving clarity.
It reminded me of a common product challenge. You ship a feature that actually solves the right problem, but users do not discover it. You start wondering if it was unnecessary. But often, it is just undiscovered.
Guidance, not tutorials
Even the smartest apps need guidance. Not tutorials. Just the right nudge at the right time. Good onboarding guides without interrupting. It teaches through timing and context, right when the feature becomes relevant in the user's journey.
Building with intention means you do not stop at it works. You build until it is understood.
It is a culture problem, not a process problem
Here is the catch. Most teams, especially local ones, are too busy building features to design smart onboarding. And that is not a process problem. It is a culture problem. If you only celebrate what is shipped, nobody gets rewarded for what is understood.
The fix is to treat discoverability as part of the feature, not an afterthought. Before you ship something new, ask how a user will first learn it exists. If the answer is they will figure it out, you have not finished the feature.
The waiter in the restaurant understood something most product teams miss. The best feature in the world is worthless if people do not know how to use it. Sometimes the highest-value work is not building more. It is making what you already built obvious.