6 ms·
I definitely share with you the view that Slack is a poor substitute for proper documentation and company communication. To me it just feels like that any proje
by rglullis 6y ago
I definitely share with you the view that Slack is a poor substitute for proper documentation and company communication. To me it just feels like that any project that is managed via Slack transplants the dynamic of open-floor offices to your computer and mobile phone. Yes, it is easy to gather everyone and share quick updates, but only in a fast-food kind of way.
One big change that I got with my team to do successfully in a company was to change the attitude regarding communication and documentation on Slack.
It involved one single, simple rule: whenever you want to ask anything you need to do your work on Slack, phrase it a way that relates to the Wiki/Knowledge Base.
In our case it was Confluence. So, instead of getting questions on channels such as "How do I do X?", we would ask "Can someone point me to the Confluence page that explains how to do X?". Instead of asking someone to send a file or spreadsheet with data that I needed, I would ask them to revise and update the Confluence page, and so on. That would apply even for meetings that were held. If someone missed a meeting and wanted a re-cap, it was easy to point to the page with the minutes of the meeting, and so on.
In the beginning we did have to prod and nag some of the colleagues so they would drop old habits, but after a couple of weeks when the majority understood that Wikis are meant to be editable freely it was working really well. There were no longer huge threads on Slack and there was no more stress about missing anything that happened on Slack. It did help (a lot) that we had the support from upper management in implementing this, as they were the ones worried the most about losing communication scattered in a million threads and channels.
- ebiester 6y agoSo, how did you solve the organization problem? That has always been the biggest problem with confluence and wikis in general. People actively dislike confluence. (And it's something that's stuck in my craw - how do we build documentation that's easy to organize? That's my quarantine project. :)
- matwood 6y agoI've thought about this problem a lot and the conclusion I came to is that tools like Confluence are like the original Yahoo directory of links. Organizing seems like a good idea when there are a small number of items, but it quickly becomes unwieldy. What I've settled on, while not perfect, is shared Google docs where owners of the doc allow suggestions to help keep it up to date.
- rglullis 6y agoConfluence as a Knowledge System is like Democracy for Political systems: the worst ever, except for everything else that was tried. As much as I'd like to replace it, it did everything we needed and was better than any alternatives that we considered for both tech/non-tech teams. The solution we had was to give one Space for each team/department in the company: one space for Customer Support, one for Engineering, Data Scientists, Business Analysts and Operations/Management. Each team lead was responsible in ensuring that other teams from the company could find the information needed, but aside from that we let each team organize itself. The only hard rule was the one I stated above, everything else came somewhat organically. Managers and Business Analysts, for instance, still preferred to work in Word/Excel, so their pages was mostly just placeholders for Office Docs and attachments. This was fine by me, as long as they could always respond quickly with the right file/link if someone else in the team asked for something.
- AsyncAwait 6y agoDokuWiki works miles better for me than Confluence ever did.
- ebiester 6y agoThe biggest problem is that "everything else that was tried" wasn't from experts who truly understand information management, nor has our industry learned patterns from other industries that also have similar problems. I'm trying to do that work now. It's not even that I don't think it can be done in confluence or wikis in general, but rather we don't have a great methodology in organizing it. I'm keeping a list of what I find at https://www.ebiester.com/annotated-links/documentation/2020/05/04/annotated-documentation-links.html https://www.ebiester.com/annotated-links/documentation/2020/... but I'm not seeing what I really want just yet.
- rglullis 6y agoI am afraid I won't be able to help you much there. Every place I saw trying to come up with a grand top-down scheme to organize documentation failed. Too much structure, and people will wait until they have all of the details needed to start contributing, or they will not contribute unless it's "their job". Too much flexibility and they don't know where to start. I found that it was always better to let documentation and knowledge sharing follow the same principles as code: let it come bottom-up, see what patterns emerge and only worry about structure when the current practices hit a bottleneck. But then again I never worked on any project that I had hundreds of people directly depending on the documentation, so it might not work as a strategy for larger-scale organizations.
- phixiuz 6y agoAlso have similar experience with Confluence, as an alternative: we adopted a VuePress static site that we host internally (behind proxy), which basically just renders a bunch of markdown files. For easy discoverability of content we use Algolia's documentation search on top of it. For updating content we either use git locally for technical people, non-technical people can also directly update the content on remote git via gitlab interface. This has been working really well for us once setup, the main challenge we still have now is how to effectively communicate changes to the relevant people at the most appropriate time. Your knowledge system keeping in sync with your version control is also a major plus, this is the primary reason why I don't like tools like Confluence, because it's easy for them to get out of sync with the actual system, and this can require too much coordination.
- rglullis 6y ago> it's easy for them to get out of sync with the actual system, and this can require too much coordination. I don't follow. How much do you have of your non-techies updating your knowledge base and how do they get to know if what they are updating is "in sync" with the system if the changes are making are orthogonal with the functionality? It seems your case is mostly about documentation of the technical product, specs, requirements. Yeah, this can go to your version control, and I would bet that you could find a Confluence plugin that would generate the documentation from version control and sync with the rest of your Confluence pages if you wanted. But I really, really doubt your method can scale beyond the IT side of any middle-to-large organization. The moment you ask Business/Customer Support people to actually go look at anything like Gitlab/Github's interface is the moment you lose 90% percent of buy-in from both non-techies and management at any company that is not absolutely dominated by Software Engineers. Requiring integration with version control is a convenience for engineers, but it is so far from the tooling from those that live on Excel sheets that you might as well ask them to never touch the documentation side.
- phixiuz 6y agoGranted, we're still a fairly small organization (+- 10), but our business and customer support people are also using Gitlab to maintain our knowledge base: once you properly guide them on how to use it, they are definitely able to handle this. All the actual git operations happen under the hood of the web interface. So we do strongly believe this is scalable, at least for our use case. This has been working fine in fact for long-lived information across multiple departments (not only technical docs, but also e.g. sales/customer support guidelines). For short-lived information we use Google Docs (e.g. meeting summaries).
- specialist 6y agoTerrific insight, strategy. Futureperfect: can those convos be mediated via a wiki? While using Confluence, I tried to keep track of activities. Like when another team updates an API I'm using. Manually. IIRC, I could watch pages. But I couldn't follow individuals, topics, teams, etc.
- rglullis 6y ago> can those convos be mediated via a wiki? In the wiki page proper? Theoretically, yes, but it would involve a lot of discipline from everyone in your team. One thing that worked for our team (i.e, our Confluence Space) was to keep all pages with a "comments" page at the end. Any comment that came up on that page was basically meant an "issue" to be resolved in the documentation: clarify a point, update another, link to a related page with more details, etc. Once the person that created the comment was satisfied, we treated the issued as resolved and deleted the comment without prejudice.
- specialist 6y agoThat purposeful culling strategy is good. I've often wished Slack et al had SnapChat style auto grooming. Something in between would be nice. I now recall that C2 wiki has convention of comments. They're immortal. It sucks. https://wiki.c2.com https://wiki.c2.com FWIW, I've been advocating everything (everything) gets a TTL. Like renewable leases. Culling is such a huge problem, burden. As others have commented (in the org-mode thread), upkeep becomes onerous. It may be cheaper just to rediscover stuff that's gone stale. -- There are different types of convos, interactions, transactions with their own use cases that all need to be implemented specifically. All of the purpose built focused tools I've seen, per that cliche, eventually add an email feature. And I can't think of a hybrid solution. Maybe bug trackers. I hope someone someday cracks this problem.