A Service Design principle on how to make forms that don't make you crazy.
You try to log in to your banking account. You enter your username and password. Press okay. You have to type a second code that you receive on your phone. Feels secure. You like that. So you enter this long code and try not to make a mistake. You finish typing and watch your computer screen... Shit!
You forgot to click on the form field. So you have to type that stupid and long code again.
It's not a terrible situation. But it can make you grumpy. Especially when it happens again and again, but this is easy to fix:
Pre-select the form when a user goes on your website or app so that he can type right away.
Little side notes
- This is the second draft of this Service Design Principle.
- I was able to reduce the lengths of this principle by 35% compared to the first version.
- Once adapted, even more, this principle will be part of the book "Service Design Principles 201-300"
- As always comments and feedback to improve this principle are welcome
- If you have a personal story that goes in that direction it would also help if you share it
Patrick Marcelissen
Patrick Marcelissen
Something like " How can you prepare the next step in the journey of the customer?"
Daniele Catalanotto
I like your example of auto filling info. Maybe challenge people to make it easier? Like why can’t I just give my zip code and have the system figure out my city and state? Or if you’re selling mainly to the US and Canada, why does the drop down menu for country start with Afghanistan and go through most of the alphabet before the US. (I get why America = US is offensive, but …)
Daniele Catalanotto
I've also used your suggestions as examples in the footnotes (see below).
Daniele Catalanotto
The third draft of this Service Design Principle
Footnotes
Daniele’s notes