Notion AI onboarding teardown

Notion does not route users to a standalone AI tab. Starters appear in the editor chrome where the cursor already is.

Context is implicit: the current page, block, or selection informs what “summarize this” or “improve writing” will target.

Embedded AI should feel like a command on the document, not a detour to another product.

Examples are grouped by task type so users browse by intent, not by prompt engineering skill.

Each starter is a complete sentence users can run with one click, then edit. That teaches effective prompts by example.

Categories scale as capabilities grow without turning the panel into an unfiltered list.

After “Write meeting agenda,” Notion opens a tighter AI surface with the starter as seed text and room to refine.

The flow stays in-document: output inserts where the user needs it, not in a side thread they must copy from.

First value is one click away; depth is still available for users who want to customize.

Invoke AI in the editor → pick a categorized starter → refine → accept output into the page.

Compare with chat-native first-run flows (empty composer + suggestions): Notion optimizes for users who already have a doc open.

Steal categorized one-click starters if your AI is embedded in a host surface (docs, design files, tickets).