home > services
… how the “save draft” and “publish” buttons in Wordpress can look *eerily* similar when you’re in the groove of writing a blog post?
Those of you lucky enough to have an RSS reader got a sneak peek of Adaptive Path’s latest R&D project earlier today when I accidentally clicked that cursed “publish” button instead of “save draft”. Monday, we’ll be posting more information on the work. Stay tuned…
At Adaptive Path, our ideas are driven by the work we do. We do consulting for user interface and user experience design, and offer conferences, training and education for UX designers.
From field ethnography, UI wireframes and task flows, to visual design and implementation, we do it and we teach it.
Learn more in our video, Adaptive Path in 2 ½ Minutes:
Want to know more about Adaptive Path? You should read more about our services or contact us to find out how we can help you!
Entries (RSS)
May 15th, 2009 at 9:02 pm
Not really. The “Publish” button clearly stands out from the other two buttons. Unlike the “Preview” and “Post” buttons underneath this comment input field…
May 16th, 2009 at 6:58 am
Maybe it is mre the problem of the forcing function of the “publish” button that was misleading, rather than the similarity.
May 16th, 2009 at 8:31 am
I’ve definitely done this myself. What with needing to choose between the similarly styled “Save Draft” and “Preview” and “Publish” button, I will often simply pick one of them at random, as though the choice doesn’t even matter.
Yikes, how it does, though! I am one of those lucky few, and the project sounds really interesting!
May 16th, 2009 at 9:21 am
I’m looking forward to reading more. My RSS caught a glimpse of the work Natasha has been keeping hush-hush all of these months.
May 17th, 2009 at 7:15 am
I wonder if they don’t look similar enough. If there were three buttons next to each other in roughly the same style — would you be more careful about reading them? Instead you have a clearly a big blue button that says “push me” and the other buttons are light and out of the way and suggest they aren’t important at all. So naturally you push the button that is screaming for your attention, assuming it will do whatever you want it it to do — publish, save as draft, snooze, whatever.
May 17th, 2009 at 5:06 pm
I don’t use WordPress but that definitely looks annoying and the dialog seems confusing as well (isn’t the status field redundant?). TypePad isn’t perfect but it seems to do a better job at preventing this sort of mistake: there is a single save button and a listbox for changing the publishing status (draft, publish on…, publish now).
May 18th, 2009 at 5:18 am
[...] Rachel points out what is likely a common example of something we all do from time to time–making a mistake with a UI. She rightly does not directly blame the UI, but a couple of commenters allude to inherent confusion or misleading characteristics in the UI. As designers, in such cases we’re predisposed to cry foul and blame a UI for its confusing or misleading design, but I hope that we don’t shut off our brains in the process. Is it not perfectly acceptable to require that users read what is on a button in order to ascertain its function? [...]
May 18th, 2009 at 10:40 pm
I would be annoyed if they were any more different. The shape of the buttons ought to be consistent in an interface. Square corners mixing with rounded corners would be a pretty inconsistent and not very elegant. I think the designers used good judgement here by using contrast and color to define the button differences, using physical space to ward off accidental press and used clear language to indicate the purpose of the button.
I’ve made similar mistakes of pushing the wrong button at an inopportune time, but the mistake was mine for not double checking my actions.