User testing each stage of the development process
•
8 likes•1,669 views
User testing throughout each stage of your company’s development process is a surefire way to keep your intentions inline with your end user’s expectations. By integrating a ‘test and optimize’ approach from the outset of a new initiative you will be much less likely to run into major roadblocks and disappointing responses when you reach the finish line. You’ll be able to navigate questions raised during executive reviews by backing up your presentation with tested certainty, and build a business case for the more skeptical stakeholders.
Recommended
More Related Content
More from UserTesting
More from UserTesting (20)
Recently uploaded
Recently uploaded (20)
User testing each stage of the development process
- 1. User Testing each stage of your development cycle
- 2. By integrating a test and optimize approach from the outset of a new initiative, you will be much less likely to run into major roadblocks and disappointing responses when you reach the finish line.
- 4. Research + Planning IN THIS SECTION • Benchmarking • Competitive Analysis • Build Feature Roadmap
- 5. Research + Planning Learn how your competitors are succeeding, and where you can differentiate. Us vs. Them
- 6. Research + Planning Look at which of your competitors have found the right mix of content and design.
- 7. Research + Planning Test your current site to help define your feature roadmap.
- 8. Research + Planning Explore how people find your product, and why they chose you.
- 9. IN THIS SECTION Design • Wireframes + Prototypes • Information Architecture • 5 Second Tests
- 10. Design Include a 5-second First Impression test to see how people react to your design.
- 11. Design Narrow down design directions by asking participants to provide feedback on their expectations of each layout.
- 12. Design Test page titles, content, menu labels, imagery or icons.
- 13. IN THIS SECTION Prototyping • Prototypes • Navigation • User Flows
- 14. Prototyping Gain access to users’ feedback on information architecture, expected results and frustrations before launching into code. before
- 15. Prototyping Put your assumptions to the test. Does your prototype flow as smoothly for others who are not familiar with your product? 1 2 3 4
- 16. Prototyping Look for feedback on grammar errors, misconceptions and messaging mishaps during this phase. “ Huh?” What the. . .”
- 17. Prototyping Make note of awkward task wording so you can optimize your tests once you go live.
- 18. Development + Testing IN THIS SECTION • Transactional Tests • Social Integration • Multiple Devices
- 19. Development + Testing Look for functionality errors and technical product glitches that slipped through the cracks.
- 20. Development + Testing See where users stumble on data collection, social sharing plugins, and more.
- 21. Development + Testing Review how users react to product-triggered automated email campaigns.
- 22. Development + Testing Test the responsiveness of your designs across multiple devices. (Lightweight QA!)
- 23. IN THIS SECTION Release • Baseline New Site or App • Omni/Multi Channel Tests • Longitudinal Studies
- 24. Release If you were updating or modifying an existing feature, test how users feel it integrates with the rest of your site.
- 25. Release Examine whether or not your product is share-worthy. Are users interested in telling others about what you offer? What is their logic?
- 26. Release Test your primary conversion points and main user flows to make sure your launch provided the right experience for your customers.
- 27. Maintenance + Optimization IN THIS SECTION • Performance Metrics • Analytics Validation • A/B Testing
- 28. Maintenance + Optimization Re-imagine the weakest part of your product, A/B test to see which directions improve the experience. A B
- 29. Maintenance + Optimization Use analytics to determine areas that may need to be improved and test to understand the logic behind these statistics.
- 30. Maintenance + Optimization Learn whether the issues you’ve identified are significant to your audience and prioritize your maintenance backlog.
- 31. GO FOR IT! Short, manageable bursts of testing will often yield very powerful insights and help to keep your budget, resources, and used time to a minimum.