The reasoning will go, yes we are losing $1 on every automated transaction, but we can make more of them, and we certainly avert one $10,000 corruption case and one $100,000 case where we get sued for human decision.
You can't sue machine learning algorighm (that how it would go). But human, you can, even frivolously.
(I am one of the researchers mentioned in the article.)
"Joe, why did you fire Carla?"
"She was late to work every other day and spent all day on her phone"
"HR-bot 5000, why did you fire Carla?"
"Weights indices 59738, 837, and 28836 added to over 0.67, yielding a score of only .85, which is below the firing threshold"
Certainly you could look at the input data and try to convince a jury that her performance wasn't acceptable but you can't prove that is why the AI fired her.
The reason developers got fired is because of clear and well-defined rules... that were never enforced except when the decision to fire them for an arbitrary reason had already been made.
I think HR-bot 5000 would treat employees more equitably by forcing employers to confront the inequity of some HR regulations. The same way self-driving cars "drive weird" because they stop at stop signs and drive the speed limit.
There will be protocols for sensitive areas.
Can't do the same with individual decision making.
The problem is that the end weight distribution is different than the GB's or TB's of training data. How do we know the training was fair and impartial? How did the trainers even know if it was? What biases crept in on this stage?
Worse yet, what if the bias of the black box does denigrate black people... Say, we take in all pictures of convicted criminals- it's disproportionaly black. I would argue part of that is because of inherent policing biases, but that's embedded in "guilty" verdict. Who's at fault for this "bias"? Is there a fault? How do we detect, other than exhaustively?
I'm eagerly awaiting for methods to "open up" ML black boxes and see what makes them tick. See their decision trees, their neural weights. I want to poke and prod to see what's behind those series of numbers like [.888271829 1.10999292992 37.999999921 1000.32 .73] . Right now, it's shove data in exhaustively and hope for the best. I don't particularly care for that way of analysis.
Much domain knowledge is in some sense innate or even subconscious, picked up in the field. I think it would be more efficient just to spy on people’s thoughts (and work) in some manner if there is a fear they could misapply their knowledge or leave a critical process hanging.