Product craft · May 2026
Five unglamorous fixes that changed a product journey.
The best product work is often less dramatic than the story we tell about it.
On one account-creation journey, completion improved by 24%. There was no heroic redesign. We found five small places where the product was asking for confidence before it had made itself clear.
1. Name the thing people are looking at.
A field label that makes sense to the team can still be unfamiliar to everyone else. We used the language people already had for the information.
2. Explain why before asking.
A phone number is not a neutral request. A short, direct explanation of what it was for removed a question that had been quietly stopping people.
3. Make the button describe the action.
“Continue” hides the consequence. A label that says what happens next gives a person the confidence to move.
4. Move the nonessential work later.
Some tasks mattered, but not in the first minute. We stopped asking for them before the person had received any value.
5. Treat errors as a conversation.
An error message should answer three things: what happened, why it happened when useful, and what to do now. “Invalid input” answers none of them.
What I take from it
People were not failing the journey. The journey was failing to explain itself. A product earns completion by making the next step feel safe, specific, and worth taking.