Thanks for the high quality content! Great steps, especially about identifying the root of the underperformance. Usually it’s a result of some other stuff. People don’t have an intent to do a poor job or piss you off 😊
I do want to add that Covid changed dynamics. I don’t see people working until 5 anymore. I don’t measure work in hours but I also see less output from people in general, especially among younger folks
what about tasks that has underwater stones? do you think that managers that don't know programming will recognize that? Or another side of the issue, programmer can justify himself that tasks often has underwater stones, but it isn't true. How for manager to be close to the truth?
Good video, but you've missed one very important thing in why such situations also happen. You describe cases when an engineer is underperforming and you shift all responsibility for such cases to the executor, but this is not always true. Shifts of the engineer between teams inside the single organisation and switching managers are also one of the reasons why that miscommunication happens. New managers can have different views and benchmarks for engineers and this is definitely not an engineer's fault 🙂 Those PIPs and discussions of performance can demotivate engineers by highlighting performance issues that are not always valid. So the main piece of advice for the engineers who face similar situations is not to take it very seriously unless you see proofs of "consistent underperformance", understand why it happens, and see that the manager is ready to help you fix them and not only leaving you with that bad feeling and then checking the status of PIP. Maybe your organisation and manager want to transform your way of working to the manner they like and this is not about performance. Or they just want to find a formal reason to say goodbye to the engineer. I personally saw many examples of such PIP-s, this is not just a single case, that why I found it useful to share
🎉🎉❤
Please share your approach on how to create a safe environment for feedback for the whole team, not only for individuals during 1-1
Thanks for the high quality content! Great steps, especially about identifying the root of the underperformance. Usually it’s a result of some other stuff. People don’t have an intent to do a poor job or piss you off 😊
I do want to add that Covid changed dynamics. I don’t see people working until 5 anymore. I don’t measure work in hours but I also see less output from people in general, especially among younger folks
Діма, ви супер! Keep going! І не звертайте увагу на ці коментарі! Щиро дякую за контент!! 🔥
Thank you for the video, I’d be curious to watch video about micro management since it’s awkward topic, but is happening often
What's an average timespan for performance improvement plan to be finished? Is it a month, or a few weeks? 🤔
industry standard is ~ 90days
What's the average employment time 🤔 I'm guessing this pays off if you have people working at least 2.5-3 years in company on average 🤔
Dima - it's amazing :) Keep making such educating content!!
what about tasks that has underwater stones? do you think that managers that don't know programming will recognize that? Or another side of the issue, programmer can justify himself that tasks often has underwater stones, but it isn't true. How for manager to be close to the truth?
🔥
Having this exact problem with my reports now.. frustrating
How do you address a developer who doesn't fit the company culture and consistently puts in minimal effort?
PIP and "time to say goodbye" if person does not want to put efforts
Чому не державною -_-
Good video, but you've missed one very important thing in why such situations also happen.
You describe cases when an engineer is underperforming and you shift all responsibility for such cases to the executor, but this is not always true.
Shifts of the engineer between teams inside the single organisation and switching managers are also one of the reasons why that miscommunication happens. New managers can have different views and benchmarks for engineers and this is definitely not an engineer's fault 🙂
Those PIPs and discussions of performance can demotivate engineers by highlighting performance issues that are not always valid.
So the main piece of advice for the engineers who face similar situations is not to take it very seriously unless you see proofs of "consistent underperformance", understand why it happens, and see that the manager is ready to help you fix them and not only leaving you with that bad feeling and then checking the status of PIP. Maybe your organisation and manager want to transform your way of working to the manner they like and this is not about performance. Or they just want to find a formal reason to say goodbye to the engineer.
I personally saw many examples of such PIP-s, this is not just a single case, that why I found it useful to share
Heloy Dmytro, senk you for this video. It was wery helpfyl for mi as a random dude, nay aй кен bi e successful manageр ін galera!
капец у тебя рязанский акцент...
i am sorry, i don't understand your language
@so_nerdy yeah, right
very Russian accent 😄
that is a most important part of the video
@MrThugws , it's Ukrainian accent 😉
@@so_nerdy скинь координати того кому акцент виявився найголовіншим висновком, маю пару дальнобійних дронів
українське IT: давайте наймемо менеджера за 3000 $ щоб він робив "Managing Underperformance" джуніорів яким платять 600$ . SUCCESS
люди погано працюють, бо шукають іншу роботу, через низьку зарплату : "Managing Underperformance"
Так воно працює всюди в ІТ, та там, де можна теоретично скинути роботу на когось дегевшого.