Recap: Lean UX Conference 2015
by Rick Damaso
Let’s face it. We have become a “Google it” society. We can answer almost any question in .00012 seconds (according to Google’s search results page) and get a pretty accurate response. So, before attending the LeanUX15 conference in Brooklyn, NY, I wondered what would Google’s response be for UX’s impact on modern day Systems Development Life Cycles (SDLCs)? Was it even possible to wrap terms like DevOps, Kanban, Lean or Agile into a neat package with a UX bow on top?
More importantly though, does this matter? Or were these terms just the buzzwords from the “The Valley” that larger companies all around were simply talking about emulating? Do new philosophies really only announce themselves when blue chip companies start adapting them?
To say it depends is a boring answer. But, of course, it depends. As a researcher, however, I wanted a straight and narrow answer.
I thought it would be prudent to first set the stage. Here are some quick snippets of what a quick Google Search will give you relating to these new SDLCs and UX.
Agile- Developers focus on sustainable development. Sustainability is about good estimation, effective branching strategies for managing code, automated testing to protect quality, and continuous deployment to get fast feedback from users.
DevOps- DevOps is a software development method that emphasizes communication, collaboration (information sharing and web service usage), integration, automation, and measurement of cooperation between software developers and other IT professionals.
Kanban- Technique for managing a software development process in a highly efficient way. Producing software is a creative activity and therefore different to mass-production (Kanbans’s roots are in auto manufacturing) allowing us to apply the underlying mechanism for managing “production lines”.
Lean UX- Lean UX is a set of principles that may be used to guide you to better, more desirable solutions for users. It’s not a process in which each tool is rigidly applied. Instead a group of ideals and principles to guide you in the design process.
So, that makes sense. If I was a designer sitting in a room with other designers, communication and putting this philosophy in practice shouldn’t be that difficult in theory. But, when you take these practices out of Silicon Valley and introduce it to the landscape of companies like Microsoft or Spotify with teams of designers on separate continents, it can make your head spin. How could you package what looks and feels like a startup mentality and scale it up effectively?
LeanUX15 took this challenge head on during a four day event in Brooklyn, NY. This conference was not all that different from any other, unless you consider flamingo colored windbreakers and Paul Bunion beards different. But, all “hipster” jokes aside, the usual laid-back vibes you find in the heart of Brooklyn’s Williamsburg neighborhood was noticeably different. Product managers, Lead Designers, Software Engineers and representatives from some of the world’s most iconic brands were buzzing with excitement on bringing these results driven practices to companies everywhere.
As UX researchers, we encounter organizations along all stages of the UX maturity cycle and work on projects from formative to summative stages, so I was pleased to hear that UX research is taking a prominent role in these SDLCs. As opposed to traditional validation testing, we were now seeing rapid production of software married with UX researchers, architects and designers alike.
So what does this force us to do? To borrow from one of the themes of the conference, it means we are now in the age of Designing for Service, Not Just Software.
Here are some quick hits as to how UX is impacting development and strategic vision:
- Visualize your work, in knowledge clusters. Ideas are then disseminated to users as solutions in terms of their problems.
- With a UX lens, setting realistic Work In Progress limits for each stage of production is critical. Accounting for time slots within stages for user testing as opposed to piecing it together at the end.
- Manage flow to clearly identify bottlenecks and accurate metrics. When infusing UX research into your design process, you are hedging against expensive “revamps” at the tail end of your SDLC.
- Make Policies Explicit. Stick to your design, research and implementation policies! However, the #1 policy should always be, “If one of your policies does not work, change it”. By first following your process and analyzing what is wrong, you will be in a much better position to fix it.
- Implement Feedback Loops. Communicating accurate measurement with your target market is key. Measurements need to be relevant to the timing of your project, not “at the end of each quarter” or when “you have time for it”.
- Empowering yourself and your team to think- you are allowed to think and change processes. These SDLCs are not recipes, instead they are thought of as disciplines. Every question you ask yourself must be phrased as, “is this a driving force to consider design for servicing users or just designing software?”
The message for us as researchers when entering a new frontier of rapid development and testing can be wrapped up with a quote by Prof. Barbara Adam:
“The message for research is unambiguously clear: learning is a process with a history and a future; it is thus not containable within observable moments. It entails a joining of life-worlds, a drawing on collective and individual past knowledge as well as projected vision, all of which are brought to bear on the interactive present.”