---
title: "Motivation, Progress & Experience Memory"
source: "/reference/motivation-progress-experience-memory"
description: "Rules for sustaining effort, making progress legible, supporting interrupted work, and designing the moments that shape how an experience is remembered."
---
# Motivation, Progress & Experience Memory

Rules for sustaining effort, making progress legible, supporting interrupted work, and designing the moments that shape how an experience is remembered.

> Rules for sustaining effort, making progress legible, supporting interrupted work, and designing the moments that shape how an experience is remembered.

Progress and memory shape whether users continue a task, return after interruption, and trust the product after a difficult moment. A system can support motivation by showing honest advancement, preserving unfinished work, reducing unnecessary interruption, and resolving high-intensity moments clearly.

These principles are easy to misuse. Progress bars can lie. Completion mechanics can turn optional behavior into pressure. Celebration can distract from important outcome details. "Engagement" can become a reason to manufacture unfinished states. Layr should evaluate motivation through the user's goal, not through a product metric alone.

The most useful findings in this category connect visible product behavior to a real journey: what the user is trying to finish, how the system signals movement, what happens when progress is interrupted, and how the final or most stressful moment is resolved.

## Principles in this category

- [Flow](/__layr/pages/reference/flow.md) — Sustained engagement is more likely when the task, feedback, difficulty, and user capability remain in a productive balance.
- [Goal-Gradient Effect](/__layr/pages/reference/goal-gradient-effect.md) — Motivation can strengthen as people perceive themselves getting closer to a meaningful goal.
- [Peak-End Rule](/__layr/pages/reference/peak-end-rule.md) — People often remember an experience disproportionately through its most intense moments and how it concludes.
- [Zeigarnik Effect](/__layr/pages/reference/zeigarnik-effect.md) — Incomplete activity can remain mentally salient, which makes visible unfinished work a powerful cue to resume a task.

## Category model

Motivation in product design should be grounded in the user's own goal. Layr should evaluate whether the product makes progress understandable, preserves effort, reduces unnecessary interruption, and resolves meaningful milestones clearly. It should avoid treating engagement, completion percentages, streaks, or return frequency as inherently positive.

The category is closely tied to time. A user begins, advances, gets interrupted, resumes, reaches a difficult point, and eventually finishes or abandons. The interface should maintain continuity across that timeline. Honest progress, recoverable drafts, durable completion state, and clear recovery all reduce uncertainty about where the user stands.

### Agent evidence hierarchy

Prefer observable task state, progress models, persistence, resume behavior, completion logic, wait states, and terminal outcomes. Be cautious when inferring emotion, motivation, or memory. The agent can identify conditions that support or disrupt those experiences without claiming direct access to the user's internal state.

## Category review questions

- Can users see meaningful, truthful progress toward a real goal?
- Does the product preserve unfinished work and provide a clear resume point?
- Do routine interactions protect concentration rather than repeatedly interrupt it?
- Are high-intensity success and failure moments designed with enough clarity and recovery?
- Does completion reflect required work rather than artificial engagement pressure?

## How agents should use this file

Treat these rules as review criteria, not as automatic violations. A finding is valid only when the interface provides observable evidence that the principle applies and that the current implementation creates a meaningful usability, comprehension, accessibility, or interaction cost.

For every finding:

1. Identify the exact component, state, route, or interaction.
2. State the observable evidence.
3. Name the principle that applies.
4. Explain the user consequence in the current context.
5. Estimate severity from the consequence, frequency, and reversibility.
6. Recommend the smallest change that addresses the issue while preserving the product's existing design system.
7. Lower confidence when intent, frequency, audience, device, or product constraints must be inferred.
8. Do not produce generic advice such as "improve hierarchy" or "make this clearer" without specifying what is wrong and why.

### Finding contract

```yaml
finding:
  rule_id: string
  location: string
  evidence:
    - observable fact
  impact: string
  severity: low | medium | high | critical
  confidence: low | medium | high
  recommendation:
    change: string
    rationale: string
    preserve:
      - existing design-system behavior
      - valid product constraints
```

A clean interface can legitimately produce zero findings.

## Agent routing hints

Route a review here when the interface manages progress, interruption, completion, waiting, resumption, or emotionally significant outcomes. Avoid inferring motivation from UI alone; tie findings to observable journey states.