Of course there are human factors involved in this error. I would put it to you that this part of the accident chain is purely human factors related, as opposed to a technical issue.
I was suggesting that there were two points that the error could have been "trapped", on entering the ZFW figures into the Laptop and on entering the V speeds into the FMC.
Surely one of the issues with this is that by bugging the speedtape through the FMS unless you are on the ball it is quite easy to enter an erroneous figure, ie one which the laptop says is correct but logic says isn't. Thus on takeoff the Rotate call will be made parrot-fashion without the usual, expected climb out.
Would things be any different if they were on old-fashioned steam-driven instruments, ie clockwork ASI with manually set bugs ? Maybe the picture would then have looked completely wrong, wrong enough to have been "trapped" before departure.