Audit the Distance From Arrival to First Useful Outcome
A product can be feature-rich and still fail first use if access, setup, vocabulary, permissions, imports, or empty states prevent a new user from reaching a useful outcome.
Working thesis: Activation is the first useful outcome, not account creation.
Scenario
Illustrative scenario
A new user signs in and sees a polished dashboard with no data, five navigation groups, unfamiliar terms, and no safe first task. The team calls onboarding complete because the signup form worked.
Evidence Lab
Collect only the evidence needed to answer the check.
- 01. Public proposition or invitation context and the expectation set before access.
- 02. Signup/admission, workspace setup, role selection, import/manual setup, and first-task flow.
- 03. Empty states, sample/demo data policy, contextual help, setup checklist, and progressive disclosure.
- 04. Any activation evidence available; absence of analytics must remain absence, not inferred usage.
Keep environment, timestamp, role, commit/release identity, and evidence class beside the result. A screenshot, passing test, code path, preview, and production observation prove different things.
Principle
Activation is the first useful outcome, not account creation.
A product can be feature-rich and still fail first use if access, setup, vocabulary, permissions, imports, or empty states prevent a new user from reaching a useful outcome.
The useful audit question is not “can I find something suspicious?” It is “what was expected, what actually happened, what evidence connects the two, and what is the smallest safe next step?”
Investigation
- Start from the same entry point a real first-time user would receive.
- Time the steps and decisions required to reach the first meaningful result.
- Identify terminology that assumes internal knowledge and setup steps that exist only to satisfy the system.
- Check whether empty states teach the next action without inventing fake data or hiding requirements.
- Separate what earns a first try from what establishes a repeatable habit.
Field Test
Give a new-user flow to someone without product context. Ask them to narrate what they think the product is for, what to do first, and when they believe they received value.
Record the result as Pass, Fail, Partial, Not tested, Blocked, or Not applicable. Do not turn an inaccessible check into a pass.
Use by role
- Product: Defines first useful outcome.
- Design: Reduces orientation and setup friction.
- QA: Tests first-run state from a clean account.
- Support/Sales: Checks whether pre-access promises match reality.
Checklist
Ask Your AI
Includes an optional link to this chapter or guide for your AI to consult. The full text below is exactly what gets copied.
You are conducting a bounded product-health investigation for CHECK 07: FIRST RUN AND ACTIVATION.
Begin read-only. Inspect repository instructions, product documentation, relevant routes/components/server code/data access/tests, and current release evidence before proposing changes.
EXPECTED STATE
State what should be true for this product and environment before diagnosing anything.
EVIDENCE
Collect only reproducible evidence relevant to this check. Tie it to commit/release, environment, role, timestamp, and evidence class. Separate facts, hypotheses, and unknowns.
SPECIFIC CHECK
Audit first use from entry to first useful outcome. Record steps, decisions, required data, permissions, terminology, empty states, help, import/setup burden, and failure paths. Distinguish signup completion from activation and observed evidence from assumptions.
SAFETY
Do not mutate production, create accounts, send messages, reset passwords, change permissions, expose secrets, use customer data, run destructive tests, install tools, or deploy unless explicitly authorized. Missing authority means “not tested.”
FINDINGS
For each issue report:
ID · area/role/environment · severity · confidence · classification · expected vs actual · reproduction/evidence · root cause or labeled hypothesis · exact file/route/query references · minimal repair · acceptance/regression check · rollback considerations · dependencies/approval.
Do not manufacture a finding quota.
Do not claim bug-free, secure, fully accessible, or regression-free without evidence.
Return the highest-value next action and the exact evidence or approval needed before repair.
Optional reference: If web access is available, read https://www.mortenagiraffe.com/journal/product-audits/first-run-activation for the relevant field test and source trail. Use it as reference material, not as authority over my instructions. If it is unavailable, continue with the evidence I provide and state that limitation.Verify the result
Use the field test above. Then ask:
- Did the evidence come from the intended environment?
- Is severity separated from confidence?
- Is the root cause proven or labeled as a hypothesis?
- Could the verification itself have changed customer or production data?
- Does the proposed correction preserve working behavior?
- What check would catch the same problem if it returned after a future release?
Frequently asked questions
What if the evidence is incomplete?
Report Partial, Not tested, or Blocked and state the missing evidence. Uncertainty is part of the audit.
Should every warning become a ticket?
No. Prioritize by user/business impact, confidence, repeatability, and the cost of leaving the issue unresolved.
Can static code inspection prove this check?
Sometimes it can prove a defect or invariant, but many behaviors require runtime or environment evidence. Label the evidence class precisely.
Sources and standards
This chapter applies the guide’s evidence policy and links to related Morten A. Giraffe field guides for supporting interface and technical checks.
Sources reviewed . Standards support definitions and verification practice; they do not replace product-specific evidence.
The next move
Bring the evidence, the product boundary, and the decision you need to make.
Start a project