- Taschenbuch: 368 Seiten
- Verlag: New Riders; Auflage: 01 (1. April 2003)
- Sprache: Englisch
- ISBN-10: 0735712506
- ISBN-13: 978-0735712508
- Größe und/oder Gewicht: 17,8 x 1,9 x 22,9 cm
- Durchschnittliche Kundenbewertung: 4 Kundenrezensionen
- Amazon Bestseller-Rang: Nr. 1.730.631 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
Information Architecture: Common Sense Guide (Voices (Smart Apple Media)) (Englisch) Taschenbuch – 1. April 2003
Dieses Buch gibt es in einer neuen Auflage:
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
All web sites have an architecture, whether you design one or not-just as every building has an architecture, from the lowly shanty by the railroad track to Chicago's tallest skyscraper. Unfortunately, most web sites are shanties, not skyscrapers. Companies that hastily threw up a web site in the dot-com boom days were visited by building inspector Jakob Neilsen, who told them their site should be condemned. But now we are entering a time of rebuilding, and we've got a chance to get it right. Information Architecture: Blueprints for the Web introduces the core concepts of information architecture: organizing web site content so that it can be found, designing web site interaction so that it's pleasant to use, and creating an interface that is easy to understand. This book will help designers, project managers, programmers, and other information architecture practitioners avoid the costly mistakes of the past by teaching the skills of information architecture swiftly and clearly. Use this book and you will pass the usability inspection with flying colors!
Über den Autor und weitere Mitwirkende
Christina Wodtke has been an information architect for four years and is a leader in the growing field of information architecture. She founded Boxes and Arrows, an online magazine of information architecture; chaired the fourth annual ASIS&T summit on information architecture; and has spoken on the topic of information architecture at conferences ranging from Seybold to Web World. Christina is a partner at Carbon IQ, a user-experience agency in San Francisco, where she designs information architectures and conducts user research in the quest to create more usable, effective, and profitable products. Clients have included Shockwave.com, Wells Fargo, Sprite, and Houghton Mifflin, as well as nonprofits such as BraveKids.org and UrbanSchool.org.
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Another thing that seriously degrades the focus is what I see as a shameless attempt to make the book thicker by including non relevant material. On pages describing the organizing of content she manages to use up half a page with a picture of her husband with the caption "Looks cold, doesn't he?".
She could also have spent more time organizing the book's content. With chapters named "Making It All Up, Writing It All Down", "All Together Now" and "Eat Me, Drink Me, Push Me" it is impossible to navigate in, impossible to look for some kind of principle behind the organizing of the content.
The book should have been called "Site Development: IA, Design and Usability for the newcomer".
The reader is directed to carefully plan the Web site, to commit it to paper first and to do a prototype which should then be shown to others for their input as users.
All this is fine. But she seems to thumb her nose at credible usability experts (while not naming them one senses one is Jakob Nielsen) by attempting to prove that the rules don't really matter all that much.
That would be obvious when you visit her personal Web site, ... You'll find locating links a considerable task.
I am sure she's very professional and very good at what she does. But this book did not speak to my desire to better understand usability and information architecture in a manner that I could adapt to my own work immediately. It was more of a survey of IA.
I much prefer the work and exhaustive studies of Jakob Nielson and others who provide workable ideas that have proven themselves over time. The author of this book doesn't seem to hold with their findings. And indeed, one must know the rules and then set about to improve on them. So I have no argument with her here.
My argument is that she puts no stock in the "rules" yet she fails to offer any alternatives. Had she done so, the book would have been a breakthrough read. It was not.
Susanna K. Hutcheson
Owner and Executive Copy Director
- Design for Wayfinding
- Set expectations and provide feedback
- Design ergonomically
- Be consistent / consider standards
- Provide error support (Prevent, Protect, and Inform)
- Rely on Recognition rather than on recall
- Provide for people of varying skill levels
- Provide contextual help and documentation
While the illustrations that drive home the subject matter can be a little clipart-ish at times, the concepts are presented in a non-technical and non-jargon based way. Each topic is explained clearly using an outline / numbered bullet format to ensure that each section can be clearly understood independently and collectively. Items such as `Who are the users?' may seem trivial at first, but imagine how many interpretations of `who are users' exist with an organization and the problems that arise when the user begins to morph throughout the product lifecycle. Wodtke and Govella decompose several non-obvious items such as persona creation and navigational types (structural, associative, and utility) into chunks that are comprehensible (Hrair Limit). I was genuinely surprised to find a section for Social Architecture which exposed me to topics such as Kurt Lewin's formula for understanding human behavior and the elements of social architecture: identity + elements, relationships + elements, and activity + elements.
The book can be read from cover to cover, if time permits. However, most of the world will probably use this book as a reference guide for completing IA related tasks as they arise. I would strongly recommend that all aspiring and current IAs give the book a once over to spawn new thoughts about the discipline or to renew the interest in keeping things usable and findable.
Given that she claims that "yes, it's a short book" (false modesty at 350 pages?) it's surprising to notice the number of digressions - into some pretty lame issues, perspectives and tips:
- How she got the idea of writing a book.
- What the book is not about.
- A 30 page discussion of guidelines she does not support.
- A comprehensive guide to the pros and cons of different ways to draw people, e.g. stick people.
- A note that you need a big notebook or a whiteboard and some markers if you want to do some topic mapping.
- A tip that when receiving guests you might break the ice by asking if it was easy to find the way.
Actually, I learned quite a few things by reading this book, but I call for the editor to wake up and give Wodtke some decent advise if she decides to go for a follow up. Any half decent editor could take a hundred pages out of this book in an hour, ending up with a much better read.
So, overall I'm rating this four stars as a good overview of Information Architecture. They manage to cover a vast and advanced field in a reasonably sized space. They do it pretty well, considering. I don't regret the purchase and I do recommend it for the beginning / intermediate user.
I can't help but see the irony in the presentation. ie ... in covering the subject matter that concerns itself with the science and methods behind classifying information simply and clearly for human consumption?:
The book is all over the map.
Headers for key subjects are not always clear, simple, and consistent at all. Key concepts that are essential to understanding a core subject - are at times buried in colloquial verbiage that serves more to make the subject more confusing that it should. At times I expected the authors to throw in little smiley faces and cute picture of puppy dogs and flowers to make the subject less intimidating and more appealing.
Not necessary - simplicity and clarity are the hallmarks of good IA, and in trying to make the book 'feel' more friendly, they break the rules inherent in what they are trying to teach you to do - and what not to do. In doing so they make it more difficult to learn, and harder to find what you are looking for ... which is exactly what they are trying to teach you not to do!
Like I said: 'Blueprints' is so ironic that it inspired me to take the time to write and post this review. In addition:
The authors are associated with an IA site called 'Boxes and Arrows'. I took a look at the site and my first impression was that it was way more difficult to navigate and understand the hierarchy than it should be: especially for an IA and content management career site.
Then - at one point in the book - they address this. They discuss a redesign of the site that will make it easier for users to find what they are looking for, and get involved with the site.
But the work was never done on the site! It's an IA site, about the field of making information clear and findable, that is not clear and the information is not findable. And they discuss this in the book that they wrote about learning good IA. Then ... they never implemented the fixes they discuss as an illustration in their own book!
Huh?? I am laughing right now because I find irony very funny :) Especially when its so cool and circular like this is. They do seem like nice people and I did get a lot out of the book however. With a bit of tweaking a new edition of the book could be a whole lot more effective (and fix the damn site!!)