New hire starts Monday. Tuesday they're asking in Slack: Where's the client deck template? How do I access the AWS account? What's our QBR format?
Three weeks later they're productive. The 'ask around' tax: 5-10 hours/week per person, every week, forever.
This is finding number five in our audits. Here's the system that kills it.
The Two-Layer System
Layer 1: File Storage (Google Drive / OneDrive / Dropbox)
- Final deliverables, contracts, assets, reference files
- Organized by entity, not by person or date
Layer 2: Knowledge Base (Notion / Confluence / GitBook)
- Processes, templates, how-tos, decisions, FAQs
- Searchable, linkable, versioned
Rule: If it's a file → Drive. If it's knowledge → Notion. Never mix.
The Drive Structure (Entity-First)
Clients
Client A
Contracts (MSA, SOWs, amendments)
Deliverables (final decks, reports, assets)
Correspondence (key emails, scope changes)
Client B
...
Internal
Finance (audits, tax, insurance, banking)
HR (policies, templates, org charts)
Operations (process docs, vendor contracts, tools)
Templates (deck templates, proposal templates, SOW templates)
Reference
Industry benchmarks
Competitor research
Tool documentation
Naming convention: YYYY-MM-DD_Client-Project_DocumentType_vN.ext Example: 2026-03-15_Acme-Q2-Brand_Deck_v2.pdf
Permissions:
- Client folders: Account team + leadership only
- Internal: Full team (view), ops/finance (edit)
- Templates: Full team (view), ops (edit)
The Notion Knowledge Base Structure
Top-level pages (sidebar):
- Start Here — Onboarding checklist, first-week links, who's who
- Processes — How we do X (one page per process)
- Templates — Copy-paste ready (proposals, QBRs, status reports)
- Tools & Access — Every tool, login method, who owns it
- Decisions Log — Why we chose X, Why we stopped doing Y
- FAQ — Searchable answers to repeat questions
- Client Playbooks — One page per major client: contacts, quirks, workflows
Each process page follows this template:
# Process: [Name]
**Owner:** @person
**Last Updated:** YYYY-MM-DD
**Review Cadence:** Quarterly
## When to Use
[Trigger conditions]
## Steps
1. [Action] — [Tool/Link] — [Owner]
2. ...
## Exceptions
[Edge cases and how to handle]
## Related
[Links to templates, tools, other processes]
The Onboarding Test
Day 1 task for every new hire: Without asking anyone, find: (1) the proposal template, (2) the AWS login, (3) the QBR process, (4) Client X's current SOW.
If they can't do it in 15 minutes, your system failed. Fix the gap they hit.
The Ask Around Replacement Protocol
When someone asks in Slack Where is X?:
- Answer with the link
- Immediately add to FAQ or relevant process page
- Reply: Added to [Notion page] for next time
After 2 weeks, the questions stop. The knowledge base becomes the source of truth.
Access Inventory (Quarterly Audit)
Every tool, every account, every permission:
- Figma | Design | Design Lead | Design + PMs | 45/mo | 2026-07-01
- AWS | Infrastructure | Tech Lead | Eng only | 2300/mo | 2026-07-01
- QuickBooks | Accounting | Controller | Finance + Founder | 90/mo | 2026-07-01
Red flags:
- Tool with no owner
- Tool where everyone has admin
- Tool paid for but less than 3 active users
- Access not revoked for departed team members
Quick Win This Week
- Pick one client folder. Restructure it to the entity-first format above.
- Create one Notion process page for your most-asked-about process.
- Run the onboarding test with your newest hire (or pretend you're new).
Fix what they can't find. Repeat weekly.
Knowledge management isn't documentation — it's operational infrastructure. Book a discovery call and we'll audit your entire system in 30 days.