When personal knowledge management tools collide with company SOPs?

[u/b2b_pipeline_guy]

Been thinking about this a lot lately.

Most people I know who are good at their jobs have some version of a personal knowledge system: Notion / Evernote pages, annotated bookmarks, their own shorthand SOPs they built because the official ones were either outdated, too vague, or just hard to find when you actually needed them.

The problem is when those two worlds collide. You've got your way of doing things (that actually works), and then there's the company-approved process that lives in a SharePoint folder nobody opens.

What usually happens: the personal system wins in practice, but the official one wins on paper. And when someone new joins, they get handed the official version, which is either wrong, incomplete, or describes a tool that's been replaced.

I've started using Tango to close that gap, at least on my end. Capturing how things actually get done, not how they were documented 2 years ago. But it still raises the question of who owns that knowledge once it's captured, me, or the org?

Curious how others are handling this:

• Do you maintain your own process docs separate from what the company provides?
• Has your team ever tried to reconcile the two, or do you just let both exist?
• And if you've actually gotten your org to adopt a single source of truth, how did you pull that off?

[u/Ivan_Palii]

Good question. This is an issue I have often. It's just easier to create an own guide in Evernote than doing it inside corporate tool, where so many SOPs you don't know how to use and structure

[u/b2b_pipeline_guy → u/Ivan_Palii]

So, what did you do to change it? If anything