# Direct Manipulation

Direct manipulation lets people act on visible interface objects with incremental, reversible actions and immediate feedback instead of abstract commands.

- Type: principle
- Domain: Experience & interface
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/direct-manipulation/>)

## What it means

Direct manipulation is an interaction style in which people operate on visible representations—dragging a card, resizing an image, or scrubbing a timeline—and see the effect as it occurs. Strong implementations keep objects visible, support small continuous actions, and make outcomes rapid and reversible.

## Why it matters

It shortens the distance between intention and action: the object, available operation, and result appear in one context. This can improve learnability and confidence for spatial tasks, while immediate feedback helps people correct course before a small mistake becomes costly.

## When to use it

Use it for arranging, selecting, resizing, navigating, drawing, or manipulating concrete objects where continuous feedback helps. Pair it with explicit controls when precision, discoverability, motor accessibility, automation, or operation at scale matters.

## How it works

1. Represent the object and its important state visibly rather than hiding everything behind commands.
2. Expose actions through handles, selection states, cursors, labels, or brief instruction.
3. Update the representation continuously or promptly while the person acts.
4. Provide cancel, undo, keyboard alternatives, accessible names, and safe intermediate states.
5. After release, confirm the committed result and reconcile it with server state.

## A practical example

In a kanban board, a person drags a task between columns while a placeholder previews the destination. Keyboard users can move it through an action menu. The move is announced to assistive technology, saved in the background, and remains undoable from a confirmation message.

## Where it breaks

Direct manipulation can hide functionality when objects do not look interactive, and dragging can be imprecise or inaccessible. It scales poorly for bulk operations and complex rules. Immediate movement must not falsely imply that a remote save succeeded; pending and committed states need distinction.

## Common mistakes

- Offering drag as the only way to perform an action
- Moving objects without preview, snap logic, cancel, or undo
- Treating visual immediacy as proof that persistence succeeded

## Sources

1. [Direct Manipulation: Definition](<https://www.nngroup.com/articles/direct-manipulation/>) — Nielsen Norman Group · Professional article
2. [A Layered Interaction Analysis of Direct Manipulation](<https://www.nngroup.com/articles/direct-manipulation-analysis/>) — Nielsen Norman Group · Research article
3. [Direct manipulation for comprehensible, predictable and controllable user interfaces](<https://dl.acm.org/doi/10.1145/238218.238281>) — ACM Digital Library · Research paper

## Related topics

- [Interaction Design](<https://wiki.soroush.uk/topic/interaction-design/>)
- [Affordance](<https://wiki.soroush.uk/topic/affordance/>)
- [Optimistic UI](<https://wiki.soroush.uk/topic/optimistic-ui/>)
