- Copertina flessibile: 201 pagine
- Editore: New Riders Pub; 2 edizione (18 agosto 2005)
- Lingua: Inglese
- ISBN-10: 0321344758
- ISBN-13: 978-0321344755
- Peso di spedizione: 408 g
- Posizione nella classifica Bestseller di Amazon:
Don't Make Me Think: A Common Sense Approach To The Web Usability (Inglese) Copertina flessibile – 18 ago 2005
|Nuovo a partire da||Usato da|
C'è una nuova edizione di questo articolo:
Chi ha acquistato questo articolo ha acquistato anche
Dalla quarta di copertina
Five years and more than 100,000 copies after it was first published, it's hard to imagine anyone working in Web design who hasn't read Steve Krug's "instant classic" on Web usability, but people are still discovering it every day. In this second edition, Steve adds three new chapters in the same style as the original: wry and entertaining, yet loaded with insights and practical advice for novice and veteran alike. Don't be surprised if it completely changes the way you think about Web design.
Three New Chapters!
- Usability as common courtesy -- Why people really leave Web sites
- Web Accessibility, CSS, and you -- Making sites usable and accessible
- Help! My boss wants me to ______. -- Surviving executive design whims
"I thought usability was the enemy of design until I read the first edition of this book. Don't Make Me Think! showed me how to put myself in the position of the person who uses my site. After reading it over a couple of hours and putting its ideas to work for the past five years, I can say it has done more to improve my abilities as a Web designer than any other book.
In this second edition, Steve Krug adds essential ammunition for those whose bosses, clients, stakeholders, and marketing managers insist on doing the wrong thing. If you design, write, program, own, or manage Web sites, you must read this book." -- Jeffrey Zeldman, author of Designing with Web Standards
Steve Krug is a usability consultant who has more than 15 years of experience as a user advocate for companies like Apple, Netscape, AOL, Lexus, and others. Based in part on the success of the first edition of Don’t Make Me Think, he has become a highly sought-after speaker on usability design.
Non è necessario possedere un dispositivo Kindle. Scarica una delle app Kindle gratuite per iniziare a leggere i libri Kindle sul tuo smartphone, tablet e computer.
Per scaricare una app gratuita, inserisci il numero di cellulare.
Garanzia e recesso: Se vuoi restituire un prodotto entro 30 giorni dal ricevimento perché hai cambiato idea, consulta la nostra pagina d'aiuto sul Diritto di Recesso. Se hai ricevuto un prodotto difettoso o danneggiato consulta la nostra pagina d'aiuto sulla Garanzia Legale. Per informazioni specifiche sugli acquisti effettuati su Marketplace consulta… Maggiori informazioni la nostra pagina d'aiuto su Resi e rimborsi per articoli Marketplace.
Quali altri articoli acquistano i clienti, dopo aver visualizzato questo articolo?
Le recensioni clienti più utili su Amazon.com (beta)
Sure - the topics in this book are obvious. There's nothing here you couldn't have figured out yourself if you took the time to do so. But that's the point - Krug took the time to assemble these obvious but numerous issues for you, so you don't have to think through all of the potential problems your web site is likely to have. IRONICALLY, THE REAL VALUE OF THIS BOOK IS NOT IN ANY BRILLIANT INSIGHTS. THE VALUE IS THAT YOU ARE FORCED TO STOP AND THINK ABOUT YOUR OWN WEB SITE AS YOU READ. That is, simply by taking the time to drift through this light read, you can't help but to ponder how your own web site suffers from each of Krug's common web page problems. You'll undoubtedly end up making a number of improvements to your own site. Krug's small suggested improvements taken collectively really do end up making a big difference to your site. I made at least ten changes to the web site that hawks my own cheesy book (Web Service and SOA Technologies) based on Krug's very good advice.
Weakness #1 - The book's pace slows down at the end. I can't help to wonder if Krug was a little concerned that he wasn't going to have enough pages. Do we really need an entire page that tells us that some people are naturally less patient than others? But even at his slower pace, there are still many sentences that make you think (errr....even if you're not supposed to).
Weakness #2 - Why didn't Krug design a checklist of issues as the last page? You can't use his table of contents as that checklist since his style is to use titles that don't mean anything without reading each chapter. He needs a summary page like this:
* Is it obvious where you can click and where you cannot? Are there "hotspots" on images that are not obvious?
* If a user were to squint and look at your web page, could they discern what each area on the page was most likely about?
* Does your search capability have confusing pulldowns?
* If a user arrives at any random page on your web site (say, from a search engine), can they figure out what site they are on, what the page name is, what are the major sections of the site, what are the best options on the page, where they are relative to the other pages, and how they can search?
* Do your user's eyes have to leap all over the page in order to figure it out?
* Does any operation ever take more than a few seconds to figure out?
* Does the reader ever have to read through instructions to figure something out? (They won't.)
* Is information organized in a clear, visual hierarchy?
* Do you violate any web page conventions?
* Does your site have excessive images and flashy items on it?
* Are your pages reasonably short? (that is, not too much scrolling required)
* Does the page have any text on it that isn't absolutely necessary? (like this parenthetical note, for example)
* Navigation on your site has to be crystal clear. If the user is "looking for a chainsaw", do they know if they should look in the "tools" section or in "lawn and garden"?
* If the user makes a bad guess when navigating your site, is it easy to recover from the error?
* Do any of your pages look so different from the others that the user might be confused if they've accidentally hyperlinked off your web site?
* When you analyze your site, have you spent the majority of your time thinking only about the higher level pages (rather than the low down, leaf node pages)?
* Does every page have a unique identifying name?
* Is every page name prominent?
* Does the page name ever not match the hyperlink that was used to arrive at that page?
* Have you favored the use of navigation tabs? (Krug is a big proponent of tabs.)
* Does your home page establish the site mission, hierarchy, and search method? Do users immediately know why they should be on your site and not someone else's?
* What items appear "above the fold" on each page? (that is, without having to scroll down)
* Does the site have any current references so users know they are not looking at an old, dead site?
* Does the company have a good, descriptive tag line?
* Is it clear where the user can search, browse, and find the best your company has to offer?
* Are you aware that display space devoted to promoting one item implicitly detracts from other items on the page?
* Have you ever observed a completely new user (with no introduction whatsoever) land on your site?
* Have you made the mistake of doing no user testing at all because comprehensive testing is too expensive?
* Did you perform usability testing very early in web development, like you should?
* Did you make the mistake of giving help to your new test user during your usability test?
* Does your site blatantly omit obvious information about your company because of embarrassment? Does it conceal information like contact phone numbers?
* How quick and easy does your site service its most common request?
* How kind is your site to the vision impaired? What happens if you change the browser font setting to "largest"? Anything?
* Does every image have "alt text"?
You may think you don't need to read the book now, but remember the real value of the book is to force you to stop and think a while about each issue. You can't do that blowing through this list in 10 seconds, especially without the examples in the book.
Overall - Despite some minor weaknesses, the book is great and offers enormous value. Don't Make Me Think has been one of the best sellers in software books since August 2005 and for good reason. Krug's "Don't Make Me Think" really does warrant some thought. If you have a web site, there's no question that you should buy this book.
Author, Web Service and SOA Technologies
The idea behind usability is simple: Look at a given design and see how accessible it is for users. Anyone can have an opinion on usability and everyone can provide input. All it takes is a clear head and the patience to look at what works (or doesn't) and why. If you use it, you have information about its usability. To get back to the subjects of Computer Science and technology, usability has lately been applied to the world of Web design.
Usability consultant Steve Krug lays out all of the basics about Web usability in his book Don't Make Me Think: A Common Sense Approach to Web Usability currently in its second edition, published in 2006 after the first edition sold nearly 100,000 copies.
As far as titles go, there are few that offer as clear a picture of the book's content as this one. Krug's main point throughout his 185-page guide is that good Web sites don't make users think. Unlike college, Krug posits that using a conventional website should not be an intellectual exercise. It should be simple, it should be neat, and it should be self-evident. In other words, if a user cannot identify the site's purpose, and where to start on said site, just by viewing the homepage something has gone horribly wrong.
Krug details how to fix such problems and how to avoid them with usability tests. That may sound self-serving save for the fact that Krug also explains how to conduct usability tests on the cheap without the benefit of a usability consultant such as himself.
Written in short chapters packed with illustrations, this book is designed to be approachable and easy to read. Krug is serious about Web usability, but that in no way means his book is stodgy or dry. Examples of usability at work are littered with cartoons and the text maintains a sense of humor. My favorite chapter title (and subtitle) "Usability as common courtesy: Why your Web site should be a mensch" might offer some idea of what tone to expect from this book.
Of course, taking a computer class to meet a core requirement in college doesn't always lead to work in the field of Web design in fact most of the time it leads to an entirely different career. But, in today's technology-driven culture, doesn't everything come back to the Internet eventually?
It might just be working as an intern at an online magazine, or a starting position where duties include entering data into online spreadsheets, or it might just be writing your own blog on a site like WordPress or Blogger. Wherever your path leads, knowing something about Web usability and how good Web sites get that way can only help. As more and more information moves to cyberspace, with websites being created and updated all the time, it's important to be prepared by knowing how to analyze not only the information found online but also how it is presented. Don't Make Me Think is one tool that can assist Web users in that preparation.
I have been in a position in corporate America to manage a corporate web site since December of 2006. After some precursory research on my favorite little book store: Amazon, I came up with Krug's web usabilty book on favorite listmania after favorite listmania. "Don't Make Me Think," made it on the top list for web designers, web page project managers, business owners, and average Joes and Jill like you and me. So I wanted to start my professional reading with a book that had some common collective wisdom behind it. Lo and behold, I was not disappointed.
Krug's book is probably best read through practice. I have already spouted off several of his principles at our weekly web page project meetings and I can tell folks are looking at me a little different these days. It could be because I'm going through my mid-life crisis and started wearing a goatee and using all this metero hair product, but I don't think that's the reason alone. I suspect it's because I scanned Krug's cartoons and sent them out to the members of our working group and executive council. I love the frame that has the project manager getting caught up in a web page design "religious debate," between a creative designer and a practical programmer with a thought bubble over her head saying, "I hate my life." Funny stuff. You'll have to read this book and sit through one of the web page design meetings to see its true truth and wisdom.
Though I've learned if you try to enact some of Krug's principles like having navigation tabs similar to those found on Amazon, you just may start some religious debates of your own. The book has a little something for everyone. For the web page design and management neophytes like myself, it has to be one of the best introductions to the ins and outs of what really works on web sites for engaging Internet users in such a way that keeps them coming back for more. For seasoned professionals in the industry, Krug's book will no doubt cause you to be challenged in your thinking, wrestle with how to gain control back from your overly-busy home page, and what can now be done with all that text you were stuffing your overly boring corporate site that no one really bothers to read.
For me the book started to drag with the two sections of web site testing. But, we recently stood up a new functionality feature that was in sore need of troubleshooting testing before pushing it live. Believe it or not, designers and ad agency managers don't catch very many mistakes before letting their clients view the page. So I found myself referring back to Krug's book to see how best to approach testing. As it turned out our work team, and some family members, caught the majority of the mistakes and folks were very happy with the final product. Another thing to watch out for is that Krug is giving advice based on what works best for the user of web page sites. Some of his advice is contrary to what I've experienced in my professional life in regards to search engine optimization. Krug says to cut out extraneous and unneeded text which is all fine and good for your web page readers, but will not get your page optimized (when a person types in keywords to yahoo or google...your page hitting the top of the search results list). So, just watch for that if you are more interested in people finding your web site vs. having an optimally pleasant experience once they get there.
So, Steve Krug is my new best friend and has helped me keep my job for another month. I think if you pick up a copy of, "Don't Make Me Think," you will be thinking Krug is your best friend too, with his egregious wit and practical knowledge of what works and doesn't on Internet web sites. He even does a minor overhaul of Amazon's site. You won't want to miss it. ...mmw
The meat of this book is the approach to usability that makes it less of a "personal opinion of the highest ranking stakeholders on the project" and more of a "predictable practice with verifiable results" kind of thing. After reading this book you will have a chance not to judge usability by a vote or by a developer who was asked to build a feature.
One thing the book doesn't do is make the case that usability is important, with any significant evidence for or against. You'll have to make this choice and find support for following up on this choice by yourself.
One last thing: I happen not to like most of the suggestions for additional reading, especially for more recently published books. Start with the titles that are presented in the book, and find better ones by browsing similar items in your favorite bookstore.
I bought this book because I was working on a related problem for a consulting firm -- how to integrate research and documentation of said research. The insights from this book into how people use a computer-based system allowed me to identify what was wrong with all of the proposed solutions -- such as software designed to handle references, like EndNote. The proposed solutions were too complex, requiring too much new learning and too many steps.
In the end we saved thousands of dollars by developing a very simple set of rules for putting together an excel spreadsheet for gathering and sourcing qualitative information -- easy to open, easy to operate, everyone already knows how to use the software.
The book was most useful because I was able to wave it in the air and announce "people won't use that feature" as we discussed different options. It was an antidote to the common tendency to feel that our co-workers "aught" or "should" do their work in a particular fashion. E.g. "Since documentation is important, people should be willing to spend some time doing it."