Practical Information Architecture: A Hands-On Approach to Structuring Successfu

Eric L. Reiss

  • 出版商: Addison Wesley
  • 出版日期: 2000-11-09
  • 售價: $1,240
  • 貴賓價: 9.8$1,215
  • 語言: 英文
  • 頁數: 192
  • 裝訂: Paperback
  • ISBN: 0201725908
  • ISBN-13: 9780201725902
  • 相關分類: 資訊架構 Information-architecture
  • 下單後立即進貨 (約5~7天)



Structure enterprise Web sites for maximum success -- one step at a time!

  • Initial planning, mechanics, fine-tuning, and beyond.
  • Easy-to-read and jargon free-no experience necessary.
  • The first practical information architecture guide written by a practicing architect and content provider.
Web users simply will not tolerate sites that are poorly organized, or make transactions difficult. Bad information architecture costs money -- but quality information architecture can deliver powerful competitive advantage. Practical Information Architecture is the very first, step-by-step handbook designed to guide readers through the entire process of creating and implementing an underlying structure for a website --from initial goal-setting to final production --so the site effectively communicates their ideas, promotes their services and sells their goods. Eric Reiss starts by reviewing the initial planning considerations associated with effective Web site information architecture, including the identification of key business objectives. Next, he walks through organizing the site's content and creating a first-draft structure; then fine-tuning the structure to reflect ongoing feedback and an increasingly deep understanding of how the site will actually be used. For every Web architect, developer, designer, and site owner; and for marketing professionals, consultants, and anyone concerned with the effectiveness of Web sites.

Eric L. Reiss currently heads the creative staff at the Cross-Border Communications business consultancy as information architect.

Back to Top

Table Of Contents

About This Book.


1. Setting the Scene.
Defining Information Architecture.
We All Learned The Basics Long Ago.
Who Needs to Know?
So Who Is the Information Architect?
What Skills Are Needed?
Size Doesn't Matter (Much).
You Have Both a Product and a Customer.
About Common Sense.
Structuring a Website Can't Be Learned in a Linear Fashion.
Heard All This Before (A Note to Experienced Information Architects).
Defining a Few Terms.

2. Defining the Task.
A Brief Introduction to the Site Development Process.
Setting Your Goals.
New Direct Sales Channel.
Streamline Existing Sales Routine.
Reduce the Need for Live Sales and Service Reps.
Reduce the Need for Pre-Printed Documentation.
Create Web Presence for Lead Generation.
Build Better Customer/Investor/Press Relationships.
Rescuing the Service Sector.
Keep Your Main Goal in Focus.
Defining Your Target Audience.
Chicken or Egg: Goals or Audience?
Goals and Audience Must Be in Harmony.
Don't Take Goals for Granted.
Your Target Audience Also Has Goals.
Researching the Organization.

3. Measuring Your Success.
Measuring Time and Money.
And When You're Up and Running … .
Customer Satisfaction Surveys.
Cannibalization of Existing Sales Channels.

4. Defining the Content.
Information Chunking.
Wish Lists.
A Structure Starts to Develop.
Role Playing.
Retain Your Primary Point of View.
Reviewing Competing Websites.
Teamwork or Lonely Nights.
The Post-It Technique.
Process or Outcome.

5. Providing Useful Services.
User Experience and Online Brand-Building.
The Battle for Share of Mind.
Why People Visit in the First Place.
Why People Come Back.
A Review of Basic Computer Capabilities.
A Note to Technically Minded Readers.
And for Everybody Else.
A (Very) Short History of the Computer Revolution.
Make Your Product the “Hero.”

6. Ensuring Successful Online Sales.
Building Shared References.
Putting Things in Perspective (Literally).
… and Figuratively.
The Shared Reference Test.
Establishing Trust.
A Few Common Tricks of the Trade.
The Ebay Feedback System.
Keep the Sales Process Moving.
Keep It Simple for Users.
Objections to Online Sales.
Different Prices from Market to Market.
Prices Vary from Customer to Customer.
Not All Products Are Available in All Markets.

7. Deciding on the Type of Site.
Generic Types.
Functional Sites.
Topical Sites.
Generic Techniques.
Multi-Target Sites.
Associative Sites.
Generic Styles.
Newsletter Sites.
Image Sites.
Tile Sites.
Traditional Sites.
Search Sites.
Hobby Sites.
Evolution on the Web.
On a Related Note … .


8. Putting Together the First Structure.
What You Want to Accomplish.
What Are You Going to Put on the First Page?
Getting Started.
Menu Length: The Myth of “Seven, Plus or Minus Two.”
So What's the Proper Number of Menu Items?
Sets of Menu Items and Completeness.
Developing Homogeneous Systems.
An Example of Main Page and Menu Considerations.
Wide and Narrow?
Good Structures Are Invisible.
One Step at a Time.
Structuring from the Bottom Up.

9. Getting It Down on Paper.
Post-Its — Again.
Written Outlines.
Electronic Applications.
Numbering Systems.
Making Notes About Specific Content.

10. Calling Things by Their Right Name.
Speak Your Audience's Language.
Be Consistent.
IA Snafus.
Eliminating Doubt.
Improving the Scent.
Cute Labels.
The Graphic Designer's (I)Con Game.
You Can't Brainstorm Labels.

11. Structuring the Lower Levels.
The Pros and Cons of Shell Structures.
Ensuring You Have Editorial Content on Each Page.
Levels of Detail.
Visitors Should Be Able to Anticipate Levels of Detail.
Optimum Editorial Content Length.
One Final Note.

12. Getting the Most Out of Hyperlinks.
Contextual Navigation.
Dynamic Billboards.
Getting Lost Through Hypertext.
Visitors Like Hyperlinks.
Orphaned Subsites.
Avoid Run-On Hyperlinks.
Short Links.
Orphaned Links.
Splashes and Other Eyecatchers.
Recommended Reading.

13. Adding Secondary Features.
Home (Main Menu).
Site Maps.
Site Indexes.
What's New.
About This Site.
First-Time Visitors.
Frequently Asked Questions (FAQs).
Quick Links.
Search Engine Options.
Typical Search Engine Problems.


14. Refining the First Structure.
Input from the Team.
Reviewing the Structure.
Navigation and Links.
Individual Pages.
Goals and Growth.
A Final Note.

15. Building a Subsite.
Typical Subsites.
When Do You Need a Subsite?
Accessing the Subsite.
Reusing Information.
Reusing Design and Navigation.
When to Create New Design and Navigation.
Adapting Existing Information from a CD-ROM.
Guided Tours.
Providing Real Value.

16. Talking to a Specific Audience.
Building One-to-One Relationships.
Creating a Depth-Segmented Sites.
Advantages and Disadvantages.
Profiled Subsites.
Advantages and Disadvantages.
Asking Questions.
Advantages and Disadvantages.
Adaptive Navigation.
Advantages and Disadvantages.

17. Moving on to the Production Phase.
The Production Phase.
Where Designers and Architects Clash: Labels.
Working With Content Providers.

18. Testing the Usability.
What It's All About.
Heuristic Evaluations.
Testing With Pencil and Paper.
Testing a Simple Navigational Interface.
Testing a Structural Prototype.
Testing a Complex Navigational Interface.
Full-Blown Beta-Testing.

19. Looking Forward.
The Advent of WAP.
What Is WAP.
What Can WAP Do?
How Does WAP Work?
Why Surf on a Five-Line Screen?
What's the New Role of the Information Architect?
The Death of the PC?
The Future of Traditional Websites.
Easier Content-Management Interfaces.
Better Electronic Tools for Information Architects.
Better Window Shopping.
The Value of External Links.
More Effective Use of Metadata.
Keeping Websites Legal.
Increased Emphasis on Personalization.
A Final Thought.

Appendix: Sample Editorial Content Forms.
Further Reading List.

Back to Top