Skip to main content

Ooching Towards Usability

You can't design a good user interface for a product up front.

The best user interfaces do typically start with an elegant preconceived concept. But achieving greatness requires going much further than the preconceived concept. Your designers must "ooch" towards usability.

Ooching towards usability means iteratively refining the interface to:

  • Optimally place the various UI elements.
  • Deal with every possible combination of user action.
  • Recognize as many so-called "user errors" as possible and turn them into valid actions.
In many cases, ooching is inelegant. It often requires heaping kludge on top of kludge to make sure your product covers all the special cases. And you'll have little idea what the most important special cases are unless you involve users in testing the product.

For a truly easy-to-use product, expect your designers to spend 80% of their design time after developers have developed an initial functional version of the product.


Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware