# A walking app with two different growth problems

Companion to /learn/what-is-aso/

## Outcome
Map the journey from a relevant search to a user who experiences the promised value.

Fictional example, not a client result.

## Scenario
TrailPocket is a fictional app for finding short local walks. Its team calls every acquisition problem an ASO problem. One visitor cannot find a suitable route in search; another installs successfully but discovers that the advertised offline feature does not exist. Both experiences matter, but they need different owners. Treating them as one keyword problem would send the team in the wrong direction.

## Reasoning
Draw the journey on paper: a person has a need, encounters a listing, evaluates its promise, chooses an action, then uses the product. Under each transition, record the evidence you actually have. A search-position observation belongs near discovery. A screenshot comprehension interview belongs near evaluation. An activation event belongs after acquisition. Do not substitute one signal for another just because it is easier to obtain.

## Action
For TrailPocket, first remove the unsupported offline claim and notify the product owner. Then inspect whether the listing explains short nearby walks clearly. Only after those decisions should the team prioritise relevant search themes. This ordering does not guarantee growth; it prevents the listing from attracting people on a false premise. A smaller, better-matched audience can be a more useful starting point than a larger disappointed one.

## Trap to avoid
Do not describe ASO as a substitute for product quality or distribution. It is work on how an app is discovered and understood within a larger acquisition system. A good listing cannot manufacture a missing feature, and a keyword position is not a count of satisfied users.

## Advanced considerations
When stakeholders disagree, ask each one to name a decision and the evidence that would change it. “We need more downloads” is an objective, not a diagnosis. “We need to know whether visitors understand that our routes fit a lunch break” is an investigable question. Keep the first learning cycle narrow enough that an answer can influence an actual change.

## Exercise
A meditation app has rising store visits but fewer users complete their first session. Which two questions should you ask before rewriting its metadata?

## Suggested answer
Ask whether the incoming audience or campaign promise changed, and whether onboarding or session availability changed. Inspect listing evidence too, but falling activation alone does not establish that metadata is the cause. The store and product teams may need to investigate together.

## Your worksheet

### Priority audience and the job they need done
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Promise visible in the listing
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Product evidence supporting that promise
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Discovery evidence and its source
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Listing-choice evidence and its definition
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Post-install evidence and responsible owner
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

## What belongs in an ASO project?
Use this scope map when someone asks you to “do ASO.” Agree the deliverable and the team boundary before assigning tasks. Ownership can vary by company; the important distinction is between work on the listing and work on the product experience it promises.

Illustrative ownership map: agree responsibilities for your own team.
Question | ASO deliverable | Collaboration boundary
Which needs can this app satisfy? | Audience and intent brief | Product confirms supported workflows
How should the listing describe those needs? | Metadata and message recommendations | Brand and product review accuracy
What should visitors see? | Screenshot narrative and creative brief | Design produces assets; product supplies valid screens
Did the change help? | Defined baseline and evaluation record | Analytics helps with attribution and downstream events
Why do people abandon setup? | Flag a promise/experience mismatch | Product team investigates and fixes onboarding

### ASO, SEO and paid acquisition: where the work meets
A website SEO project works on a web property; an ASO project works on the app’s store presence. Paid acquisition buys distribution to an audience. They can share research and messaging, but each has different implementation surfaces and evidence. If a campaign sends people to the listing, the campaign promise and store promise should agree. Do not assume that improving either surface proves the other caused a result.

### A first session that produces something useful
Open one current listing and write down its apparent audience, promise and supporting screen. Compare that with one complete product workflow. Mark one mismatch or one unresolved question, then identify who can resolve it. This is a first-pass review, not a full audit. Finish with an evidence request or a specific correction rather than a long list of speculative tactics.

### What progress looks like before growth is measurable
An accurate claim, a documented audience choice and an implementable creative brief are meaningful delivery milestones. They are not proof of acquisition growth. Keep delivery progress and outcome evidence separate in reporting, so work can be evaluated honestly while enough behavioural evidence accumulates.

## Continue reading
- /learn/aso-strategy/
- /learn/measurement/aso-kpis/
- /learn/conversion/value-proposition/