You’re convinced, some folks within your team are convinced but there’s still a few hold-outs to incorporating user feedback sessions into your product’s development cycle. Over my years as a designer on various software teams, here are some methods I’ve found to be successful in gaining larger buy-in for the UX processes within an agile environment.
In a nutshell I recommend that you clarify any misconceptions of UX testing, iterate in public and then stay consistent with your processes.
In last week’s edition of my Product Design Newsletter, I wrote in detail about conducting regular benchmark usability tests. The described process worked quite well within my agile software development team to ensure the ongoing high quality of our software. If you haven’t read that article just yet, go here and read about the process behind monthly benchmark user testing.
As the data from months of these benchmark tests accumulated, my team realized there were some additional positive, though unintended, consequences of the new testing schedule. Once these were realized, we were able to leverage these and attain even more results from the regular testing schedule. These results included:
- 01 — Internal User Experience Training
- 02 — User Testing Awareness
- 03 — Increased Team Empathy Read more
Benchmark Usability Testing A baseline strategy for core user flows Paul, an early supporter of my product design mailing list recently reached out to ask me about the specifics of my process & strategy surrounding new features. Simply put, how did I get new feature ideas ranked, validated and built?
A fantastic question and one that led to some introspection about my validation process from past projects. What worked and didn’t work? What could I recommend to a fellow product designer to save him time? In short, the answer is to talk with your product’s target users. Then talk with them some more.