#Principle
People often remember an experience disproportionately through its most intense moments and how it concludes.
#Why it matters
A product journey is not remembered as a precise average of every screen. Success moments, failures, payment, waiting, destructive actions, support encounters, and completion states can dominate the later impression. Designing these moments carefully improves clarity and emotional quality, while a weak ending can erase confidence built earlier.
#Deeper design interpretation
People often remember an experience through a small number of emotionally or operationally intense moments and through how the journey ends. Product interfaces contain obvious peaks: payment, failure, deletion, deployment, migration completion, support escalation, identity verification, and recovery after something goes wrong.
These moments deserve disproportionate design attention because they shape confidence in the whole system. A smooth journey can feel unreliable if the final state is ambiguous. A difficult journey can still feel controlled when the product handles the failure clearly and finishes with a trustworthy resolution.
Layr should identify peaks from task consequence and system state rather than manufacture them through animation or celebration.
#What the agent should reason about
Trace the journey and mark high-consequence, high-uncertainty, and terminal states. Ask whether the user can verify what happened, what changed, what failed, and what comes next. Preserve records such as receipts, logs, reports, or status pages when later verification is likely.
Negative peaks deserve recovery design. A good error state reduces uncertainty and offers a credible path forward.
#Common failure patterns
- Major success is confirmed only by a disappearing toast.
- A failure state offers no retry or recovery.
- A cancellation ends without clarifying retained data or remaining access.
- Long waiting is most ambiguous at the point of greatest consequence.
- A final screen introduces unexpected work after users believed they were done.
#Audit questions
- What are the most consequential moments in this journey?
- Does the user leave each peak knowing what happened?
- Is the final state durable enough to verify later?
- Does recovery reduce uncertainty after failure?
#Example agent finding
High — Migration completion ends with a generic “Done” toast. The progress view closes automatically and users cannot see which records succeeded or failed. Replace the transient toast with a durable completion summary containing totals, exceptions, validation status, and next actions.
#Agent directive
Identify high-intensity and terminal moments in a journey. Make outcomes clear, reduce avoidable stress, and ensure the final state resolves uncertainty.
#Apply this when
- Checkout, publishing, deployment, migration, cancellation, error recovery, uploads, onboarding completion, support, and destructive workflows.
#Observable signals
- A major success ends with a generic toast that disappears before users can verify outcome.
- A failure state gives no recovery path.
- Long waiting produces uncertainty at the most stressful point of the journey.
- Cancellation or deletion ends abruptly without confirming what remains.
- A final screen introduces a new requirement after the user believed the task was complete.
#Recommended actions
- Design consequential success and failure states deliberately.
- Confirm what happened, what changed, and what users can do next.
- Provide recovery where possible at negative peaks.
- Avoid celebratory UI that obscures important outcome details.
- Preserve receipts, logs, or status for actions users may need to verify later.
#Do not over-apply
Do not manufacture emotional peaks with excessive animation or gamification. The important moment should arise from the user's task and outcome.
#Example
Weak
After a large data migration completes, the interface only shows 'Done' and closes the progress view, leaving users unsure what migrated or failed.
Stronger
Completion summarizes totals, exceptions, validation status, and next actions, and the report remains available later.
#Evaluation notes
- Default severity: High for consequential journeys; medium for general experience quality.
- Typical confidence: High when journey peaks and endings are evident; medium for predicted memory effects.
- Primary evidence: Journey map, error/success states, terminal screens, wait states, recovery paths.
- Related rules: Goal-Gradient Effect, Serial Position Effect, Aesthetic-Usability Effect, Doherty Threshold