[[Notion]] for one user drops the multi-author complications, leaving templates, typed databases, and AI assistance against a backdrop of vendor lock-in — for [[Personal Knowledge management|personal knowledge management]] the question is whether database-style organisation outweighs the loss of relationship-graph visibility. ## [[Notion]] ![[Notion#^definition]] For single-user PKM, the multi-user complications fall away, leaving template-driven note structures, typed databases with multiple views (table, kanban, calendar, gallery, timeline), and AI assistance. ## [[Personal Knowledge management]] fit For personal knowledge management the relevant requirements are the four baseline axes from [[Knowledge management]] - the three collective-only axes (Securability, Ownership clarity, Agent-readiness for multi-author governance) drop out because the single user is the producer, reviewer, and consumer. ### [[Discoverability]] ![[Knowledge problems#^discoverability]] Mixed. Notion's search returns matching pages; backlinks exist but flat; no graph view. For PKM the single user knows their own schema, partly offsetting the absence of graph navigation - but discovering unexpected connections across topics is not the tool's strength. ^discoverability ### [[Maintainability]] ![[Knowledge problems#^maintainability]] Strong. Hosted, no setup, AI assistance for routine updates, templates for repeatable note shapes. The user maintains content; Notion maintains the platform. Updates are real-time and require no infrastructure. ^maintainability ### [[Connectivity]] ![[Knowledge problems#^connectivity]] Weak. Backlinks are flat; no graph view. Inline page mentions exist but cannot be queried as a relationship graph. Database relations are flat, not traversable. For users whose personal knowledge is shaped by connections between concepts, this is a significant gap. ^connectivity ### [[Survivability]] ![[Knowledge problems#^survivability]] Weak. Proprietary block model. Export gives Markdown or HTML but loses the relational structure, embedded blocks, and formula columns. If Notion changes pricing or pivots, migration costs are high and the migrated knowledge is shape-only. ^survivability ## Verdict - [/] [[#Discoverability]] - [x] [[#Maintainability]] - [-] [[#Connectivity]] - [-] [[#Survivability]] ^verdict Adopt where database-style organisation, typed views, and zero-infrastructure matter - and the user accepts vendor lock-in. Avoid for PKM organised around relationships between concepts, or for users who want their knowledge to survive a tool change without significant migration cost. ^answer The conclusion lives in none of the requirements on its own. Notion's strength is maintainability (the platform takes care of itself); its weaknesses are connectivity and survivability. The verdict depends on whether your personal knowledge is shaped more by typed records or by relationship graphs.