31st
March
2000
“We define Information architecture as a systematic, question-based process for creating communication products that improve users’ performance. A system is a set of interrelated parts that work together toward a defined goal. In building web sites, you can think of the system as a methodical, structured, means for helping people find and use information. The entire system is performance-based.”
posted in Information architecture | Permalink |
31st
March
2000
“What makes for bad design is trying to solve problems in isolation, so that one particular force, like time or market or compatibility or usability, dominates.”
posted in Usability | Permalink |
31st
March
2000
“Part of the design rationale is to develop a design process that is user-centered… A design rationale should be documented to be used as a tool for expressing the foundation for the hundreds of decisions and tradeoffs that need to be made for each design instance. A design rationale is a lot like the ‘vision’ for design. While it does not answer every question for every instance of a design decision, it keeps you focused on the objectives for the site and supports the design decisions and tradeoffs that are inevitable. The design rationale also acts as a reference for developers and agencies that will develop content for a site.”
posted in Web design | Permalink |
