Hacker News new | ask | show | jobs
by KoenDG 2351 days ago
That, and proper internal documentation. And if that exists, encourage people to use it.

Usually when a single person is swamped with questions by co-workers, this will be because the information isn't properly documented in some sort of internal repository.

Wouldn't be the first time I've heard it argued that this takes too much time to implement.

I'd argue that it takes far less time than fielding all those questions manually.

2 comments

That's actually a really good point. Internal documentation is severely lacking. Encouraging people to submit more questions by mail/chat would probably make it easier to build up an internal knowledge base (in the sense that I can copy/paste those questions & answers as a starting point).
Kindof like a private stackoverflow... or something else...

I've tried Confluence but without strict adherence to a set of internal rules, that can easily become a mess.

Also if the internal docs didnt work out for them they should probably update it once they figure out how to make it work.
Indeed.

My first question in these situations is: why didn't they go for the internal documentation? And if they did, why isn't that good enough?