Notion's mid-life crisis

Overall sentiment about Notion’s “mid‑life crisis”

• Many see the piece as playful but are unsure what concrete point it makes; they infer Notion feels older, less exciting, and chasing “sports car” features like AI and CRM.
• Several argue Notion has drifted from a clean, elegant note/wiki tool into a cluttered, “kitchen sink” platform trying to do everything.

Shift toward CRM and enterprise “anything app”

• Strong skepticism about positioning Notion as a CRM; some call it irresponsible or naive, though others say it’s workable for lightweight CRM or simple project management.
• Explanation: once big customers arrive, product roadmaps skew to their feature requests, pushing the tool toward all‑in‑one enterprise use.
• Some see this as rational market expansion (competing with Salesforce, revenue tooling); others view it as dilution of product “taste.”

AI features and privacy concerns

• Serious concern over AI integrations that send private notes to third‑party LLM providers (OpenAI, Anthropic), including accidental sends via confusing UI.
• A few users have quit Notion for more private or self‑hosted tools.
• Notion employees in the thread stress that training on customer data would be too risky, but some commenters don’t trust that this won’t change under investor pressure.

UX, performance, and technical critiques

• Complaints about latency, CPU usage (especially on macOS/Electron), and heavy JS leading to slow, distracting editing experiences.
• Mixed experiences with keyboard and mouse interactions; some find it keyboard‑friendly, others find selection and block manipulation infuriating.
• Markdown export/import is seen as lossy and unreliable.

Use cases, flexibility, and alternatives

• Fans praise flexible databases, block‑based editing, and ability to unify wiki, tasks, and light CRM; they see Notion as a powerful “hub.”
• Critics say it’s a “jack of all trades, master of none” and prefer specialized tools: Obsidian, Apple Notes, Confluence, Google Docs, Jira, self‑hosted options, etc.
• Several note that wiki‑style tools inevitably suffer from “zombie” documents and require active curation, regardless of platform.

Data model, lock‑in, and APIs

• Concern about vendor lock‑in and complex JSON API formats.
• Notion staff explain a verbose union‑like API schema chosen to aid statically typed languages; some commenters argue simpler tagged unions are feasible.

Adoption patterns and future

• Observations that Notion is very popular among students and non‑technical staff, while many developers remain skeptical or indifferent.
• Some predict another migration wave away from Notion (as happened from Evernote), while others compare its role to Excel: imperfect, but the tool “everyone can understand.”