UX Bookclub, London – Announcing first meeting 25 Feb

In the past month or so, UX Bookclub‘s have started popping up all over the world. I’m pleased to let you know that the same is about to happen in London, and if you’re interested in reading about and discussing issues related to User Experience, then you’re more then welcome to come along!

We’re meeting at 6.30pm on 25 Feb at BDP Studios, in Clerkenwell and we’re going to be talking about Sketching User Experiences: Getting the design right and the right design by Bill Buxton.

We can only host limited numbers so if you’d like to come along, please register here.

Look forward to seeing you then!

Come to UX London!

UX London

People of, or near, London, have you registered for UX London yet? It’s a brand new conference brought to you by the people behind the most excellent dConstruct conference. I’m very excited about UX London not only because I’m lucky enough to be running a Design Research workshop, but also because we’re going to get to see The Don, Dr. Don Norman, live and in the flesh.

Please stop me from asking him to autograph my copy of ‘The Design of Everyday Thing’. That would be almost as embarrassing as when I asked Jesse James Garrett to autograph my copy of ‘The Elements of User Experience’. (Fortunately I don’t think JJG remembers that).

There are a bunch of other great speakers including the ever entertaining Jared Spool, Peter Merholz, Jeff Veen, Donna Spencer, Eric Reiss, and more, more, more!

Anyway, UX London promises to be a great couple of days of talks and workshops, with an emphasis on practical learning that you can take back and apply to your own practice immediately. I know, for one, that my Design Research workshop is going to be all about sharing a lot of what I do now for work, especially the range of design research approaches and analysis methods that I use for all kinds of clients and projects and, importantly, budgets.

I hope to see you there!

Drupal.org redesign – why is it so? Some insights into our design strategies.

Drupal Redesign V10

Over the past few days I’ve been posting a lot in the Drupal Groups at Drupal.org about the rationale for some of the design decisions we have taken on the Drupal.org redesign. I thought you might find them interesting, so I’ll copy them over here as well.

In particular we’re talking about why the header is so big, the global navigation is so small, search is so prominent, the ‘dashboard’ tabs are more prominent than the global header and why there is no ‘download now’ link on the homepage.

I can’t guarantee that the rationale is entirely holeproof, however it has definitely been based on paying close attention to what a broad range of people want to do on Drupal.org, making some decisions around how to best prioritise these needs, designing to suit these prioritised needs and then testing to check that the new design does actually support key user tasks.

There is one fatal flaw in this version of the redesign and that is that we accidentally left off the big ‘Get Started’ call to action from the homepage… d’uh! (Definitely one of the downsides of designing at speed to fit into weekly iterations is that these kinds of oversights can happen – thankfully the Drupal community let us know about it quick smart!)

You can see the interactive prototype here and the historical archive of the past 10 iterations here.

This is directly copied from my forum posts so hopefully make sense in this context… be warned… it’s long!

Post One: Get Started and the Download Button

evaluating a website design is a really difficult task, as the discussion here and elsewhere demonstrates. It is tremendously difficult to see the design from perspectives other than your own and to get some kind of distance from the content. It is also really hard to judge how well a design works from just looking at it and meandering through it – it can really only be properly judged ‘in action’ – does it actually let people achieve the tasks they need to achieve. Does it make easy things easy? Does it make difficult things achievable? Does it support the objectives we have for Drupal as an organisation? for Drupal end users? and on and on. This is why we’re trying to get the design out in as many ways as possible to see how it’s doing – both online and in person, amongst ‘insiders’, ‘outsiders’ and another groups we’ve recently started calling ‘mid-siders’.

Disclaimers aside, there are a few things that might help move the conversation forward, hopefully! I’m going to tackle the first one here and some others in posts to follow shortly.

Get Started and the Download Button

you are dead right, the strong call to action for Get Started from the homepage has disappeared and this was an oversight on our part. Expect to see this re-instated on the next iteration and thank you for making us aware of it. We have been focussing a lot more on other ‘internal’ pages and just made a few small changes to the homepage this iteration which resulted in this dropping off. Our bad.

If you’ve been following the redesign you’ll probably have noticed that we actually started with an enormous ‘Download’ button, which then evolved into an enormous ‘Get Started’ button which then evolved into more of a ‘Why Choose Drupal’ section. As Mark said, this is a part of a deliberate strategy on our part to ‘bury’ the download button a little – what we are trying to do is to make sure that they actually know what they are getting into when they ‘download’ Drupal, and to ‘scaffold’ that experience a little.

We want them not to expect it to be completely easy to set up a website using Drupal (not to apply mental models of the hosted blogging services, for example, which seem to be quite strong in people’s minds), and we want them to know that there is both a strong and supportive opensource community and commercial ecosystem that can help them along the learning curve if they need it. And, I’m sure you know this already – a lot of people who are interested in Drupal will need that support. For many people who are evaluating Drupal as a solution, particularly within larger organisations, the last thing they should be doing is downloading Drupal.

So, the people we are primarily designing the homepage for are people who are coming to Drupal.org to consider it as a solution for whatever their requirements are, and who are not particularly experienced developers, or possibly not even particularly experienced with Content Management Systems/Platforms/Frameworks etc. This means that people who do have this experience, who do understand the existing Drupal vocabulary, who do want to evaluate the platform by downloading it and taking a look – these people are going to have to work a little harder to get to what they want and they will have to put up with some fluffy language (like the Legos, although I think the Lego reference is being deleted as I write this… which I think is a bit of a shame actually). But the thing is that this audience is capable of doing that little extra work, and they are also more likely to easily recognise what is so great about Drupal.

So, to summarise,

  • we are deliberately making the download link a little more difficult to find so as to better support the experience of newcomers to Drupal who do not have the ability or time to evaluate the product by downloading it, however;
  • the current iteration is missing a strong call to action to ‘Get Started’. This was a (bad!) oversight on our part and we’ll make sure it gets back in there in the next iteration.

I hope this helps make things a little more understandable. Do let me know if you have any questions that I can answer regarding this. I’m going to post some notes re: the size of the header and the placement/relative size of the global navigation next. If there are other issues you’d like me to address specifically, then let me know.

Post Two: That header is so big and it’s all about search? What the?!

First up, I’d like to acknowledge that yes, that is one big old header. It is bigger than your average header and designing a header that size does mean that you’re going to fit less ‘above the fold’. This may seem like an unusual strategy, but it’s certainly not unique, nor does it imply bad design or usability IF it is being done to support a strong strategic objective.

Hopefully you won’t be surprised to hear that we do have some strategic objectives in having such a big-ass header!

Again, if you have been following the redesign process, you’ll have noticed that the big-ass header is actually a relatively recent introduction to the homepage design, coming as late as iteration 7. Here is the last version before it: http://drupal.markboultondesign.com/visual/iteration6/homepage_notlogged…

1. approachability

Use of white space (or in this case, blue space) is very important to design, as I’m sure you know. Allowing breathing space around elements helps you to more easily review the content on the screen and for the designer to guide your eye from element to element. Mark is much more the expert on this tho, (In face, he’s written a bunch about it that is not directly relevant to this conversation but you might find interesting here: http://alistapart.com/articles/whitespace/ )

When I’ve been observing people using this ‘big ass header’ design, the response has been overwhelmingly positive. People say that it feels calm and approachable and easy. People have compared it to a horizon line. It does seem to create a positive effect. This is great because we are trying to ensure that people aren’t overwhelmed by Drupal, and that they feel positive in their ability to understand and engage with it. Everything that I’ve observed to date has demonstrated that the big-ass header is very helpful in achieving this end.

I can’t overstate how intimidating Drupal can be to novice users, although it may strike you as ridiculous. Alleviating this intimidation without getting in the way of active Drupal users is one of the big challenges for this project and the size of the header is a big part of that.

2. focus on search

As you’ve picked up, one of the reasons that the header is so large is because the search element is so large. As with the header, this is somewhat unconventional, but we’ve done this to support the way that people want to use the Drupal.org website.

I’m going to do a separate post about the size/placement etc. of the global navigation and the rationale for that, but suffice to say that for the majority of users, and especially for regular users of the site, Drupal.org is not a ‘browsing’ site- it is predominently a searching site, and secondarily a place to monitor and engage with activity and conversations.

This makes perfect sense, though, when you think about what people actually come to the site to do.

This is a big part of how we conduct our research. A lot of it is talking, asking people about what tasks they need to do on d.o, watching how they currently perform those tasks (much use of Google, as you’d imagine!), getting them to perform those tasks on the new design.

Invariably, for regular users of Drupal, search was the way that people wanted to get to their content. Many people would just just Google search, when compelled to use our redesigned site, they’d go straight to search. I can’t tell you how many times I’ve had to ask people ‘if you had to use the navigation, which link would you choose?’ when asking them to perform a task. This was true back when the global navigation was much more extensive and prominent, and it remains true today.

It was in response to the strong demand for search that we re-made the header to be so big and search focused.

We did some A/B testing between the more conventional navigation approach and the search-centric approach and the search-centric approach was more successful.

If you’re not convinced I’d encourage you (as I have encouraged the community throughout the project) to do your own research – get people who are regular d.o users to define the tasks they do on d.o and have them ‘do’ the tasks using each of the designs – and see what you find. I’d be really interested to hear the results.

Finally, the size of the search element is a show of faith in the ability of the d.o search to ‘do the job’ in finding the information. Generally speaking, search on sites is rubbish and a conventional positioning carries this expectation of rubbish-ness.

The bold positioning of the search element here says – search is the right option for finding what you’re looking for. Give it a try. (And yes, we have been assured that much work will be done on the search functionality for Drupal.org so that it does deliver on this promise).

3. search ‘furniture’

Some other feedback we’ve received is about the ‘stuff’ that’s around the search field and that it takes up space/wouldn’t be used etc.
I agree that the vast majority of people won’t refine their search on the homepage, nor will they use the ‘most popular’ searches… although these are able to be used, their primary purpose is to give information about the search capabilities of the site and to help people use the search properly.

By showing the ‘filter’ options, what we are telling people (more or less subconsiously) is the types of content that will be shown in the search results and that you are able to filter out types of content. We’re exposing the range of content on the site and providing a hint that the search will be more fully functioned than a typical ‘sitewide search’, and certainly than the current d.o website. (and yes, significantly improved search functionality is on the menu for the implementation of the redesign!)

By showing the ‘popular’ searches what we’re doing is alleviating ‘blank page syndrome’ – what do I search for? They are tiny prompts that are intended to help people formulate a search query, and especially if they are relatively new to Drupal, help to expose what others are looking at.

I could quite happily live without ‘popular’ searches, or replace it with something else, but the ‘filter’ options play an important role and should not be removed. In fact, we intend to add ‘API’ to the list of filters in the next release.

search results

A big part of this strategy is a much improved search results page. We’ve only shown hints of this so far in releases, but the next iteration will hopefully show the enhanced faceted navigation within search results to make it a really powerful and useful tool for locating information on the site.

not everyone searches!

There is an important audience who do NOT search, and they are our newer, less technical/experienced audience. They are the least likely to use the search element, and for that reason, the majority of the ‘index’ or ‘landing’ pages are designed specifically for their needs. Starting with the homepage and through all of the ‘section’ landing pages.

OK. That’s a bit of an overview of the rationale and reasoning.

Post Three: Teeny, (Relatively) Tiny Header

ok. This is the last in my series of three monster posts trying to throw some light on why things are as they are in the Drupal.org redesign.

Before you read this, make sure you’ve read the previous monster post on the big header and search, it’s related.

Several people, on this forum and others, have made note of the fact that global navigation on the current design is relatively understated and certainly not one of the most prominent elements of the design. Absolutely true and, for what it’s worth, entirely intentional.

Why so? Well, a number of reasons.

First and foremost, when we considered what the most important and most frequent user journeys on d.o would be, accessing the landing page for a site ‘section’ was very low on the list. Finding out about Drupal, getting access to specific information, monitoring issues and continuing conversations – these were much more important. None of these important user journeys require global navigation.

For ‘new’ users (outsiders) , we consider the movement from Home to About/Why Choose Drupal and/or Get Started the most important user journey. (granted you can’t tell this from the missing links to these on the current iteration homepage – our bad, and an accidental omission as discussed elsewhere)

for ‘existing’ users (insiders) the primary user journeys are to specific content via search/search results and to monitor content/issues/discussions/news etc. which is done via the dashboard.

Hence the emphasis on the search element and the dashboard element (which for existing users will generally replace the generic homepage and will be highly customisable and focussed on monitoring content of personal interest). And hence the demotion of the generic ‘global’ navigation.

We also know that you guys, once you get involved with Drupal, don’t tend to use the global navigation yourself. You use bookmarks, you use the URL (eg. groups.drupal.org etc.) using the browsers memory – both of these are more efficient than going to the homepage and navigating through a hierarchical navigation structure.

Yes, it does seem like a somewhat unorthodox approach, and contradictory to ‘good usability’, but that’s not necessarily the case either.

There is a lot of evidence that shows that people would really rather NOT use global navigation if they can avoid it. People much prefer to use contextual (in content) links for navigation and local (relevant to that section) navigation to get to where they want to go. Global navigation is usually used only as a last resort (or if someone forces you to use it in a usability test!)

Again, if in doubt I encourage you to conduct your own research. Get people to define a few tasks that they would ‘do’ on d.o then put them in front of this prototype and ask them to do the tasks here, and watch them. very few people will go to the global navigation as their first port of call. In my experience, if they are doing that, it’s because there is important information and links missing from the central content area.

A few authors more eminent than me have written on exactly this behaviour. If you have a moment, take a look and see what their experience has been with global navigation vs. local/contextual navigation and search.

http://www.useit.com/alertbox/20000109.html

http://blogoscoped.com/archive/2004_05_25_index.html

http://www.guuui.com/issues/01_05.php

http://www.uie.com/brainsparks/2005/10/19/global-navigation-not-worthwhile/

hope this makes sense and, as ever, awaiting your feedback.

Drupal.org redesign – a strategy for the documentation section

Docs Home

Leisa Reichelt:15:36:39
ok. here’s the theory
Leisa Reichelt:15:36:49
drupal documentation is essentially like wikipedia
Leisa Reichelt:15:36:53
lots of pages
Leisa Reichelt:15:36:59
it’s not hierarchical
Leisa Reichelt:15:37:06
because it is grouped around so many things
Leisa Reichelt:15:37:14
so doing a hierarchical IA for it is nonsense
Leisa Reichelt:15:37:23
will only show how complex it is and where it is incomplete
Leisa Reichelt:15:37:25
which we want to avoid
Leisa Reichelt:15:37:30
hence our emphasis on search
Mark Boulton:15:37:32
yep – agree with that
Leisa Reichelt:15:37:44
ok, that’s the first part of the strategy
Leisa Reichelt:15:37:46
here’s the next
Leisa Reichelt:15:37:53
there are three key pathways to documentation content
Leisa Reichelt:15:38:01
1. i have a specific problem I need an answer to
Leisa Reichelt:15:38:05
in which case, i search
Leisa Reichelt:15:38:16
2. i’m new at drupal, or some aspect of drupal and I need to get up to speed
Leisa Reichelt:15:38:31
in which cse, i need access to some ‘designed’ content (eg. tutorials)
Leisa Reichelt:15:38:37
and I’m likely to hit the docs landing page
Leisa Reichelt:15:38:52
or 3. i need more information about <x> which I am looking at now
Leisa Reichelt:15:39:02
eg. I want to see the documentation associated with this module that I might choose
Leisa Reichelt:15:39:12
in which case, I want to see the documentation contextually linked
Leisa Reichelt:15:39:21
convincing so far?
Mark Boulton:15:39:27
absolutely
Leisa Reichelt:15:39:30
ok
Leisa Reichelt:15:39:38
so, pathway A is covered already
Leisa Reichelt:15:39:54
pathway C is also covered (although we’ll need to check for other places where contextual linking is appropriate)
Leisa Reichelt:15:40:02
pathway B is the tough one
Leisa Reichelt:15:40:13
because what *is* this section if we don’t have hierarchical navigation?
Leisa Reichelt:15:40:24
what do we have to draw inspiration from?
Leisa Reichelt:15:40:30
wikis, of course!
Leisa Reichelt:15:40:55
so, the sub navigation for docs becomes something like: docs home | API | Index | Recently Updated
Mark Boulton:15:41:03
makes a lot of sense
Leisa Reichelt:15:41:10
API needs to be kept separate I think
Leisa Reichelt:15:41:21
and we can play around with exactly how the INdex works
Leisa Reichelt:15:41:37
and then the landing page of docs is all for new people needing structured guidance
Leisa Reichelt:15:41:52
so it links off to whatever of this we have available
Mark Boulton:15:41:58
sort of orientation
Leisa Reichelt:15:42:00
including, I think, the recipes?
Leisa Reichelt:15:42:07
yes, indeed.
Mark Boulton:15:42:19
I like it – it solves the problem
Leisa Reichelt:15:42:24
and there are two main kinds of documentation pages
Mark Boulton:15:42:40
plus it gives the freedom to the community to tailor it to their needs as they evolve
Leisa Reichelt:15:42:43
the actual documentation, and then a more flexible ‘index’ template that people can use to group documentation in whichever way they like
Leisa Reichelt:15:42:52
exactly
Leisa Reichelt:15:43:16
and, it doesn’t make it look as though there is too much/too little documentation at a glance
Mark Boulton:15:43:28
exactly – the holes aren’t as visible
Leisa Reichelt:15:43:35
exactly
Leisa Reichelt:15:43:38
ok.
Mark Boulton:15:43:47
I might do a dance now
Mark Boulton:15:43:50
:)
Leisa Reichelt:15:44:00
lol

Docs - Article