Essential department fields
The core information categories every department page should carry, so knowledge is consistent and findable.
Three organizational patterns
1. Hub-and-spoke
Central department hub with spokes to specialized sub-sections. Best for mid-to-large departments with distinct functions.
Operations (hub)
├─ Delivery operations
├─ Support
├─ Procurement
└─ Customer success
├─ Delivery operations
├─ Support
├─ Procurement
└─ Customer success
2. Database-first
Everything lives in databases with multiple views. Best for process-heavy, data-driven teams.
Master databases
├─ SOPs (by frequency)
├─ Meetings & decisions
├─ Projects
└─ People & roles
├─ SOPs (by frequency)
├─ Meetings & decisions
├─ Projects
└─ People & roles
3. Task-oriented
Organized by what users need to do. Best for user-facing and support teams.
Quick actions
├─ Onboard a new hire
├─ Request a purchase
├─ Report an incident
└─ Find an owner
├─ Onboard a new hire
├─ Request a purchase
├─ Report an incident
└─ Find an owner
Implementation checklist
Readiness score0 / 7
Core design principles
One source of truth. A fact has one home; interfaces may differ, truth does not.
One accountable owner for every page, process and metric.
Structure should serve people, not the other way around — optimize for the new hire.
Review on a clock. Stale documentation is worse than none.