Tweeted twitter.com/StackUX/status/834878566286360578
2 added 195 characters in body
source | link

My client says that is mandatory to send a code, so the developers suggest this screen where you have "mail field" for the code to be send, but besides that you have "code field". Both of them with his own cta's. I don't want to have 2 cta's in the same screen, really don't want to and I came up with this "solution?".

enter image description here

My question is:

¿How many UX axiomas am I tearing apart with a screen like this? and... How can I make the "forgot password" experience less stressfull for users counting on the client demands?

Save me from my suffering please.

Btw, I sent that screens to garbage and came up with something else (yeah, I copied it from instagram)

enter image description here

My client says that is mandatory to send a code, so the developers suggest this screen where you have "mail field" for the code to be send, but besides that you have "code field". Both of them with his own cta's. I don't want to have 2 cta's in the same screen, really don't want to and I came up with this "solution?".

enter image description here

My question is:

¿How many UX axiomas am I tearing apart with a screen like this? and... How can I make the "forgot password" experience less stressfull for users counting on the client demands?

Save me from my suffering please.

My client says that is mandatory to send a code, so the developers suggest this screen where you have "mail field" for the code to be send, but besides that you have "code field". Both of them with his own cta's. I don't want to have 2 cta's in the same screen, really don't want to and I came up with this "solution?".

enter image description here

My question is:

¿How many UX axiomas am I tearing apart with a screen like this? and... How can I make the "forgot password" experience less stressfull for users counting on the client demands?

Save me from my suffering please.

Btw, I sent that screens to garbage and came up with something else (yeah, I copied it from instagram)

enter image description here

1
source | link

The correct way to figure out how to solve my "forgot password" screen

My client says that is mandatory to send a code, so the developers suggest this screen where you have "mail field" for the code to be send, but besides that you have "code field". Both of them with his own cta's. I don't want to have 2 cta's in the same screen, really don't want to and I came up with this "solution?".

enter image description here

My question is:

¿How many UX axiomas am I tearing apart with a screen like this? and... How can I make the "forgot password" experience less stressfull for users counting on the client demands?

Save me from my suffering please.