5 ms·

The trouble with putting the current task on the submit button is that the user is already doing that task and they might think that the button is a link to sta

The trouble with putting the current task on the submit button is that the user is already doing that task and they might think that the button is a link to start the task over, particularly if they clicked on identical text to get to the form in the first place. I have personally made this mistake while using some sites. I try to include some context in the submit button but still make it clear that it will submit the form. Short, generic verbs seem to work well, like "Save", "Delete", or "Send". EDIT: thinking more about this, I think what's important is to use a verb that applies specifically to the form data as opposed to the whole task: You send a reply, you don't reply a reply.

burgerbrain 16y ago
Exactly, I've had this issue a few times and actually consider "submit"/"finish"/etc to be far more user friendly for this reason. Presumably I already clicked something to the effect of "create user" to get to the form, and now I have to click "create user" again? What?
- thwarted 16y ago
  There's possible value is calling out the genericness of getting to the empty form vs the specificness of the submitting the data on a single instance of the form. "Create user" takes you to a form that has potential to be any user (because it's empty), "Create this user" finalizes the action based on the filled-in data on the form.
  - sp4rki 16y ago
    If you click on a link or button called 'Create a User' that that takes yo to a form, it would be almost universally more usable to have the button at the end say 'Save' instead of 'Create this user'. Verbosity is not always a good thing on the web.
    - rue 16y ago
      I'm probably in the minority but when I see "save", I assume it's "saving my progress". In a user creation form, even just "create" is clearer than "save".
      - sp4rki 16y ago
        But then we're back in "is it telling me to create the user again when I already clicked the other button on creating a user on the other page?" territory. I think we should use whatever feels right and A/B test the hell out of it, but spend more time actually solving more substantial problems that the copy on a submit button.
Charuru 16y ago
Pretty much need testing and data. I've heard arguments both ways.
- deleted 16y ago
  [deleted]
rprasad 16y ago
Or you could resolve the issue by combining the verb with the noun being acted upon: "Send Reply", "Save Changes", etc.
billmcneale 16y ago
> The trouble with putting the current task on the submit button is that the user is already doing that task and they might think that the button is a link to start the task over Yup. Another risk is using an ambiguous phrasing, such as on this very web site: in order to post your comment, you have to click on a button that says "Leave comment". Does this mean the button will post my comment or abandon it because I want to leave?

burgerbrain 16y ago

Exactly, I've had this issue a few times and actually consider "submit"/"finish"/etc to be far more user friendly for this reason. Presumably I already clicked something to the effect of "create user" to get to the form, and now I have to click "create user" again? What?

thwarted 16y ago
There's possible value is calling out the genericness of getting to the empty form vs the specificness of the submitting the data on a single instance of the form. "Create user" takes you to a form that has potential to be any user (because it's empty), "Create this user" finalizes the action based on the filled-in data on the form.
- sp4rki 16y ago
  If you click on a link or button called 'Create a User' that that takes yo to a form, it would be almost universally more usable to have the button at the end say 'Save' instead of 'Create this user'. Verbosity is not always a good thing on the web.
  - rue 16y ago
    I'm probably in the minority but when I see "save", I assume it's "saving my progress". In a user creation form, even just "create" is clearer than "save".
    - sp4rki 16y ago
      But then we're back in "is it telling me to create the user again when I already clicked the other button on creating a user on the other page?" territory. I think we should use whatever feels right and A/B test the hell out of it, but spend more time actually solving more substantial problems that the copy on a submit button.

Charuru 16y ago

Pretty much need testing and data. I've heard arguments both ways.

deleted 16y ago
[deleted]

rprasad 16y ago

Or you could resolve the issue by combining the verb with the noun being acted upon: "Send Reply", "Save Changes", etc.

billmcneale 16y ago

> The trouble with putting the current task on the submit button is that the user is already doing that task and they might think that the button is a link to start the task over Yup. Another risk is using an ambiguous phrasing, such as on this very web site: in order to post your comment, you have to click on a button that says "Leave comment". Does this mean the button will post my comment or abandon it because I want to leave?