User Acceptance Testing Challenges

  • Dedicate team member time: It doesn’t work to have UAT performed as an additional responsibility for team members who already have full plates and schedules. UAT will not be performed well, and the product will be viewed negatively by those who are asked to perform UAT in addition to their regular work, especially if it means after-hours work.
  • Single point of contact: Multiple team members can be doing UAT, but the feedback and findings need to flow through a single person. Too many people trying to communicate and collaborate with the product team on issues or clarity of functionality creates confusion. One person should be responsible for distilling and communicating with the product team on any UAT issues.
  • Context: One of the reasons to have a single person manage UAT findings is that this person should have the context of how the functionality of a product is expected to work and why. Not just at a basic functional level but at an experiential level too. This helps speed the communication and remediation of an issue with the product team. It will also allow the person to prune the list of issues before involving the development team.
  • Timely: UAT happening promptly is critical because the more time elapses, the more it impacts a product’s timeline, the more context gets lost, and the more expensive the effort becomes. UAT that happens randomly or at unexpected times isn’t accounted for as part of a production schedule and roadmap, so it will cause the product team to have to adjust. It will also create workflow and staffing challenges for a product team expecting UAT to happen at a particular time and pace. Unexpected timing and workflow from UAT send product teams into reactive mode instead of a planned mode. This causes friction around designer, developer, quality assurance, and DevOps involvement and scattered work rather than intentional.
  • One place to track findings: All UAT findings should be tracked in one place. It doesn’t matter where so long as the UAT lead and product team agree on where and how. The tool for tracking UAT findings matters less than it happens in one place in an agreed-upon manner. Too often, UAT findings are being tracked and documented differently by team members performing UAT. The UAT lead needs to enforce where and how UAT findings are captured. This is another reason to have a UAT lead.
  • Significant releases: The intent is to have iterative, minor releases, but when a substantial release is unavoidable, the workweek should be organized to remove most regular duties from SMEs involved in testing and allow that group to focus on testing during a designated block of days strictly. This ensures all testing gets done promptly and everyone is given the appropriate time and space to be thorough.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store



We help companies fuel growth through technology. Connect with us at