Answering the brief we set ourselves
As mentioned in my last post, we were working both in a collaborative and ‘agile’ project. This basically means the designers, user experience experts, developers and the client all work together in parallel: continually iterating designs, wireframes and actual prototypes together, regularly testing with users and trying to gradually get the designs right by a process of trial and error. Weekly ‘show and tells’ with the whole team and wider presentations to key stakeholders might have seemed time consuming, but it kept the whole design process on track.
How we deliver
In this post I’m going to outline the way in which we, as a team, have delivered this project to date as well as highlight some of the processes and tools we’ve utilised and hopefully give a bit more perspective on the scale of some of the tasks this project is trying to overcome.
Building solid foundations
First came the brief: Design a new look and feel for tfl.gov.uk: a site used by 75% of Londoners that already has a satisfaction score of 90% and working in an ‘agile’ project with the TfL team and two other agencies.
No problem, we’ll just go and fetch our thinking caps and get started.
However, what we hadn’t quite appreciated was the fact that when you’re in the pub in London and you mention you are working on the new TfL site – absolutely EVERYBODY has an opinion.
So no pressure then…
Where on earth to begin?