I'm really interested in how different teams manage to keep all their important project links organized. In busy environments filled with dashboards, documents, and various tools, it seems like links often get scattered across Slack messages, old documents, bookmarks, and tickets. This leads to constant "where's the link for X?" questions, particularly during onboarding or emergencies. For those in DevOps or infrastructure-heavy teams, where do you usually keep important links? What tends to break down as teams grow or speed up? Is this just a minor annoyance, or does it really slow things down? I'd love to hear about practical approaches that work in the real world.
1 Answer
Most teams try to solve this by creating a wiki, but it often ends up being neglected until someone desperately needs a link at 2 AM during an incident. The best solution seems to be a shared bookmark folder in whatever tool everyone is already using, like Confluence or GitHub wiki. However, people typically don't trust this so they keep their own copied links instead.
That's so true! The real issue isn't just where the links are stored; it's about the lack of trust in the shared resources. In your experience, what’s the best way to rebuild that trust in a shared link repository? Is it about ownership, fresh updates, or something else?