avoiding user testing too late, some challenges

The classic usability complaint is that projects just tack a usability test on at the end of development when it is too late to make any changes. Which leaves the usability consultant in the uneviable position of having to tell the project team that their product doesn’t work, when they can’t do anything about it.  It can feel like a waste of time and money.

In reality these sessions are rarely entirely useless and I’d prefer to run them rather than having nothing at all. A lot of feedback is often about content which can usually be changed at the last minute.  You can also capture general customer research insights that can feed into the next project.

A couple of projects I’ve got involved with recently have involved late stage usability testing . We need to tackle this but we’ve got some bigger challenges than usual in bringing in a better approach to usability testing.

1. The organisation can’t afford rounds of testing

This is hardly unique to us and I fully expected this when I took the job. The answer usually involves the word “guerrilla” at some point.

2. We have some challenges in doing guerrilla testing

Our target audience (blind and partially sighted people)  is a small section of the population and can’t easily be found by popping into libraries and coffee shops. Everybody else really isn’t representative and would give completely different results. Although admittedly our target audience can often be found in our own offices, or rather in the public resource centre downstairs. But you can’t just get them to test on your laptop as you need to have the access tech that they are used to using. We might need to try and find folks who are both willing to test and also use the access tech we have available. Not insurmountable problems, but will take a bit of planning.

3. Can’t easily do paper-based testing or flat onscreen mock-ups.

I’ve mentioned this particular challenge before. We can survey and interview quite easily. We can test existing or competitor systems. But when it comes to trying out how well new designs are working, our options get a lot fewer. Whilst it would be interesting to experiment with tactile mock-ups, the admin overheads and learning curve probably aren’t justified.  Really we should just concentrate on working prototypes, rather than getting carried away with how cool an IA presentation idea “tactile wireframes” is.

accessibility
rnib
ucd

Comments (1)

Permalink

working with people who demean their colleagues

A while back I read The No Asshole Rule: Building a Civilised Workplace and Surviving One That Isn’t

Back then I was in daily contact with someone who could have been the inspiration for Sutton’s book. Some of you will have had your ears bent about that delightful situation.

I’m far luckier in my working environment these days. My current boss and colleagues are all pretty much universally supportive, considerate and rational.

Occasionally I still encounter less pleasant folks but they are mostly at arms length which makes them far easier to deal with.  My most recent encounter sent me back to my book shelves to read Sutton’s book.

The book makes a distinction between people who demean others and people who are constructively argumentative and challenging.  Sutton describes two tests for spotting the former:

  • Test One: Does the ‘target’ feel oppressed, humiliated, de-energised, or belittled by the person? In particular, does the target feel worse about him or herself?
  • Test Two: Is the venom aimed at people who are less powerful rather than at those people who are more powerful?

Sutton argues that the bullies cause obvious damage to their immediate targets but they also damage bystanders, themselves and the organisation.

There’s a good section in the book called “Teach People How to Fight”.

I’ve been struck that through bullying these individuals can control what people do but they can’t control what people keep from them. No-one is going to voluntarily help them out.  People will let them shoot themselves in the foot.

happiness
psychology
work

Comments (1)

Permalink

the trouble with careers advice

The main memory of my school’s careers advice was an interaction that went something like this:

“You appear to be rather good at science…have you thought about being a scientist? No? How about a science teacher?”

I don’t remember anyone ever suggesting that there were hundreds of thousands of jobs out there that don’t appear in Happy Families.

And the range of generic professions suggested seemed to be based on what subject you were better than your peers at. Enjoyment didn’t come into it.

I was very good at physics and I even found the lessons moderately enjoyable.  But left to my own devices, physics didn’t particularly feature in the way I spent my time (barring a bookish interest in astronomy).

I played with my dog, went swimming, spent a lot of time on the swings, read heaps on books, wrote stories, sketched, painted, cooked, drew maps of fantasy places, drew plans for imaginary buildings and gardens, and made models of buildings and towns.

That stuff made me happy (and it still sounds pretty good today).

Reading that list, it does sound like architecture (the proper kind) would have been a sensible direction. At 15 I did a stint of work experience at an architects practice and I had great fun clambering around building sites and drawing up plans.

The architect got me to draw up a plan for my dream house.  He had a look at how I was getting on and suggested I should be more ambitious because:

“this is the last chance you’ll have to design a house that you actually like”

And that was the end of my career as an architect.

At the heart of his comment was a real problem with careers advice. Even if we can direct children to learn crafts that they will enjoy that doesn’t ensure they will enjoy the day-to-day realities of their work.

career
happiness

Comments (0)

Permalink

what Haringey thinks is my local area

One of the things that Haringey Council send us is the Haringey People “Local News” magazine for  Northumberland Park and White Hart Lane.

I largely disinterestedly flicked through the last one, none of the stories particularly catching my attention.

At the back was a nice little map of the area that shed light on my disinterest. This was clearly labelled ”your local map” and helpfully explained ”your local neighbourhood has been highlighted on the map of the borough”.

What Haringey thinks is my local area

But I don’t really go places in either of the two wards that Haringey has decided are my local area. My house is there (and my allotment!) but tube/rail stations, doctors, dentist, pubs, restaurants, shops, post office, parks, supermarkets and actual markets, vets, garden centres are all in other wards.  Even my bus stop isn’t technically in *my* ward.

Partly this tells us that these wards are pretty deprived, even by Haringey’s standards. Not just financially but culturally. There’s not a lot of reasons for me to venture deeper into my own ward.

Another part of the problem is the print medium. Online they could have defined local in a circle around my location rather than relying on political boundaries. A circle would have been better but would still have a included a lot of space to the north that I’m not particularly interested in.

Local for me is stretched in a particular shape. That shape is formed by the gravitational pull of transport links into London (i.e to the south), the facilities available in the wealthier west of the borough but also by the cheap shops and restaurants further south.

I actually wanted to read the newsletters from all the six other local areas and not my own. Thanks to the internet I can but the glossy magazine is going to be rather a waste.

cities
town planning

Comments (0)

Permalink

for newspapers, content is (still) the problem

I’m not exactly a digital native, more first generation immigrant. Nor am I an enthusiastic internet pirate.

I grew up with the habit of newspaper buying. I once worked for a national newspaper. I enthusiastically read the paper cover to cover.

Not anymore.

I stopped buying during the week, once we moved away from Finchley Central. The combination of the regular delays on the Northern line and a newspaper  shop on the southbound platform meant a reasonably regular thought process of  ”sod it, might as well buy a paper while we wait”.  The mere geography of the new tube station undermined the purchase process.

For a while it remained a weekend pleasure (with coffee and cats) but in the end I stopped that too.

I stopped because the content alienated me. I was disappointed with the bizarre fashion supplements, with the obsession with new media (biogs for authors that were nothing more than “who blogs at”) and some frustratingly elitist editorials ( Few people know nothing at all by Beethoven). I’m still annoyed about the folksonomic zeitgeist.

And I felt like I knew little more when I put down the paper than when I had picked it up. I knew the gist of the news before I read it and I could guess what the columnists were going to say about. There was never any real analysis, nothing that made me understand.

I tried other papers, even straying a long way from my political comfort land. They all annoyed me. Oddly the Financial Times annoyed me least, perhaps because I had a lot to learn about their particular view of the world. And then I just gave up and saved the pounds.

These days I don’t normally get news from the internet, whether that be blogs, the BBC or newspapers. I get it from the radio.

I do go to newspaper websites (of all stripes) to read the comment stuff but mostly it just annoys me.  Reading it is irrational but I still do it. Paywalls will help me stop irritating myself.

I do still like the supplements ( food , money, gardening and the like)  but figured I might as well just buy a dedicated magazine. They’ll cover those subjects better anyway.  And so we do. Shedloads of magazines still pass through our house.  Proper dead tree media.

So perhaps we could move on from all this paywall business and complaining about the internet.  Maybe it is time to sort out the lazy, trite content instead?

internet

Comments (1)

Permalink

e-commerce project: the browse structure

This article is part of a series about our e-commerce redesign.

The browse structure of any website is always controversial within the organisation. I’m always struck by the discrepancy between how interested the organisation is in browse (as opposed to search) and how interested the users are. I’m not saying users don’t want a sensible, intuitive navigation scheme but they also want a really effective search engine. Most web design project involve huge amounts of effort invested in agreeing the navigation and very few discussions of how search will work.

Partly this is because navigation is easy for stakeholders to visualise. We can show them a sitemap and they can instantly see where their content is going to sit. And they know the project team is perfectly capable of changing it if they can twist their arm. With search on the other hand, stakeholders often aren’t sure how they want it to work (until they use it) and they’re not sure if it is possible to change anyway (search being a mysterious technical thing).

Even forgetting search, the focus on navigation is almost always about primary navigation with most stakeholders have very little interest in the cross-links or related journeys. The unspoken assumption is still that the important journey is arriving at the homepage and drilling down the hierarchy.

So I went into the e-commerce project assuming we’d need to spend alot of time consulting around the navigation structure (but knowing that I’d need to make sure I put equal energy into site search, seo and cross-linking, regardless of whether I was getting nagged about it).

A quick glance also showed that the navigation wasn’t going to be simple to put together. Some of my colleagues thought I wasn’t sufficiently worried but I’m used to the pain of categorising big diverse websites or herding cats as Martin puts it. I participated in at least three redesigns of the BBC’s category structure, which endeavours to provide a top-down view of the BBC’s several million pages on topics as diverse as Clifford the Big Red Dog, the War on Terror and Egg Fried Rice.

My new challenge was a simple, user friendly browse structure that would cover a huge book catalogue,  RNIB publications, subscriptions to various services, magazines, and a very diverse product catalogue of mobility aids, cookware, electronics and stationery. And those bumpons, of course.

Card-sorting is usually the IA’s weapon of choice in these circumstances. Now I’ve got my doubts about card-sorting anyway, particularly where you are asking users to sort a large, diverse set of content of which they are only interested in a little bit of it. Card-sorting for bbc.co.uk always came up with a very fair, balanced set of categories but one that didn’t really seem to match what the site was all about. It was too generous to the obscurer and less trafficked bits of the site and didn’t show due respect to the big guns. Users didn’t really use it, probably even the users who’d sorted it that way in the testing. My favourite card-sorting anecdote was the  guy who sorted into two piles “stuff I like” and “stuff I don’t like”. Which I think also alludes to why card-sorting isn’t always successful.

In any case, card-sorting isn’t going to half as simple and cheap when your users can’t see.

We decided to put together our best stab at a structure and create a way for users to browse on screen. Again not just any old prototyping methods is going to work here – however the browse structure was created would need to be readable with a screenreader.  So coded properly.

I wrote some principles for categories and circulated them to the stakeholders. Nothing controversial but it is helpful to agree the ground rules so you can refer back to them when disagreements occur later.

I reviewed the existing structure, which has been shaped over the years by technical constraints and the usual org structure influence.  I also looked at lots of proposed re-categorisations that various teams had worked on. I looked at which items and categories currently performed well. I reviewed the categorisation structures as part of the competitive review.

I basically gathered lots of information. And then stopped. And looked at it for a bit. And wondered what to do next.  Which is also pretty normal for this sort of problem.

(actually one of the things I did at this point was write up the bulk of this blog post – I find it really, really helpful to reset my thinking by writing up what I’m doing)

Somewhat inevitably I got the post-it notes out. I wrote out a post-it for each type of product and laid them out in groups based on similarity (close together for very similiar products and further away as the relationship gets weaker). This is inevitably my sense of similarity but remember this is a first stab to test with users.

Where obvious groups developed I labelled them with a simple word, some like books or toys. If a group needed a more complex label then I broke it up or combined it until I felt I had very simple, easily understood labels (essentially a stab at “basic categories”).

There were too many groupings and there were also a scattering of items that didn’t fit any group (the inevitable miscellaneous group). I dug out the analytics for the shop to see how my grouping compared in terms of traffic. I made sure the busiest groups were kept and the less popular sections got grouped up or subsumed.

This gave me a first draft to share with the business units. Which we argued about. A lot.

I referred everyone back to the principles we’d agreed and the analytics used to make the decisions. Everyone smiled sweetly at me and carried on with the debate.

After some advice from my eminently sensible project manager, I conceded one of the major sticking points. As I reported on Twitter at the time:

“Have given in and allowed the addition of a 13th category. Will the gates of hell open?”

Luckily at this stage we were finally able to do some usability testing with some real users. Only four mind, but they all managed to navigate the site fine and actually said some nice stuff about the categories. One tester even thought there must be more products on the new site, in spite of us cutting the categories by two-thirds.

So if someone attempts to re-open the browse debate, hopefully we can let usability tester #2 have the last word as in her opinion the new shop is…

“very, very clearly divided up”

Enough navigation, time to concentrate on search….

Related posts:
Re-branding miscellaneous

categorisation
e-commerce
navigation
rnib

Comments (0)

Permalink

clever flat-pack design

Rabbit themed UX insights continue today.

The rabbit hutch is here, built and ready for baby rabbits. The building process was helped by a nifty idea from the German manufacturer.

Helpful flat-pack

All the screws and bolts came attached to a piece of card, labelled with pictures of all the fixings and their names. This meant you could see at a glance if anything was missing and you didn’t have to compare screws to work out which one was the long one.

design

Comments (0)

Permalink

tripped up by “you might also like”

My rabbit hutch purchasing has been an interesting vein of UX experiences. In the end I bought a hutch from JustRabbitHutches, whose website was mostly pleasant to use and whose service was great.

That said, once I’d added my hutch to the basket I noticed they’d been tripped up by recommendations. Under my basket were suggestions that I might enjoy. Unfortunately one of them was a “delivery surcharge”.

Surcharges are always so much fun

Now this isn’t as damaging as Walmart’s dodgy DVD recommendations but it’s another example of how careful you have to be.

You could also ask why JustRabbitHutches thought they needed a recommendation engine here. After all the clue is in the title. If I’m buying a rabbit hutch, how likely is it that they’ll be able to sell me another one?

e-commerce
recommendations

Comments (0)

Permalink

my newly complicated job title

The eagled-eye amongst you (or those with a fondness for the detail of LinkedIn updates) have noticed that my job title has changed.

I’m now officially “Business Analyst/Information Architect”. Yup, there is genuinely a slash in my job title.

Now part of me is genuinely impressed that RNIB is chilled enough about such things. We all get in a lot of tangles trying to come up with one job title that sums up what we do (both to our colleagues and the outside world). That slash is a nice acknowledgement of a messy reality (although you’d probably need to tack another couple of job titles on end before you had an accurate representation of reality).

So why Business Analyst?

1. IA isn’t well understood inside my organisation, outside of my immediate colleagues and unusually the chairman (and before you start, user experience designer would be even less illuminating). People have a reasonably good idea of the space that Business Analysts work in, if not an understanding of the exact details.

2. But more importantly I was already doing business analyst work. A lot of IA/UX training assumes that no BA work has been done, so you start with that before doing the design work. So I naturally did stuff that my BA colleagues recognised as business analysis.

When I did my BA qualification last year, I was struck by how similar the tools and problem spaces are to those in UX world. The cultural context is different so the language used is more business than design, the outputs are less pretty, and there’s often an emphasis on users being staff not customers. Creating such detailed requirements documents was new to me but everything was familiar.

3. There’s more business analysis work that needs doing than there are business analysts. Now you might say that there is surely a lot of IA work that needs doing, and only one IA. And there is. I’ll be putting IA problems on the backburner that need fixing. But I’m comfortable with this because the BA role puts a greater emphasis on ensuring the right problems are being solved, rather than just implementing the chosen problem well.

Again I know there’s plenty of folks who’d say that IA (and UXDers more so) should absolutely be part of the process of picking the problems. That’s fine, you can say that. I’d support you pushing for that to be the case. But the reality on the ground for many IA/UX types is they get told what the project is.

There’s a greater expectation that the business analyst shapes the projects. So for me that route is the fastest way to my destination. And that destination isn’t championing a professional cause. It’s about making sure the money given to the charity is spent well on the people who need it.

career
rnib

Comments (0)

Permalink

why your search engine (probably) isn’t rubbish

Now all search engines struggle,  to varying degrees,  with the knotty mess that is natural language. But they don’t generally don’t get called rubbish for not succeeding with the meaty search challenges.

Rubbish search engines are the ones that can’t seem to answer the most basic requests in a sensible manner. These are ones that get mocked as “random link generators”, the jibbering wrecks of their breed.

Go to  Homebase and search for “rabbit hutch” (we need another one as two of our girls are about to produce heaps of bunnies at the same time).

The first result is “Small plastic pet carrier”. There’s a number of other carriers and cages. Then there’s a “Beech Finish Small Corner Desk with Hutch”. Finally there’s a Pentland Rabbit Hutch at result no #8.  This is a rubbish set of results. I asked for “rabbit hutch” and they’ve got a rabbit hutch to sell me but they’re showing me pet carriers and beech finish corner desks.

This is a rubbish set of results. But it doesn’t mean the search engine is rubbish.

Somebody made a rubbish decision. They’ve set it up shonky.

So before you reach for the million pound enterprise search project, try having a quick look under the bonnet with a spanner.

Is it AND or OR?

This is reasonably easy to test, if you can’t ask someone who knows.

Pick a word that will be rare on your site and another word that doesn’t appear with the rare one  e.g.  ”Topaz form” for my intranet.  A rare word is one that should only appear one or two times in the entire dataset so you can check that the other word doesn’t appear with it.  You may need to be a bit imaginative but unique things like product codes can be helpful here.  If the query returns no results you’ve probably got an AND search.  More than a couple of results (and ones that don’t mention Topaz) and you’ve probably got OR.

(this can get messed up if there is query expansion going on but hopefully the rare word isn’t one whatever query expansion rules there are will work on).

AND is more likely to be problematic as a setting. You’ll get lots of “no results”. You’ll need your users to be super precise with their terminology and spell every word right.  If they are looking for “holiday form” and the form is called “annual leave form” they’ll get no results.

OR will generate lots of results. This is ok if the sort order is sensible. Very few people care that Google returned 2,009,990 results for their query. They just care that the first result is spot-on.

So most of the time you probably want an OR set-up.

(preferably combined with support for phrase searching so the users can choose to put their searches in nice speech marks to run an AND search if they want to and know how to).

Is there crazy stemming/query expansion going on?

Query expansion is search systems trying to be clever,  often getting it wrong and not telling you what they’ve done so you can unpick it. Basically the search system is taking the words you gave it and giving you results for those words, plus some others that it thinks are relevant or related.

Typical types of expansion are stemming (expand a search for fish to include fishes and fishing), misspellings and synonyms (expand a search for cockerel to include rooster).

This is probably what is happening if you are getting results that don’t seem to include the words you searched for anywhere on the page (although metadata is another option).

Now this stuff can be really, really helpful. If it is any good.

Have you got smart sophisticated query expansion like Google?  Or does it do silly (from a day-to-day not a Latin perspective) stemming like equating animation with animals? If it is the silly version then definitely switch it off (or tweak it if you can).

Even if you’ve got smart expansion options available, it’s generally best practice to either give the user the option of running the expanding (or alternate) query, or at the very least of undoing it if you’ve got it wrong. They won’t always spot the options (Google puts lots of effort into coming up with the right way of doing this) but it’s bad search engine etiquette to force your query on a user.

Is the sort order sensible?

That Homebase example. The main problem here is sorting by price low-high. That’d be fine (actually very considerate of Homebase) if I’d navigated to a category full of rabbit hutches. But I didn’t. I searched for rabbit hutches and got a mixed bag of results that included plenty of things that a small child could tell you aren’t rabbit hutches.

The solution? Sort by relevancy.

I’ve seen quite a lot of bad search set-ups recently where the search order was set to alphabetical. Why? Unless as Martin said when I bemoaned this on Twitter your main use case is “to enable people to find stuff about aardvarks”.

News sites sometimes go with most recent as the sort order. Kinda makes sense but you need to be sure the top results are still relevant not just recent.

Interestingly sort order doesn’t matter so much if you’ve gone for AND searches and you haven’t got any query expansion going on. If you’re pretty sure that everything in the result set is relevant, then you’ve got more freedom over sort order.  If not,  stick with relevancy.

(I don’t need to tell you that you want relevancy is high-low, do I?)

So people stop giving me grief over navigation.  Let’s talk about that rubbish search engine you’ve got.  I could probably fix that for you.

search

Comments (0)

Permalink