What this checkpoint covers
The questions are set at Tobsquay Uniforms, an invented online school uniform supplier whose orders peak before term. They draw on the tutorial on running a conversion research sprint, the guide to usability testing a conversion journey and the tutorial on turning customer language into page copy, and follow the research sprint exercise for a picture framer. If test design still feels unsteady, the intermediate CRO level comes first.
Task
- Write a one-line answer and an action for each question, marked confident or unsure.
- Compare with the explanations and note the rule behind every miss.
- Reread the linked guide for any confident miss before the next module.
Questions
- The marketing manager wants one sprint to cover both the school-to-basket journey and account sign-up, with the founder and the developer both deciding. What do you change?
- The phone FunnelModel of the customer journey stages. in the first example below falls sharply at the size step from the week a new theme went live. The manager wants recordings of that step at once. What comes first, and why?
- Recordings at the located step show parents opening and closing the size chart repeatedly; the poll there mostly returns answers about delivery dates; one support thread blames the school search. How do you treat each?
- The draft usability task reads "Use the size guide to choose a blazer size, then tap Add to basket." In the pilot, asked "Is it this link?", the facilitator said "Yes, the blue one." What is wrong with each?
- In the round shown in the second example, a colleague says the school-search problem "only affected one participant, so it is a fifth of visitors and can wait". What do you say?
- After reading reviews and tickets, the copywriter drafts "Parents love our hard-wearing fabrics", citing one vivid review and "lots of mentions". What went wrong?
- The agency proposes to close the sprint with a slide deck of every observation. What should it hand over?
Tobsquay Uniforms: phone funnel around the theme change
| Step | Four weeks before the theme | Four weeks after the theme |
|---|---|---|
| School found | 6,400 | 6,600 |
| Items chosen | 4,100 | 4,300 |
| Size chosen | 3,700 | 1,200 |
| Added to basket | 3,300 | 3,450 |
The new theme replaced the phone size buttons with a drop-down menu. Desktop step rates did not change, and orders in the shop's own system rose in line with baskets as term approached.
Tobsquay Uniforms: a moderated usability round on phones
| Problem | Participants who met it (of 5) | What happened |
|---|---|---|
| School search found nothing for the school's common short name | 1 | Could not continue without help |
| Size chart too small to read without zooming | 4 | Zoomed, guessed, continued |
Each row records how many of the five participants met the problem and what they did next, as the moderator's notes from the round recorded it.
Answers explained
- One funnel, one question, one owner. Two funnels point the methods at different visitors, and two deciders mean nobody acts. The research sprint tutorial writes the question about visitors, a place and a decision, with one owner and a fixed end date. Sign-up waits for a later sprint.
- The tracking check. Baskets held while size selections collapsed, which a real loss cannot produce: nobody adds a sized item without a size. The likelier cause is an event the new drop-down stopped sending. Walk the journey with the debug view, fix the event, then locate the leak. Recordings aimed at a tracking fault study a bug.
- Size chart: evidence once a second method explains it; school search: a lead; delivery: split first. The sprint tutorial counts a finding sized, watched and explained as evidence and a single-method finding as a lead. Disagreement usually means two segments: check whether the delivery answers come from returning parents ordering late.
- The task gives the answer away, and the facilitator helped. The usability testing guide writes tasks as goals without the button words: "Your daughter starts at a new school soon and has grown since spring. Order her blazer." Asked "Is it this link?", the facilitator asks what the participant would do alone. A rescued participant is a hidden finding.
- Severity decides, and the count describes the round. The problem stopped a participant, which the usability guide rates as blocking however many met it, and counts describe the usability testA research session in which a person attempts a realistic task on a site, app or prototype while an observer notes where they struggle., not all visitors. A search that fails on a common short name is a bug: fix it now and check it in the next round.
- Paraphrased, ranked by vividness, unchecked. The customer language tutorial keeps exact phrases with their source, ranks codes by how many independent sources share them, not by mentions, and checks every claim can be substantiated. "Parents love" is the team's phrase, not a parent's.
- Backlog rows, fixed bugs and a short readout. The sprint tutorial ends with each finding as a row (problem, location, evidence, reach, cost, status, decision), bugs fixed and noted, and a readout of what was found, why it matters and what happens next; the strongest rows each become a HypothesisA testable statement of the change to make, the effect expected on a named metric and the evidence-based reason for expecting it.. A deck without rows is forgotten by the next sprint.
Where to go next
Missed scope or tracking? Rework the picture framer research sprint exercise without its tracking fix. Then start the second module with evaluating a website relaunch for a cookware maker, where the split test is no longer the default tool.
