
For example, an architect probably thinks that a doorway is used as a passageway from one room to another. But if you spend much time in public buildings, you will learn that a huge percentage of people use the doorway as a place to stop and decide which way to go. Or a place to stop and find out who or what is in the next room. Or a place to turn around and go back where they came from. Or a place to hold a conversation. Doorways often turn out to be, not entrances, but blockades. Perhaps if architects really understood this, they would make the doorways in museums, government buildings and shops a little wider. Or perhaps they would add signs reminding people to keep moving. Or windows next to the doorway so people can see the next room before they get there. And so on.
What does this have to do with software developers? If we could secretly watch our customers and potential customers as they try to navigate our websites or use our software, we might be surprised to see that what they do is often not what we expected them to do. Things that "make sense" to us because we already know how they are supposed to work may actually slow down or confuse our users. Or, like the person who just wants to peek through a doorway rather than actually enter a new room, our users may have agendas for our products, or paths through our websites, that aren't quite what we envisioned.
How hard is it for a website visitor to find out what your product really does or how much it costs? How many menu layers does a user have to go through to do the one thing he considers most important? How hard is it for someone to use your help system to actually get help? All of these things affect your sales.
[Reposted with permission from the ESC members-only newsgroup]





