http://tc.eserver.org/authors/Olshavsky,_Ryan A bibliography of works by Olshavsky, Ryan in the field of technical communication. en-us Copyright (c) 2005-08 by the EServer. All rights reserved. tclib-editorial@eserver.org (TC Library Editorial Board) webmaster@eserver.org (Geoffrey Sauer) http://tc.eserver.org/images/newlogo.gif http://tc.eserver.org/dir/Olshavsky,_Ryan http://tc.eserver.org/28316.html http://tc.eserver.org/28316.html Documentation is a crucial component of successful product planning and implementation, so it's important that it communicates as effectively as possible. Good organization, complete information, and clear writing are, of course, key to the success of any design document, but there are some other, less-obvious techniques you can use to make your documents more readable and understandable. Here are a few of them. http://tc.eserver.org/25619.html http://tc.eserver.org/25619.html Good organization, complete information, and clear writing are, of course, key to the success of any design document, but there are some other, less-obvious techniques you can use to make your documents more readable and understandable. Here are a few of them. http://tc.eserver.org/23984.html http://tc.eserver.org/23984.html Developing a new product or service is tricky. When everything goes well, the product can redefine a market or even create an entirely new one, to the benefit of its manufacturer and its consumers. When the product doesn't click with its audience, though, the costs—development, employee, manufacturing—can be staggering. How do you ensure that your new product doesn't flop? One effective method is to conduct a requirements definition phase before developing a new product. http://tc.eserver.org/23975.html http://tc.eserver.org/23975.html Let's say your development organization has embraced design as a key to creating successful products. You've devoted time and energy to creating the perfect, goal-directed design for your product. Your programmers are ready and eager to start putting that design into code. So…now what? How do you communicate your design to your development team, accurately and in sufficient detail? One approach is to produce a Form & Behavior Specification. http://tc.eserver.org/21353.html http://tc.eserver.org/21353.html While there are many fine books that go into great depth on various aspects of the information architecture and design process, 'Information Architecture: Blueprints for the Web' is, essentially, a primer on successful website design.