With AI agents that can interact with and contol UIs becoming widely available, I would use them to do rapid A/B testing. Define a set of tasks and repeat the process with a variety of agent models. I'm sure the results would provide valuable insights.

Its called BETA testing 🤷 (name it that way and the users will do the job for you) 🤝 EA It's In The Game (dabum tss) 125 characters reached 🫥

When faced with limited resources for usability testing in rapid projects, focus on lightweight, high-impact methods like guerrilla testing, remote testing, or hallway testing with a small number of users to quickly gather actionable insights. Prioritize testing the most critical user flows and use prototypes, even low-fidelity ones, to validate key interactions. Leverage internal feedback from cross-functional team members, use heuristic evaluations, and apply UX best practices to identify obvious issues. Additionally, iterate frequently based on quick feedback loops to maintain UX quality despite tight constraints.

What I have come to understand is that having no usability testing is bad as compared to having few usability testing. You can actually reduce the number of users to a reasonable size and not go above an beyond for what might actually become a repetitive output. Stick with a size that isn't too small to give you an accurate data and isn't too large that takes a chunk of your resources.

Improving UX quality can be done by focusing on user needs and problems that are informed by simple direct interviews. Quality can also be improved by doing rapid prototyping so that feedback can be obtained quickly. Learning from other similar products can also help improve UX quality.

1. Prioritize Critical User Flows: Focus testing efforts on the most essential user tasks and flows that directly impact the core functionality of your product. 2. Lean Usability Methods: Utilize quick and cost-effective testing methods like guerrilla testing, remote unmoderated testing, or hallway testing to gather valuable feedback efficiently. 3. Leverage Existing User Data: Analyze existing user data, such as analytics, support tickets, and feedback forms, to identify potential usability issues and inform your design decisions.

When facing limited testing resources on rapid projects, quality UX is about strategic focus, not exhaustive testing. Start by identifying the make-or-break user journeys that truly matter. A quick 15-minute session with just 3 to 5 users or coworkers from other teams often reveals more actionable insights. Another consideration is don’t overlook what you already know. Existing analytics and patterns from similar features can validate decisions when you can't test everything from scratch. Remote testing tools have also been game changers, allowing teams to collect focused feedback asynchronously while completing other work.

Use built-in quality principles with "shifting to the left" steps. The main idea is to perform quality checks from planning stages and through the execution so that quality is maintained throughout the development, and is checked early & often. As oppose to performing quality only towards the end of the development. You will get least quality issues through this path and will overall spend less resources and time.

Ensure UX quality with limited resources by focusing on high-risk areas, using guerrilla and remote testing, leveraging heuristics, internal feedback, and existing data. Prototype early, rely on design systems, and plan for quick post-launch fixes.