This is the first book on the topic of simplicity aimed specifically at interaction designers. It shows how to drill down and simplify user experiences when designing digital tools and applications.

     The role of the devil's advocate is nearly universal in business today. It allows individuals to step outside themselves and raise questions and concerns that effectively kill new projects and ideas, while claiming no personal responsibility. Nothing is more potent in stifling innovation. Drawing on nearly 20 years of experience managing IDEO, Kelley identifies ten roles people can play in an organization to foster innovation and new ideas while offering an effective counter to naysayers. Among these approaches are the Anthropologist—the person who goes into the field to see how customers use and respond to products, to come up with new innovations; the Cross-pollinator who mixes and matches ideas, people, and technology to create new ideas that can drive growth; and the Hurdler, who instantly looks for ways to overcome the limits and challenges to any situation. Filled with engaging stories of how companies like Kraft, Procter and Gamble, Cargill and Samsung have incorporated IDEO's thinking to transform the customer experience, THE TEN FACES OF INNOVATION is an extraordinary guide to nurturing and sustaining a culture of continuous innovation and renewal.

    At under 200 pages it's quick reading too. Makes a great airplane book.

    Spanning over a century of sweeping changes, from women's rights to the Great Depression to World War II to the rise of the digital era, this book unpacks the ways in which the world has been--and continues to be--remade according to the principles of the once-obscure discipline of user-experience design.In this essential text, Kuang and Fabricant map the hidden rules of the designed world and shed light on how those rules have caused our world to change--an underappreciated but essential history that's pieced together for the first time. Combining the expertise and insight of a leading journalist and a pioneering designer, User Friendly provides a definitive, thoughtful, and practical perspective on a topic that has rapidly gone from arcane to urgent to inescapable. In User Friendly, Kuang and Fabricant tell the whole story for the first time--and you'll never interact with technology the same way again.

    In this practical guide, author Amir Shevat shows you how to design and build great conversational experiences and delightful bots that makes people s life more fun and productive.You ll explore several real-world bot examples to understand what works and what doesn t, and learn practical design patterns for your own bot-building toolbox. This book is ideal for beginners and intermediate designers, as well as senior professionals exploring the conversational user experience paradigm. No coding experience or prior knowledge of conversational UI is required.Learn what bots are, and understand bot types and major components that compose a botExplore different use-cases of bots and best practices around these use casesExamine real-life examples and learn from their experienceUnderstand the bot anatomy (Onboarding, Notifications, Conversations, Advance UI controls) and their associated design patternsPrototype your own first bot and experiment with user feedback"

    They think that UI design is like graphic design--the mysterious process by which creative, latte-drinking, all-black-wearing people produce cool-looking, artistic pieces. Most programmers see themselves as analytic, logical thinkers instead--strong at reasoning, weak on artistic judgment, and incapable of doing UI design.In this brilliantly readable book, author Joel Spolsky proposes simple, logical rules that can be applied without any artistic talent to improve any user interface, from traditional GUI applications to websites to consumer electronics. Spolsky's primary axiom, the importance of bringing the program model in line with the user model, is both rational and simple.In a fun and entertaining way, Spolky makesuser interfacedesign easy for programmers to grasp. After reading User Interface Design for Programmers, you'll know how to design interfaces with the user in mind. You'll learn the important principles that underlie all good UI design, and you'll learn how to perform usability testing that works."

    The revised structure, separating out the introductory and more advanced material will make it easier to use the book on a variety of courses. This new edition now includes chapters on Interaction Design, Universal Access and Rich Interaction, as well as covering the latest developments in ubiquitous computing and Web technologies, making it the ideal text to provide a grounding in HCI theory and practice.

    In this book for designers, developers, and product managers, expert developer and user interface designer Lukas Mathis explains how to make usability the cornerstone of every point in your design process, walking you through the necessary steps to plan the design for an application or website, test it, and get usage data after the design is complete. He shows you how to focus your design process on the most important thing: helping people get things done, easily and efficiently. The author presents a collection of valuable tips - organized in four distinct parts, filled with clever illustrations, and supported by fascinating psychological research. He teaches techniques that help you plan and evaluate your user interface design, and inspires you to look at design in a whole new way. He tells you exactly what to look for, and what to avoid, in creating applications and websites that people will be excited to use.

    It will enable making a design for almost any kind of building, or any part of the built environment. ‘Patterns,’ the units of this language, are answers to design problems: how high should a window sill be?; how many stories should a building have?; how much space in a neighborhood should be devoted to grass and trees?More than 250 of the patterns in this language are outlined, each consisting of a problem statement, a discussion of the problem with an illustration, and a solution. As the authors say in their introduction, many of the patterns are archetypal, so deeply rooted in the nature of things that it seems likely that they will be a part of human nature and human action as much in five hundred years as they are today.A Pattern Language is related to Alexander’s other works in the Center for Environmental Structure series: The Timeless Way of Building (introductory volume) and The Oregon Experiment.

    As the size and complexity of commercial software have grown, the gap between academic computer science and industry has widened. It's an open secret that there is little engineering in software engineering, which continues to rely not on codified scientific knowledge but on intuition and experience.Barr, who worked as a programmer for more than twenty years, describes how the industry has evolved, from the era of mainframes and Fortran to today's embrace of the cloud. He explains bugs and why software has so many of them, and why today's interconnected computers offer fertile ground for viruses and worms. The difference between good and bad software can be a single line of code, and Barr includes code to illustrate the consequences of seemingly inconsequential choices by programmers. Looking to the future, Barr writes that the best prospect for improving software engineering is the move to the cloud. When software is a service and not a product, companies will have more incentive to make it good rather than "good enough to ship."

    "This book is a guide to how we do product development at Basecamp. It’s also a toolbox full of techniques that you can apply in your own way to your own process.Whether you’re a founder, CTO, product manager, designer, or developer, you’re probably here because of some common challenges that all software companies have to face."

    Treat it as the UX expert on your bookshelf that you can read from cover-to-cover, or to dip into as the need arises, regardless of whether you have 'UX' in your job title or not.

    By presenting actual experiences and analyzing them as they are described, the author conveys the developmental thought processes employed and shows a style of thinking that leads to successful results is something that can be learned. Along with spectacular successes, the author also conveys how failures contributed to shaping the thought processes. Provides the reader with a style of thinking that will enhance a person's ability to function as a problem-solver of complex technical issues. Consists of a collection of stories about the author's participation in significant discoveries, relating how those discoveries came about and, most importantly, provides analysis about the thought processes and reasoning that took place as the author and his associates progressed through engineering problems.

    Instead of forcing users to conform to a product design or experience, designers need to learn how users behave and interact with various digital interfaces.This guide provides some key principles from psychology to help you design more intuitive, human-centered products and experiences. Humans have an underlying blueprint for how we perceive and process the world around us, and through simple lessons in psychology, this guide will help you define this blueprint.

    I would love to write that book, but at this time I have no indication that such a book would be worth writing. Most books fail in the market, and most of them fail not because they are poorly written or edited, but because there aren’t enough people interested in them. They are not the right it.What you are reading now is a pretotype edition of the book. I wrote and “edited” it in days instead of months, just to test the level of interest in such a book. I had a few friends and colleagues review it, but don’t be surprised if you find typos, misspellings, bad grammar, awkward formatting and all sorts of misteaks.Releasing it in its present state is not easy for me.The toughest thing about pretotyping is not developing pretotypes, that’s the fun part. The tough part is getting over our compulsion for prema- ture perfectionism and our desire to add more features, or content, before releasing the first version. The tough part is getting our pretotypes in front of people, where they will be judged, criticized and – possibly – rejected.Reid Hoffman, founder of LinkedIn once said: “If you are not embarrassed by the first version of your product, you’ve launched too late.”I am plenty embarrassed. I must be on the right track.http://www.pretotyping.org/pretotype-...