#killer robot interface

Strive for consistency.

Try to make it so the user knows what to do because they’ve seen the same situation before throughout your interface.

 Enable frequent users to use shortcuts.

This is especially valid for users that use the interface on a regular basis. Somethings to consider might be, abbreviations, function keys, hidden commands and automated actions.

Offer informative feedback.

For every action that the user does, there should be some sort of feedback, either good or bad. For more frequent and minor actions the response can be minimal. For infrequent and major actions the feed back should be more substantial.

Walk user through more complicated tasks.

When you have an action that requires several steps, be sure to separate it into a logical beginning, middle and end. After each step be sure to give feedback that will clarify that the step was done correctly and they can move on to the next step. At the end of all the steps be sure to let the user know that they are completed and that they have finished all the requirements.

Offer simple error handling.

As much as possible, design the system so the user cannot make a serious error. If an error is made, the system should be able to detect the error and offer simple, comprehensible solution for handling the error.

Permit easy reversal of actions.

Give a way for the user to undo an error. This will help keep the user at ease if they know that not everything has to be perfect. This will encourage further exploration of your interface. You might want to place an undo feature when dealing with a single actions, a data entry or a complete group of actions.

Make the user feel in control.

Experienced users always want to feel like they are in control of the system. Make sure the design makes the user feel in control and not just responding to a situation.

Keep it simple

People have a limited short-term memory. Having to keep track of several things at once can leave a user frustrated or incapable of using your interface. Try and consolidate multiple pages, reduce unneeded motion, and generally just keep things simple. This will go a long way to help your user’s frustration level.

                     In the killer robot, the developers should've gave preliminary verifications about the UI and in handling the robot to the testers so that possible accident may be prevented. And safety protocols must be followed first by the testers so that if ever accident happens, at least they are properly protected to any equipments they have. Not only did the system allows numerous opportunities for error, but when an error actually occurred, it was something that was not likely to be repeated. From the part of the UI designer, he should've made the UI very informative for the product they are creating will be used in real time application and since it is a robot, it may also harm people due to its physical components.

“If you build the guts to do something, anything, then you better save enough to face the consequences. Actions always have consequences”