UserZoom → UserTesting

Refine the Decision Tool: give each of the 11 research goals its own icon and a short 3–5 word label on the card. When a UserZoom result shows, tint the result panel with the UserZoom accent; when UserTesting, use the UserTesting accent, so the tool is obvious at a glance. Add a small "Why is this a keep?" expandable under each UserZoom result.

On the Comparison page, add a text search box that filters rows by keyword in the "Research need" column, and keep the All / UserTesting / UserZoom toggle. Add a count ("Showing X of 11"). Make the table horizontally scrollable on mobile without breaking layout.

Turn "Rebuild Your First Study" into a horizontal stepper with a progress indicator (Step 3 of 7), Next/Back buttons, and one step visible at a time. Each step keeps its expandable detail. Add a "Start over" button at the end.

Make the Cheat Sheet a single printable page: the one-line rule at top, the full decision table, and a boxed "Keep on UserZoom" list. Add @media print styles that hide the nav and buttons and fit everything on one US-Letter page in portrait. Verify the Print button triggers the browser print dialog.

On the Seats and Access page, render the roles model as a simple diagram: the 20 Creator roles as a capped band, and Viewer/Collaborator roles as a separate unlimited/free band holding all 30+ designers. Below it, show the plan as steps: everyone gets a free Collaborator role; ~15 Creator roles go to frequent launchers; ~5 Creator roles form a rotating Flex pool; Admin reassigns Creator to Collaborator in seconds; monthly audit reclaims idle Creator roles. Keep it calm and enterprise-clean.

Add a new page titled "How to do it in UserTesting" - a step-by-step reference for designers coming from UserZoom. Present it as 6 expandable cards; each card has an icon, a title, numbered steps, and a highlighted "vs UserZoom" note at the bottom. Use this exact content:

1) Create a study (test) from scratch. Steps: Dashboard > Create test > pick Unmoderated test, Survey, or Live conversation (moderated). Pick what you're testing: Prototype, Website, or App, or start from a Template. Choose recruitment: Build audience (panel or Custom Network) or Create link (your own users). Build the Test plan: set Scenario + Starting URL, drag Task and Question blocks in. Name > Preview > Launch; pilot with 1 participant then add the rest. vs UserZoom: a "test" is the whole unit (no separate Study hierarchy); drag-and-drop canvas, not a study-type wizard.

2) Use an audience (targeting + screener). Steps: choose Build audience (Contributor Network or your Custom Network) or Create link (Invite Network). In the Audience builder set count, device, and demographic filters. Add screener questions (multiple choice; mark options Accept/Reject or May/Must select/Reject). Set count (qual 5-8, quant up to 30, surveys up to 1,000/segment). After launch you can add more of the SAME audience but not a new one. vs UserZoom: screeners are multiple-choice only; audience locks at launch.

3) Test a prototype. Steps: two paths - Interaction test + Figma task (click paths, heat maps, success rate) or a think-out-loud video test. Figma is the only native source; others go in as a plain URL. Create test > Interaction test > Add > Figma task > Connect prototype > paste link > define success path > add questions > audience > Preview > Launch. Results: Paths, Heat maps, Success rate, Steps, Clicks, Time on task. vs UserZoom: only Figma gets built-in path/heat-map capture.

4) Integrate a Figma prototype. Steps: in Figma - Present > Options > set scaling > Share Prototype > access Anyone > Copy link (the Present link with Node-IDs). In UserTesting - Create test > Interaction test > Add > Figma task > Connect prototype > Connect account > sign in > grant permissions > paste link. Define success path, add follow-ups, Preview. Pitfalls: re-copy link after any change; enable "Viewers can copy, share, and export" if connect fails; one interaction per component. vs UserZoom: never edit the prototype or success path after launch (breaks tracking).

5) Create written tasks. Steps: set Scenario + Starting URL. Drag the Task block, write the instruction. Optional Blur PII; Task metrics toggle Success/Difficulty. Phrase as a scenario with a clear STOP/endpoint. Keep Tasks separate from Questions. vs UserZoom: drag-and-drop palette instead of a "+New Task" dropdown; default task is think-aloud + recorded.

6) Add post-task questions. Steps: drag the question block AFTER the task. Multiple choice: type question + options, choose single or multi-select, add "Please explain your answer." Written response for open-ended. Rating scale 5/7/9/11-point (1 = negative); no native SUS type, build SUS as rating-scale questions. Optional post-test questionnaire appends 4 written Qs (4th = NPS). vs UserZoom: same single/multi concept, dropped as a block; missing native SUS is a real difference.

Keep it clean and enterprise-consistent with the rest of the guide.

Add a new page titled "Build the same study: UserZoom to UserTesting" - for designers who already build studies in UserZoom. Show 4 study types as cards; each card has the study type as a title and two side-by-side columns, "In UserZoom" (left) and "In UserTesting" (right) connected by an arrow, plus a highlighted "Key difference" note. Content:

1) Unmoderated usability study. UserZoom: Study Builder > Unmoderated Usability; add tasks with success metrics; set panel + quotas; launch; read the quant dashboard. UserTesting: Create test > Unmoderated (think-out-loud); set Scenario + Starting URL, drag Task blocks, toggle Success/Difficulty; build audience + screeners; Preview; pilot with 1 then launch. Key difference: video think-aloud is the primary output, quant is lighter, always pilot with 1 first.

2) Moderated interview. UserZoom: recruit + schedule sessions, moderate live, record separately. UserTesting: Create test > Live Conversation; set 30/60-min slots + calendar availability; choose audience; sessions run over Zoom, auto-recorded with transcript + sentiment. Key difference: scheduling, Zoom, transcript and sentiment are built in.

3) Prototype test. UserZoom: drop the prototype behind a task, flag success screens yourself, collect click data. UserTesting: Create test > Interaction test > Figma task; connect prototype, define the success path before launch; launch for auto paths, heatmaps, success rate. Key difference: native Figma click-path + heatmap engine; never edit the prototype or success path after launch.

4) Survey / screener study. UserZoom: survey study type with branching logic + quotas. UserTesting: Survey test type or questions in a test; screeners live in the Audience builder as multiple-choice. Key difference: screeners are multiple-choice only, surveys are lighter, audience locks at launch.

Keep it clean and enterprise-consistent.

Add a new page titled "UserTesting's AI tools" - for designers coming from UserZoom, which had no AI. Open with one line: UserTesting does a first pass of the analysis for you, so your time goes to judgment not grunt work; availability varies by plan tier. Then show these as a grid of cards (icon, name, one-line description):
- Auto transcripts: every session gets a searchable, timestamped transcript automatically; powers search across studies.
- Sentiment analysis: green/red markers on the video timeline flag emotional highs and lows; click to jump.
- Smart Tags: auto-tags feedback by theme (easy, pain point, suggestion), color-coded; replaces manual coding.
- Friction detection: automatically flags where users struggled (excessive clicks/scrolls), within and across sessions.
- Instant highlight reels: one click compiles every participant's take on the same task into one shareable video.
- AI Insight Summary: on the Metrics tab, Generate summary writes a task-level findings summary (unmoderated, up to 25 participants).
- AI test creation: describe your research goal in plain language and it drafts the test plan, tasks, and questions to edit.
- Insights Discovery: ask your whole research library questions in plain English; a queryable research memory, the most new-to-UserZoom capability.
Keep it clean and enterprise-consistent.