Your documentation exists. Nobody can find it.
You’ve written the documentation. It’s in the wiki. It’s comprehensive.
Your engineers still ask each other in Slack because finding the right article takes longer than asking a colleague. The problem isn’t the content. It’s the structure.
The scenario:
You want to reorganise your internal documentation so engineers find answers in under 60 seconds.
The prompt:
You’re restructuring your internal knowledge base.
Context: [paste your current documentation structure or wiki table of contents]
Redesign the structure to:
Organise by task, not by topic ("How do I..." not "About networking")
Create a top-10 runbook page for the 10 most common tickets
Add a decision tree for each common scenario (if X, do Y)
Standardise article format: problem, steps, verification, escalation
Tag every article by client, technology, and severity
Include a 30-day migration plan and a process for keeping articles current.