Notion · AI product · Mid · 45 to 60 minutes

How should Notion add AI to core workflows?

Notion is a workspace where people create and organize notes, docs, wikis, projects, and databases using flexible content blocks. Answer this product management case and get it graded line by line against a weighted rubric.

Product strategy
AI product sense
Prioritization
UX judgment
Metrics

The situation

You are a PM on Notion's core creation experience. The Head of Product and a design lead have asked you for a recommendation on how generative AI should enter the product. Interest is rising quickly, users are starting to expect AI help with writing and organizing work, and competitors are shipping simple chat style experiences. Notion already has a mature product with pages, blocks, databases, templates, and many different workflows across personal notes and team collaboration. The challenge is that a fast, general AI entry point could be easy to launch, but it may feel detached from how Notion works today. A deeper integration could make AI more useful, but it risks clutter, confusing behavior, privacy concerns, and inconsistent experiences across surfaces. The team needs a point of view on where AI should show up first, what user moments to prioritize, how much structure versus freeform prompting to offer, and how to keep the product simple for mainstream users while still leaving room for advanced customization.

What to produce

Write a 1 to 2 page product strategy memo.

Your answer must

Define the primary user problems to solve first, and identify 2 to 3 key user moments in Notion where AI could help most.
Recommend an initial product direction for where AI should live in the experience, including the balance between structured actions and freeform prompting.
Prioritize a launch scope of 3 to 5 AI use cases, with rationale based on user value, fit with Notion, and implementation risk.
Explain what product context the AI should use at launch, and what context it should not use yet.
Propose success metrics, guardrails, and a learning plan for the first release and the next iteration.

Constraints

Your proposal must work within Notion's existing concepts, pages, blocks, databases, templates, and team collaboration surfaces.
Do not assume a separate standalone product or a full redesign of the editor.
Model output can be slow or wrong at times, so the experience must preserve user trust and control.
The first release should serve broad, common workflows, not only a niche persona or one specialized team use case.

Format

Use five headings: problem framing, target moments, product direction, launch scope, metrics and risks.

How Notion actually played it

Notion's design lead explains how AI had to fit Notion's building blocks instead of being a thin wrapper around a blank text input. The post covers principles for integrating AI into an existing product. A helpful framing for PMs adding AI to a mature product.

Integrate AI into existing objects, not a blank prompt.
Context from the workspace is the advantage.
Make AI feel native to the product's structure.

Built from The design thinking behind Notion AI by Ryo Lu.