# Lesson 60: How to build a 90-day ASO strategy and action plan

Combine the course artifacts into a feasible 90-day plan with evidence, owners, dependencies and review gates.

Prerequisite: Your completed audit, research map, approved metadata, creative brief and measurement records.

Teaching examples are fictional unless explicitly identified as platform definitions.

## Foundations

### Return to the business objective

Review whether the original growth diagnosis still holds after the research. Update the objective only with a documented reason. Choose a small set of priorities that address the strongest supported constraints. The capstone should connect the work, not merely collect every exercise into one large folder.

### Sequence learning and production

Use the first phase to resolve critical evidence and accuracy issues, the next to execute focused work and the final phase to evaluate and choose the next cycle. These are planning phases, not guaranteed ranking timelines. Respect product releases, traffic and reviewer capacity. Keep explicit decision gates between dependent tasks.

### Defend the tradeoffs

Explain why selected work matters, why other ideas wait and what evidence would change the sequence. Assign owners and acceptance conditions. Include a plan for uncertainty and incidents. A professional plan remains useful when a test is inconclusive or a dependency slips because it contains alternative actions rather than one optimistic forecast.

## Apply the method

### Assemble an evidence chain, not a folder of exercises

Connect the diagnosis to the audience, research map, metadata, creative and measurement plan. Each artifact should explain a decision in the next one. If the audit identifies navigation confusion but the proposed screenshots still lead with a map, resolve that contradiction before scheduling production. Revisit the business objective using what the course work revealed. Keep the original objective and the reason for any change so the plan's history remains intelligible.

### Use phases with explicit exit conditions

A first phase can establish trustworthy evidence and correct inaccurate claims. Its exit condition is not simply day 30; it is that the key baseline and release dependencies are ready. A second phase can implement or test focused changes. A third can interpret results and choose the next cycle. The phases may overlap when dependencies permit. Traffic, review timing and product releases can change the calendar, so define alternative actions instead of treating the horizon as a guaranteed growth deadline.

### Defend capacity and opportunity cost

Assign a real role to every action and include review, release and analysis time. Name what will not be done this cycle and why. If a test is inconclusive, state whether the next step is a stronger concept, more observation or another method. If localization readiness slips, identify useful work that can continue. A professional plan remains actionable under uncertainty because it describes decisions and dependencies, not only dates and optimistic outcomes.

## Procedure

1. Review the diagnosis and select the highest-priority decisions.
2. Map artifacts and dependencies to a realistic three-phase schedule.
3. Assign owners, acceptance checks and evidence reviews.
4. Present the plan and record challenges, revisions and approved next actions.

## Worked example

Trail Notes first corrects inaccurate offers and validates activation data, then develops a clearer journal-focused listing and a scoped creative experiment. Localization remains gated by product readiness. The final review decides whether to expand, revise the message or investigate onboarding rather than automatically launching the next market.

| Phase | Core work | Exit condition |
| --- | --- | --- |
| Establish | Correct claims and validate baseline | Evidence and approvals are usable |
| Execute | Prepare and run focused intervention | Actual treatment and exposure are verified |
| Evaluate | Interpret result and choose next cycle | Owned keep, revise or investigate decision |

The three phases are an organizational scaffold, not a ranking forecast. For Trail Notes, a tracking defect could extend the establish phase while customer-language research proceeds independently. A creative experiment might finish without a clear winner, yet still produce a documented decision and better next hypothesis. The capstone should show those alternatives so a missed assumption does not collapse the entire plan.

## Your ASO assignment

1. Build a five-action plan covering evidence, production and evaluation.
2. Attach the supporting course artifacts and a dependency map.
3. Defend two exclusions and one alternative plan if a dependency fails.

Present your plan in ten minutes. Defend two priorities, two exclusions and one contingency. A reviewer should be able to identify tomorrow's action and explain what changes if your leading hypothesis is wrong.

## Handover

### Objective and diagnosis

State the useful outcome, current constraint and evidence supporting the focus.

### Prioritized actions

Limit the first batch and attach the relevant course artifacts and rationale.

### Dependencies and capacity

Assign owners, review resources and prerequisites for each action.

### Decision gates

Define acceptance and interpretation conditions, including inconclusive or delayed outcomes.

### Operating handover

Provide the review calendar, change log, maintenance ownership and next-cycle decision process.

## Check your work

- Every action serves the stated objective and has a reason.
- Dependencies and capacity make the sequence feasible.
- Uncertainty leads to explicit alternative actions rather than unsupported guarantees.

## Common mistakes

- Scheduling every course technique whether or not the app needs it.
- Treating the 90-day horizon as a promise of ranking or revenue outcomes.

## Knowledge check

What proves that the capstone is operationally complete?

Another person can identify the next action, its owner, evidence, dependencies and completion check, and can explain what happens if the expected result does not occur. A polished calendar without those decisions is incomplete.

## Sources

- [Apple — Creating your product page](https://developer.apple.com/app-store/product-page/) — Product-page fields and presentation guidance.
- [Google Play — Create and set up your app](https://support.google.com/googleplay/android-developer/answer/9859152?hl=en) — Listing fields, language and text limits.
- [Apple — Acquisition analytics](https://developer.apple.com/help/app-store-connect-analytics/acquisition/acquisition) — Acquisition metric definitions and source attribution.

Platform references reviewed 29 September 2026.
www.asoagency.com