Infogineering Processes: Layered Complexity |
|
Layered Complexity gets around the problem that you can simplify/filter too far, and take out information that the reader/listener actually wanted. How do you solve the problem of making it simple for the majority of readers, without excluding those than need to know more? Have you ever had a remote control for your TV or DVD player that had a few buttons at the top, with a door or slider at the bottom that covered most of the buttons? e.g. if you wanted to change the contrast, set the time, or something that were unlikely to use - it was probably hidden. Play, Record, the numbers 0-9... all of these were easy to get to? This is the principle of Layered Complexity - you limit the available features to the ones that your user is likely to use most of the time, while still providing the other features if they need them on a different level. This principle can easily be applied to information. Rather than giving as much information as possible immediately, just provide the basics - with a link to get more information if needed. Examples
|
|
|
|
Related Articles
You can use the links below to post this article on your preferred social networking site. To link to this site, please copy the following HTML code into your web page, blog or Social Networking page.
Title: Infogineering Processes: Layered Complexity |

