| > This is a great response Hard disagree. > accepting that it was handled poorly Technically he accepted it 'wasn't perfect'. Which is different to 'poorly' (other side of average). > reinforcing that this was purely about the person/role fit rather than the person He hinted at three reasons (without actually stating which one applies in the individual case): poor performance, lack of improvement after communicating poor performance and "poor fit". In the original video the the individual countered the first two by pointing out the fact their manager's communications to them were all positive. Additionally, they've only been "off ramp" for a month. In my experience one month is pretty short for expecting someone to improve when they're performing badly.... especially when they haven't been told they were performing badly. --- my take away: either [edit: or both] - cloudflare needed to do some layoffs, did some quick stats and didn't set limits on when people were hired when doing the stats. this person got mixed up in it as a result. - manager fckd up and didn't tell the individual they were performing badly. in which case, really bad individual management. |
> did some quick stats and didn't set limits on when people were hired when doing the stats
> manager fckd up and didn't tell the individual they were performing badly
This is even more likely when you account for Nov 20 - Jan 2 being the most likely time of the year for extended vacations (for manager, analytics, and buyers), corporate distractions (holiday parties and team building, next year planning), and a slowdown in all sales cycles.