User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It only takes a minute to sign up.
Sign up to join this community
After the user Registers for an event (he goes to cart and pays, etc.) the next time he visits the page, the event for which he registered now shows a less emphasized Unregister button, which does the exact opposite of what it did until the event was purchased.
Is it a good practice to have the same button change it's function or is it bad and confusing?
Update:
If it helps anyone, I went with this layout:
You've replaced the button label with the only available action: reverting (unregistering).
Where it starts to get a little confusing is you have a checkmark alongside the button label.
One approach is to separate them. Separate the status 'You are attending' from the action.
Since the primary action when scanning the list is Register, you can make the Unregister button more subtle.
Depending on the business goals, if you need to deemphasize the act of unregistering, you can perhaps make a subtle link.
This example emphasizes the current state 'Attending' so it's clear at a glance.
This also uses distinct language to more clearly differentiate state from action.
I would keep the general style of the button, to be consistent. However I think the most important thing is to confirm that you have registered, and not have this state be confusingly similar to not being registered, except for "Un". Since the important thing is that you have already registered I would put that on top, with the unregister button underneath. Having the lighter style also makes it less likely that a quick perusal would mistake it for needing to register. Like this:
For comparison, social media sites usually have something like that button for following/unfollowing.
Some examples:
Tumblr:
Reddit:
Twitter:
YouTube:
Facebook:
Do not jeopardise your users' experience in the favor of discouraging an action!
These are two different buttons with two different functionalities that are EQUALLY important to the users.
Apparently users should be able to Register and to Unregister. Similarly I am able to buy from Amazon and I am able to make a return or cancel an order. Although Amazon would prefer less returns/cancellation happening, they do/should not make the Return/Cancel buttons confusing and less accessible.
*Less emphasizing does not mean confusing the user and making the task hard to achieve.
*There is nothing wrong with having the "Unregister" button replacing the "Register" button.
Recommendations:
See suggestions in the update sections below.
UPDATE (1):
I just noticed Mike's answer (I think it was posted a couple minutes before mine). I echo his idea: "Depending on the business goals, if you need to deemphasize the act of unregistering, you can perhaps make a subtle link".
END OF UPDATE (1)
This update is to suggest a design improvement based on the OP update and other answers:
