# ASO Agency — Lesson 3: ASO audience research and app value propositions

Outcome: Describe one audience through its problem and buying context rather than a broad demographic label.

App / store / market / locale:
Prepared by / date:
Product or listing version:

## Your ASO assignment

1. Create a situation-to-benefit-to-proof table with three rows.

Your response:

2. Mark unsupported claims and name who can verify them.

Your response:

3. Draft a 20-word positioning statement for your primary situation.

Your response:

## Scenario challenge

Draft two first-screenshot headlines for Trail Notes: one for remembering walks and one for finding routes. Explain why the second must be rejected for the current product even if respondents prefer its wording. Then identify one uncertainty you would investigate about the first.

Your reasoning:

## Handover

### Primary situation

Describe the trigger and desired result in ordinary customer language. Include the current workaround so the benefit has context.

Your evidence and decision:

### Value statement

Write one sentence connecting a released capability to the outcome. Avoid stacking unrelated audiences into the same sentence.

Your evidence and decision:

### Evidence

Attach a product screen or documented workflow for each important promise, including the app version reviewed.

Your evidence and decision:

### Objection

Name the question most likely to stop a suitable user and the proof available to answer it honestly.

Your evidence and decision:

### Boundary

Record unsupported use cases such as navigation, and explain why they must not enter keywords or creative.

Your evidence and decision:

## Submission check

- [ ] The situation is recognizable without demographic stereotypes.
- [ ] Every promise can be traced to a real feature or clearly stated limitation.
- [ ] The chosen audience has a reason to use the app after installation.

## Next action
Owner:
Required evidence:
Due date:
Review decision:

www.asoagency.com