Old Tin Roof

A little bit of me, and everything else

Design Jam London #3 — Serendipitree

Last week­end I attended a one day UX-fest called Design Jam Lon­don #3.

It was brought to my atten­tion by my col­league Jae Lee , here at For­ward, and with­out his help I wouldn’t have been able to bag a ticket.  There were only 50 tick­ets avail­able, and as they were free, there were a lot of peo­ple keen to get hold on one — thank­fully Jae’s fast mouse-work man­aged to secure me one.

I’ve not been to a work­shop / hack­day type day before, so entered the event won­der­ing what would hap­pen, what type of peo­ple I’d meet, and more impor­tantly what could I con­tribute & learn.

The event was held at the City Uni­ver­sity build­ing just off Northamp­ton Square, near Lon­don, which was thank­fully a nice sunny 15 minute stroll from my apartment.

Johanna intro­duced the day, set out the brief and a few tech details, and got the teams to start work.  We had essen­tially 7 hours or so to take a design chal­lenge and come up with some kind of pro­to­type or at least wire­frames of a product.

Team Waltz

We assigned our­selves into groups based on our skillset, and I found myself in team 3.  There were four of us (left to right in the photo): Adam (@admataz), Steve (@subcide), Jason (@jasonchanoz), and me.

Adam, Steve, Jason, Les

We came up with the team name very quickly — Steve said as we were team 3 with 4 peo­ple, it was like the time sig­na­ture for a waltz: 3/4 — so from that point we were Team Waltz.  This pretty much turned out to be the norm for us for the rest of the day, as we were able to get past the small details and get in to the big issues & work on the brief pretty quickly.

We all brought dif­fer­ent skills to the table, with devel­op­ment, design, and UX all rep­re­sented in pretty equal measures.

The teams were encour­aged to keep track of what they were doing on tum­blr blogs.  I found this to be a great way of doc­u­ment­ing the process, so I tried to write out the dif­fer­ent phases we cov­ered dur­ing the day.

Rather than repeat­ing myself and typ­ing out every­thing we did on the day, here’s the tum­blr blog for our team:

Team Waltz

At the end of the day we held pre­sen­ta­tions to show what we had all man­aged to put together in the time allowed, using the tum­blrs (thank good­ness I’d been typ­ing for most of the day) and any sketches we needed.

I was happy to present our teams work as I was really proud of what we’d achieved, and every­one else was more than happy to let me!

What I learned

As I men­tioned ear­lier, I’ve not done any full time UX work in nearly 2 years, but found to my relief that a lot of the tech­niques I’ve been using for a many years before are still valid.

In the time allot­ted to the prob­lem we were acutely aware that some really use­ful UX tech­niques were impractical.

We really didn’t have time to do any user research, and as such didn’t feel we could build valid per­sonas to base our work on (hence the very rough generic per­sona we created).

We also didn’t really have any time to do any paper pro­to­typ­ing, or any user test­ing of our ideas, rely­ing only on the good bal­ance of peo­ple in our group.

How­ever, even though there were a lot of restric­tions on what tech­niques we were able to use, the team worked really well together, and it rein­forced how much I enjoy work­ing in a team to resolve a com­plex problem.

It was great to see what the other teams were able to achieve in the time too — and to see the var­i­ous tech­niques employed to get to the final result. You can read the other teams tum­blrs: Team 1Team 2Team 4,Team 5Team 6Team 7Team 8Team 9 & Team 10.

I’d def­i­nitely do another one of these UX days, and have now started to look into other UX events that are going on.  I’ve missed the design and user expe­ri­ence part of my work as I’ve been focussing only on front end devel­op­ment for the past 18 months.

Design Jam relit the fire for me!