Skip to main content
spelling, grammar and incorrect tag removal
Source Link
Devin
  • 38.3k
  • 15
  • 81
  • 143

Summary: Currently, our standards are to have green colored buttons for primary actions and links for secondary actions. SomeIn some cases we use red for deletesbuttons, such as for exampledelete actions. 

The problem I am havinghave now is that we are findingfind that most people who say they need username help with their username also need to reset their password reset. This would requiremean that the user would have to go through the security process twice, once to get the username and once to getreset the password reset. 

The solution was decidedis to giveallow the user the ability to havereset their password reset after completingthey have completed the security process for gettingobtaining the username. OfThis of course this now means that we now have one action to just get just the username, and another action to get the username and get a link to create a new password. I am trying to figure out how to have two primary actions that don't really have a preferred choice. 

My startingquestion is: how to have two primary actions that do not really have a preferred choice?

My first mock up-up is below (please ignore the grammar in the text):

Mock up of the screen I was proposing allowing the user to choose whether they want to get the username only or also have their password reset.

Summary: Currently our standards are to have green colored buttons for primary actions and links for secondary actions. Some cases we use red for deletes for example. The problem I am having now is we are finding that most people who say they need username help also need their password reset. This would require the user to go through the security process twice, once to get username and once to get the password reset. The solution was decided to give the user the ability to have their password reset after completing the security for getting the username. Of course this now means we have one action to just get the username and another action to get the username and get a link to create a new password. I am trying to figure out how to have two primary actions that don't really have a preferred choice. My starting mock up is below (please ignore the grammar in the text):

Mock up of the screen I was proposing allowing the user to choose whether they want to get the username only or also have their password reset.

Currently, our standards are green colored buttons for primary actions and links for secondary actions. In some cases we use red buttons, such as for delete actions. 

The problem I have now is that we find that most people who say they need help with their username also need to reset their password. This would mean that the user would have to go through the security process twice, once to get the username and once to reset the password. 

The solution is to allow the user to reset their password after they have completed the security process for obtaining the username. This of course means that we now have one action to get just the username, and another action to get the username and get a link to create a new password. 

My question is: how to have two primary actions that do not really have a preferred choice?

My first mock-up is below (please ignore the grammar in the text):

Mock up of the screen I was proposing allowing the user to choose whether they want to get the username only or also have their password reset.

added 40 characters in body
Source Link

Summary: Currently our standards are to have green colored buttons for primary actions and links for secondary actions. Some cases we use red for deletes for example. The problem I am having now is we are finding that most people who say they need username help also need their password reset. This would require the user to go through the security process twice, once to get username and once to get the password reset. The solution was decided to give the user the ability to have their password reset after completing the security for getting the username. Of course this now means we have one action to just get the username and another action to get the username and get a link to create a new password. I am trying to figure out how to have two primary actions that don't really have a preferred choice. My starting mock up is below (please ignore the grammar in the text):

Mock up of the screen I was proposing allowing the user to choose whether they want to get the username only or also have their password reset.

Summary: Currently our standards are to have green colored buttons for primary actions and links for secondary actions. Some cases we use red for deletes for example. The problem I am having now is we are finding that most people who say they need username help also need their password reset. This would require the user to go through the security process twice, once to get username and once to get the password reset. The solution was decided to give the user the ability to have their password reset after completing the security for getting the username. Of course this now means we have one action to just get the username and another action to get the username and get a link to create a new password. I am trying to figure out how to have two primary actions that don't really have a preferred choice. My starting mock up is below:

Mock up of the screen I was proposing allowing the user to choose whether they want to get the username only or also have their password reset.

Summary: Currently our standards are to have green colored buttons for primary actions and links for secondary actions. Some cases we use red for deletes for example. The problem I am having now is we are finding that most people who say they need username help also need their password reset. This would require the user to go through the security process twice, once to get username and once to get the password reset. The solution was decided to give the user the ability to have their password reset after completing the security for getting the username. Of course this now means we have one action to just get the username and another action to get the username and get a link to create a new password. I am trying to figure out how to have two primary actions that don't really have a preferred choice. My starting mock up is below (please ignore the grammar in the text):

Mock up of the screen I was proposing allowing the user to choose whether they want to get the username only or also have their password reset.

Source Link

Two Buttons That Have the Same Weight

Summary: Currently our standards are to have green colored buttons for primary actions and links for secondary actions. Some cases we use red for deletes for example. The problem I am having now is we are finding that most people who say they need username help also need their password reset. This would require the user to go through the security process twice, once to get username and once to get the password reset. The solution was decided to give the user the ability to have their password reset after completing the security for getting the username. Of course this now means we have one action to just get the username and another action to get the username and get a link to create a new password. I am trying to figure out how to have two primary actions that don't really have a preferred choice. My starting mock up is below:

Mock up of the screen I was proposing allowing the user to choose whether they want to get the username only or also have their password reset.