SlideShare a Scribd company logo

Witness wednesdays informing agile software development with continuous user insights

•
•
Rebecca Destello
Rebecca Destello

In the startup world speed to market is everything. This talk covers how it is possible to embed user insights into a rapid software development cycle by conducting usability studies that break the stereotype that "research takes too long." Justin Marx and Rebecca Destello illustrate how to plan, conduct, analyze and inform development sprints in just one week with what famously became known as "Witness Wednesdays." Justin Marx, Product Designer and Rebecca Destello, Manager, Research & Insights - both with Atlas Informatics.

1 of 29
Download to read offline
Witness Wednesdays Informing Agile Software Development with Continuous User Insight REBECCA DESTELLO & JUSTIN MARX ATLAS INFORMATICS
Rebecca Destello Manager, Research & Insights, Atlas Informatics @rebeccadestello Justin Marx Product Designer, Atlas Informatics justinmarxdesign.com
Atlas Recall is a photographic memory for your digital life — it’s your searchable index for everything you see across all your devices and apps. atlas.co
“By the time I’ve gotten research results, I’m working on the next feature.” “It’s hard to write stable production code when you keep changing things.” “High quality research takes more time than you think.” DESIGNERS TELL RESEARCHERS: RESEARCHERS TELL DESIGNERS: DEVELOPERS TELL EVERYONE:
The opportunity to iteratively validate assumptions DESIGNERS NEED... Validation that’s fast enough to keep up with Agile development A body of research upon which to base future assumptions
Active engagement from the team to identify problems and recommend solutions RESEARCHERS NEED... Organizational buy-in of their research findings
A validated, coherent design that allows them to plan ahead with confidence DEVELOPERS NEED... Minimal re-work so they can focus on building the next thing
Witness Wednesdays RITE + Agile usability testing WE SOLVE THIS WITH
WITNESS WEDNESDAYS ARE A fast-moving approach to providing continuous insight that lines up with Agile workflows A method that emphasizes team involvement in the research process, increasing buy-in and engagement
WHY ATLAS TOOK THIS APPROACH Research came in after the product was already built and in private beta First usability study demonstrated an urgent need for an onboarding experience Design team wanted to learn what was needed to help users understand how to use our product Urgent need to get ahead of the development cycle and validate features before they’re built
WHEN TO CONSIDER THIS APPROACH You want to load up the design team with user insight
WHEN TO CONSIDER THIS APPROACH The research program has fallen behind the development cycle
WHEN TO CONSIDER THIS APPROACH You need to get the larger organization on board with user research
WHEN TO CONSIDER THIS APPROACH Your team is suffering from analysis paralysis
Process
1. PREP THE ORGANIZATION Get researchers, designers and stakeholders together to define the study’s subject, scope, and expected outcome Get commitments from key people to attend observation throughout the study
2. TAKE CARE OF THE LOGISTICS Determine the recurring day for participant sessions (Wednesdays work well) Recruit 5 participants per week Secure the session venue and technology Determine the study’s duration
3. CONDUCT THE STUDY Researchers and designers collaborate to plan the study and accompanying prototype Mon Tue Wed Thu Fri Researchers begin writing the script, designers begin building the prototype
Researchers finish the script, designers finish the prototype, then review together Mon Tue Wed Thu Fri Prep the participant session room and technology 3. CONDUCT THE STUDY
Researchers conduct participant sessions Mon Tue Wed Thu Fri As much of the organization as possible observes participant sessions Researchers debrief with observers after each participant session Consider low-risk iterations after the third participant 3. CONDUCT THE STUDY
Researchers generate a brief email report to the organization outlining the findings Mon Tue Wed Thu Fri Researchers, designers and stakeholders discuss the results and ideate on solutions to top line issues 3. CONDUCT THE STUDY
Discussion and ideation continues, if needed Mon Tue Wed Thu Fri Given time, researchers begin work on the next week’s script, while designers begin work on the next prototype 3. CONDUCT THE STUDY
Mon Tue Wed Thu Fri Repeat for as many times as you planned, then evaluate extending the study 3. CONDUCT THE STUDY
Is this right for you?
WHERE ARE YOU IN THE PRODUCT CYCLE? Initial product or feature ideation Post-release optimization Leading up to release
CONS Taxing on the organization Analysis is not as thorough Subtle issues can be harder to discover Easy to blow through research budget
PROS Helps get research and design ahead of the development cycle Rapidly builds understanding around a product or feature Encourages the organization to build on MVPs
PROS Encourages experimentalism, because the risk is low Instills a culture of validation and iteration Biggest pro: Smashes the perception that research takes too long
Questions? REBECCA DESTELLO rebecca@atlas.co @rebeccadestello JUSTIN MARX marx@atlas.co justinmarxdesign.com

More Related Content

Witness wednesdays informing agile software development with continuous user insights

  • 1. Witness Wednesdays Informing Agile Software Development with Continuous User Insight REBECCA DESTELLO & JUSTIN MARX ATLAS INFORMATICS
  • 2. Rebecca Destello Manager, Research & Insights, Atlas Informatics @rebeccadestello Justin Marx Product Designer, Atlas Informatics justinmarxdesign.com
  • 3. Atlas Recall is a photographic memory for your digital life — it’s your searchable index for everything you see across all your devices and apps. atlas.co
  • 4. “By the time I’ve gotten research results, I’m working on the next feature.” “It’s hard to write stable production code when you keep changing things.” “High quality research takes more time than you think.” DESIGNERS TELL RESEARCHERS: RESEARCHERS TELL DESIGNERS: DEVELOPERS TELL EVERYONE:
  • 5. The opportunity to iteratively validate assumptions DESIGNERS NEED... Validation that’s fast enough to keep up with Agile development A body of research upon which to base future assumptions
  • 6. Active engagement from the team to identify problems and recommend solutions RESEARCHERS NEED... Organizational buy-in of their research findings
  • 7. A validated, coherent design that allows them to plan ahead with confidence DEVELOPERS NEED... Minimal re-work so they can focus on building the next thing
  • 8. Witness Wednesdays RITE + Agile usability testing WE SOLVE THIS WITH
  • 9. WITNESS WEDNESDAYS ARE A fast-moving approach to providing continuous insight that lines up with Agile workflows A method that emphasizes team involvement in the research process, increasing buy-in and engagement
  • 10. WHY ATLAS TOOK THIS APPROACH Research came in after the product was already built and in private beta First usability study demonstrated an urgent need for an onboarding experience Design team wanted to learn what was needed to help users understand how to use our product Urgent need to get ahead of the development cycle and validate features before they’re built
  • 11. WHEN TO CONSIDER THIS APPROACH You want to load up the design team with user insight
  • 12. WHEN TO CONSIDER THIS APPROACH The research program has fallen behind the development cycle
  • 13. WHEN TO CONSIDER THIS APPROACH You need to get the larger organization on board with user research
  • 14. WHEN TO CONSIDER THIS APPROACH Your team is suffering from analysis paralysis
  • 16. 1. PREP THE ORGANIZATION Get researchers, designers and stakeholders together to define the study’s subject, scope, and expected outcome Get commitments from key people to attend observation throughout the study
  • 17. 2. TAKE CARE OF THE LOGISTICS Determine the recurring day for participant sessions (Wednesdays work well) Recruit 5 participants per week Secure the session venue and technology Determine the study’s duration
  • 18. 3. CONDUCT THE STUDY Researchers and designers collaborate to plan the study and accompanying prototype Mon Tue Wed Thu Fri Researchers begin writing the script, designers begin building the prototype
  • 19. Researchers finish the script, designers finish the prototype, then review together Mon Tue Wed Thu Fri Prep the participant session room and technology 3. CONDUCT THE STUDY
  • 20. Researchers conduct participant sessions Mon Tue Wed Thu Fri As much of the organization as possible observes participant sessions Researchers debrief with observers after each participant session Consider low-risk iterations after the third participant 3. CONDUCT THE STUDY
  • 21. Researchers generate a brief email report to the organization outlining the findings Mon Tue Wed Thu Fri Researchers, designers and stakeholders discuss the results and ideate on solutions to top line issues 3. CONDUCT THE STUDY
  • 22. Discussion and ideation continues, if needed Mon Tue Wed Thu Fri Given time, researchers begin work on the next week’s script, while designers begin work on the next prototype 3. CONDUCT THE STUDY
  • 23. Mon Tue Wed Thu Fri Repeat for as many times as you planned, then evaluate extending the study 3. CONDUCT THE STUDY
  • 24. Is this right for you?
  • 25. WHERE ARE YOU IN THE PRODUCT CYCLE? Initial product or feature ideation Post-release optimization Leading up to release
  • 26. CONS Taxing on the organization Analysis is not as thorough Subtle issues can be harder to discover Easy to blow through research budget
  • 27. PROS Helps get research and design ahead of the development cycle Rapidly builds understanding around a product or feature Encourages the organization to build on MVPs
  • 28. PROS Encourages experimentalism, because the risk is low Instills a culture of validation and iteration Biggest pro: Smashes the perception that research takes too long