Team Wiki Structure for Notion or Similar Tools
Organize shared knowledge people can find.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Design a team wiki structure. Team or company, size, and function: [TEAM_AND_SIZE]. Tool (Notion, Confluence, Obsidian publish, shared drive): [TOOL]. Types of knowledge to store (processes, onboarding, product, decisions, policies, templates): [KNOWLEDGE_TYPES]. Problems now (can't find things, outdated pages, duplicates): [PROBLEMS]. Return: 1. Information architecture: top-level sections (no more than 7) with a description and example pages; a text tree to two levels. 2. Page types and templates: how-to, reference, policy, decision record, meeting notes, project brief; for each, the structure, required fields (owner, last reviewed, status), and an example. 3. Naming and linking conventions: titles that match how people search, a standard glossary page, internal links over duplicates. 4. Ownership and governance: who owns each section; review cycles (quarterly for processes); an archive rule for stale pages; a process to propose changes. 5. Search and navigation: a home page with the 10 most-needed links; tags or properties for filtering; "start here" for new hires. 6. Migration plan from the current state: audit, delete, merge, move; a two-week schedule. 7. Metrics: search success, page views of key pages, percentage of pages reviewed within the cycle. Include permissions guidance (who can edit; sensitive content in restricted areas), and a short onboarding guide for contributors.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.