本文へ移動
cccskills
無料GitHub で公開

zeigarnik-effect

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`.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9022026年9月6日 更新

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9022026年9月6日 更新

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9022026年9月6日 更新

Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9022026年9月6日 更新

Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9022026年9月6日 更新

Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9022026年9月6日 更新

Owl-Listener のスキルをすべて見る

このスキルの問題を報告する