Dont Make Me Think Web Design Funnies
See a Problem?
Thanks for telling us about the problem.
Friend Reviews
Reader Q&A
Community Reviews
But Steve Krug makes the topic of web usability genuinely entertaing. He holds a light writing style with a touch of wit that helps to keep your attention from cover to cover. Add to that the short size of the book at only a couple of hundred pages, and the vibrant but clear layout and you've got a book
Well, this is an absolute gem of a book. I picked this up the day after finishing Beautiful Code and to be honest, really wasn't in the mood for any more particularly heavy content for a few days.But Steve Krug makes the topic of web usability genuinely entertaing. He holds a light writing style with a touch of wit that helps to keep your attention from cover to cover. Add to that the short size of the book at only a couple of hundred pages, and the vibrant but clear layout and you've got a book that's in itself extremely usable and accessible.
When it comes to the content itself, it couldn't be explained clearer. Steve's chapters are logical and concise, you won't find any waffle in here that doesn't help to communicate the message of the chapter. He uses a adequate number of examples to illustrate his points, and even helps to demonstrate how various stakeholders in web projects can all contribute to the usability of the site.
For me, the most interesting idea was of usability testing. Having led a relatively sheltered web life, with most of my work either focusing on small scale projects or internal projects, the concept of usability testing presented as a lightweight process that can be repeated at minimal cost over and over again had not occured to me. Steve presents a framework for running these sessions that elimates all excuses for usability testing to be included in a project lifecycle.
Who would I recommend the book to? Anybody with a stake in web projects. Managers should read it (on one of their first-class trans-atlantic trips), designers should read it and keep the golden rules to heart before they put pen to paper (or stylus to tablet) and programmers/developers should read it to understand the technical requirements of implementing usability. Rarely do I say a book has opened my eyes, but I think I'll make an exception with this one.
...more
Every developer needs to read it.
It makes me think deeply about usability and accessibility.
For example, after I read a chapter on accessibility, I decided to design a website that could be helpful for blind people. Its main purpose is to help us have a better life. Because we use the software more than anything else now. You are reading my review on a website or on an application. Steve Krug's style makes me have a smile on my face while reading and understand it ve a pensive book for developers
Every developer needs to read it.
It makes me think deeply about usability and accessibility.
For example, after I read a chapter on accessibility, I decided to design a website that could be helpful for blind people. Its main purpose is to help us have a better life. Because we use the software more than anything else now. You are reading my review on a website or on an application. Steve Krug's style makes me have a smile on my face while reading and understand it very well. ...more
This short and highly readable book covers topics such as: how people really use websites (they don't actually read, they like to scan and browse mindlessly… but we already knew that, didn't we?), how to design na
I read this handbook on Web usability for work related reasons. It was originally published in the early 2000's, shortly after Jakob Nielsen's Designing Web Usability. Both Krug and Nielsen have since become (along with Steve Jobs and Jony Ives, at Apple) the head honchos of Web Design.This short and highly readable book covers topics such as: how people really use websites (they don't actually read, they like to scan and browse mindlessly… but we already knew that, didn't we?), how to design navigation and breadcrumbs, etc. Krug insists on the importance of usability testing: one chapter is actually a cookbook on how to conduct user tests without getting top-heavy on the matter. This recent republication also includes a chapter on designing for mobile and accessibility.
A very enjoyable, casual (and oftentimes fun) read, that the staff at Goodreads should consider rereading from time to time: a word to the wise is enough!
Thus far, I'd say our old bookahs are still more usable than anything digital… or aren't they? :)
...more
It really is a book that can stand the test of time, though all three iterations, it keeps the tone and message: "good web design starts with instinct of the user."
Krug's book focuses on web usability, fundamentals of good design, and user experience testing. Every web designer should get their hands on this as it is a referen
Quick, thorough, and to the point, as it suggests. Even inspired me to write a review, on the web. I don't even NEED to think twice to say this was a VERY GOOD * e^3 read!!It really is a book that can stand the test of time, though all three iterations, it keeps the tone and message: "good web design starts with instinct of the user."
Krug's book focuses on web usability, fundamentals of good design, and user experience testing. Every web designer should get their hands on this as it is a reference for the mind about the mind! give it a go, it will have you thinking differently.
...more
Goodreads and LOTS of other sites should have their managment teams read this.
MUST READ for anyone with any say over the look & feel of a commercial web page (designers, managers, marketing people, executives, etc.). It's a quick and easy read and is like having my own web usability consultant.Goodreads and LOTS of other sites should have their managment teams read this.
...more
One thing this book has going for it is its brevity. Before agreeing to publish a second edition, Krug insisted upon first discovering what could be removed from the first edition so t
I was predisposed in favor of this book because it's the most-voted-for on the UX Stack Exchange. It wasn't all I'd hoped it would be. If this were the first text about usability I'd read, I might have gotten more out of it. As it was, the overwhelming majority of the topics presented seemed patently obvious to me.One thing this book has going for it is its brevity. Before agreeing to publish a second edition, Krug insisted upon first discovering what could be removed from the first edition so that no extra length would be added. Rather than writing about details of debates relevant only to people completely immersed in usability, he aims to convey the most essential concepts of the usability field as briefly as possible. In this he succeeds. The book is a clear introduction to some of the most important principles of the field. However, it glosses over them without going into depth.
Perhaps the most useful part of the book is a transcript of a sample usability test, including what to say and do at the beginning of the test. The introduction says that this chapter was abridged from three chapters in an earlier version of the book and some of the content was moved to Krug's site and expanded upon in a later book, which I am now interested in reading.
Some other (less useful) things this book says are:
(view spoiler)[
- The function of every element on the page should be as obvious as possible. Aim to make things self-evident, but make them self-explanatory at the very least.
- Expect users to skim, satisfice, and muddle through pages. Designers should make it easy to skim and make it so that users have to muddle as little as possible.
- Use a clear visual hierarchy to help users find things faster.
- Don't go against conventions unless your change brings a significant and easy-to-learn improvement.
- Assume that every element is visual noise.
- Use navigation elements not just to show people how to find what they're looking for, but also to give them a sense of where they are and what else the site contains.
- Navigation should be consistently laid out through all the levels of the site, not just the top two.
- Navigation elements (particularly those showing the location of the current page) should stick out.
- Tabs connecting to the pages below are strong navigational elements.
- All headers and labels should be clearly associated visually with the elements they relate to (framing those elements).
- Make sure that the homepage conveys the big picture. It should tell what the site is about. Use taglines rather than mottos next to site logos. (Tell what the site does, not what it's ideals are.)
- The navigation should be the same on all pages except for the homepage and pages with forms.
- Avoid the Tragedy of the Commons that occurs when too many things are added to the homepage. All departments will want homepage links, but too many homepage links will devalue the homepage. (The sections of the book about the homepage are decreasing in importance owing to the decreasing number of users actually landing on site home pages.)
- You shouldn't expect any one feature to be the best way of doing something for all users (or a mythic Average User); instead focus on whether it creates a good experience for users who encounter it in its current context.
- Focus groups are for initial planning; usability tests are for iterative improvement.
- Test early, informally, and often. This way, you can improve the product and encounter issues in later tests that weren't evident until issues from the first test were resolved.
- You can set up an inexpensive yet effective usability lab by placing a camcorder monitoring the screen in one room leading to a TV displaying the video to stakeholders in another room. Use a screen recorder as well.
- Before you have a working prototype, run tests on a couple of sites with similar features or functionality to get a sense of what works well about them.
- Be considerate of the user. Try to have their best interests at heart.
- To help make a site accessible to people with disabilities, first make sure it's usable for people without disabilities.
- Several small tweaks in the code can drastically improve accessibility.
(hide spoiler)]
- The simple language used to explain normally complex matter;
- The good humour, examples and metaphors the writer uses to explain things. They really work.
Now the bad parts:
- I find the information in the book to be a little too simplistic and common sense. Even for people with only interest on the area of web usability they may find that they already know, or at least thought in a very similar way when they browse daily;
- I understand that this isn't a scientific book and the aut
What I liked:- The simple language used to explain normally complex matter;
- The good humour, examples and metaphors the writer uses to explain things. They really work.
Now the bad parts:
- I find the information in the book to be a little too simplistic and common sense. Even for people with only interest on the area of web usability they may find that they already know, or at least thought in a very similar way when they browse daily;
- I understand that this isn't a scientific book and the author does refer to Nielsen a couple of times but all in all the knowledge in this book comes directly from the writer's mind with very little scientific sources to confirm what it's being said;
- Even the second edition is from 2005, almost 8 years have passed and most of the webpage elements he focus on the book, aren't really that used anymore. Still, this isn't the author's fault. Books age and so does the content they possess.
...more
An essential book for anyone working on websites. The book title is the main point, but Krug does a good job at explaining how to go about doing web usability well. My favorite analogy is treating a website like a well organized store (like Lowes). A person can walk into a store and easily navigate it to accomplish the task at hand. We need to make sure websites are set up to do the same.
The book lays bare the facts, that -
1. Users do not read the text in a web page.
2. Users muddle through a web page, no matter how well thought out the layout, and menus are.
And as a designer, your task is to take these two facts into account when designing your website.
The author, Steve Krug, is very perceptive. While this is evident throughout the book, what did it for me was the footnote about the Site ID being on the top
This book is what it states - a common sense approach to web usability.The book lays bare the facts, that -
1. Users do not read the text in a web page.
2. Users muddle through a web page, no matter how well thought out the layout, and menus are.
And as a designer, your task is to take these two facts into account when designing your website.
The author, Steve Krug, is very perceptive. While this is evident throughout the book, what did it for me was the footnote about the Site ID being on the top right corner in web pages with right to left languages, and his comment about inconsistent navigation options in many sites once you are two or three pages deep. The first one is a nice call-out, the second - I've been burnt by it so many times!
The section that talks about how to resolve "design" (people) problems, when members of different teams prefer one design over another, is a life-saver for any Project / Development / Product Manager. It clearly brings the focus back to the problem - are we doing the right thing for the intended users of this website?
The graphic showing what a webpage means to a CEO, Developer, Designer, and Marketing, nails each group's perspective on the head.
The difference between a focus group, and a usability testing team is explained well.
The chapters on usability testing is a must read for all QA teams. The table showing how much it would cost to do "Get it" and task-based usability testing is very concise, and useful. I would recommend taking this no-frills approach; a part of my org's development methodology.
That said, the book is roughly ten years old. The principles, no doubt, still hold good. But, it would be nice to see an updated version that talks about
1. The proliferation of social media, and how to design for that.
2. Web-based Enterprise application UI design.
#2 above is closer to home for me. Type of question that I would like to be tackled - In web based Enterprise apps that specifically deal with a particular vertical (say Insurance), how much can you assume that the user knows about the domain, and consequently, how does that affect your design?
The book is well laid out, and you can see evidence of the author eating his own dog food. The footnotes offer interesting segues (sometimes not about web usability), and the Recommended Reading section is a big plus.
It is an easy read, at a little under 200 pages - no reason your web dev team can't find time to read (and re-read) it!
...more
When I started looking for web design books, Steve Krug's classic on web usability frequently appeared at the top of most lists, along with Designi
An excellent introduction to creating usable websites. As the title states, every website's design and functionality should be so simple that people barely need to think to use it. The book's 2nd edition is from 2005, so some examples are dated, but the concepts are quite relevant. This was a fun read due to its straightforward style and Krug's humor.When I started looking for web design books, Steve Krug's classic on web usability frequently appeared at the top of most lists, along with Designing with Web Standards by Jeffrey Zeldman (see my review). I highly recommend both books.
Steve Krug's Laws of Usability
First Law: Don't make me think. Make things obvious and self-evident, or at least self-explanatory. People scan; they don't read. People choose the first reasonable option. People muddle through things rather than figure them out.
Second Law: It doesn't matter how many times I have to click, as long as each click is a mindless, unambiguous choice. Make choices mindless for ease of use.
Third Law: Get rid of half the words on each page, then get rid of half of what's left. Be ruthlessly concise.
Usability testing
Test early and often. Test with 3 or 4 users. Have each user think out loud as they use the site. Use a screen recorder to record the session for reference. Fix any problems, then test again. Review the results as soon as possible.
Additional notes
Navigation helps users find things, tells them where they are, reveals content, and tells how to use the site. It must be good enough to help people who land on any page.
The home page should have a personable, lively tagline conveying a value proposition. The home page also needs a short, scannable welcome blurb describing the site.
Know what people want, and make those things obvious and easy.
Only ask for information necessary to complete the transaction.
Only make a site look good if it's not at the expense of making it work well.
The most valuable information I found in Don't Make Me Think was the little quizzes in the middle of the book where readers are presented with sample we
The book was a short, quick and easy read that can easily be finished on a plane ride. It's in full color with a couple of helpful diagrams, but I mostly found the comics in it annoying and patronizing. A lot of what Krug brings up in the first half seems like common sense, but he does delve deeper into some points, which may be helpful for some.The most valuable information I found in Don't Make Me Think was the little quizzes in the middle of the book where readers are presented with sample websites and asked what was wrong or needed improvement. Krug walks through important aspects of those sites in a clear and concise manner. I wish that more of the book was made up of examples like those.
...more
I've dabbled in different design tools to create sample mockups for products I wished to build, but I always copied what looks good
I've been working in software for my entire professional career. Except for the past year, I've been a backend software engineer for backend code in data platforms, web apps, and operations. Throughout my years as an engineer, I've neglected studying design. It's always been the elusive facet of product development that Ive appreciated, but never come to understand.I've dabbled in different design tools to create sample mockups for products I wished to build, but I always copied what looks good instead of putting design pieces together. This year, I wanted to change my perception of design and learn how a designer thinks when working on a project. To start my journey as an amateur designer, I thought best to begin with the fundamental books about web design. That's is how I was led to Steve Krug's book, Don't Make Me Think.
I started reading it with high hopes. It began with a friendly welcoming attitude to the world of design – a world I had only experienced from the outside. With Krug's definition of usability, I learned some basic principles that I had only heard vaguely mentioned by colleagues in the past. However, after these abstract principles, I felt the rest of the book wasn't as helpful as I was expecting.
Written in 2000, but updated in 2013, there were a lot of concepts that have been outdated in today's web world. The majority of the chapters were written with concrete examples, and while some layout tips might be applicable to today's modern apps, the rest were artifacts of an older browsing history.
Obviously, rapid changes are extremely difficult to account for when writing a book about the design of the web. Because of this difficulty, it would have been better to have discussed the top usability concepts, rather than specific examples. A great example of this issue is the entire chapter dedicated to the Home page.
Another nit picky problem I had while reading was the unnecessary amount of book recommendations. It's one thing to source where a concept has come from, but it's another to introduce the importance of a specific usability application (e.g. font styles and sizes), then spend a few sentences introducing it and instead of summarizing it, recommend an entire book on the subject. I came for a distillation of usability principles and applications, not to build a library of books that I'm never going to get to.
The worst offender was the accessibility chapter. Two of the four recommendations to fix the problem of accessibility was to read an article and another book! That's not the type of advice I'm looking for when I'm reading a book about usability.
Nonetheless, I did learn a few interesting helpful tips about usability. The chapter on usability testing and DIY testing solidified some high level understandings I had about user testing. There were also multiple instances where I said "ohhh" out loud after learning the "why" behind UX concepts (e.g. goodwill reservoir) that I heard colleagues mention but never clarified.
Unfortunately, these instances were short and far between. Instead, I had to wade streams of light-jokes and quirky writing that got annoying after awhile. Even the random off topic footnotes the author injected got tiresome by the end. I get that he was trying to give the text some mensch, but it wasn't landing for me.
Overall, this wasn't the book I was hoping for. I wasn't trying to get buy in from my manager to perform usability tests. I wasn't trying to compare UX to usability. Instead, I wanted to learn about some core principles of UX and design that I could use in my daily workflow. I guess I'll have to keep looking.
...more
Here's an insight: most people think users hate making lots of clicks to find their way to way to what they want. Not true. Users want to know that the search will be fruitful. They also want to find the right links intiatively and they want to be able to retrace their steps quickly if they turn down a wrong alley.
I strongly recommend this book for anyone, novices and experts, who are serious about web design.
My only regret is that I didn't read this book before I started to develop my company's portal.
...more
There are applications of what he says far beyond web design. I teach pronunciation, and know
In this book, Krug shows you how to make things easy for visitors to your site by making sure everything on it is obvious at a glance and easy to find and get to. And he practices what he preaches - I picked this book in large part because of its clear, attractive, reader-friendly design. It's a quick read, but you may want to take your time on it a bit to make sure you fully register everything he says.There are applications of what he says far beyond web design. I teach pronunciation, and know that people really don't want to have to grapple with poor pronunciation and incorrect grammar to get at what a speaker actually meant to say. Those who say the listener should do some of the work too are not thinking about how competition for attention and resources works in the real world.
If you have a web site, blog, or any other online presence, I highly recommend you get and read this book NOW!
...more
It is well written, easy to understand and most things are not surprising at all, but the way they are packaged and presented leaves an impact.
Each paragraph has a short list of things that the reader could easily implement, leaving the feeling that improving is actually easy or at least starting is easy
I can't believe I hadn't read this book before. I remember seeing the cover _everywhere_ for a long time but never looked into what it was. Anyhow. It's about web usability and damn is it good.It is well written, easy to understand and most things are not surprising at all, but the way they are packaged and presented leaves an impact.
Each paragraph has a short list of things that the reader could easily implement, leaving the feeling that improving is actually easy or at least starting is easy for anyone.
I will not look at web pages or our own product the same ever again.
A good book is usually the one that I "swallow" quickly and that sparks a few ideas. This was a good book and all product managers should read it. At the minimum it will at least confirm many of the things that you are already doing towards good usability but might also spark a few new ideas to level up.
...more
This should be a reference book, read from time to time. Great book for any developers that want to take a look inside a user's head, better understanding their behaviors and how to influence them.
This should be a reference book, read from time to time. ...more
Don't Make Me Think is a book about web usability. Usability is basically how easy it is too efficiently use a website. It tests how to make a website easier for the average visitor.
This book gives you insights into how to make a website easy to use. The first principle is to make your website as obvious as possible. For example, if the visitor is looking for employment information, it should use the
Don't Make Me Think A Common Sense Approach To Web Usability, Second Edition, Steve Krug-- ReviewDon't Make Me Think is a book about web usability. Usability is basically how easy it is too efficiently use a website. It tests how to make a website easier for the average visitor.
This book gives you insights into how to make a website easy to use. The first principle is to make your website as obvious as possible. For example, if the visitor is looking for employment information, it should use the most obvious words to describe employment like jobs or resume.
The other point it makes is that people don't read websites they do magazines or books, they scan through a website quickly. Most people do not want to scroll through screens of information. They want to go to the first place which gives them relevant information. They are seeking "satisficing", that is the place where they will get the information they need, not the best information.
Steve Krug describes how a website is more like a billboard than a magazine. The title should be prominently displayed on all the pages, and there should be a link back to the home page on every page. The most important piece of information on the web page should be the most visible.
Links should be obviously shown as links. This is why I usually put the full url in my blog posts for sites that you can visit.
Steve Krug quotes from The Elements of Style, "Omit needless words." He further says you must eliminate happy talk, marketing talk, and jargon from your site. People do not have very much patience on the internet.
There are some interesting concepts described about how people find things. He has many diagrams on how people seek out to buy things on the web. These diagrams explain how to make the experience quicker and easier. He also describes how to create a visual trail for the user on a web site. This often called "breadcrumbs." At times this gets a bit complex.
There is also a description of the basic elements of a homepage for a business. This book is mostly focused on business and professional websites, not the home user. It often describes how a development team in a business would build or test a website. This is my first experience with this kind of material.
Some of the elements in a professional homepage are search functionality, timely content, and shortcuts. He mentions that the title of websites should have a catchy tagline attached to them. This should explain exactly what the website is about.
The final chapters are how to do usability testing in a very inexpensive manner. He describes the basic setup with a camcorder, cabling, computers, and screen capture software. Then he tells how you can test a website with small groups of people to see whether or not it is easy for them to use. I understood the majority of this. However, it is not something I am planning on doing immediately.
Immediately after the cheap usability testing, he gives an outline of the context of what generates goodwill and bad will in a website. For example, some of the elements which generate goodwill are making it easy to recover from errors, putting in printer friendly pages, and knowing what the main thing people want in your website then implementing it.
The last few pages have several books which he recommends you read to improve your web site usability. Some of them look quite interesting. I may order several of them for my library. There is an index in the back of the book as well.
The book is illustrated in full color. There are pictures on almost every page. The artwork is pleasant to look and relevant to the content of the book. The book itself is designed so it is easy to read. The author claims you should be able to read through the book in about two hours. It took me three hours with several interruptions.
This book is very basic. It gives you an idea of what web usability is. I think it is helpful for basic tips on how to improve a website. The material is not advanced or complicated. It is the kind of thing you can read in an afternoon. This is a beginners book.
...more
The only downside (and hence a 4 star rating) is that the book could use more real world examples. Seeing many more screenshots of websites that do something well, side by side with those that do it poorly--or better yet, examples
A nice overview of basic usability principles for building user interfaces. The call for do-it-yourself user testing is extremely important, though ignored or unknown to many companies. The sense of humor is great and the advice is fairly actionable and easy to follow.The only downside (and hence a 4 star rating) is that the book could use more real world examples. Seeing many more screenshots of websites that do something well, side by side with those that do it poorly--or better yet, examples of incrementally improving a single design based on user testing--would make the lessons much more sticky.
Fun quotes from the book:
It's not rocket surgery.
The actual Average User is kept in a hermetically sealed vault at the International Bureau of Standards in Geneva.
What they actually do most of the time (if we're lucky) is glance at each new page, scan some of the text, and click on the first link that catches their interest or vaguely resembles the thing they're looking for. There are almost always large parts of the page that they don't even look at. We're thinking "great literature" (or at least "product brochure"), while the user's reality is much closer to "billboard going by at 60 miles an hour."
FACT OF LIFE #1: We don't read pages. We scan them.
If your audience is going to act like you're designing billboards, then design great billboards.
It doesn't matter how many times I have to click, as long as each click is a mindless, unambiguous choice. —KRUG'S SECOND LAW OF USABILITY
The main thing you need to know about instructions is that no one is going to read them.
I think every Web development team should spend one morning a month doing usability testing. In a morning, you can test three users, then debrief over lunch. That's it. When you leave the debriefing, the team will have decided what you're going to fix before the next round of testing, and you'll be done with testing for the month.
Experts are rarely insulted by something that is clear enough for beginners.
People are just as likely to be using their mobile devices while sitting on the couch at home, and they want (and expect) to be able to do everything. Or at least, everybody wants to do some things, and if you add them all up it amounts to everything.
...more
The Book
Although usability is becoming more and more popular among web projects these days, it is still an underrated feature. In this book, Steve Krug explains usability in a
What comes to your mind when you think about usability in web design? "Less clicks is better"? "Design to the average user"? "Content is king"? "Users leave your website if it doesn't load in X seconds"? If you take any of these as a rule for your websites then you need to read this book: Don't Make Me Think, by Steve Krug.The Book
Although usability is becoming more and more popular among web projects these days, it is still an underrated feature. In this book, Steve Krug explains usability in a fun and direct way, using illustrations to mimic real life situations in which we all have been before. The examples and the websites featured in this book are a little outdated – the first edition was released in 2000 – but the problems are still around only with a modern design.
Myths and Tips
Every chapter contains precious gems and "facts of life" (as the author says) that show us how we really use websites. One example is the fact that he explains how we scan pages instead of reading them, and how this makes "content is king" a myth. Speaking about content, Steve Krug advices us to get rid of half the words on each page, then get rid of half of what's left. This may sound weird, specially under a SEO point of view, but if you think again, by doing this you will end up having only the essential content (or keywords), the one that matters to your user.
Conclusion
Don't let the fact that the book was originally written the year 2000 put you off. As I said before, we still face the same issues today. In 2005 was released the second version of this book which has three new chapters, including one where he talks about CSS & web usability and another one – one of the best IMHO – where he advices us on how to answer to our bosses when they have bad ideas. If you're still wondering if buying the book is a good idea or not, the fact that it is recommended by Jeffrey Zeldman should be enough for you to buy it!
[Visit my website and read the book review.]
...more
Reading this book generated more ideas and interest in a needed web redesign than I thought possible. Its approach is not a heavy-handed laying down of rules, but descriptions of typical scenarios and problems and possible solutions in a way that stimulates creative thought in the reader. It's formatted to be easily browsable and readable, making it a quick reference for web developers with time budgets—as if there were any other kind! This book will benefit anyone who is putting together a website, offering tips on making it more logical and informative, thus more popular among users.
...moreGoodreads is hiring!
Learn more »
His second book is the usability testing handbook Rocket Surgery Made Easy: The Do-It-Yourself Guide to Finding and Fixing Usability Problems.
The books were based on the 20+ years he spent as a usability consultant
Steve Krug (pronounced "kroog") is best known as the author of Don't Make Me Think: A Common Sense Approach to Web Usability, now in its third edition with over 600,000 copies in print.His second book is the usability testing handbook Rocket Surgery Made Easy: The Do-It-Yourself Guide to Finding and Fixing Usability Problems.
The books were based on the 20+ years he spent as a usability consultant for a wide variety of clients like Apple, Bloomberg.com, Lexus.com, NPR, the International Monetary Fund, and many others.
His consulting firm, Advanced Common Sense ("just me and a few well-placed mirrors") is based in Chestnut Hill, MA.
Steve currently spends most of his time writing, teaching usability workshops, and watching old movies on tv.
...moreNews & Interviews
Welcome back. Just a moment while we sign you in to your Goodreads account.
laurenswastfultaint.blogspot.com
Source: https://www.goodreads.com/book/show/18197267-don-t-make-me-think-revisited
0 Response to "Dont Make Me Think Web Design Funnies"
Post a Comment