Live data from Hacker News

What to do when employees quit

groovehq.com

1–10 of 61 posts

Re: What to do when employees quit

#2
As good as slack is for communicating I don't think it should be used as a "knowledge" store. At a previous employer I found that commit messages were a great way to store information. Maybe commit messages aren't as great for question and answers, but searching slack doesn't seem very intuitive.

Idea: A slack bot that searches for questions and answers and creates a wiki out of the scraped information.

Re: What to do when employees quit

#3

As good as slack is for communicating I don't think it should be used as a "knowledge" store. At a previous employer I found that commit messages were a great way to store information. Maybe commit messages aren't as great for question and answers, but searching slack doesn't seem very intuitive. Idea: A slack bot that searches for questions and answers and creates a wiki out of the scraped information.

What's really great is when you go back in the Slack history from the day you interviewed and see what people said about you... I imagine that can sometimes be awkward.

Re: What to do when employees quit

#4
post #3

As good as slack is for communicating I don't think it should be used as a "knowledge" store. At a previous employer I found that commit messages were a great way to store information. Maybe commit messages aren't as great for question and answers, but searching slack doesn't seem very intuitive. Idea: A slack bot that searches for questions and answers and creates a wiki out of the scraped information.

What's really great is when you go back in the Slack history from the day you interviewed and see what people said about you... I imagine that can sometimes be awkward.

Private email should always be used for chatting about potential hires, instead of Slack.

Re: What to do when employees quit

#6
post #3

As good as slack is for communicating I don't think it should be used as a "knowledge" store. At a previous employer I found that commit messages were a great way to store information. Maybe commit messages aren't as great for question and answers, but searching slack doesn't seem very intuitive. Idea: A slack bot that searches for questions and answers and creates a wiki out of the scraped information.

What's really great is when you go back in the Slack history from the day you interviewed and see what people said about you... I imagine that can sometimes be awkward.

sounds like they are using it wrong. user error.

Re: What to do when employees quit

#9
This part is key:

> Take the time, on a regular basis, to talk to your employees about their lives, goals and challenges. Ask them what they hope to accomplish, not just in the next week, but in the next year, five years and ten years in their careers. Listen intently to what they say, and think about how you can help them achieve that. And then act.

Anyone who asks me those questions will get double the loyalty out of me - they'll know before I even think of going elsewhere. I've been at way too many places that just don't give a damn, or assume that people will look out for themselves. They will, but probably to another place. But if you want them to be dedicated and loyal to working for you you need to get out in front. Solve the little problems before they become big ones, or lose your best employees (who can easily get a job elsewhere) and let your companies morale and productivity die.

Re: What to do when employees quit

#10
You can document institutional knowledge and try and make sure nobody is indispensable but ultimately you will still take a huge blow.

You should focus most of your attention on improving retention.

I left a full 200 page notebook full of product ideas/customer notes/requirements/designs when I left my last job. Hopefully it helps the team but it is only in note form and completely unordered. More likely they won't look at it and the knowledge will just be lost.

Post reply on HN