Portfolio / Expertise / Policy & SOP Development
Policy & SOP Development
Policies that nobody uses are decoration. I write compliance manuals and standard operating procedures that survive turnover — documented from the real process, built with the people who execute them, and adopted, not imposed.
The Workflow — How I Approach It
Observe the real process first
Document what actually happens — not the idealized version.
Write step-by-step with owners
Every step has a responsible person — no anonymous process.
Socialize with stakeholders
Built with the people who’ll use it — so it reflects reality and earns buy-in.
Version and review regularly
Policies age; schedule the refresh so they don’t go stale.
Keep it executable
Anyone can follow it correctly after turnover — that’s the test.
My Operating View — The 2 Cents
An SOP that survives turnover is the highest-leverage artifact in HR. My 2 cents: write it from the real process, with the people who run it. Document the ideal and you’ve built a compliance prop; document the real and you’ve built a control that actually works.
What Worked & What Didn’t
What Worked
- Compliance manuals and SOPs that survived team turnover.
- Adoption because the process was built with its users.
What Didn’t
- Writing policies nobody used — decoration, not control.
- Documenting the ideal instead of the real — staff couldn’t follow it.