Goal-Gradient Effect

Motivation can strengthen as people perceive themselves getting closer to a meaningful goal.

Visible progress turns an abstract task into a path with a reachable end. Progress indicators, completed steps, milestones, and remaining work can help users sustain effort. The effect should reflect real advancement. Inflated, reset, or misleading progress damages trust and can make completion feel farther away than before.

Progress changes effort when the user can see that meaningful completion is getting closer. A visible path converts an abstract task into a bounded journey and reduces uncertainty about how much work remains. This is useful in onboarding, long forms, migrations, uploads, learning, and setup.

Progress must correspond to real work. Decorative percentages or artificially inflated completion can produce the opposite effect when they stall, reset, or reveal unexpected work near the end. Trust in the progress model is part of the experience.

Layr should prefer truthful stages over false precision. When exact percentage cannot be known, milestones such as “ingesting,” “mapping,” “relationships,” and “validation” can be more informative than a number.

Compare the displayed model of progress with the actual job or task state. Determine whether optional work is counted as required completion. Check whether progress persists across sessions and whether completion clearly communicates what has been achieved.

The agent should also inspect whether the next step becomes clearer as the user advances, rather than only whether a progress bar exists.

• Progress percentages jump or stall without relation to actual work.
• Optional enrichment prevents a task from reaching 100%.
• Long tasks reset visible progress after navigation or refresh.
• Users cannot tell which stages are finished, active, or remaining.
• Completion celebration obscures validation or exceptions.

• What does the progress indicator actually measure?
• Can the system support the precision it displays?
• Are required and optional work clearly separated?
• Does the user know what completion unlocks or changes?

High — Migration progress is decorative rather than state-based. The UI jumps to 80% immediately and remains there through several unrelated backend phases. Replace the fabricated percentage with durable stages and stage-specific counts where measurable so users can understand real advancement and remaining work.

Expose honest progress when a task has meaningful stages or accumulated effort. Show what remains and what completion unlocks.

• Onboarding, checkout, setup, migration, learning, uploads, long forms, rewards, and long-running operations.

• A multi-step task gives no indication of current stage or remaining work.
• Progress percentages jump unpredictably or stall near completion.
• Completed work is visually indistinguishable from remaining work.
• Optional steps are counted as required progress.
• A long operation resets visible progress when the user returns.

• Show stage, completed work, and remaining work using a model the system can support truthfully.
• Use milestones when exact percentage is unknowable.
• Preserve progress across sessions for durable tasks.
• Celebrate meaningful completion without blocking the next action.
• Separate optional enrichment from required completion.

Never fabricate progress. If duration is uncertain, show stages or activity instead of a false percentage.

• Default severity: Medium; high when misleading progress causes abandonment, duplicate actions, or false expectations.
• Typical confidence: High when progress model can be compared with actual job state.
• Primary evidence: Job stages, completion logic, progress calculation, persistence, optional/required distinction.
• Related rules: Zeigarnik Effect, Doherty Threshold, Parkinson's Law, Peak-End Rule