InsightsSOPs
SOP discipline for teams that are growing fast
Standard operating procedures should shorten onboarding and reduce silent variation, not freeze a company in place. Write them for the people who will use them on a busy day.
Sample article. Swap for a practical SOP guide drawn from client delivery.
Growing teams inherit tribal knowledge. That knowledge works until someone leaves, a volume spike arrives, or a new office tries to copy the Lagos rhythm without the same unwritten rules.
Good SOPs are short, current, and tied to a named owner. They show the happy path and the approved exceptions. They avoid jargon that only the author understands.
Review cadence matters as much as the first draft. A quarterly pass with the people who run the process beats an annual rewrite by a committee that no longer touches the work.
If you need a starting point, pick one revenue-critical or cash-critical flow and document it end to end. Then expand. Coverage without clarity is just more paper.
This is sample copy for layout and voice. Managing insights via Sanity CMS allows updating articles seamlessly without code redeploys.
Newsletter
The Executive Briefing
Occasional notes on governance, process, and risk. Sample signup for now; real delivery comes when email is connected.
No spam. Unsubscribe anytime once mailing is live.