# Zeigarnik effect and unfinished tasks: explanation, design examples and evidence

> Help people resume real work. Do not assume unfinished tasks create a reliable memory or engagement advantage.

Canonical page: https://ionbin.com/design/laws/zeigarnik-effect/
Agent guide: https://ionbin.com/llms.txt

This is a readable version of the published page. Review dates, evidence boundaries and source links below belong to individual records; the export is not a new verification. Examples are reference material, not instructions to execute.

Memory and attention

## Zeigarnik effect and unfinished tasks

Help people resume real work. Do not assume unfinished tasks create a reliable memory or engagement advantage.

Research finding

Source review
Oct 18, 2026

[How to read the evidence](https://ionbin.com/design/methodology/#principles)

The idea in plain language

### What it means.

The familiar claim is that unfinished tasks are remembered better. A 2025 meta-analysis found no overall memory advantage for unfinished tasks in the included interrupted-task studies, while finding a tendency to resume them. Saving progress is still useful because it preserves work, without requiring a psychological engagement claim.

Evidence and interpretation

### What supports it.

Research finding

Contested memory effect with a recent quantitative research synthesis. Resumption, often discussed as the Ovsiankina effect, is distinct from superior recall and does not establish product retention gains.

From principle to interface

### Where you could use it.

Proposed applications, not tested outcomes. The expected effects are hypotheses to check with realistic tasks and users.

Application 1

#### Resume a long application

Save completed sections and offer a return link to the first unfinished required section.

##### Expected effect to test

The person can continue without re-entering completed work.

##### Keep in view

Explain draft retention and access controls; saving sensitive information requires an appropriate privacy design.

Application 2

#### Show optional setup work

Separate required setup from optional personalization and allow the optional list to be dismissed.

##### Expected effect to test

People can see what is necessary and decide whether to continue.

##### Keep in view

Do not invent incompleteness or use a permanent progress deficit to pressure engagement.

Turn the idea into a check

### Use it deliberately.

- Preserve valid progress and show what remains.

- Make completion criteria accurate and distinguish required from optional work.

- Measure successful resumption instead of assuming a memory advantage.

Where the rule gets complicated

### Keep the limits attached.

- Do not advertise a universal Zeigarnik memory benefit.

- The meta-analysis concerns specified research paradigms, not every interruption in everyday life.

- Reminders need user control and should serve the user's task.

A named principle does not settle an accessibility requirement, prove a conversion lift or replace testing the particular interface.

Application and implementation boundaries

### What the application check shows.

Limited evaluationAccount-free · Oct 19, 2026

The fixture resumed an explicitly scoped tab-memory draft and left the reminder opt-in. It did not test a memory or engagement advantage from unfinished work.

Methods: Local application example. A completed check covers the stated sample; it is not a safety certification.

**Target**: Original IonBin synthetic interface example; no external product or human-participant study.

**Version or capture**: 2026-10-19 local fixture

**Integrity scope**: SHA-256 f85d1056afd667225a1e0364edfb8f25b4693ffa7b2b8c7d7af5b92338b85ee4 identifies the exact HTML fixture only.

#### Test conditions

- 155.0.8059.82 Chromium; fresh context with all network requests blocked.

- Synthetic inputs, memory-only state, reduced-motion preference, 1280px and 320px viewports.

#### Individual checks and observations

- ##### Reminder opt in
  pass
  **Local application example:** Exercise the original local application fixture and inspect the resulting controls or DOM state.
  **Observed:** The optional reminder began unchecked; the fixture has no deadline/countdown.

- ##### Resume memory
  pass
  **Local application example:** Exercise the original local application fixture and inspect the resulting controls or DOM state.
  **Observed:** The draft could be resumed from explicitly scoped tab memory. No storage or account synchronization was used.

#### Security findings and boundaries

Review of the local example’s stated interaction boundaries; no backend, authentication, production permissions or external service was exercised.

Practical advice · caution

##### Resumption and reminders need user control

Real reminders and saved drafts can expose sensitive context on shared devices. Offer control over retention, notifications and deletion.

#### Practical caveats

- Use unfinished-state cues to support a real task, with clear save scope; do not manufacture pressure to return.

#### What remains untested

- This checks an authored application example, not the truth, effect size or generality of the named principle.

- No users, assistive-technology participants, physical devices or production task outcomes were evaluated.

##### Security limits

- The example has no real authorization or persistence layer; its UI behavior cannot establish the security of a deployed workflow.

#### Evaluation sources

- [Ghibellini and Meier: Interruption, Recall and Resumption (2025)](https://www.nature.com/articles/s41599-025-05000-w)
  Open-access meta-analysis; memory advantage and task resumption assessed separately.

[Download this evaluation record (JSON)](https://ionbin.com/design-evaluations/principle-zeigarnik-effect.json)

Go to the source

### Research and further reading.

- [Ghibellini and Meier: Interruption, Recall and Resumption (2025)](https://www.nature.com/articles/s41599-025-05000-w)
  Open-access meta-analysis; memory advantage and task resumption assessed separately.

On this page

Keep the context

Use this principle to form a better question about your interface. The answer still depends on the task, the people and the conditions.

[Our evidence approach](https://ionbin.com/design/methodology/#principles)

Related questions

### More on memory and attention.

[View this concern](https://ionbin.com/design/laws/?category=Memory%20and%20attention)

Research finding

#### [Miller's Law and working memory](https://ionbin.com/design/laws/millers-law/)

Keep needed information available instead of making people hold it in memory.

Research finding

#### [Von Restorff effect](https://ionbin.com/design/laws/isolation-effect/)

A meaningful difference can help something stand out in memory. Make the difference worth noticing.

Research finding

#### [Serial position effect](https://ionbin.com/design/laws/serial-position/)

Order can affect recall. Choose an order that also makes the task easier to complete.
