# An invoice app that promises more than it shows

Companion to /learn/how-to-do-an-aso-audit/

## Outcome
Produce an evidence-backed audit with prioritised findings and a clear implementation handoff.

Fictional example, not a client result.

## Scenario
InvoiceNest is a fictional freelancer invoicing app. Its title suggests simple invoicing, but its first screenshot is a reporting dashboard. Reviews mention confusion about sending the first invoice. You have access to the listing and public reviews, but no acquisition reports or product event data. The audit must make that evidence boundary visible.

## Reasoning
Capture the current store, locale, device context and date before writing recommendations. For each finding, separate observation, interpretation and proposed action. “The first frame shows a dashboard” is observable. “Visitors think setup is complicated” is an interpretation that needs evidence. A disciplined audit preserves this distinction even when the proposed redesign seems obvious.

## Action
Inspect the actual first-invoice workflow with the product team. If it is genuinely straightforward, brief a sequence showing creation, preview and sending. If it is difficult, raise a product issue rather than hiding it behind a promise of simplicity. Ask for segmented reports to decide whether the creative issue is also a commercially important bottleneck. Deliver a short priority list with owners and acceptance criteria.

## Trap to avoid
Do not turn every personal preference into an urgent finding. A colour you dislike, an unfamiliar illustration style, or a competitor feature is not evidence of a user problem. Prioritise accuracy, comprehension and relevant measurable obstacles before aesthetic opinions.

## Advanced considerations
Separate a public listing review from a full performance audit. The former can inspect copy, visuals and positioning; it cannot establish private conversion, retention or revenue outcomes. Include a limitations section in the deliverable and identify which recommendations remain provisional until analytics or product access is available. This makes the audit more credible and easier to implement.

## Exercise
A stakeholder asks you to score the app 42/100 because that looks convincing in a presentation. How should the audit handle this?

## Suggested answer
Use a transparent rubric only if its criteria and limitations are useful. Do not imply that an invented score predicts growth. A documented high-priority finding, its evidence and the next decision are more actionable than an unexplained overall number.

## Your worksheet

### Store, locale, date and review scope
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Observation with evidence reference
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Interpretation and confidence
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Missing information or access
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Action, owner and dependencies
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Acceptance criteria and follow-up evidence
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

## Turn findings into a usable issue register
Severity describes the consequence of a problem; confidence describes how well you understand it. Keep them separate. These editorial categories are a working rubric, not a statistical model or a prediction of revenue impact.

Editorial triage rubric: priority is not an estimated uplift.
Priority category | Example finding | Release or investigation action
Correct before promotion | Listing advertises a feature unavailable in the current product | Verify the claim; correct it and confirm the published version
Investigate promptly | A comparable audience appears to complete fewer defined actions | Check definitions and concurrent changes before proposing a cause
Plan an experiment or review | Opening screenshot may obscure the primary workflow | Document the mechanism and choose suitable evidence collection
Optional refinement | Reviewer prefers another decorative colour | Defer unless it addresses a documented user problem

### A completed finding with acceptance criteria
Finding INV-01: the first screenshot of fictional InvoiceNest shows a reporting dashboard although the listing promises simple invoice creation. Evidence: a dated capture of the current listing. Interpretation: the opening may fail to demonstrate the first-use workflow. Confidence: high in the visible observation, uncertain in its effect on visitor behaviour. Owner: creative lead, with product review. Next action: inspect the actual create-to-send workflow and draft a supported opening.

### Define “done” before handing over the finding
For INV-01, done means the creative brief identifies the intended audience, uses an available product workflow, includes readable captions and has a named approver. Publication is a separate milestone, and demonstrated performance improvement is a separate question again. This prevents a team from closing an issue merely because a presentation was delivered—or keeping it open indefinitely while waiting for an outcome it cannot guarantee.

### Request access according to the question
For a public message review, preserve listing captures and product information supplied by the owner. For a performance investigation, request relevant report exports with definitions, dates, filters and the change timeline; use appropriate read-only access if needed. Request the minimum necessary information and do not ask for shared account passwords. If the evidence is unavailable, narrow the conclusion rather than inventing the missing explanation.

## Continue reading
- /learn/aso-checklist/
- /learn/measurement/metadata-change-log/
- /learn/aso-roadmap/