Download your lesson workbook · Open the assignment tool →
Your ASO learning objective
Build a small evidence table that connects audience language to a supported screenshot message.
- Step 1Record the original words
- Step 2Write your interpretation separately
- Step 3Map a supported message to proof
Collect language with its context
Useful screenshot copy often begins with how users describe a task, not with an internal feature label. Review support conversations, interviews and app reviews you are permitted to use. For every excerpt, retain its source, date, audience context and the product version when available. Remove identifying details from anything you place in a shared brief.
Use a deliberate sampling rule. For practice, examine ten recent reviews and five support notes, but treat those counts as a manageable exercise, not a representative survey. Include positive experiences, confusion and unmet expectations. Selecting only comments that support the proposed design makes the evidence look stronger than it is.
Separate observation from interpretation
An observation is what the source actually says. An interpretation is what you think it means. A proposed message is your response. Keep these in separate columns. For example, a person asking where their previous walks went may be describing a navigation problem inside the app. That does not automatically mean the store screenshots need to lead with a history feature.
Look for repeated jobs and vocabulary, then check each candidate against the product. Prefer a narrow, demonstrable benefit to an attractive phrase that changes the category of the app. Competitor listings can reveal common messages, but they do not establish that those messages work or that your audience wants the same thing.
Translate research into a creative choice
Write two candidate messages using different interpretations of the same evidence. State what each makes clearer and what it leaves unanswered. Choose one for the next review and preserve the alternative. Research is useful when it changes a decision; a large collection of quotes without an explicit creative consequence is not a finished brief.
Worked example: Trail Notes
This fictional hiking-journal app is the teaching project. Treat the example as a reasoning exercise you can adapt to your own evidence.
- Original draftFictional review excerpt: ‘I want to remember the little things from each walk.’ Proposed headline: ‘Advanced adventure platform.’
- Revised proposalCandidate message: ‘Remember every walk.’ Proof: a saved walk showing a dated photo and personal note.
- Why it changesThe candidate follows the stated job and uses a visible journal capability. One fictional quote is a teaching input, not evidence of market demand; a real project would preserve actual sources and test interpretation.
Your ASO assignment
- Collect five source excerpts using a documented sampling rule. Label any fictional material as practice data.
- Choose two candidate opening messages and record the evidence for each in screenshot cards A and B.
- Write one reason the sample might mislead you and one follow-up research question in your version notes.
Your handover and assessment criteria
Your work is ready for review when each deliverable below can be understood without a verbal explanation. Include the source or product reference, the decision owner and any unresolved evidence gap. If a reviewer cannot verify a claim, record the missing evidence before treating the proposal as approved.
- Deliverable 1Source table with dates and sampling rule
- Deliverable 2Two candidate messages and supporting excerpts
- Deliverable 3Chosen interpretation and remaining uncertainty
Check your understanding
Three reviews mention getting lost. Can the journal app claim ‘Never get lost again’?
Read the interpretation
No. A complaint is not proof that the product solves it. Determine whether the app offers the relevant navigation capability; otherwise choose a journal benefit and record navigation as a product or research issue.
Record your progress
Mark this lesson complete after checking your assignment against the handover criteria. Progress stays in this browser, separately from your tool project.
Sources and further reading
Platform references checked 30 September 2026.