Back-end user experience
I’m sure you spend a lot of time making sure your website’s user experience is up to scratch. But are you thinking about all of your users? What about the poor sap who has to use the content management system (CMS) that drives it all? Are you making life easier for them?
I’ve come to the conclusion that a lot of default CMS installations are just plain horrible to use. They’re over-complicated, difficult and ugly. After the initial
Oooh, I’ve got a shiny new toy to play with! feeling has worn off, you (and your users) just don’t want to use them. If the user doesn’t want to update the website, the website simply won’t get updated.
So what’s the answer? You can either find yourself a new CMS and rebuild the website around that, or you can make the best of what you’ve got.
Now, it’s likely that your CMS users won’t know HTML and nor will they want to. To help them out, the CMS often comes with a WYSIWYG HTML editor that tries to look, feel and work like Microsoft Word.
That’s all well and good, but they often come with absolutely everything enabled. Imagine Word with all of it’s toolbars switched on – it’s got buttons that’ll do the washing up, summon a small army and invade New Zealand or even change the colour of your text. It all adds up to make an editor that’s hard to use and intimidating to the new user. Besides, do you actually want the user to be able to change the text colour? Won’t that contravene your brand guidelines or ruin your lovely design?
Keep it simple, stupid
Now for a tangent: A lot of people love Apple products. Why? One reson is their simplicity:
The most fundamental thing about Apple … is that they’re just as smart about what they don’t do. Great products can be made more beautiful by omitting things.
It’s that good old maxim again: Keep it simple, stupid. So what happens if we apply that to our HTML editor?
I started by removing absolutely all of the buttons and drop-downs. Every last one. I was left with a blank canvas on which to type. Obviously this is a bit limiting, so I slowly added back the functions I needed to do the job (and nothing more). The end result is vastly simplified; an environment that lets you focus on the content, not the features of the editor. What’s more, by stripping out some of the more advanced features, I reduced the likelihood of the editor going bananas and cranking out the sort of HTML that Word itself would be proud of *.
Now, this is obviously just one small aspect of the CMS. But apply that principle across the whole system and the end result will be simpler, easier to use and less intimidating.
Don’t stop there either. If you’re able to customise the look and feel of the interface, make it look good, too. Here’s that article again:
Attractive things work better… When you wash and wax a car, it drives better, doesn’t it? Or at least feels like it does.
(also from technologyreview.com).
If you get the interface right, it makes life easier for your users and they’ll love you for that (or at the very least, harbour less of a desire to kill you).
* Not sure what I mean? Open a document in Word, then visit File > Save as Web Page. Open the result up in your text editor of choice and — as Mr. T would say —
Let me introduce you to my friend pain!