About 21 minutes reading · 39 minutes practice
You will produce: A stakeholder readout with evidence, limitations, recommendation and a recorded decision request.
Lead with the decision
State what the stakeholder needs to decide and the evidence that matters. A list of completed tasks is useful context but not the result. Explain whether useful acquisition changed, what is known about the cause and what action follows. Keep technical detail available without burying the main point.
Report uncertainty in useful language
Use counts and correctly labeled rates. Distinguish controlled results from observational changes and identify important alternative explanations. Avoid vague caveats that say everything might be wrong; name the limitation and how it affects the decision. An uncertain result can still justify a focused investigation.
Connect recommendations to resources
Every recommended action needs an owner, dependency and expected learning or outcome. Explain what will be deferred. If more budget is requested, show what decision or capability it enables rather than promising an unsupported growth number. Preserve the report and the stakeholder's decision in the operating record.
Quick check · pick a response
Make the call before you scroll.
Go deeper: practical decisions and tradeoffs
Write a headline that survives scrutiny
The headline should reflect the strongest supported conclusion. “Downloads rose 50%; activation stayed flat” is more informative than “ASO delivered exceptional growth” when useful users did not increase. State the objective and comparison context early. Keep the original counts and definitions accessible. A stakeholder should understand whether the report describes activity, an observed outcome or a controlled estimate before being asked to approve the next investment.
Explain limitations through their decision impact
Avoid a generic paragraph saying results may vary. Name the issue: paid traffic changed, the cohort is immature, attribution is incomplete or the experiment is inconclusive. Then explain what claim that prevents and what decision remains possible. For example, an audience-mix change may prevent attributing the total lift to screenshots while still justifying further investment in a productive channel. This makes uncertainty useful rather than evasive. Include unfavorable and neutral evidence that materially affects the recommendation.
Ask for a specific next decision
End with a recommendation, owner, required resource and review point. If asking for another test, explain how it differs from the last one and why the expected learning is worth the effort. If recommending no change, state the evidence needed to revisit that choice. Separate completed work from pending approval. Record the stakeholder's decision afterward so the report becomes part of the operating history rather than a presentation that is forgotten once delivered.
Platform references for this work: Apple — Acquisition analytics · Google Play — Understand and grow your user base
Your turn · two-minute exercise
Try the scenario. Make your case.
Rewrite “Our redesign increased conversion 25%” when the rate moved from 20% to 25% during a major paid-campaign change. Include the five-percentage-point change and the attribution limitation.
Autosaved on this browser. Your work is private and does not sync between devices.
Your step-by-step procedure
Write a one-paragraph decision summary.
Select the few metrics that answer the objective and show definitions.
Separate activities, outcomes and causal evidence.
Present an owned next-step plan with resource tradeoffs.
Completed example · use the reasoning
A one-page stakeholder report
Gabriel’s take: A stakeholder needs a decision, not seventeen charts trying to avoid one.
Constructed teaching material, not a client result. Adapt the evidence and product facts before using it for your app.
Outcome
Downloads 2,000 → 3,000; activated users 600 → 600
Interpretation
More acquisition, no increase in the defined useful outcome
Uncertainty
Paid mix and release changes prevent a clean listing attribution
Decision
Validate tracking and first-use flow before increasing spend
Owner and review
Analyst and product lead return with reconciled events and journey checks at the next weekly review.
Your turn · repair the decision
Make the call. Then compare.
Write the opening paragraph without hiding flat activation behind download growth.
Autosaved on this browser. Your work is private and does not sync between devices.
Explore the supporting case and interpretation
A report says downloads rose while activated users stayed flat and the paid mix changed. It recommends validating audience expectations before expanding spend. It does not describe the screenshot refresh as a proven growth win simply because it shipped during the same period.
Statement: New screenshots shipped
Evidence level: Activity
Appropriate wording: Production completed and verified
Statement: Downloads increased
Evidence level: Observed outcome
Appropriate wording: Increase occurred in this period
Statement: Randomized test supports uplift
Evidence level: Bounded causal evidence
Appropriate wording: Result applies to tested setup and audience
Statement: New market will double revenue
Evidence level: Unsupported forecast
Appropriate wording: Replace with assumptions and learning plan
The categories prevent activity from being sold as impact and forecasts from being presented as facts. A report can include all three legitimate levels if they are labeled clearly. The final recommendation should rely on the evidence relevant to the decision, not on whichever chart is most impressive. Keep speculative business scenarios in a separate assumptions section.
Build a handover someone can use
Executive summary
State objective, outcome, evidence strength and requested decision in plain language.
Metric appendix
Provide counts, formulas, definitions, windows and filters needed to reproduce results.
Context
List changes and limitations that materially affect interpretation.
Recommendation
Name action, owner, resource tradeoff and expected learning.
Decision record
Capture approval, deferral or revision and the next review condition.
Your ASO assignment
Use your own app and evidence, or work through the teaching case. Keep your observations separate from assumptions and explain the reasoning behind your decisions.
Build something · track your work
Your assignment checklist
Tick each item after you have produced the work. Reading it does not count. The strategy deck will survive.
0 of 3 tasks checked.
Autosaved on this browser. Your work is private and does not sync between devices. Course completion is recorded separately.
Assess your work
- The headline matches the strength of the evidence.
- Activity is not substituted for business impact.
- The requested decision is concrete and resourced.
Common mistakes to catch
- Showing only favorable segments or metrics.
- Ending a report with generic recommendations that have no owner.
Sources and further reading
Platform references reviewed 29 September 2026. These sources support platform capabilities and constraints; the teaching frameworks, assignments and illustrative cases are original course material.
- Apple — Acquisition analytics — Acquisition metric definitions and source attribution.
- Google Play — Understand and grow your user base — Current listing-click reporting, completed acquisitions and segmentation.
Your ASO lesson notes
Use this space for your assignment, evidence and handover. Your notes save automatically in this browser. Download a copy to take with you.
Notes stay on this device and are not submitted to ASO Agency.
Complete your assignment with the App store conversion calculator.
Loading your progress…
Progress is saved only in this browser. It does not sync across devices. Mark a lesson complete after doing its exercise.