Skip to main content

Being a forklift operator possibly leads to car accidents. An example of bad UI design.

I ran into this comment the other day on the Internets:
If you think that driving a car with reversed turn signal and wiper levers is bad, try driving a fork lift which slams into reverse every time you hit what would normally be the left turn signal.

That is not the scary part. I have known numerous forklift drivers that got so used to using the lever to switch from forward to reverse throughout the day, that at the end of their shift they would get in their stick shift car with it in first gear, start the car, turn on the left turn signal, look over their shoulder, release the clutch and drive into the car in front of them.

Life Lesson: Never park directly in front of a fork lift driver.
I'm sure there is a reason for the lever to be conveniently placed at that location, but, if the bigger picture is taken into account, this is a pretty good case of UI design that results in expensive damage to property. Car insurance providers should take a look at this scenario to see how common that combination actually is (assuming that comment isn't a troll disseminating bad information). If it turns out to be a legit issue, then raise car insurance rates for that specific combination to some astronomical cost (stick shift car + forklift operator = very high insurance rate, automatic car + forklift operator = normal rate). Or, better yet, fix forklifts so that it isn't a problem regardless of the type of car that a forklift operator drives.

The real takeaway for us developers: Just because a user interface streamlines one specific process doesn't mean that it won't cause other, more serious problems. A responsible, competent developer will take ownership of a problem and fix it. The irresponsible, incompetent developer will just ignore the problem and point the finger of blame toward anyone else but themselves.