- Paperback: 224 pages
- Publisher: New Riders; 1 edition (November 8, 2013)
- Language: English
- ISBN-10: 0321929039
- ISBN-13: 978-0321929037
- Product Dimensions: 6 x 0.6 x 9 inches
- Shipping Weight: 1.1 pounds (View shipping rates and policies)
- Average Customer Review: 24 customer reviews
- Amazon Best Sellers Rank: #405,487 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Product Design for the Web: Principles of Designing and Releasing Web Products 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
"Rebound" by Kwame Alexander
Don't miss best-selling author Kwame Alexander's "Rebound," a new companion novel to his Newbery Award-winner, "The Crossover,"" illustrated with striking graphic novel panels. Pre-order today
Frequently bought together
Customers who bought this item also bought
Customers who viewed this item also viewed
About the Author
Randy J. Hunt is creative director at Etsy, where he leads a team of designers building web products and creating off-line experiences. Prior to joining Etsy, Hunt co-founded Supermarket, a curated design marketplace; founded Citizen Scholar Inc.; and worked at both Milton Glaser Inc. and Number 17. Hunt writes and lectures about design and has been a visiting designer and critic at many colleges and universities. In 2009, he was named a New Visual Artist by Print. Hunt received his MFA in design from the School of Visual Arts.
Author interviews, book reviews, editors picks, and more. Read it now
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
As I was going through this huge learning curve the first year or so, I started following experienced product designers on Twitter like Randy Hunt. I preordered his book and I read the whole thing in a couple a days. The read is extremely clear and straightforward but the most valuable part was that it had a lot of answers to the problems that I was looking for that involved defining and understand roles, processes and the org in general. It helped bring up decisions about the importance of design with a clearer understanding of what that meant. I think startups, like ours, tend to go through many types of processes to find the right one that fits for them, which ends up spending more time defining roles than working more on solving actual product problems, this book really helped identify all those things from communication, balancing constraints, user behavior, roles, team building, identifying problems and so much more. Evidently, this really helped us build better products, understand the web and our users because we had a stronger communication across the org how important design was and how it will impact the future of our business.
This book enlightened and supported many of my thoughts of how we should experiment with different processes and to involve design more and how we should tackle our products. Randy talks more than just defining roles (which was the biggest issue at our company at the time) but about how we work together to create, iterate, and repeat our process as a team. That transparency among departments helps products succeed (or fail, which are just learning experiences) since we're all striving for the same goals. To not be afraid to ship, learn for what works and what doesn't, and that change is overall a good thing.
I vouch for this book for anyone who has any questions about how product design works, how it should be involved or anyone who just wants to understand what it takes to build applications for the web (or mobile). Thanks Randy!
Unfortunately, there are a lot of chapters, particularly in the second half, that deal with issues in a fairly superficial way. For example, there are chapters on engineering corners like performance and management concerns like leading and inspiring teams that, while relevant, would seem better addressed by more focused books on those topics.
If you are starting out in web product design, then these topics, even in gloss, may prove valuable in giving you a view of the field, but if you are an experienced designer then you've probably encountered this stuff already. However, Hunt's insights into how to use analytical and iterative processes to sculpt a design are still worth while.
Hunt's expertise and true belief in the topics and processes discussed in the book are evident throughout, and the information is presented in a way that makes it easy to comprehend. This is something I think is lacking in other books on this subject, which more often than not, are targeted towards an audience of individuals who are continuously in a development mindset rather than at designers looking for ways to see the whole picture and gain insights into how to support a more productive and efficient alternative to the way their organization approaches the product design process.
Within the book, Hunt is able to break down important aspects of the process that has worked for him (and those that have worked for Etsy) into concise topics that are easy for product designers to relate to. Overall, I highly recommend this book to solo product designers, product teams within larger organization, as well as to aspiring product designers, as I feel the principles contained within it, as well as the amount of key concepts and insights into establishing highly productive (and fulfilling) workflows, can greatly benefit any of those audiences.
However, there was nothing in this book that I did not already know. That was disappointing. Now if you have never worked in engineering or product management in the Silicon Valley, and you are starting your first job, then it is a great book and you will get a lot out of it. The book is just not targeted at experienced engineers and product managers.
A core theme of the book is that web products are never done, and so the philosophy of iteration and constant change permeates each chapter. You'll get a snapshot of the steps and thinking required at each stage of development - from idea to research to testing to launch...to rinse and repeat.
This isn't a highly tactical "how to" book, but rather a collection of truisms that are easily forgotten in the daily grind. I read this as a marketer and also found it useful in a marketing context. A read it in a morning over coffee...quick read, easy to digest, and impactful.