Operations Teams, HR, Managers, Founders, Support Teams
Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.
1. Copy the Workflow Prompt. 2. Paste it into your AI tool. 3. Replace the "Required Inputs" 4. Run the prompt.
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
You are designing an internal knowledge base.
### Required Input
- Content Types: [e.g. SOPs, policies, guides]
- Users: [who will access it]
- Current Issues: [e.g. hard to find info]
- Scale: [team size or expected growth]
### Input Validation
If content or users are unclear, ask clarifying questions. Pause until structure can be designed properly.
### Instructions
Design a logical and scalable structure.
Define:
- Main categories
- Subcategories
- Tagging system
Ensure:
- Easy navigation
- Minimal duplication
- Clear ownership of updates
Include maintenance processes and update responsibilities.
### Output
1. Knowledge base structure
2. Category hierarchy
3. Tagging rules
4. Maintenance process
5. Ownership model
6. Common failure points
Add search optimisation tips.
Fictitious Company: Aero-Vantage (Sustainable Aviation Fuel R&D)
Users: 150+ employees across Engineering, Compliance, and Marketing Operations.
Current Issues: Information is scattered across individual Google Drive folders and Slack pins, leading to “knowledge silos” and outdated data usage.
The Aero-Intel Hub is built on a “Three-Click Rule”: users should find any document within three clicks of the homepage. It uses a hybrid structure of Functional Departments and Cross-Functional Pillars.
| Primary Category | Subcategories | Primary Content Type |
|---|---|---|
| 01. The Launchpad | Onboarding, Company Mission, Org Chart, Benefits. | Policies / Culture |
| 02. Governance & Compliance | Legal Templates, Safety Standards (SAF), Audit Logs. | Certifications / Templates |
| 03. Operations & SOPs | Lab Protocols, Supply Chain Workflows, CRM Guides. | Step-by-Step Guides |
| 04. Project Archives | Project “Eagle-Eye,” Project “Bio-Jet,” Past Case Studies. | Technical Reports |
| 05. Tech Stack & Tooling | Software Licenses, AI Tool Policies, Hardware Requests. | User Manuals |
Tags act as a secondary “horizontal” navigation layer. All articles must have at least one tag from each of the following groups:
#Draft, #Verified, #Legacy (Archived).#Engineering, #Sales, #All-Staff.#Critical-Path (Must know), #Reference-Only.To prevent “content rot,” Aero-Vantage follows a Quarterly Knowledge Scrub:
#Requires-Review tag.Get access to all workflows, across every sector, with structured systems built for better results.