Case Study: Notion's Database UX Shift — Inline Relations and Templates

Design · 6 min read

Case Study: Notion's Database UX Shift — Inline Relations and Templates

Notion moved from a page-centric to a relationship-first model by promoting inline relations and rollups to primary controls. Instead of buried relation pickers, users can create and edit related items inline, which reduces context switching and increases discoverability of linked content.

Template discovery is also redesigned: Notion now surfaces templates contextually based on detected content and common patterns in the workspace. The UI uses soft onboarding cues and sample data to reduce the cost of trying a new template. Crucially, templates remain fully editable, preserving Notion’s philosophy of composability.

To support power users, Notion added keyboard-friendly quick commands and a compact view that prioritizes dense information scanning. For new users, progressive disclosure and pre-populated examples lower the activation threshold. The trade-off is slightly higher UI complexity for beginners, but the contextual help mitigates that by teaching patterns in situ.