4 ms·
I don't have HR or management experience, but I can speculate: - an employee avoids sharing key technical information with colleagues, either verbally or writi
by shoo 4y ago
I don't have HR or management experience, but I can speculate:
- an employee avoids sharing key technical information with colleagues, either verbally or writing anything down, and becomes a bottleneck for all changes relating to some system or component. this could be adapted to maximise tenure at a previous org that had decided to outsource/"offshore" technical roles, where sharing key knowledge would result in you being promptly laid off
- an employee demonstrates an extreme reluctance to estimate when any task they are involved with might be done. this could be adapted to survive in environments where estimates from individuals are interpreted politically as commitments to deadlines for unconditional delivery of work, and used to pressure workers to extract free labor (unpaid overtime)
- an employee never communicates bad news about schedule delays, plans not being feasible, designs having serious flaws, etc. this could be adapted to prior environments where voicing bad news triggers retribution, and only good news flows up the org chart
- wildrhythms 4y ago>- an employee demonstrates an extreme reluctance to estimate when any task they are involved with might be done. Ah, there are so many reasons for this. I won't give a deadline when I anticipate the requirements will change. Experienced workers can look at a planned implementation and tell management 'This isn't going to work, we're going to have to change this' and be handwaved away, because they know inevitably, after management has played out whatever fabricated 'negotiation' they've set up for themselves, inevitably the requirements will change and a new deadline will need to be established.
- deleted 4y ago[deleted]