Plan AW: Team Onboarding & SOP Library

Role inventory → process mapping → SOP writing → knowledge base → maintenance

Time
3-5 days
Cost
Low
Difficulty
Advanced

Best for

For teams turning scattered work experience into processes new hires can follow, plus onboarding material, to stop repeating the same answers.

Steps

Role inventory

0.5-1 day

Notion + you

Collect each role's daily tasks, frequent questions, handover items and hard-won lessons into a role map. Ask a veteran on the team to walk through their typical day — that's the cheapest first-hand material.

💡Start from 'questions a new hire asks in their first 30 days' and prioritize the places where the same answers get repeated most.

Process mapping

1 day

ChatGPT / Claude

Turn repetitive work from the role map into flows: trigger → steps → output → owner. Have the model check for missing links, unclear ownership, and when to escalate.

💡Ask the model to flag exceptions and gray zones in every process — most SOP failures happen in the exceptions.

SOP writing

1-2 days

Claude / ChatGPT

Convert flows into followable SOPs: each step states what to do, which tool, what 'done' looks like, common mistakes, and where screenshots go. Have the model compress wordy prose into step checklists and review it from a new-hire perspective.

💡Have a real new hire walk through the SOP once; fix wherever they stall — more effective than self-review.

Knowledge base

0.5-1 day

Notion / Confluence

File SOPs into the knowledge base by department and process, with a table of contents, tags and search, and permission tiers to keep confidential material inside. Put the onboarding handbook (accounts, environment, day-one checklist) front and center.

💡Stamp every SOP with 'last updated + owner'; a knowledge base nobody maintains is as good as none.

Maintenance

0.5 day per quarter

GitHub / scheduled review

Review SOPs quarterly or whenever a process changes: track edits with GitHub or KB versioning, update stale steps and screenshots, and have AI diff old vs new flows to flag linked documents that need syncing.

💡Keep an SOP revision log — which entry, why, and who changed it — and point new hires at the docs before asking people.

Tools involved

NotionChatGPTClaudeGitHubConfluence

Pitfalls to avoid

SOPs too abstract to follow

'Follow up responsibly' gives a new hire nothing to do; every step needs an action, a tool and a done-criteria so they can execute without hand-holding.

Building a library that's never maintained

A stale SOP misleads more than its absence; schedule quarterly reviews and a revision log so maintenance becomes routine.

Loose access control

Knowledge bases often hold client info and internal decisions; share by permission tier and revoke accounts promptly on departure.

Waiting for perfection

Ship an 80-point usable version, let new hires break it in, then iterate; waiting for a 100-point release usually means it never ships.

Related Workflows

Plan I: AI Presentations (Slides)

Topic & audience → outline & storyline → per-slide generation → visual consistency → speaker notes → rehearsal

Time：
30-60 min / deck
Cost：
Low
Difficulty：
Beginner

Plan J: AI Data Analysis / Research Report

Define the question → clean data → exploratory analysis → deep modeling → visualize & narrate → conclusions

Time：
2-6 hours / report
Cost：
Low-Medium
Difficulty：
Advanced

Plan K: AI Meeting Notes Workflow

Record & transcribe → AI summary → extract action items → archive & distribute → follow up & review

Time：
15-30 min / session
Cost：
Low
Difficulty：
Beginner