Quickstart

This walks through running your first simulation against a live URL.

Before you start: you may only test properties you own, operate, or are expressly authorized to test. See Authorization & limits.

1. Open Fraser#

Sign in at fraser.lythe.ai, or add the Fraser teammate to your Slack or Microsoft Teams workspace and run everything from there. If you don't have access yet, contact sales. New here? Walk through Onboarding first to connect your workspace, Jira/Linear, dev tools, and PostHog.

2. Choose a target#

A target is what the personas will actually interact with. For a first run, use a public URL you own or are authorized to test. A pricing page or a signup flow is a good choice, because friction there is easy to recognize.

Fraser also accepts screenshots, prototypes, and Android APK files. See Simulations for the full list.

3. Pick your personas#

Start with two or three contrasting personas rather than a crowd. A useful default trio:

• someone impatient, who abandons on any extra step
• someone evaluating whether to adopt, who wants specifics and proof
• someone who navigates by keyboard and screen reader

Contrast is what makes the findings legible, if every persona agrees, you learn less.

4. Set the goal#

Give the run a concrete objective, phrased the way a real user would hold it in their head:

Find out what this product costs for a team of 10,
and decide whether to book a demo.

Vague goals ("look around the site") produce vague findings.

5. Run it, then read the findings#

Each finding names the specific screen and the behavior it caused, for example:

Unlabeled left nav icons cause hesitation
Navigation icons in the left sidebar lack text labels, causing users
to hover over each icon to discover its purpose before navigating.

Findings come with suggested fixes. Read Findings & reports for how to triage them and what the severity signals mean.

6. File what matters#

From the run, or from Slack or Teams, send any finding to Jira or Linear as a ticket. The suggested fix rides along, so the ticket is ready for someone to pick up. See Slack, Teams & tickets.

Next steps#

• Re-run the same personas against your own flows across builds to calibrate what "good" looks like.
• Wire a re-run into your release checklist so regressions surface early.
• Read Testing a web flow for a deeper worked example.