Skip to content
cccskills
FreePublished on GitHub

zeigarnik-effect

Design progress indicators, draft resumption, and reminders using the Zeigarnik Effect: unfinished tasks tend to stay in mind. Specify clear remaining steps, saved progress, and ways to resume without pressuring people to finish.

OriginalShow the original description

Apply the Zeigarnik Effect — incomplete tasks stay mentally active. Use when designing progress indicators, saved drafts, and return hooks. For the emotional shape of the ending, use `peak-end-rule`.

Run score Not tested

See how to install

Good for

  • Designing progress displays for setup flows
  • Planning draft saving and resumption
  • Writing reminders for interrupted tasks
  • Reviewing onboarding checklists

Files included (1)

  • SKILL.md3.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Zeigarnik Effect

You are an expert in task completion psychology and motivational design.

What You Do

You apply the Zeigarnik Effect to design progress states, interruption handling, and re-engagement patterns that use incompleteness as a motivational signal — without abusing it.

The Principle

Bluma Zeigarnik observed that people remember uncompleted or interrupted tasks better than completed ones. Unfinished tasks occupy open loops in working memory — the brain keeps returning to them because the tension of incompleteness is unresolved.

Design implication: incompleteness is a motivational state. Progress that is started but not finished creates a pull toward completion.

Applications

Progress indicators and multi-step flows

Showing a user how far they have come — and that a defined, finite distance remains — is more motivating than showing neither:

  • Progress bars on profile completion, course modules, or setup flows activate the Zeigarnik loop
  • "You're 60% done" is more compelling than "complete your profile" without a completion signal
  • Named steps with clear endpoints give working memory something concrete to hold and return to

Re-engagement touchpoints

"You left something in your cart" works because the Zeigarnik loop is already open — the user started a task and did not finish it. The re-engagement surfaces a real cognitive state:

  • Draft resumption: "You have an unsaved draft" keeps an open loop visible
  • Onboarding re-entry: "You're one step away from completing setup" references the specific uncompleted state
  • Abandoned flow recovery: showing the exact step where the user stopped is more effective than a generic call to action

Interruption handling

If a flow can be interrupted mid-completion, the product must:

  1. Save state automatically, without requiring the user to act
  2. Signal clearly that the task can be resumed exactly where it was left
  3. Restore context completely on return — the user's mental model of "where I was" must match the actual state

Checklists and completion meters

Checklists make open loops explicit and visible. Each unchecked item maintains a Zeigarnik loop; completing items provides resolution. This is the mechanism behind:

  • Onboarding checklists
  • Profile completion meters and nudges
  • Achievement and progress systems in productivity and learning tools

When the Zeigarnik Effect Creates Problems

  • Too many open loops simultaneously: more than two or three competing incomplete states overwhelm rather than motivate
  • Re-engagement for low-priority tasks: prompts for tasks the user has implicitly abandoned read as manipulation, not helpfulness
  • Incomplete states that cannot be completed: showing a progress bar with no clear completion path creates frustration rather than motivation

Best Practices

  • Surface one or two open loops at a time; more is noise
  • Always provide a clear path to completion when referencing an unfinished task — incomplete without a route is anxiety, not motivation
  • Design autosave first; progress motivation only works if state is reliably preserved
  • Use incompleteness honestly — only surface it for tasks the user has genuinely started
  • Test re-engagement copy for tone; Zeigarnik-driven messages should feel like helpful reminders, not guilt

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

a-b-test-design

FreeSummary

Plan A/B experiments to measure the effect of a design change. Define a hypothesis, control and treatment versions, success metrics, sample size, and duration, with supporting measures to detect unintended consequences.

  • Planning a comparison between current and proposed designs
  • Defining success metrics for a change
  • Estimating sample size and test duration
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Assess an existing interface against WCAG 2.2 accessibility guidelines. Identify barriers in content and interactions, rate their severity and user impact, and document affected locations, remediation steps, and code examples to guide improvements.

  • Reviewing accessibility in an existing design or build
  • Checking keyboard access and assistive technology compatibility
  • Prioritizing fixes by severity and user impact
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Plan accessibility testing with people who use assistive technologies, such as screen readers and voice control. Define participant criteria, test environments, session procedures, coverage of WCAG accessibility guidelines, and a consistent format for reporting issues.

  • Planning test sessions with assistive technology users
  • Defining participant recruitment criteria
  • Mapping key user flows to test environments
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Review visual consistency to understand how an interface shapes trust and perceived ease of use. Examine spacing, alignment, typography, and overlooked screen states to guide visual improvements alongside usability testing.

  • Investigating poor feedback on a functional interface
  • Checking visual consistency before launch
  • Reviewing error, empty, and loading states
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

affinity-diagram

FreeSummary

Turn interview notes, observations, and survey responses into themes and actionable research insights. Group related evidence without preset categories, retain participant references, and prioritize findings by their impact on design decisions while noting patterns found in only one interview.

  • Synthesize findings across multiple interviews
  • Organize observation notes and survey responses
  • Prioritize research insights for design decisions
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Refine a specific interface animation by choosing easing, meaning changes in speed, along with duration and movement order. Use it to tune buttons, modals, transitions, or loading indicators so motion guides attention and communicates changes.

  • Tune how a modal enters and exits
  • Adjust button and toggle animations
  • Coordinate the order of related movements
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

See all skills by Owl-Listener

Report a problem with this skill