Remember your first Agile project? It took a lot to convince people to trade lengthy spec documents for a stack of index cards, but everyone knew things needed to change. Even still, success wasn’t guaranteed and there was plenty of anxiety to go around.
Now imagine that same software team changing processes yet again, this time taking their first steps to incorporate user-centered design into their work. How will everyone feel? Who’s rooting for the change? How high are the stakes?
Avoiding a Big Bang
I’d argue this team should consider ramping up gradually and deepening their design process over time. Depending on the interpersonal dynamics, a Big Bang for design can be unnecessarily risky.
When start a project with a new client, the “bang” we gravitate towards is bang for the buck. We begin with lightweight techniques that yield outsized results and give the client a taste of what user-centered design offers. Here’s a few examples:
- Story Mapping is a lo-fi activity that uses sticky notes to take agile user stories to the next level. You start by calling out the users’ target outcomes, and then you break out the sequence of activities users actually perform to achieve each one. It’s a great way to clearly define the problem you’re solving, enabling you to work backwards and design a solution that fits.
- Personas are very tricky for inexperienced teams; if you’re just getting your feet wet, schedule five interviews with real users and discuss what you learned with the core contributors. Most teams walk away with at least a few ways to improve their offering and a better sense of the users’ target outcomes.
- If you think the team is ready for a more specific mental picture of the users, pull the names of your archetypes (i.e. personas) from the characters used in your marketing demos. You’ll have to pick some names to use for your demos anyway, and this gives the team a way to connect the personas to something concrete.
- Basic usability testing can be done in the hallway; skip the fancy lab environments with one-way glass until you really need it.
Each of these methods pave the way for more extensive practices in the future while building credibility and comfort with a design-driven process. The idea is to hand out an appetizer and see how people react before serving a big plate full of UX methodology.
One step at a time
I recently saw Dr. Steve Julius, former psychologist for the Chicago Bulls, give a presentation about behavior and process change within teams. When asked about the number one mistake people make in this area, he offered this:
They try to change too much, too fast—and they become zealots.
Sometimes, slow and steady wins the race.
Most of the tips above have been collected from the following (fabulous) books; I strongly encourage you to dig into them for more.
- Lean UX: Applying Lean Principles to Improve User Experience, by Jeff Gothelf and Josh Seiden
- Undercover User Experience Design, by Cennydd Bowles and James Box
- The User Experience Team of One, by Leah Buley
- User Story Mapping, by Jeff Patton