3 ms·
I agree that a company-wide knowledgebase could reduce interruptions. However, the assumption is that most of the data people need will be there. Not sure how e
by alexakisalex 10y ago
I agree that a company-wide knowledgebase could reduce interruptions. However, the assumption is that most of the data people need will be there. Not sure how easy that would be. Definitely not the case in my company. A slackbot that does pretty much what you are describing is this one https://butter.ai/ https://butter.ai/. Haven't tried it yet though but seems promising.
- sheraz 10y agoI think that assumption needs to be tested. For this particular company it would seem that there is a lot of duplicate and triplicate questions that get floated. And let's not forget about developer on-boarding into enterprise products with lots of technical debt! New devs can benefit greatly from reading threads that rationalize what _seems_ like a bad decision but is reality works well for a number of non-technical reasons...