At the beginning of this project we invited you to do a ‘show and tell’ of anything you’ve done to a Drupal Admin System that you think we should pay attention to – anything from a customised administration system, to a better view of content, to an in-line editing tool – whatever you think we should see. Happily, we’ve seen a few people participate and some interesting concept. (You can see some of there on our YouTube group).
You may also remember a little exercise we did for the Drupal.org project where we invited anyone to submit a wireframe of a page they though needed some attention and what they’d do to it (you can see the original post here)…
well… now is the time for us to bring that all together and to kick off ‘Pimp Your *Imaginary* Admin’ for the D7UX project!
Here’s how it works:
pick *something* or *somewhere* in Drupal admin that you think is particularly in need of love
get out your pen, pencil, visio, powerpoint, whatever works best for you (I’d encourage you to consider pencil!)
sketch out how you think it *should* work.
post your sketch(s) somewhere we can see them – the Flickr group is ideal for this if you’re a Flickr member (or inclined to become one) but if you post it on your own site, or wherever you share pictures and link to it in the comments below we will *definitely* take a look.
this is optional but we would consider you most excellent if you do it – take a short movie of your sketch(es) and talk us through them. Your movie should include: a) a statement of the problem – what are you fixing? what is currently wrong with it? b) an overview of your solution – how it works, why it solves the problem. Post the movie to YouTube and add it to our YouTube Group (again, same applies here, if you’d rather post it elsewhere, just link to it in comments below and we’ll make sure it gets looked at!)you can see a kind-of example of what your video might look like in the prototype walk-thru we do around 3 mins into this video.
go fast! Don’t spend too long on it – try to spend no more than a few minutes on a wireframe. If you’re not happy with it (and you probably won’t be at first!) just put it to one side and start fresh. You don’t want to labour over them too much at this stage.
you don’t have to be good at drawing: just take a quick browser through the images on the Flickr group if you want to get a sense of how un-pretty our wireframes usually are (particularly mine!). They’re not meant to be pretty, they’re meant to communicate. Even if they don’t do that, we have the video :) Don’t be shy.
everyone’s invited (not just ‘designers’) – Don’t think you have to be a designer or a UX person to participate in this exercise – this is all hands on deck. If you’re not an experience Drupal user or designer, you may actually be at an advantage in this exercise!
Really, really, really looking forward to seeing what you come up with!
As you may have noticed, this is not your typical design project… there are things about it that are pretty unusual, but there are also some pretty standard aspects as well. We thought it might be useful to give you a high level view of the approach we plan to take.
On a project like this, however, a highlevel view is really the only one we *can* give because, in all honesty, we’re not exactly sure what we’ll be doing in 2-3 weeks time let alone 2-3 months time. We have a mud-map though, and this is roughly what it looks like.
We are working with the team at Acquia on this project and they run an Agile shop, so we’re going to be trying to synch into their iterations as best we can.
One of the biggest challenges for User Experience and Design work in an Agile environment is getting the strategy and vision of the design worked through – to that end we are very thankful that our friends at Acquia have been flexible enough to give us a nice big chunk of time which we’re calling ‘Iteration Zero‘ and in this time we are doing a whole load of thinking, and strategising and talking with you to work out what our overall strategy is. This is why we’re asking about audience, and tone of voice and those more ‘abstract’ questions.
By the end of Iteration Zero, which for us is around 14 April, we hope to have an overarching strategy and ‘framework’ for the proposed interface for D7 in the form of some pencil sketches and a sitemap, an agreed experience strategy, audience matrix and tone of voice. We will have tested framework using some low fidelity (paper) prototypes with a range of participants across the spectrum of our audience matrix and we will feel confident that we know what we are doing and where we are headed.
During this time we will be working closely with the Drupal community to understand *how* our framework can best be implemented for release with D7.
The remainder of our time on the project, (which runs until around the end of July) will be spent working through exactly how the strategy is implemented, looking at the very many fine details and issues that will need to be resolved, whilst also testing and iterating the work we have done based on the results of our testing.
How and when can you get involved?
During iteration zero – it is VITAL that we get the foundations of our strategy correct so please engage and continue to engage with us as we work through the strategy, audience and tone issues. This will be mostly in the form of you reviewing what we’ve come up with and providing us with your feedback.
Get involved with the framework design – we’re going to be posting (very soon) some initial sketches that show the direction we’re heading in – we would love to have your feedback on that.
As we did with the d.o redesign project, we’ll be doing a CrowdSourced Wireframe activity that we would invite you to participate in where we’ll be asking you to take a part of the Drupal Admin you think needs work and drawing up a solution (or, if you’ve done it already, why not submit a screencast to ‘Pimp Your Admin’ on our YouTube channel!)
We are also going to re-launch the Crowdsourced Usability Testing for this project – this time with a little more warning and some more structure – so we would invite you to help us test our designs with people around you and contribute to our understanding of what is working and what is not, and help validate our approach. In the coming week I will be releasing a lot more information around this, including some timings, so it would be great to have you on board with this exercise (and it would also make a great exercise for interns, students, people new to usability/UX who want to get some experience doing usability testing).
As the Acquia team start to take designs from us, they will also start releasing a working prototype that you will be able to review and comment on – I’m not sure on timings for that but I’d expect probably mid-late May (I’ll update when I know more).
So as you can see – there will be LOTS of ways for you to contribute all the way through the project, and, don’t let us limit you! If you have ideas we need to see, or other ways you’d like to contribute – please let us know!
You may have noticed that this is a WordPress blog. Both the D7UX and the Disambiguity blogs run WordPress. Mark Boulton Design uses Expression Engine. Since we first started working with Drupal there have been questions (and the occasional shout of #fail) that we continue to use these platforms and haven’t switched to Drupal.
Don’t we know Drupal can do all that WordPress can do and more?! Don’t we love Drupal?!
Well, yes and yes. We know Drupal is amazing and we love it (well, more to the point, we love the people all around Drupal), but unfortunately, for the time being, it is too broken for us to be able to do the work we need to do on this project at the pace that we need to do it. We don’t have time to ‘learn’ Drupal, nor the skills to bend it to our will (and make it look acceptably pretty), we can’t even get a blog post on the homepage (as you’ll see in the videos that follow the installation video about which I’ll post as soon as they finally make it up to YouTube).
We appreciate all the offers of porting this blog over to Drupal, but to be honest, I really like using WordPress and nothing I’ve seen of Drupal makes me want to switch over at the moment.
See, I love the *idea* of Drupal, but the sooner we all agree that from a User Experience perspective it is horribly broken and concentrate on FIXING that, the better it will be. Admitting this doesn’t make us Drupal Haters, far from it. It just makes us honest and informed. After all, we use a whole raft of tools to make and administer websites all the time – we actually have a pretty good perspective to be making this call.
If we didn’t *really* care about making Drupal amazing, we wouldn’t start difficult conversations like these ones. And there is a big reason why one of the key success criteria for this project is that once this project is done Mark & I will *want* to switch from WordPress and Expression Engine to Drupal.
And what of ‘eating our own dogfood?’ – well, again, back to that success criteria of Mark & I using Drupal once the new UX is implemented. If we’re not using Drupal then, I’m happy to be called on this. For now, the fact that we are NOT entrenched Drupal users is actually a great advantage to us, rather than a disadvantage. It gives us perspective, distance from the project that allows us to see things differently, to challenge accepted ideas and approaches, to re-hash conversations that have been had a thousand times already and have them a little differently. It helps us not see that things might be impossible (and, at this stage of the project, that’s a good thing).
We’re not entirely ignorant of Drupal, not at all. And becoming less so every day. And we are surrounded by an incredibly informed and amazingly helpful community who give us *way* more help coming to terms with Drupal than the average ‘newcomer’ would have.
We know that Drupal is not WordPress, and we have no intention of making it so, but using WordPress helps us get our work done faster and easier for the time being, and it helps us maintain perspective and distance – and for now those things are really important to us.
But if, this time next year, this blog isn’t running on Drupal and if it doesn’t look amazing – then please come and shout #fail as loudly as you can. Because then you’ll be completely right, we will have failed.
Let’s not do that. Let’s make Drupal amazing.
And thanks so much to everyone who has come on board and started to help shape D7UX by responding to our initial Experience Strategy, Audience Matrix and Personality Quiz. The feedback has been incredible and insightful. We’ll have more for you to look at soon!
So, there we were, just starting to work through the workflow for Drupal – we got as far as the login screen when we thought ‘let’s write something nice on this screen’, and, pen poised… we were stumped.
We wanted to write something friendly like Moo would. Or Innocent drinks. We wanted to make it visually interesting like Vimeo do. Or Picnik. But… is that Drupal?
We realised we have no idea what Drupal’s personality is. And it would make our lives much easier, and help make a much better User Experience, if we can work out what it is.
Isn’t this completely touchy-feely and a waste of time?
Well no. One way or another, words will go on screens and a personality will emerge. Or, worse still, a few personalities, or a few dozen personalities. Much better that we spend a little time and give a little thought and see what we can come up with.
So, here’s where you come in:
The Personality Exercise:
Take a minute to v quickly answer the following five questions. Go with your gut reaction, don’t over think it. Try not to read everyone elses’ responses first. Don’t worry about being silly! (This is a kind of silly exercise after all, albeit useful)
If Drupal was an animal, what would it be?
If Drupal was a celebrity, who would it be?
If Drupal was a car, what would it be?
If Drupal was a profession/career what would it be?
So your answers might look something like this:
Drupal would be a squirrel/Paris Hilton/SS Commodore Ute/Teacher*
Get to it – what do you reckon?
*the opinions expressed above are not those of the author. Except for the SS Commodore one.
My name is Leisa Reichelt. I am the Head of User Research at the Government Digital Service in the Cabinet Office.
I lead a team of great researchers who work in agile, multidisciplinary digital teams to help continuously connect the people who design products with the people who will use them and support experimentation and ongoing learning in product design.
If you're interested in working with me or would like to talk more please email me