Opening reference…
Rules for sustaining effort, making progress legible, supporting interrupted work, and designing the moments that shape how an experience is remembered.
4 principlesRules 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.
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.