to some extent this is inevitable. people die, people quit, people take vacations, get pregnant, whtaever. the show goes on. you need succession plans.
> VIP workers being treated fairly
admittedly management chronically forgets to include many hidden costs.
some of those errors are well documented by now (they tend not to include the cost of onboarding, familiarizing someone to the environment, whatever "duct taping" [graeber] that person does, knowledge taken when they leave)
i'm not sure where in all this really addresses the concept of iterative systems in an engineering sense. toyota is a famous case of such an iterative system: the plant convenes once a month to pick a metric to improve and a strategy to do it, and then re-convences later to see if the plant runs better or not.
i would put them to a competency test and randomly pull a passing subset to be trial by fired live and then either dumped or kept on probation. the general HR method doesn't seem to be worth anything.
@icedquinn@7666@nyanide the hiring process itself is an iterative system whereby a unit is brought in and evaluated and repeatedly re-evaluated via the performance process. It should be obvious to you that the hiring process is iterative. If you were to implement it in python yourself you'd obviously use an iterator that iterates over the set of applicants, passing one forward into the performance analysis iterator on successful hire and rejecting the applicant (potentially back into the applicant pool) on failure
@7666@icedquinn@nyanide@s8n check out how microsoft does it, they rank performance according to several metrics and then they fire the bottom several percent, no matter what the performance distribution is or how well the average was, etc
@anemone@7666@s8n@sun@nyanide barrows-wheeler is one of the companies where they try really hard not to fire people. they invite you to transfer to another department or take training courses, or try to find you a new job somewhere else, unless you are actively sabtaging workers
@sun@icedquinn@nyanide@s8n yes this is known as stack ranking and all it does is make everyone fight each other. hunger games for the workplace.
“If you were on a team of 10 people, you walked in the first day knowing that, no matter how good everyone was, two people were going to get a great review, seven were going to get mediocre reviews, and one was going to get a terrible review. It leads to employees focusing on competing with each other rather than competing with other companies.” - an actual former Microsoft employee
It's not an iterative system because you iterate over the array of applicants, it's an iterative system because you keep improving it through iterations until you are satisfied with it.