[Use cases](https://letsfindwhy.com/use-cases) # Remote usability testing your whole team can watch LetsFindWhy runs moderated usability tests over video in the browser. The respondent joins from a link with no account or download, shares their screen once you approve it, and works through your tasks while you guide them. Designers and engineers watch live as hidden observers and talk it over in the Backroom, and every session is recorded and transcribed. ## Why watching beats reading the report Usability findings land differently when the team sees someone struggle with their design first-hand. Most teams know this, but fitting six colleagues into a calendar slot, and keeping them silent and off camera, is hard enough that it rarely happens. Observers in LetsFindWhy never share a camera or microphone and do not appear in the respondent’s participant list, so you can invite the whole team without changing the session. ## How to run a usability test in LetsFindWhy 1. **Put the tasks in a guide** Write each task as a guide question, such as “Find last month’s invoice and download it”. The guide becomes a live checklist in the meeting room, so no task gets skipped. 2. **Send the links** Each interview has a link per role. Send the panelist link to the respondent and the observer link to your team. Respondents need only a browser. 3. **Run the session** Admit the respondent from the waiting room and approve their screen share request. Ask them to think aloud while your team discusses what they see in the Backroom. 4. **Review and share** The recording and transcript follow the session. Search the transcript, click a line to jump to that moment, and download the MP4 to cut a highlight reel. ## Example usability test guide 1. Tell me a little about how you handle invoices today. (Open ended) 2. Task 1: you need last month’s invoice for your accountant. Show me how you would get it. (Open ended) 3. From 1 to 5, how easy was that? (Rating or choice) 4. Task 2: give a teammate read-only access to your workspace. (Open ended) 5. What did you expect to happen when you clicked that? (Open ended) 6. If you could change one thing about what you just did, what would it be? (Open ended) ## Tips for better results - Write tasks as goals, not instructions. “Find last month’s invoice” tests your navigation; “Click Billing” tests nothing. - Run a pilot session with a colleague first. A task that reads clearly in the guide often turns out to give the answer away. - Tell observers that the Backroom is theirs: the respondent cannot read it or see that it exists, so they can comment freely. ## Frequently asked questions ### Does the respondent need to install anything? No. LetsFindWhy runs in the browser. Respondents join from a link as a guest, set up their camera and microphone, and wait in a waiting room until you let them in. ### Can the AI moderator run a usability test? The AI moderator is built for interviews: it asks your questions and follows up on what people say, but it does not watch the screen. For task-based testing, moderate the session yourself, and use the AI moderator for interview-style studies. ### How many people can watch a session? It depends on the plan. The pricing page lists how many observers each plan allows per session. ## Learn more - [Live interviews & meetings](https://letsfindwhy.com/docs/meetings) - [Recording & playback](https://letsfindwhy.com/docs/recording) - [Plans and pricing](https://letsfindwhy.com/pricing)