SOP & Knowledge
Management
A five-flow system that turns a leadership directive into a documented, trained, and communicated process update — with a single human review gate before anything publishes.
The Gap I Found
The same information,
written three times.
Every process change starts as a leadership directive — an email, a meeting note, a Slack message. From there, someone has to write the SOP, update the training materials, and communicate the change to the relevant team. Three separate tasks. All derived from the same source. All requiring separate, sequential effort from the same person.
The result is always inconsistency at some layer: the SOP gets written but training lags behind by weeks. The team gets notified before the documentation is ready. Or the page lands in the wrong Confluence folder — buried under a different team's workspace — and the policy change quietly never reaches the people it was meant for.
The work was getting done. But it was never quite in sync, and no one could tell where the drift was happening until someone asked a question the system couldn't answer.
Why It Happens
The directive and the documentation are two separate systems with nothing between them.
SOPs, training documents, and team communications each live in different tools with no trigger connecting them. A leadership directive has no structured path to become a documented, trained, and communicated process update. That path is rebuilt manually every single time.
And because the path is manual, it compresses under pressure. The busiest moments — when the most changes are happening — are exactly when the documentation falls furthest behind. The gap isn't a failure of intention. It's a failure of architecture.
What I Designed
Five flows. One entry point.
One review gate.
The system is built around a single principle: a directive should only enter the operation once. Everything downstream — the draft, the Confluence page, the training update, the team email, the quiz — runs from that single structured entry in Airtable.
The five flows below cover the full lifecycle: from capturing a change to training the team on it, with a human review gate at the only point that requires judgment.
Systems Involved
What Changed
One entry. Everything downstream takes care of itself.
The person managing the process change fills out a form once. They do not write the article. They do not post to Slack. They do not schedule a training session. The system handles all of it.
1x
Single entry point
One form submission is the only manual step. Everything else fires automatically.
0
Missed announcements
Team notification is tied to publication, not to someone remembering to post.
→
Review before publish
Every article goes through a human reviewer. Nothing reaches the team unreviewed.
100%
Training visibility
Every flagged SOP generates a quiz. Completion is logged without chasing.
How It Connects
The knowledge layer that runs through everything.
SOP & Knowledge Management does not operate in isolation. Process changes affect how projects run, how time is tracked, how payroll is calculated, and what the dashboard reflects. Each connection below is a place where a documentation change needs to propagate without someone manually coordinating it.