This is a really insightful piece, and one that any dev can relate to.
I've personally found those 5 reasons to start popping up in folks heads once the org starts pulling back on transparency and/or communication, so little doubts and wonderments creep in.
Folks who've been burned in the past by re-orgs / outsourcing / project cancelations tend to be on the lookout for "writing on the wall", which seems to appear in the void of adequate communication.
Anywho, thanks for the article! Will share it around.
Thanks! A lack of transparency enhance those reasons, but I'm not sure the questions start only in those cases. Especially the feelings of being appreciated and connected.
Hi Anton, man, I’ve been there. I had 3 people leave my team this year and 1 more will leave this month.
Each took ownership of their career and left to improve their finances, career growth, or location faster than the company would. I used to take it personally. But as long I tried my best, I’ve also learned that’s it isn’t all in my hands.
Sometimes there’s company politics that affect someone’s interest in staying and other times, people’s needs and wants change.
My tip to new engineering managers? It’s okay to code once in a while. Engineers are going to leave. You might have to take on IC work to help your team during a transition.
And sometimes you should be encouraging your best people to leave before they quit.
This happens when they outgrow the position you have for them and the best thing you can do is help them find more opportunities to grow.
In the short term you lose someone great, in the long term you've built a great relationship and a great advocate.
That's a very tough one to do, at least for me. I think that if we are creative, there are a lot of things we can do inside the company.
But I agree, sometimes it's the best way.
Couldn't agree more. In some cases they can stay in the same company, but in a different team/area.
From my point of view this is one of the situations when you show with action that you truly care about them.
This is a really insightful piece, and one that any dev can relate to.
I've personally found those 5 reasons to start popping up in folks heads once the org starts pulling back on transparency and/or communication, so little doubts and wonderments creep in.
Folks who've been burned in the past by re-orgs / outsourcing / project cancelations tend to be on the lookout for "writing on the wall", which seems to appear in the void of adequate communication.
Anywho, thanks for the article! Will share it around.
- the folks @ https://whattheportal.com
Thanks! A lack of transparency enhance those reasons, but I'm not sure the questions start only in those cases. Especially the feelings of being appreciated and connected.
Hi Anton, man, I’ve been there. I had 3 people leave my team this year and 1 more will leave this month.
Each took ownership of their career and left to improve their finances, career growth, or location faster than the company would. I used to take it personally. But as long I tried my best, I’ve also learned that’s it isn’t all in my hands.
Sometimes there’s company politics that affect someone’s interest in staying and other times, people’s needs and wants change.
My tip to new engineering managers? It’s okay to code once in a while. Engineers are going to leave. You might have to take on IC work to help your team during a transition.
Thanks for sharing Jio, great advice.
It's definitely not always in our hands, and not use beating ourself up for it.