I recently presented The Designer is Present as the closing keynote for Interact 15. I adapted a workshop I had given at Fluxible, UX Australia and World IA Day into a shorter interactive talk. Below is the video, slides and a short interview.
Video
Slides
Interview with James Royal-Lawson and Per Axbom for the User Experience podcast
I was interviewed by James Royal-Lawson and Per Axbom for the User Experience podcast, in advance of today’s keynote The Designer is Present. You can listen to our short conversation below.
To download the audio Right-Click and Save As… (Windows) or Ctrl-Click (Mac).
I was stunned and saddened the other day to learn that Steve Sato had passed away. I had known him as a friend and colleague for many many years. In 2014, Steve contributed a War Story and then got up at my CHIFOO presentation and told his story to the group. It’s a lovely story that I think captures Steve’s humanity as he reveals how life at home grounded him creatively and intellectually no matter how far away, geographically, he was.
Thanks to CHIFOO, we’ve got a short video of Steve’s talk (embedded below) and I’m reposting his story below that.
Finding Mojo In The Moment
We were three days into our 18-day research trip. The clock was ticking and our progress had been frustratingly slow. We had nary an insight to show for our time spent here so far. It was 9 o’clock in the morning and we were already hot and sweaty after having walked a quarter of a mile on the footpath, the only way to a remote village in Uganda. Our team was doing field research on making microfinance more efficient and reliable, so banks and other financial institutions would find it profitable for them to extend their services to include microfinancing. The current system of paper and pencil, traveling back and forth to an office two hours away, and then transcribing notes onto a PC (“sneaker net”) was inefficient and fraught with errors and omissions. Furthermore, what was required was not only an IT system that could span “the last mile” but we had 15 days left to prototype an interaction model that would augment the device. It needed to be a process that the field agents and their clients would trust and adopt without much help. On top of that we had to identify what other not-for-profit and for-profit organizations (e.g., medical, agriculture, manufacturing and so on) would find the field device useful (so we could size the potential market for the device).
I was responsible for the research and the results. I really was feeling the stress and the jet lag and I had heartburn non-stop from the first day here.
We arrived at the village and our team was introduced by the microfinance agent to a group of a dozen women who were her clients. After a few minutes of conversation the women gathered and sat down, with the field agent, on the ground in a large circle. Two researchers stationed themselves behind the agent while the rest of us positioned ourselves around the perimeter of the circle. I turned on the video camera and thought “Whew! We’ve been prepping this for nearly a month and now we’ll finally get to make some interesting discoveries!” But then I spent the next half hour struggling to stay focused, to listen to the conversation and watch the exchange between a woman and the field agent. Then some amount of self-awareness seeped into my head: “The breeze feels so good, gosh! I’m so exhausted, I could go to sleep right now…let me see, it’s 11ish at night in Portland…Ohh! I promised I’d call my wife today!”
Without thinking, I pulled out my cell phone and looked to see if I had a signal. To my surprise I had one bar! By walking away from the group towards a little rise I could get 2-3 bars which was good enough!
It was good to hear my wife’s voice. I closed my eyes while talking with her for about five minutes, like I was only a block away. I felt calm relief return.
But then my eyes popped open, because with the relief came a realization, triggered by my ability to connect to my wife halfway around the world while I’m in the African back country, gazing at a group of women sitting in the grass under the shade of a huge tree, with puffy white clouds against a bright blue sky. It was surreal and so powerful. I experientially understood our mission: to connect the people here to the world in a way that would make their everyday lives better, as was happening to me in the moment. Suddenly I was re-energized and fully present. Throughout the rest of the trip I kept coming back to relive this experience. It kept me energized, engaged and focused, no matter how exhausted I felt. I honestly believe it made a positive difference in what we discovered, what we surmised and in our final designs.
I’m working on another book! It’s Epic Fail: Design Research War Stories, and is based on the War Stories that I’ve been gathering since 2012.
As design researchers, we love stories. At its simplest, our job is to gather stories and to retell them. War stories are accounts of contextual user research (research out in the field) and the inevitable mishaps that ensue. These stories are in turn bizarre, comic, tragic, and generally astonishing. This book will share some of the best stories, examine the patterns revealed by the stories, and articulate the valuable lessons they reveal.
Watch this space for a big announcement about the War Stories coming up after Labor Day. In the meantime, I’ve applied to speak about War Stories in design research at SXSW. You can help here (whether or not you are planning to attend SXSW) by creating an account, voting thumbs up for the proposed talk and even adding a comment.
We’ve got three recent stories, all from the Kitchener-Waterloo area: Jennifer’s War Story: Keeping the Lights on in Vegas
, Julia’s War Story: For Want Of A Shoe
and Susie’s War Story: A Sigh Is Just A Sigh. And coming up next month at Fluxible in Kitchener-Waterloo, I’ll be presenting Epic FAIL: Takeaways from the War Stories Project.
Jennifer Pretti is the Manager of the User Experience Design Team at Christie Digital in Kitchener, Canada.
At Christie Digital, we have a very niche population of users. Opportunities to observe them using our projectors are highly coveted by my UX team. In February 2014, we were invited by a good customer of ours, Staging Techniques, to observe their setup for the keynote address at Microsoft’s SharePoint Conference. The event was taking place at the Venetian Hotel, in Las Vegas, and the keynote speaker was going to be Bill Clinton. Bill Clinton!
Three of us from Christie made the trip: me, Chris (my lead industrial designer), and a software developer, Eric. Although I had conducted many user sessions for Christie before, this was the first time I was going on site to observe a live event setup and I wasn’t sure what to expect. My biggest worry was that, even though we made it clear we were there just to observe, I would be asked to answer a technical question or troubleshoot some problem and not have a clue what to say or do.
Setup was to begin at midnight the day we arrived. Working night shifts is very common for projectionists since it’s the best time to see and calibrate the light as other setup crews are already done and out of the way. The thought of staying up for a night shift wasn’t something I was particularly looking forward to, especially given jet lag was going to make it feel 3 hours later. But I hoped a mix of adrenaline and caffeine would do the trick.
After landing in Vegas, we headed down to the Expo Hall to get our bearings. The scale of everything in Vegas is massive and oversized, and the hall was no exception. It was a gigantic space – at least two football fields long and one football field wide – and it was completely empty and bare. Whatever vision the event planners had for the space seemed hopelessly unattainable in the 5 days left before the show.
When we arrived, big transport trucks were pulling into the hall to start unloading the many tons of equipment that would be needed to run the show. It was clear that they were behind schedule already. Trusses and scaffolding needed for rigging the projectors hadn’t yet been built, so we decided to split up, with Chris covering the first night shift, and Eric and I heading to bed to get some much needed sleep.
Eric and I returned to the site early the next morning to relieve Chris. The first few hours of our observation time were slow and uneventful due to continued delays with the truss work, but eventually things picked up, and soon projectors were being powered on and rigged into position. Excitement peaked when one of the projectors failed to power on. I stood poised to capture an epic story of problem solving and error recovery, but the crew just shrugged, taped an ‘X’ on the top of the projector, and replaced it with a spare one. Even after I got in touch with tech support to help explain the error code (highlighting quite clearly that our error messages need a lot of work), it didn’t change their approach. Time is money and using a functional projector was simply the most efficient option. Whatever the problem was, it could wait until they were back in the office to sort out.
It became clear by the end of the second night that the most interesting portions of the setup would be delayed past our planned departure date. The senior projectionist, Pete, pleaded for one of us to stay a bit longer. I think there was mix of professional pride in his insistence, but (happily for us) a realization of the mutual benefit of our presence, observing their workflows and listening to their wishlists. It was on account of his enthusiasm that I agreed to change my flight and stay an extra night. My fatigued body howled in despair. Another night shift? Are you crazy?!
There is no better place to change your sleeping patterns than Vegas. That city looks the same no matter what the hour: there are always people walking around, always a restaurant open, and enough indoor walkways that it could be any time of day. Hotel rooms come equipped with industrial-strength black-out curtains, whose existence I suddenly appreciated in a whole new light (pun intended), as I tried to convince my body that falling asleep at 10 AM was a totally legit plan.
The little sleep I got left me with major doubts that I could keep up a respectable and coherent state of mind for my last night. However, early into the shift, Pete insisted I help him colour match the displays. Colour matching 26 projectors is a very laborious activity that had us whizzing around on a golf cart, playing with light meters, and debating whether one projector was a fraction more magenta than the other. Shifting from observer to honorary crew member made the night fly by and gave me a more rich perspective of how our products are used.
I didn’t sleep until I was on the airplane later that afternoon. I welcomed the rest, but felt a pang of regret for not extending my trip long enough to see Bill Clinton speak. As social media began to light up with pictures of the event, I cheered for Staging Techniques and Christie for a job well done. And smiled knowing that Bill Clinton was walking on the same stage where I had been, just 24 hours ago.
I know it’s Thursday, but I’ve been on vacation all week, so here’s what’s going on for the remainder of this week
Julia Thompson is a Design Research & Insights Analyst at BlackBerry in Waterloo, Canada.
It all started with a simple question from the dispatcher: “Do you want a call when your taxi arrives?” My nonchalant answer: “No thanks, I should be okay.” was the nail in my coffin. This was my first error in a series of cascading mistakes.
The next morning I was heading out-of-country for in-home interviews. That night, in an effort to be as prepared as possible, I called to arrange a taxi for an early morning pickup. I hung up the phone and proceeded to pack my bags. I considered carefully what to pack. I visualised my next few days: what would the weather be like? What would be my mode of transportation? What clothing would be appropriate for the work – casual enough to fit into a home environment and dressy enough to fit into an office environment? I was sure that I had considered all the details. Unfortunately, the most important detail, my alarm, was what I missed.
Satisfied with my preparation, I went to bed, and slept well. The next morning I awoke feeling refreshed. With birds chirping outside, sunlight filled the room. Yet something felt terribly wrong. What time was it? Why was it so light out? I picked up my phone, checked my alarm, and then checked the time. My stomach fell to the floor. My flight was leaving now. Sheer panic overtook me. I couldn’t think straight. I had never missed a flight before. I felt like I was going to throw up. I was paralyzed, I had no idea what to do. I grabbed my phone and called our corporate travel agent. It felt like hours as I waited on hold to ask my pressing questions: Could I still make my interview? When was the next flight? Could I fly out of a different airport instead? The sound of my heartbeat drowned out every noise as I sat there waiting, palms sweating, phone clutched. The agent came back on the line and said there was a flight leaving from another airport in 2 hours. Could I make it there in time? It’s almost rush hour. It’s an hour’s drive with no traffic. What about parking? Customs? Security? If I took the car, how would my husband get to work? On top of all that the agent still wasn’t sure whether there was room on the flight. We decided, together, that I should start driving and I should stay on the line while she called the airline to confirm availability. I jumped in the car, with my phone on the passenger seat and that awful music taunting me as I continued to wait, on hold. I got about 10 minutes down the road when the agent told me to pull over and go home. That flight wouldn’t be mine. I would settle for another flight, hours later, and hours after my scheduled interview.
Later that day, as my plane came in for its landing, I just felt low. I was tired from the emotional rollercoaster of missing my flight, I was anxious knowing I’d have to tell the people I was working with what had happened and I was sad that I had missed out on an interview and the opportunity to see, first-hand, into the life of one of our customers. The only thing saving me was the fact that I was the client and so, even though I missed the interview, it still went ahead as scheduled.
The following day I awoke, in the right place and at the right time, with a better perspective on life. Our local research partner was gracious enough to include me in an interview that day. I was thankful. I was relieved. But now, that meant there would be four of us attending this interview. Two consultants and two clients; two too many. The consultant had called ahead and confirmed with our interviewee that it would be okay if an additional person (me!) attended the interview. Our interviewee was very accommodating and agreed to have all four of us into her home. I was so preoccupied with resolving my own error that I didn’t consider, until later, how the dynamic of the interview would now be affected.
We all got to the interview, we all walked in, we all sat down in the chairs offered to us by our interviewee. As everyone was setting up I started to look around and take note of the environment. I noticed several pairs of shoes neatly arranged by the front door. I looked over at our host, I looked down: bare feet. My eyes darted around the room, I looked down at all our feet. All four of us had our shoes on, laces tied. Bah! We were the worst guests ever. Weren’t we all, as researchers, supposed to notice something so simple but so important?
I spent the next five minutes cursing myself, my missed flight, the totally wrong and overpowering dynamic of four researchers to one customer, and the miss on basic shoe etiquette. I had to shake it off – all the feelings of shame, all the feelings of doubt – and I had to focus. I had to be in the moment, I had to get the most I could out of the interview and I had to show the interviewee the respect she deserved.
It ended up being a great discussion. It was, by no means, a textbook in-context interview, but we had a nice dynamic emerge nonetheless. My story is not one of a single epic fail, but instead of a series of errors with a cascading effect. “For want of a nail the shoe was lost, for want of a shoe the horse was lost…” Here, we had not a want for a shoe, we had too many.
Happy August!