Having development conversation = layoff? Or is development a routine check-in topic this time of the year? Thank you.
8 replies (most recent on top)
Agreed with being careful in terms of trust. Trust at your own risk…
They will rank everyone, which management calls “rack and stack” and then use that forced ranking to make layoff decisions.
Every check-in, every review will become and can become an excuse to get rid of you. Things have changed to be very negative. You cannot and should not trust anything your manager tells you. EMG tells me to tell my team things, words to use, etc. It's a dog-eat-dog situation. While the Manager/Director is told what to say, they are documented and can be nailed. You cannot trust anyone at USAA unless you are their favorite child.
This is normal for this time of year. We are now doing quarterly development "check-ins". Not a big deal.
I’ve always had development conversations with my people. But focused on the conversation and making sure the plan made sense for what their goals were and what their gaps were (soft/technical skills). I’d encourage them to self-document.
This year is. Different.
I’m working 70 fu----g hours a week. I bring my laptop on PTO. These aren’t humble brags and NO it’s not me hoarding work. There’s no backfills.
When and how in the fu-k am I supposed to add “development” on top of this insane workload? How? When?
I have a black belt. Agile certs. Product Management. Toast Masters. CAMS. CFE. CRCM.
Plus 80+ compliance courses and a dozen OneSource learning courses from my boss.
When?
How?
Not routine. Hyper focus on the documentation and tracking weather you meet all of your development items.
There’s never been this much focus before / rigor before.
Leaders have never had so much structure required for documentation and training on how to have these conversations.
When there’s SO much focus on documentation (in OneSource) vs. focus on the quality of the development or just having the conversation. That’s a red flag (for me).