Here are 67 books that Contextual Design fans have personally recommended if you like
Contextual Design.
Shepherd is a community of 10,000+ authors and super readers sharing their favorite books with the world.
Shepherd is reader supported. When you buy books, we may earn an affiliate commission.
I have been designing user interfaces since graduate school at Stanford, where I studied psychology and computer science. Over the five decades since then, I have designed many digital products and services, learning a lot about how to make them usable and useful. Two decades ago, I turned more towards sharing my knowledge and experience through writing (articles and books) and teaching (professionals and students). I’ve taught at Stanford University, Mills College, the University of Canterbury (New Zealand), the University of San Francisco, and at professional conferences and companies. Google invited me twice to speak in their Authors @ Google series, and ACM and SIGCHI have given me several awards.
If you design Web sites, you’ve almost certainly already read Steve’s book; it may be the best-selling Web design book of all time. If not, do.
It succinctly explains most of what designers need to know about Website usability. The title of the book – Don’t Make Me Think – is the book’s main point: “If your website makes me think about how to use it, distracting me from my own goals (e.g., booking a flight), I’m out of here.”
In relatively few pages, Steve explains how to design Websites so visitors need not think about how to use them.
Since Don't Make Me Think was first published in 2000, hundreds of thousands of Web designers and developers have relied on usability guru Steve Krug's guide to help them understand the principles of intuitive navigation and information design. Witty, commonsensical, and eminently practical, it's one of the best-loved and most recommended books on the subject.
Now Steve returns with fresh perspective to reexamine the principles that made Don't Make Me Think a classic-with updated examples and a new chapter on mobile usability. And it's still short, profusely illustrated...and best of all-fun to read.
I would like to consider myself an experienced and successful designer, researcher, and educator. I'm an Associate Professor in Communication Design and the Head of Education for the School of Design at Northumbria University in the United Kingdom, where I've taught and researched for the last twenty years so I'm super passionate about this subject and love explaining how design works. Before joining academia, I worked internationally as a designer and creative director for numerous prestigious design and media organizations, including Philips, Time-Warner, Windmill Lane Pictures, and WPP in the UK, Ireland, USA, and Southeast Asia. Working in these different businesses and locations gave me a broad perspective on the role and importance of design.
This essential book by Don Norman does not need any more plugging, but it would be impossible to leave it out.
The book forms a brilliant introduction to User Experience Design by explaining how the design of everyday objects relies on an intuitive understanding of how they work. Once we translate this thinking from the physical to the digital world, we are halfway there as UX/UI designers.
Even the smartest among us can feel inept as we fail to figure out which light switch or oven burner to turn on, or whether to push, pull, or slide a door. The fault, argues this ingenious,even liberating,book, lies not in ourselves, but in product design that ignores the needs of users and the principles of cognitive psychology. The problems range from ambiguous and hidden controls to arbitrary relationships between controls and functions, coupled with a lack of feedback or other assistance and unreasonable demands on memorization. The Design of Everyday Things shows that good, usable design is possible. The…
I have been designing user interfaces since graduate school at Stanford, where I studied psychology and computer science. Over the five decades since then, I have designed many digital products and services, learning a lot about how to make them usable and useful. Two decades ago, I turned more towards sharing my knowledge and experience through writing (articles and books) and teaching (professionals and students). I’ve taught at Stanford University, Mills College, the University of Canterbury (New Zealand), the University of San Francisco, and at professional conferences and companies. Google invited me twice to speak in their Authors @ Google series, and ACM and SIGCHI have given me several awards.
I like this book because it fills a gap in the UI/UX design process: getting from requirements to a final design.
The title – UX Magic – is actually an insider joke among UI/UX designers: many software development managers believe expert UX designers somehow magically conjure up good designs from requirements. There’s nothing magic about it.
Instead, we use knowledge of human perception, cognition, and learning, task analysis, conceptual analysis, UX design guidelines, prototyping, and usability testing to narrow down and weed out design alternatives and progress towards good designs.
It takes conviction to title a user experience book that stands solidly on a cognitive science foundation as “Magic” but through the practice of the Semantic Interaction Design method this breakthrough book introduces, you will appear to many as possessing superhero UX powers. The Semantic IxD method is laser focused on transforming product requirements into experiences guaranteed to result in the minimum cognitive load with the smallest number of screens and fewest flow steps possible. An additional benefit it provides is a 10X speed increase at which designers can achieve these magical results. It provides an antidote to the expensive…
I have been designing user interfaces since graduate school at Stanford, where I studied psychology and computer science. Over the five decades since then, I have designed many digital products and services, learning a lot about how to make them usable and useful. Two decades ago, I turned more towards sharing my knowledge and experience through writing (articles and books) and teaching (professionals and students). I’ve taught at Stanford University, Mills College, the University of Canterbury (New Zealand), the University of San Francisco, and at professional conferences and companies. Google invited me twice to speak in their Authors @ Google series, and ACM and SIGCHI have given me several awards.
When people browse or search the Web for information, they don’t read; they scan, looking for anything matching their goal. Scan, click, scan, click, etc.
Most web designers include waaay too much text in their sites, slowing people down, frustrating poor readers (which unfortunately is a large percentage of the population). Most text on the Web is simply ignored.
I like Ginny’s book because it does a great job of driving that point home and explaining how to cut the text down to what is necessary. It has become a classic in the UX and Web design fields.
Web site design and development continues to become more sophisticated. An important part of this maturity originates with well-laid-out and well-written content. Ginny Redish is a world-renowned expert on information design and how to produce clear writing in plain language for the web. All of the invaluable information that she shared in the first edition is included with numerous new examples. New information on content strategy for web sites, search engine optimization (SEO), and social media make this once again the only book you need to own to optimize your writing for the web.
Defining and managing the requirements for a software system is hard! I’ve been interested in improving how projects handle their requirements for more than 35 years. I realized how important this was when I saw how many projects—including my own—struggled and failed when they neglected to build a solid foundation of well-understood and clearly communicated requirements. I’ve personally used nearly all of the techniques described in my book Software Requirements, and I got always better results when I applied those techniques. My books, articles, training courses, presentations, and videos on requirements have been helpful to thousands of business analysts worldwide for many years.
I recognized the value of use cases the first time I used them successfully on a project. Some years later I developed a 1-day training course on use cases. I read four of the most popular use case books then available, cover to cover, one right after the other. Use Cases: Requirements in Context did the best job of presenting a practical approach to applying the use case technique.
Shifting the requirements focus from system features to a usage-centric viewpoint provides many benefits, and use cases are the best way I’ve found to approach that. They provide an organizational structure for grouping related information relating to how users will interact with the system to perform tasks. This book describes a solid way to apply the use case technique.
This book describes how to gather and define software requirements using a process based on use cases. It shows systems analysts and designers how use cases can provide solutions to the most challenging requirements issues, resulting in effective, quality systems that meet the needs of users.
Use Cases, Second Edition: Requirements in Context describes a three-step method for establishing requirements-an iterative process that produces increasingly refined requirements. Drawing on their extensive, real-world experience, the authors offer a wealth of advice on use-case driven lifecycles, planning for change, and keeping on track. In addition, they include numerous detailed examples to illustrate…
Being able to understand and change reality through our knowledge and skill is literal magic. We’re building systems with so many exciting and unexpected properties that can be exploited and repurposed for both good and evil. I want to keep some of that magic and help people engineer – build great systems that make people’s lives better. I’ve been securing (and breaking) systems, from operating rooms to spaceships, from banks to self-driving cars for over 25 years. The biggest lesson I’ve learned is that if security is not infused from the start, we’re forced to rely on what ought to be our last lines of defense. This list helps you infuse security into your systems.
This book captures lessons from many authors at Google, some of whom I’ve worked with over the years. The chapters on availability (7, 8, 9) were a revelation to me. I had no idea how Google approaches the topic of resilience and recovery in their systems, and I now think of the whole topic very differently. The biggest takeaway is how to think about the design of systems.
Can a system be considered truly reliable if it isn't fundamentally secure? Or can it be considered secure if it's unreliable? Security is crucial to the design and operation of scalable systems in production, as it plays an important part in product quality, performance, and availability. In this book, experts from Google share best practices to help your organization design scalable and reliable systems that are fundamentally secure.
Two previous O'Reilly books from Google-Site Reliability Engineering and The Site Reliability Workbook-demonstrated how and why a commitment to the entire service lifecycle enables organizations to successfully build, deploy, monitor, and maintain…
There is a scene in the 1960 movie adaptation of The Time Traveler by HG Wells where the protagonist goes rapidly into the future as he watches a whole city spin into existence around him. That’s how I feel about my career. I started in 1994 and have watched UX grow into an incredible field! I’ve run my own business since 2008 focused exclusively on qualitative research consulting while also doing all sorts of exciting thought leadership activities – from writing to speaking to creating a number of courses on LinkedIn Learning – and I love to build my UX network too! I live in Silver Spring, Maryland.
There are a whole host of books about UX methods, but in our world of ever-advancing technology, there are few books that are really up to date with how to practice UX when the medium is no longer one-dimensional or even a physical product.
As AR and VR experiences are becoming more and more normal, I’ve appreciated being able to read a book that really captures the most recent evolution of UX methods towards a new virtual world of possibilities.
1. Provides a toolkit of templates for common VR interactions, as well as practical advice on when to use them and how to tailor them for specific use cases; 2. Includes case studies detailing the practical application of interaction theory discussed in each chapter; 3. Presents tables of guidelines for practicing VR developers, for reference during software development; 4. Covers procedures for Interface Evaluation - formulas and testing methodologies to ensure that VR interfaces are effective, efficient, engaging, error-tolerant, and easy to learn; 5. Non-linear organisation - chapters of the book on different concepts can be read to gain knowledge…
I’m a professional software developer for more than 22 years now. I’ve used many programming languages, platforms, frameworks, etc. throughout my career. However, the only constant for me personally was the practice of Test-Driven Development. I’ve never stopped learning about the principles and practices behind it, and it paid huge dividends throughout my career. I’m very humbled and grateful to be able to learn from all those amazing people over the years, that I decided to write a book on the topic. Giving back some of the knowledge that I gathered about TDD throughout 18+ years.
This is the most recent book I'm recommending, and it’s also more than just a book on Test-Driven Development. I often proclaim that Test-Driven Development and software design are two sides of the same coin. One cannot separate one from the other. So learning about Test-Driven Development also means that one has to learn about software design principles. This book teaches both. The first part of the book is all about Test-Driven Development, while the remainder of the book also touches on object calisthenics, refactoring, code smells, design patterns, the S.O.L.I.D. principles, connascence, the four elements of simple design, and much more. Whether you’re new to programming software, or whether you’re a seasoned developer, there’s much to learn from this book.
Delve deep into the various technical practices, principles, and values of Agile.
Key Features
Discover the essence of Agile software development and the key principles of software design
Explore the fundamental practices of Agile working, including test-driven development (TDD), refactoring, pair programming, and continuous integration
Learn and apply the four elements of simple designBook Description
The number of popular technical practices has grown exponentially in the last few years. Learning the common fundamental software development practices can help you become a better programmer. This book uses the term Agile as a wide umbrella and covers Agile principles and practices, as…
Markus Gärtner works as Organizational Design Consultant, Certified Scrum Trainer, and Agile Coach for it-agile GmbH, Hamburg, Germany. Markus, author of ATDD by Example - A Practical Guide to Acceptance Test-Driven Development, a student of the work of Jerry Weinberg, received the Most Influential Agile Testing Professional Person Award in 2013 and contributes to the Softwerkskammer, the German Software Craft movement. Markus regularly presents at Agile and testing conferences all over the globe, as well as dedicating himself to writing about agile software development, software craft, and software testing, foremost in an Agile context.
“Good agile testing is good context-driven testing applied in an agile context.”
I recall reading through the authors’ lessons on software testing at about the same time I dived into more agile topics. Lessons Learned in Software Testing helped me keep the connection towards more traditional contexts – more so since I was still working in a more traditional context.
With their more than 100 lessons some of them applied to me, others did not. I am sure, other readers will find the same in their context.
Most companies developing software employ something they call "Agile." But there's widespread misunderstanding of what Agile is and how to use it. If you want to improve your software development team's agility, this comprehensive guidebook's clear, concrete, and detailed guidance explains what to do and why, and when to make trade-offs.
In this thorough update of the classic Agile how-to guide, James Shore provides no-nonsense advice on Agile adoption, planning, development, delivery, and management taken from over two decades of Agile experience. He brings the latest ideas from Extreme Programming, Scrum, Lean, DevOps, and more into a cohesive whole. Learn…
Defining and managing the requirements for a software system is hard! I’ve been interested in improving how projects handle their requirements for more than 35 years. I realized how important this was when I saw how many projects—including my own—struggled and failed when they neglected to build a solid foundation of well-understood and clearly communicated requirements. I’ve personally used nearly all of the techniques described in my book Software Requirements, and I got always better results when I applied those techniques. My books, articles, training courses, presentations, and videos on requirements have been helpful to thousands of business analysts worldwide for many years.
Many agile projects employ user stories as a way to represent requirements rather than a more traditional approach combining use cases and functional requirements. I favor the latter approach for several reasons. Nonetheless, user stories are well established in the agile development world, and if you wish to learn about them, there’s no better author to read than Mike Cohn. Cohn describes how to craft user stories well and how they fit into the agile development process.
Thoroughly reviewed and eagerly anticipated by the agile community, User Stories Applied offers a requirements process that saves time, eliminates rework, and leads directly to better software.
The best way to build software that meets users' needs is to begin with "user stories": simple, clear, brief descriptions of functionality that will be valuable to real users. In User Stories Applied, Mike Cohn provides you with a front-to-back blueprint for writing these user stories and weaving them into your development lifecycle.
You'll learn what makes a great user story, and what makes a bad one. You'll discover practical ways to gather…
