Monday 22 December 2008

The shop metaphor

It's generally difficult to get points about web management across to people who are not web experts themselves - and that, unfortunately, likely includes all the people with any kind of power over the web in your institution. Whether you're dealing with complete novices ("Can you explain what you mean by 'home page'?") or with power users who have latched on to a particular concept as the solution to all things web ("But having more pages will help our search engine optimisation!"), you'll find it distressingly difficult put across what you *mean* when you talk about the web.

That's where metaphors come in useful. If you relate the web to something more familiar, and then get people to think about that instead, suddenly the expressions of confusion or of mulish determination are replaced by - joy! - understanding . Unless you're dealing with complete idiots (and I haven't yet).

The metaphor I find myself using most is that of a shop. People understand shopping. They know that shops are there to sell stuff, and that people go there to get what they want and then get out. All of which makes this a great metaphor for a website.

Sample uses:
  • Case for collecting web stats beyond "how many hits did we get on our site": say we have a shop; measuring hits is like measuring how many people look at the shop window. There's some use to it, but what we really want to know is how many people came in, and how many bought something.

  • Reducing use of explanatory text: if you ask the shopkeeper where something is, do you want him to tell you, or do you want him to spend five minutes telling you why the thing you want is so great?

  • Calling things what they are: which makes you think less, an aisle called "tea and coffee", or one called "variety of hot beverages"?
I'm sure you can come up with your own exampes, and I am equally sure that my metaphor breaks down at some point. But I haven't found that point yet!

Any advances on good web metaphors to use?

Friday 19 December 2008

Things I've learned that make life easier #1: Don't put things right - yet

When you're dealing with information, it's easy to focus on the job at hand. You're the information expert, after all, and chances are that, from your perspective, *everyone* else is doing information the wrong way. Heck, leave out "from your perspective".
It's very easy to want to put things right, straight away. So you feel you've made a difference. Out of a sense of professional pride. In self-preservation - you're the one who gets the stick if someone else realises how rubbish the information is.

Resist that urge.

If you start putting things right straight away, three things will happen. One, you will find that putting things right is a *lot* more work than you would have ever thought possible. Two, it will be difficult to get help for the stuff you need help with, because no one sees there is a problem. Three, you will get nothing like the recognition you deserve for the work that you do.

At the start of a new job, take some time to get to know the problems that are there. Write lists, critiques, action plans; anything that will document the work that needs doing in a way that your managers can appreciate. Depending on the environment you're working in, you may have months, weeks or days to do this in - but make sure you do it. And make sure, before you start putting things right, that your managers are aware of what you're going to put right, how much work it is, and what help you will need.