> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/cognitive-tools/ux-laws-principles/concepts-and-models/chunking.md).

# Chunking

Chunking is a memory technique that groups individual pieces of information into larger, more meaningful units (or "chunks"). This strategy significantly increases the amount of information the user can process and retain.

Chunking directly leverages Miller's Law, which suggests that the average person can only hold about 7 (plus or minus 2) items in their Working Memory at once. By combining multiple data points into a single, recognisable "chunk," designers can circumvent this limitation and vastly reduce Cognitive Load.

#### Why Chunking Works

* **Reduces Cognitive Load**: Instead of forcing the brain to process many discrete data points, the interface presents fewer, larger, and more recognizable units.
* **Enhances Memorability**: Grouped information is easier to encode into long-term memory than a stream of random, unorganized data.
* **Improves Scanning**: Users can quickly locate the required information block without reading every item individually.

#### Practical UX Applications of Chunking

Chunking is one of the most fundamental tactics for improving readability and data entry:

**1. Data Formatting**

* **Application**: Breaking up long strings of numbers or letters into smaller, fixed-length groups.
* **Examples**:
  * Phone numbers: $$555−123−4567$$ (instead of 5551234567)
  * Credit Card numbers: $$4242 4242 4242 4242$$
  * Confirmation codes: $$ABC−123−XYZ$$

**2. Interface and Content Structure**

* **Application**: Grouping related content, actions, or navigation elements using visual proximity.
* **Examples**:
  * Navigation Menus: Grouping 10 links into 3 or 4 top-level categories.
  * Forms: Separating a long form into sections with distinct headings (e.g., "Personal Info," "Shipping Address," "Payment Details").
  * Body Text: Using bullet points, short paragraphs, and clear headings to break up large walls of text.

**3. Sequential Task Flow**

* **Application**: Breaking a complex, multi-step process into sequential, manageable stages.
* **Example**: A checkout process that uses a Progress Indicator to show "Cart," "Shipping," "Payment," and "Review." Each step is a manageable chunk of the overall task.

#### Takeaway

Don't make users count. Group information logically so the brain perceives it as a single, easily digestible unit.

#### Further Reading

{% embed url="<https://www.nngroup.com/articles/chunking/>" %}

{% embed url="<https://www.nngroup.com/videos/chunking/>" %}

{% embed url="<https://www.interaction-design.org/literature/book/the-glossary-of-human-computer-interaction/chunking>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.designreference.xyz/cognitive-tools/ux-laws-principles/concepts-and-models/chunking.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.