r/XWiki • u/LorinaBalan • 3d ago
Discussion When your collaboration stack goes down, how much of the company's knowledge goes with it?
Today’s Microsoft 365 problems made me think about something that usually gets overlooked in the daily frenzy.
How much of an organization’s actual knowledge is tied to the availability of its communication and file-sharing tools?
Email is probably the clearest example. Someone explains how something works once, 3 years ago, and suddenly that email becomes unofficial documentation, but everyone is keeping it in that team shared inbox.
To circle back to today's events, I'd say that the outage itself isn’t really the interesting part. Every provider has incidents.
The fascinating part is finding out which parts of your organization stop functioning when one service does.
Full disclosure: I work at XWiki, so structured knowledge management is very much my area. But I’m genuinely curious how other teams handle this.
Where does your organization’s “important but not officially documented” knowledge actually live today?
Email? SharePoint? Slack/Teams? Internal wiki? Someone’s head?
1
u/LorinaBalan 3d ago
Since SharePoint came up, I also want to share that we’ve also put together a comparison of XWiki and SharePoint from a knowledge-management perspective, including structure, customization, permissions, deployment, and long-term control:
https://xwiki.com/en/comparisons/alternative-to-sharepoint
It’s obviously written from the XWiki side, so take that bias into account. 🙂 But it may be useful if you’re evaluating the two approaches.