Why Do We Do What We Do?

Whether the user is a worker using an office application, or a programmer using a development tool, the person at the computer is the user. And to the user, the interface is the software. A less-than-usable front-end can totally scuttle a brilliant back-end design. Most of us have seen this many times. But why?

Expectations

Users have always been filled with expectations. In the past, they wanted features, bells and whistles. Today they want access and usability. Yesterday's innovation can be tomorrow's expectation. But users always expect software to look the way it works, and work the way it looks.

Innovation vs. Standardization

All too often, innovations are introduced because they are possible, not because there is a need for them. This is innovation for the sake of innovation, and it is unnecessary. Users are forced to learn new paradigms without benefit. It is unfortunate that so much software eschews standardization and denies users the opportunity to leverage off their accumulated knowledge, experience, and previous learning. Standardization enables users to learn more easily and rapidly, and become more productive sooner while requiring less support.

However, if an obvious or discoverable innovation enhances usability and productivity, we are obliged to implement it, regardless of the rules it breaks. Here, users don't miss a beat, and the benefits are great.

Memory Management

No, not RAM. We're talking about human memory management here. With Windows and Web applications getting more complex and sophisticated, remembering all their details becomes more difficult. Usability becomes more important every day. As designers and developers, it is our responsibility to make software easier to use.

Psychological Impact of the User Interface

Every little detail in a user interface is important. Users notice the details subconsciously. Attention to details instills user confidence in a program. A typo starts the user wondering if the program is calculating correctly or generating accurate reports.

GUI Does Not Equal Usable

And, just in case you were wondering, just because it's GUI, doesn't mean it's usable. Not all applications need a GUI. Graphical elements have the potential of wasting system and human resources, increasing download times, and not enhancing productivity.

Note: This page is part of a text-only, scaled-down version of the main GUIguy web site which is located at http://guiguy.com. The reason for creating this mini-site is so that people with disabilities and people with older browsers could still learn about the GUIguy and his company. This message will be near the end of each page in this mini-site.

Home

What We Do

Why We Do It

Who is the GUIguy?

Clients

Training

Accessibility

Contact Us

 

Main Site

Copyright

Hosting

Site Update Notification

Privacy Policy

Terms of Use