moowmoow

We're exploring a problem that seems universal in growing companies: SOPs (Standard Operating Procedures) drift from reality almost immediately after they're written.

The pattern we keep seeing:

- Team writes SOP in Google Docs/Confluence/Notion

- First month: everyone follows it

- Month 3: half the team has their own variations

- Month 6: the SOP is outdated, nobody updates it, new hires get confused

We're testing a hypothesis that the root cause is the separation between "process definition" (the document) and "process execution" (the tickets/tasks/checklists). If the SOP itself could generate the work items and evolve as the process changes, maybe the drift problem goes away.

Curious to hear from HN:

1. How does your team handle SOP maintenance?

2. What tools do you use? (Confluence, Notion, custom wiki, etc.)

3. Have you found anything that actually keeps documentation in sync with how work gets done?

We're building a platform around this idea — if it sounds relevant to your team, you can check it out here: https://project-g.grepfruits.com

Would love to hear war stories and approaches.