---
title: "Notion | Skills We Assign For | Azendo"
description: "Notion for documentation and research — structure, drift, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/notion/"
---

[Skills](https://azendo.co/skills/) Design and research 

# Notion.

Notion is a workspace tool combining documents, databases, wikis and project tracking, used for documentation, research repositories, design specifications and process definition.

## Where Notion fits on a long engagement.

Notion's flexibility is why it spreads and why it degrades. Anyone can create a page, which means documentation exists; nobody owns the structure, which means finding anything becomes progressively harder until people stop looking and ask a colleague instead.

Databases with consistent properties are what make it more than a document store. Research findings, design decisions and components as structured records can be filtered and related, where the same content as free-form pages cannot.

## What an assigned team does with Notion.

Documentation that is wrong is worse than documentation that is missing, because people act on it. A page describing a process that changed six months ago actively misleads whoever finds it.

Ownership with a review cadence is the only thing that prevents that, and it is part of the working standards held by the assigned specialists under [outsource ux design](https://azendo.co/services/ux-ui-design/).

## What we use Notion for.

* Research findings as structured records Filterable and relatable rather than free-form pages nobody can search.
* Design decisions with their rationale Why something was decided, kept where the next team will find it.
* Ownership and a review cadence Pages with an owner, because stale documentation actively misleads.

## How Notion capacity is assigned.

Documentation practice sits inside the assigned capacity, with ownership and review treated as part of the work rather than an overhead.

## Service lines it sits in

* [UX/UI design](https://azendo.co/services/ux-ui-design/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in design and research

* [Storybook — skill we assign for](https://azendo.co/skills/storybook/)
* [Maze — skill we assign for](https://azendo.co/skills/maze/)
* [Hotjar — skill we assign for](https://azendo.co/skills/hotjar/)
* [usability testing — skill we assign for](https://azendo.co/skills/usability-testing/)
* [design systems — skill we assign for](https://azendo.co/skills/design-systems/)
* [design tokens — skill we assign for](https://azendo.co/skills/design-tokens/)
* [component libraries — skill we assign for](https://azendo.co/skills/component-libraries/)
* [Figma Dev Mode — skill we assign for](https://azendo.co/skills/figma-dev-mode/)

## Tell us what your roadmap needs Notion for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)