1
4 Comments

How do you manage SOPs and internal processes at your company?

Hey IH 👋

I'm building a platform that helps teams define, evolve, and automate their internal processes — think SOPs, onboarding workflows, asset tracking, ticket management, etc.

Before going too deep, I want to validate whether the problems I've experienced are shared by others. I'd love to hear from you.

A few quick questions:

  1. How do you currently manage SOPs / internal processes? (Notion, Confluence, Google Docs, spreadsheets, or just... tribal knowledge?)

  2. What's your biggest frustration? For me, it was SOPs becoming outdated the moment they were written. Nobody updates them, and new hires end up following zombie docs.

  3. Have you tried automating any of it? If so, what worked and what didn't?

  4. If a tool could keep your SOPs "alive" — versioned, tied to actual workflows, and evolving with your team — would that be worth paying for?

I put together a short survey (< 3 min) to collect more structured feedback. Would really appreciate it if you could fill it out:

👉 https://project-g.grepfruits.com

Happy to share the results with the community once I have enough responses. And of course, if you have strong opinions about this space, drop a comment — I'd love to chat.

Thanks! 🙏

on March 2, 2026
  1. 1

    the hardest part for us wasn't finding a tool. it was getting people to actually document things. we had a Notion database nobody opened because the real workflows lived in Slack threads and Zoom recordings. what actually worked was going back to those and converting them into structured SOPs instead of asking people to write things from scratch. the knowledge was already there. it just never became a document. what's the biggest documentation headache for your team right now? is it creating them or keeping them updated?

  2. 1

    Confluence is the name of the game for us. The main challenge is that even in Confluence, which makes it easy to find content no matter where it is, gets created haphazardly and in a fragmented, inconsistent way.

    1. 1

      That's a really common pattern with Confluence — the tool itself is powerful, but without strict governance, the content sprawls fast. We've heard the same from multiple teams: search works fine technically, but when SOPs are created by different people with different structures and naming conventions, "findable" doesn't mean "usable."

      Curious — have you tried any workarounds to keep things consistent? (Templates, naming conventions, page trees?) Or has it been more of a losing battle?

      1. 1

        Tried, yes! Succeeded... hmmm.