This book is great for people who are new to the information architecture/usability/interface design field. This was the first book I read in this area, and it was a great starter book which has kick started my desire to learn more. Even if you aren't in those fields, its a great book for software designers and developers to read and should have you improving your apps usability in no time.

There are some great tips that just make so much sense, its hard to understand why more people don't follow these principles. The book is also really easy to read, and can be hard to put down at times.

If you are trying to decide between this or "Don't make me think" (which was the case with me), I recommend you get both, as they both have some great points and are nice and quick to read.

If you already know quite a bit about web app design and usability, then this may not be the book for you, but its fantastic for beginners.

This book contains so many eye opening facts about obvious designs for web applications. It is a very useful for the designers and usability people of web applications. Though it has less practical stuff and more of theories, they fit with almost all kind of applications and helps if implemented. Very good to have kind of book.

This book is deceptively thin but it took me a long time to read it because I kept stopping every few pages or even paragraphs to reflect. The points that he brings up and the examples he presents are great and he gives me a framework for how to think about designing applications. A lot of of the ideas in this book like inline validation and reducing features are things I already knew. Hoekman just puts all this information in an short and sweet book. I've already started using some of the suggestions to solve design problems on various projects.

As a UI designer I enjoyed the book. It was clearly written with many useful nuggets of wisdom for those of us building web apps. Typically books like this deal with informational websites or ecommerce, this one covers the missing gap. While most of the examples were fairly light-weight web apps, the foundations covered in this book apply across the board. Usually I skip around in these books since the writing is so dry. Robert has written this one in a conversational tone and I read it cover to cover. Recommended.

Focuses less on actual design tips, but more on the design mentality - being willing to cut stuff out and focus on what's important. It was a good read, had some good examples, and reference good websites to check out.

The danger in reading a book that tells you to do obvious things is that you may find yourself thinking that since you could have thought of each piece of advice on your own, you would have. Alas, unless you have the depth of experience that someone like Robert Hoekman has acquired by working on dozens of projects, chances are there is at least one obvious thing in this book that you have missed in your last project.

If you're like me there is probably considerably more than one thing.

Hoekman lays out the basic principles of web application design clearly and succinctly. He starts by describing some of the practices that designers should adopt in order to understand how their users actually behave and what they really need. These practices are meant to cure readers of the habit of asking users what they want, which frequently results in honest but inaccurate answers. Hoekman's tools of choice for generating understanding are various forms of shadowing users while they do the tasks your application will perform, and his preferred method of documentation is the use case. No one who has worked in software development for any period of time will be surprised at the use case rules he lays out, but the example he gives is a rare glimpse into how the mind of an expert polishes a basic use case into something truly professional.

He next tackles the question of what features to put into your design and which to leave out. Here Hoekman is firmly in the minimalist camp exemplified by 37 Signals. He advocates ruthlessly stripping out "nice to have" features, and simplifying the rest. Although I had previously read much the same argument in "Getting Real", ([...]) once again I found that the example at the end of the chapter gave greater practical insight into how to actually select features to remove.

I found the chapter titled "Support the User's Mental Model" to be the most valuable in the book. As someone who is more often on the project management than the implementation side of web applications, I have often had an engineer propose a feature or refinement that makes perfect logical sense, but for some reason doesn't feel right. After reading this chapter, all of those vague feelings snapped into focus for me. Engineers are so deeply immersed in how the application works, and the possibilities that are available, that they sometimes want to structure interactions in ways that reflect the logic of the code rather than the logic of the activity. Previously I had been attributing most of these errors to the desire to provide more options to the user. Being able to distinguish between the two should help me in approaching these proposals better in the future.

The chapters on helping first time visitors become intermediate users quickly and on handling errors were also valuable, mostly because they focused on the introductory experience. There are dozens of books on design and interactions, but I have yet to see one that focuses exclusively on the crucial first visit of a user to a new site. Since this is where most of our products either succeed or fail, it's great to get some practical advice on how to gently guide a neophyte while still preserving the power a more experienced user will demand. Once again the blow by blow examples that tackle specific interaction problems and solve them are worth their weight in gold.

The rest of the book emphasizes the value of uniformity and novelty, and seemed less useful to me. It's possible that at my intermediate level of knowledge, those were the obvious things I HAVE thought of!

I only had one quibble with the book. Hoekman includes lots and lots of references to web sites and online articles that could be helpful, but each one is buried in the text. A page at the back that simply listed each of these sites would have been very helpful. Or better yet, list them on the author's web site and keep them up to date! What better way to promote yourself as an author long after the original book is dogeared and falling apart?

But this book is an invaluable resource, and one I expect will still be on my shelf long after all the sites it references have gone offline.

This is one of a small collection of work-related books that I read cover to cover and it was completely worth it. The perspective and insight that this book provided has given me more to consider when building applications. Within minutes of finishing the book, I found ways to simplify and enhance applications I was working on.
If you don't have it, get it. If you have it, make sure you read the whole thing, this isn't a book that you flip through, this is a book you read from beginning to end.

As the popularity of WordPress has grown I've learned many lessons about design and usability, often the hard way. I wish this book had been around 4 years ago when WP got started, because we could have avoided dozens of mistakes along the way.

After I was about half-way through this book I ordered a copy for everyone in my company, even non-developers, because it concisely summarized so much of what I think we should do.

This is a good book for people designing general purpose web applications (including customer registration forms and so forth, which most wouldn't see as 'web applications').

I like it's focus on doing things in a simple sense, especially at the end where it proposes Just-In-Time Design and Just-In-Time Review as a way of avoiding lengthy and often uneccessary specification and design phases.

While not as in depth as some in conceptual material (I'd recommend Alan Cooper's latest edition of 'About Face' for this), I enjoyed reading it and got some good, practical things from it.

I think the book gives good advice or pointers for web design beginners (someone who is entering the industry after studies i.e.) so we can get our fundamentals right from the start. Although the examples are focused on designing web applications many of them are good even if you are building a more traditional site heavy with information. This book contains information that everybody in the business should know but is so obvious (as said in the title) that you can easily forget it while tackling with the techy stuff in your project.

The book is fast and fun to read and the author's style of writing is entertaining. The English is easy and it took me only a few nights to read the book even when I am not a native speaker. I wish that it would have been longer and filled with more practical advice like the one talking about form validation. While the book is different from the Steve Krug's "Don't Make Me Think: A Common Sense Approach to Web Usability" I think they go well hand in hand.

From 9 to 5 (well, a "little" after 5 most days), I am an Application Development Manager in my company. In my years doing this, I have read a lot of books on the topic of Web and User Experience Design. So far, only a handful stand out above "Designing the Obvious" by Robert Hoekman Jr. and even some of those, he takes his hat off to (such as the case of "Don't Make Me Think", for instance).

Hoekman proposes the "unthinkable" for those entrenched into rusty web design practices, but when you step back and reconsider the experiences you've had, his framework makes perfect sense. Here are a couple of thoughts he brings to the table, to give you an idea:
-Design an application that does one thing, and does it very well. For every additional feature, there is more to learn, more to tweak and configure, more to customize, more to read about in the help document, and more that can go wrong.
-People (users) don't always make the right choices. They make comfortable choices... they make choices they know how to make. To deal with this, he supports Goal-Directed (also called Activity-Centered) Design, as opposed to Human-Centered Design.

Web Design anathema? Violation of User Interface "basics"? Maybe it sounds so at first, but if you read through his arguments, you will find them very compelling and may end up (like myself) reconsidering some of your initial assumptions.

One of the reasons why his proposal resonated so much with me is because throughout the book, Hoekman introduces concepts that are not familiar in the Web space, borrowing them from long-established best practices in manufacturing (where I worked the first four years of my professional life), such as:
-Kaizen: improving things constantly, in little tiny ways that add up to gigantic results.
-Poka-Yoke: software "devices" meant to prevent user errors from occurring.
-Pareto (80/20 rule): Good, clean Web application design means that 80 percent of an application's usefulness comes from 20 percent of its features.

For longtime professionals and newcomers into the field of User Experience Design, Hoekman's book has turned into an absolute must read.

I must say after reading this book I felt like I had a better idea on how to develop web apps for the ground-up. The author does an excellent job of explaining his points and concepts while keeping the reading interesting and engaging. Examples are used extensively through-out the book to further illustrate his points.

It a book any web developer/designer should have on their bookshelf!

Even this book is meant for web UI designers, I think that it is a must read for any developer that has an application with a UI. The concepts and examples will really make you think about how you have designed your applications in the past.

This book is extremely easy to read and is well organized. The book starts out with a great overview of what the rest of the book will talk about in detail. After just reading the overview I was able to have discuss with other team members that had read the whole book cause we had a common vocabulary. As I have gotten further into the book, I am referencing it on a daily basis with my project team. We have changed a ton of the UI based on this book because we were experiencing many of the same issues that are discussed in the book.

I thought this book was very useful on many points. Through the use of illustrative examples, the author really points out what people are doing wrong (and right) in a lot of common web designs. His philosophy, essentially functional minimalism, means that you spend a lot more time stripping features off of applications than putting them on, and this is probably a great idea.

The only issue I have with this idea is that some of the exercises he proposes to help you pare things down are (in my opinion) very hard, or impossible. After all, if we were all decisive enough to excise things from the spec when they weren't strictly useful, they probably wouldn't be there in the first place.

Basically, it boils down to this: Figure out exactly what your application does. This is ONE thing. Then, remove everything that doesn't do that. If you can still do that thing, you won, and have a good design. The book goes into greater detail about a lot of things you can do to make your application as smooth for the user as possible, and helps to avoid common pitfalls. All designers should read this book - and all engineers should read it twice.

Hoekman's book, Designing the Obvious, is a great resource for anyone involved in the creation of web applications. As a person relatively new to the usability and user interaction field, I found the book easy to understand and was able to immediately apply what I learned to the applications our company is building. The book should be required reading for anyone involved in designing web applications - developers, project managers, interface designers, business analysts...

This book will tell you that you need to make your applications (and development process) simpler, provide more helpful error messages, be more consistent etc. I can't help but agree, but oh boy, this guy has really drunk the Kool-Aid... Nevertheless all points are well argued and backed up with examples (usually from "Web 2.0" sites).

I have to admit that although I love all the new bells and whistles that come with each new upgrade of my favorite software, I sometimes use the older versions. Why? Because the older versions have a lower learning curve and are less complicated to use. This is also true for the internet and the new web technologies. Many website designers continue to create simple, static webpages because they are easier to create and their readers find them easier to use.

Designing websites today isn't as easy as it was just a few years ago, especially with the increased popularity of Ajax and other new scripting languages. Websites are becoming more like desktop applications and less like those old static pages. Of course, internet users expect to see these new features on your websites and that's the way it should be. After all, that's what makes the internet so exciting. However when creating these new, powerful twenty-first century websites, you also need to keep them user-friendly. The author, Robert Hoekman, Jr., shows you how to do just that in Designing the Obvious.

He begins by explaining his approach to designing user-friendly websites. He covers the basics such as understanding the user and evaluating what new features to use on your site. He uses many well known websites to demonstrate how today's new web technologies are being used successfully. After discussing how to design your site for these new website improvements, he then shows you how to implement them into your site.

Once you have the wireframe, or blueprint, for your site, he identifies the usual problem areas and common mistakes and shows how to avoid them. I especially liked the section that covered how to design user-friendly web forms. Web forms are still the best way to collect information from your site visitors for many web applications and the author shows you how to use the new technology to improve the usability of your web forms. He shows may ways to add what he calls Help Aids that assist the user as he progresses through the form and how to design your forms so that user mistakes are almost impossible.

Robert Hoekman, Jr. is a professional Interaction Designer and Usability Specialist. He has authored many books and training courses in this area.

I have been designing web sites and web applications for many years. I purchased over 100 books on web development and I have to say that "Designing the Obvious" is a breakthough book for web design and application development.

Clearly and precisely, Robert Hoekman Jr., explains the how's and why's of proper web design. The book not only explains the concepts of common sense designs, but why they should be implemented. The reader is given examples of web sites both wrong and right, for comparison.

The book is laid out in several chapters and covers every aspect of design, from simple registration screens, to complex content editing. The techniques represented show a clear method to allow you, the designer, to create the next application that can rival even the best web sites out there.

Robert also introduces you to a set of tools that can assist you in creating the perfect web application. After reading about them, I registered for several of the free features and even upgraded one to the full pay version. (Thanks Robert!)

Don't think this book is just for programmers. This book is also for web designers, whether graphic designers, Flash designers or otherwise. The book is well rounded and teaches many design from many perspectives.

This book is a must for anyone who designs, writes, edits, critiques or reviews web sites.

5 stars is not enough.

Design should be obvious. It is a really simple concept actually; if you want to make something usable, make it as easy to use as a door or a light switch. However, the genius of this book is not only its ability to make that argument, but also to instill the knowledge necessary for those of us lacking a design sense to make a usable interface.

In my personal opinion, every application designer and developer can benefit from the wealth of information and experience in this book. My company has adopted it as required reading for every one of our developers.