I was recently speaking with a potential client about a project that I very much wanted to work on. Due to scheduling issues (theirs and mine) we ended up with one week in which we could both be available to work on the project. At first, it seemed like the logical thing to do was to walk away and hopefully refer them to someone else with more time on their hands… but we really wanted to work together. We started thinking… could it be possible?
And so it was that we ended up working on one of the most intensive design and research projects I can remember working on. It was hard work, but good work and – in the end, we got the job done. I thought it might be useful to share the format we used so you can consider potentially this approach if you find yourself in a similarly time challenged situation some day!
Important note: this is not a sustainable way of working. You can do this for a week, you can’t do this week in, week out for a year.
We started the week with lot of data/content in a database, a target audience (digitally excluded), a content management system (SharePoint 2010), an accessibility goal (triple A) and a logo.
We needed to end the week with a high fidelity prototype that could be taken into production the following week.
We wanted to do this taking a user centric approach, ensuring that our concepts were evaluated by members of our target audience throughout the design process.
It was evident from the get-go that this was going to take more than me. I’m a freelancer, so this mean that I had the pleasure of hand picking a team to work with me on this.
I also asked
We pretty quickly realised this was a great opportunity to invite an intern to work with us. Not only could we really use an extra set of hands, it was a rare opportunity to see pretty much a full UCD project in the space of a week. We were thrilled when
In addition to this we also had four members of our client team on site for the entire week including decision-making-enabled representatives from marketing, content, technical and their project manager.
Finally, we had a daily call scheduled with the
We needed a space that would allow for our team to be onsite, to do workshops, design work and to conduct research. We booked some space at the
On the final day, we de-camped back to the client’s offices to wrap up our work and prepare for a presentation to the larger client team.
The general shape of the project was this:
- 1 day of UX ‘foundations’ and initial concept development
- 3 days of prototyping, researching, iterating
- 1 day of completing templates, annotating and preparing presentation
- a day or two in the following weeks to finalise any outstanding work.
- 3x UX resources for all 5 days, 1x ‘visual’ design for the last 4 days (+ several extra days in following weeks)
The general shape of the day tended to be:
- project team ‘kick off’ meeting in nearby cafe around 8am
- full team kick off in labs around 9am
- work, work, work, work, work,
- full team debrief at end of day
- project team continue work/debrief at pub/over dinner that evening.
There was limited time for preparation, and this largely consisted of agreeing a recruit brief for research, briefing recruiters, reviewing existing materials that the client had (mostly from an aborted previous attempt at this project), and project planning – working out a rough idea of what we were going to do on each day and a fairly specific plan for day one.
Day one: UX Fundamentals
This day had to provide the grounding for the rest of the weeks work – we needed to:
- clearly articulate the value proposition
- clearly identify and describe the priority audience(s)
- understand the primary scenarios of use that we wanted to support
- come up with some concepts for how we might present the our content to this audience to support these scenarios in a way that clearly expressed and supported the value proposition.
Our approach to the first three items entailed extensive use of post it notes, individual brainstorming, collaborative affinity sorting and prioritisation. Our approach to the final item involved a lot of group sketching (including our client team, of course), discussion and ranking.
As we left the lab at the end of the first day we did have a couple of concepts we were going to move forward with but we weren’t feeling particularly inspired by them. Upon decamping to a local pub that evening (in preparation for meeting and briefing Mark who was joining the team that evening) it became clear that we had quite a bit of affection for one of the concepts that we’d dropped while in conversation with the client – it was perceived as a little too risky. Over a pint, we did a little more work on this concept and got it into a sufficiently good shape to include as an option to present in research the following day. We then went to get pizza and bring Mark up to speed.
After our morning kick off, Mark took the client team off to start work on the ‘look and feel’ of the site, starting with a mood board exercise. Meanwhile, in the observation room, the UX team were frantically building prototypes of 3 concepts (using
By midday, three very rough prototypes and one very unrehearsed discussion guide in place – the research began. We saw six people in the rest of that day – tag teaming research between Andrew & myself, clients watching every moment of the interviews, and design happening on the fly meaning that no two participants saw exactly the same prototypes.
By the end of that day, we had learned a lot. We’d abandoned one concept entirely, introduced another, were pretty sure two concepts were not right and that the concept we’d rescued in the pub the night previous – the risky one – was going to be the right way forward – but it still felt a little scary. We needed more evidence it was right. We didn’t have much to show the Shaw Trust for them to advise on.
That night, we were all pretty nervous.
Four more research participants today. At some point it becomes evident that the ‘risky’ version is definitely the way forward. A whole range of participants have now managed to identify personally with it (beyond our expectations) when our initial fear was that it would be alienating. We leave Mark to grapple with increasing the fidelity of the design and move onto tackling the more content rich templates and, as it turns out, the content itself.
We uncover a range of information architecture issues, particularly around terminology/labelling on a freshly ‘redesigned’ content model, we completely reshape the way the content is presented and in the process get very excited about a fancy faceted navigation system.
The Shaw Trust remind us that people with cognitive disability will struggle to make sense of our fancy faceted interface. We realise we’ve gotten excited about an idea and forgotten about our audience (who are not necessarily cognitively disabled, but who are the least experienced web users). We prepare to kill our darlings.
Another four participants today. Having sketched all the way home yesterday and back again this morning, over coffee before our kick off meeting I have a feeling I may have replaced yesterdays darling facets with a much simpler solution that properly matches the needs we’re hearing coming out of research.
Our clients are more energised and excited about this project than they were at kick off and this is in no small part due to them having the chance to actually witness the people they work to help every day, actually using the system we’re designing for them. These people are stepping out from behind stereotypes and suddenly feeling a lot like us – but with the specific needs they have more clearly articulated than ever.
We test the newly simplified data-rich interface and struggle to keep a straight face when the participants describe the hard to make sense of page they’re expecting to see, then react with visible delight when they see our stripped down page, designed to focus specifically on the content they are seeking. (You don’t get those proper delight moments often, we cherish those).
We copy and paste ‘high fidelity’ designs into our prototypes as parts of them are ‘ready’. Headers and footers first, then bits of content as it starts to feel like it’s working.
We’re having all kinds of difficult discussions with the client about corporate colours and logos, but we’re also able to test our variations as we go – to understand which fights are really worth having and which are less so.
Even now, we rarely show the same prototype twice. Constantly refining.
We leave the lab on day four feeling pretty amazed at how confident we feel that we’ve actually, really cracked this. That it’s actually going to work.
We’ve got a meeting room at the client’s offices. We make a window full of post it notes of outstanding tasks, we prioritise and allocate the tasks. We make tea. Lisa, miraculously, produces a packet of chocolate biscuits.
We work as fast as we possibly can to work through the details of the templates, to make sure we can map the database to our templates, that we can make any ‘massaging’ that needs to happen to the content relatively painless, that we’ve thought through various states and orders in the flows.
We put together a presentation of the work we’ve done over the past week, our rationale and our designs. We do this so quickly it takes less time to make the presentation than it does to give it.
We kick off our presentation by showing some of the profiles of participants we’d met that week – young single mothers, people suffering from mental illness, people who are now or were recently homeless, or in prison. People who really need us to help make access to services easier to find – especially as more and more of those services go online.
Our client is happy with the work we’ve done, but we’re not really surprised because they’ve been there, with us, helping make decisions and seeing how and why decisions were being made the entire time.
Wrapping up and next steps:
Not everything happens in a week. The following week we put the wireframes into a more formal document with annotations and some notes to capture the general principles of the design approach and content strategy.
Mark has more work to ‘design’ all the wireframes into developer-ready templates. We’re still struggling with the homepage … we know the components that need to be there but getting them to work visually is tricky.
We do a handover meeting with the client to talk through everything including any questions they have outstanding. There’s a bit of work required to properly map the database to the templates. We agree there is a whole other project required to look at the information architecture and bring it into alignment with our new findings and approach.
What we learned:
- your team is everything – you need a good, flexible, friendly, committed team to work this way
- having the client on site is invaluable. This approach would probably not have worked (or at least, worked so well) if they hadn’t been there participate, observe, field our questions, respond to our challenges.
- you don’t need to sacrifice research just because your timeframes are short. You will have to be flexible and not get hung up on process, but you will learn what you need to make good, informed, decisions. Also, you give your client the opportunity to see their ‘customers’ in real life. Both of these are invaluable.
- although you’re in a hurry, you need to take time to communicate.
- if you want to work like this you need to be brave and confident, you can’t be a perfectionist, you have to be careful with your client seeing you making mistakes and being wrong (all part of the process)
- not only does an approach like this work but it works well. As a team, we were inspired and energised and felt we’d probably done some of our best work because of the way we were working not in spite of it. I think we’d all be keen to work this way again. (As soon as we get leave from our families who we saw very little of that week).
Photos by Lisa Drake. Thanks to Start Here for being brave enough to work with us this way!