---
title: "Understand"
description: "Grasp the abstractions and mental models the product is built around."
doc_version: "2025-01-09"
last_updated: "2026-08-08"
canonical_url: "https://7act.org/actions/understand/"
language: "en"
license: "CC BY 4.0"
---

# Understand

Software products are usually built around abstractions that are difficult to grasp yet fundamental to the proper usage of an application or service. While conceptual documentation is not always consumed in the first place, it's often used alongside exploration/practice docs to anchor learnings.

Examples of docs that address understanding are [Kubernetes' Concepts](https://kubernetes.io/docs/concepts/overview/components/), [Thinking in React](https://react.dev/learn/thinking-in-react), and [What is OLAP?](https://www.linode.com/docs/guides/what-is-olap/) They all provide conceptual explanations around concepts that they either implement or introduce. In doing so, they transcend the barriers of their own product and become universal learning materials.

While hard to produce and easy to underestimate, docs that support understanding also serve educational initiatives, like product academies or classrooms. They're valuable because they sit at the very center of the [Circles of Product Truth](https://passo.uno/circles-product-truth/). All documentation sets should address this need.


## What the user wants to do

Software products are built around abstractions that are difficult to grasp yet fundamental to proper usage. Conceptual documentation anchors learnings alongside exploration and practice.

## Signals that your docs miss it

- Users can operate the product but cannot explain why it works the way it does.
- Concepts are explained only in code comments or internal wikis.
- There is no glossary or conceptual guide for the product's core abstractions.

## Two examples in the wild

- [Kubernetes Concepts](https://kubernetes.io/docs/concepts/overview/components/)
- [Thinking in React](https://react.dev/learn/thinking-in-react)

## Common content types

- DITA: <concept>, <glossentry>, <section>
- Diataxis: Explanation
- Good Docs Project: Concept guide, Glossary

## One metric

concept coverage — Share of core abstractions with a dedicated conceptual page.

## Sitemap

- [Seven-Action Documentation Model](https://7act.org/index.md)
- [Introduction](https://7act.org/rationale/index.md)
- [Actions](https://7act.org/actions/index.md)
- [Appraise](https://7act.org/actions/appraise/index.md)
- [Understand](https://7act.org/actions/understand/index.md)
- [Explore](https://7act.org/actions/explore/index.md)
- [Practice](https://7act.org/actions/practice/index.md)
- [Remember](https://7act.org/actions/remember/index.md)
- [Develop](https://7act.org/actions/develop/index.md)
- [Troubleshoot](https://7act.org/actions/troubleshoot/index.md)
- [Glossary](https://7act.org/glossary/index.md)
- [Seven-Action Documentation skill](https://7act.org/skill/index.md)