4 ms·
I'm actually shocked that so many companies handle performance improvement and coaching so badly. We implemented a coaching system for our support team about a
by csydas 4y ago
I'm actually shocked that so many companies handle performance improvement and coaching so badly.
We implemented a coaching system for our support team about a year ago with the explicit purpose that individual coaching does not directly affect KPI, and that as much coaching can and should be done freely without worry of impacting the support team. The system tracks both the person being coached and their team lead who does the coaching. The coaching is directed to be as instructive as possible, that it's not about punishment, but better ways of handling specific technical situations or adherence to the support policy.
Long term reviews consider not just the person being coached, but also the leader as well, as a high number of coaching options across multiple persons on the same team would suggest an issue with the leadership as the root cause, and more qualitative reviews focus on that element as well. The entire point is to ensure that Performance Improvement Plans don't have to be a thing, and that there is constructive feedback flowing into the system.
Adoption was slow, but with strict adherence to what a coaching instruction must include, we've seen exceptionally high improvement and much calmer conversations when mistakes are made since the support persons realize "this isn't a KPI penalty or a PIP; it's just trying to prevent that." Having the system "open", i.e., the support persons can see every entry they have at any time with a few clicks of a button means no secrets.
It's a lot of documenting, but so far we're seeing a ton of success with it and positive feedback to having this process for constructive criticism, and the focus on also considering "this might be a leadership issue" also helps add some comfort.
- galangalalgol 4y agoI've seen this work well, especially with some flexibility. Had a very dramatic underperformer on a team that sat near me. His lead went down every paperwork rabbit hole to get him fired, and the improvement plan was the last step. He simply couldn't knock out a simple backlog item without a lot of help. I'm not sure how he graduated with a degree. But the improvement plan had him doing some ops work as well as development, and low and behold he was a natural born ops wizard... It all made sense to him. Had never heard of k8s or helm and was spitting out helm charts, docker files, conan files etc. in less than a month, burning down the whole teams ops backlog.
- andrekandre 4y agothats a really cool story, and i think that may be true of a lot of oeople who end up fired: they just didn't find (or weren't placed in) a position where they can shine with their talents... maybe some places are too quick to fire...