---
title: "Goal-Gradient Effect"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Completion"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Completion"
source_slug: "Completion"
track: "Persuasive Design Patterns"
group: "Game mechanics"
subgroup: "Gameplay rewards"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Set and communicate expectations and progress."
  - "Making the completion official"
  - "Provide artificial progress"
  - "Beware of the post-reward reset effect"
  - "Divide larger tasks into sub-tasks"
  - "Rationale"
example_count: 4
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Goal-Gradient Effect

> Catalog pointer for the UI Patterns source page: [Goal-Gradient Effect](https://ui-patterns.com/patterns/Completion).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Game mechanics
- Subgroup: Gameplay rewards
- Source breadcrumb: Design Patterns > Game mechanics > Gameplay rewards > Goal-Gradient Effect

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Completion
- Page title: Goal-Gradient Effect design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Set and communicate expectations and progress., Making the completion official, Provide artificial progress, Beware of the post-reward reset effect, Divide larger tasks into sub-tasks, Rationale
- Example screenshots detected at source: 4
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 10 words on source page
- Example: 72 words on source page
- Usage: 50 words on source page
- Solution: 362 words on source page
- Set and communicate expectations and progress.: 112 words on source page
- Making the completion official: 71 words on source page
- Provide artificial progress: 39 words on source page
- Beware of the post-reward reset effect: 32 words on source page
- Divide larger tasks into sub-tasks: 7 words on source page
- Rationale: 257 words on source page

## Source Navigation

- Previous source navigation: Value Attribution
- Next source navigation: Trigger