Too often developers excuse horrific processes and user experiences to "getting things done," or commonly the lack of a user interface design is excused with a weak contrast of consumer and industrial - after all, you only design an interface for flashy consumer gimmicky software and instead you should dump your industrial and business interfaces on users from a-high (akin to a pigeon shitting on your shoulder).
Most of our control work is fixed within the SCADA and networking of plant systems, so more often than not, we're involved with designing interfaces that control large motors, pneumatic actuators and quite often high pressure steam. And yet the portfolio of products designed for this industry isn't frankly good enough to automate a kettle. As a result, we've had to work outside the box and draw from our years of experience building enterprise-grade systems (both hardware and software), to distill what's expected at the high end of IT and deliver it to the field (quite literally).
And yet it's a struggle to convince people that a rainbow colour screen with randomly placed information, weird animations that are linked to unrelated attributes and all running on a crapped out consumer Windoze PC is not the high of industrial automation.
It does frustrate me that more time and effort is put into the graphics and displays seen on films, then are ever put into the real-life counterparts. For what it's worth, we're trying to change this and introduce a level of user experience that matches the serious nature and importance of the systems involved.
For now, I'll leave you with these first class UX/UI designers:
Post a Comment