Читать книгу The User Experience Team of One - Leah Buley - Страница 5
ОглавлениеHOW TO USE THIS BOOK
Who Should Read This Book?
While many people are attracted to the field of user experience because they want to be champions for users, simply loving users doesn’t guarantee that you’ll be a successful user experience team of one. UX teams of one are people who love users and also make sure that designs get tested, business people’s questions are answered, design problems receive an appropriate amount of creative exploration, UX specifications are implemented according to plan, the product is continually monitored and improved upon, and support for UX is ever growing. And they do it all without a roadmap or a blueprint, with the help of people who may or may not be active supporters of UX themselves.
This book is for anyone who is interested in taking on the challenging and rewarding work of spreading a user-centered mindset to new places where it’s never been before. While this book is intended to be approachable for anyone who picks it up, it was written with two particular audiences in mind.
• One core audience for this book is people who are already working on product teams in another role but are interested in transitioning into the field of UX. If that sounds like you, that may mean that you’ve never thought of yourself as a UX professional before, and you’re interested in crossing over into the field, either as a main role or part of an adjacent role. For this type of reader, Chapters 1 and 2 are a must.
• Another core audience for this book is more experienced practitioners who are seeking ways to work more effectively within a cross-functional team. For this type of reader, Chapters 3 and 4 are highly recommended.
What’s in This Book?
The user experience team of one ethos is equal parts philosophy and practice (see Figure 0.1). It focuses on having the right attitude, seeking out opportunities, being patient and inclusive, and doing the best work you can. Between philosophy and practice, I’ll cover not just guiding principles, but also the nuts and bolts of how to successfully run a UX project as a team of one.
Accordingly, this book is organized in two parts: Part I is philosophy, and Part II is practice.
FIGURE 0.1 Being a successful UX team of one is equal parts thought and action, head and hand, philosophy and practice.
Part I, “Philosophy,” is a frank walk-through of the UX team of one’s concerns, from start to finish. In this section, I’ll explain what it means to be a UX team of one, how to establish a successful foundation, how to grow yourself and your career, and how to involve others and build support for UX along the way.
• Chapter 1, “UX 101,” gives an overview of what UX is, how it came to be, and what it takes to be a UX practitioner.
• Chapter 2, “Getting Started,” focuses on how to begin, including the fundamentals of user research and design for the new and aspiring UX team of one.
• Chapter 3, “Building Support for Your Work,” addresses some of the most challenging parts of life as a team of one: how to build support and do great work in spite of real-world organizational and interpersonal constraints.
• Chapter 4, “Growing Yourself and Your Career,” is a blueprint for thriving and flourishing as you grow yourself and your career in user experience.
In Part II, “Practice,” I’ll focus on the nuts and bolts of user experience work. This half of the book is intended to function as a ready reference, full of practical methods that have been selected and, in some cases, adapted to fit the realities of a UX team-of-one’s situation. What is this reality? Most importantly, teams of one must rely heavily on their non-UX colleagues to help them get work done. That means there is a preference here for methods that can be done in a quick-and-dirty fashion, and an even greater bias toward methods that invite collaboration and cross-functional participation. In some cases, these methods may already be familiar to you, but the approach and tips are adapted for the work of a team of one.
• Chapter 5, “Planning and Discovery Methods,” helps you set up a UX project for success. It includes planning and discovery of the team’s requirements and expectations. It also covers techniques for establishing a shared UX strategy with the team.
• Chapter 6, “Research Methods,” is all about research. This includes research with users, the centerpiece of a UX practice, as well as research into competitors and best practices.
• Chapter 7, “Design Methods,” covers methods and techniques for inclusive and participatory user experience design.
• Chapter 8, “Testing and Validation Methods,” provides methods for validating that your strategy, research, and design work has led you in the right direction.
• Chapter 9, “Evangelism Methods,” brings our discussion of philosophy and practice full circle, and finishes up with approaches for building support and awareness of UX throughout your organization.
• Chapter 10, “What’s Next,” closes with a personal challenge for you to think critically about where you’re taking your work in UX and how it aligns with the growth of the field overall.
Parts I and II are heavily cross-referenced, so methods that are described in detail in Part II are explained in context in Part I and vice versa.
The book is designed so that you can dip in and out as needed when you face a specific challenge or are working at a particular point in a project. That said, reading Part I from start to finish will give you a sense of the common growth path for a UX team of one. And reading Part II sequentially will give you a complete plan for how to run a UX project.
What Comes with This Book?
This book’s companion website (rosenfeldmedia.com/books/ux-team-of-one/) contains some templates, discussion, and additional content. The book’s diagrams and other illustrations are available under a Creative Commons license (when possible) for you to download and include in your own presentations. You can find these on Flickr at www.flickr.com/photos/rosenfeldmedia/sets/.