Глава 1
When One Person Must Champion the User's Voice
Imagine being the lone advocate for users in an organization that's racing to launch products without ever asking what customers actually need. You're constantly torn between perfectionism and pragmatism, between educating colleagues and getting work done. This is the reality for countless professionals who find themselves as a "UX team of one" - a position that's both challenging and uniquely powerful. Leah Buley's groundbreaking guide has become essential reading for these solo practitioners since its 2013 publication, earning praise from design leaders at companies like Google and Facebook. The book resonated so strongly that it sparked a movement of UX professionals who realized they weren't alone in their struggles. Drawing from her experience transitioning from a solo practitioner to a design strategist at Intuit, Buley offers a roadmap that transforms isolation into influence through practical methods that work in real-world constraints.
Глава 2
The Evolving Definition of User Experience
User experience is simultaneously a professional practice and a resulting outcome - the overall effect created when someone interacts with a product or service. It's what people describe when they say they "love" or "hate" using something, or find it "intuitive" or "frustrating." This concept has become increasingly important as technology mediates more aspects of our daily lives.
The field has deep historical roots stretching back to the machine age. Early industrial pioneers like Frederick Taylor and Henry Ford focused on efficiency but were criticized for dehumanizing workers. By mid-century, human factors research emerged, particularly through aviation studies during World War II. Toyota's Production System introduced "respect for people" by involving workers in process improvement, while industrial designer Henry Dreyfuss championed human-centered design in his 1955 book "Designing for People." Meanwhile, cognitive scientists explored human-computer interaction, with Xerox PARC developing foundational UI elements in the 1970s. The term "user experience" itself originated at Apple in the early 1990s when Donald Norman wanted a broader term than "human interface" to encompass all aspects of a person's interaction with a system.
Today's UX professionals come from diverse backgrounds - web designers who've witnessed user interactions firsthand, editors who understand reader needs, graphic designers who create meaningful visuals, researchers from sociology and psychology who understand human behavior, engineers who iterate between making and testing, and product managers who bridge different perspectives. What unites them is the belief that user experience makes the difference between products that must be suffered through versus those that delight.
As a UX team of one, your first challenge is often explaining what user experience is and why it matters. Having a clear definition supported by concrete examples helps illustrate the complexity of user experience and what elements must be executed well to create positive interactions.
Глава 3
Starting Your UX Journey Without Permission
Many UX professionals begin by crossing over from adjacent fields like engineering, visual design, or project management. These transitions often feel like revelations, transforming practitioners into enthusiastic ambassadors for user-centered approaches. Whether UX becomes your full-time focus or just part of your role, getting started requires just four simple steps.
First, familiarize yourself with the UX toolkit. While there's no certified process that all practitioners follow, the field has developed relatively standard activities and deliverables. Various models illustrate these differently - from Todd Zaki Warfel's sequential overview to David Armano's conceptual phases (Uncover > Define > Ideate > Build > Design). Understanding the full range of options helps you select which are most valuable for your specific context.
Second, establish a point of view on what needs improvement. You don't need permission to be a UX team of one - you can infuse user-centered philosophy into your current work and find small opportunities to start. Rather than requesting a wholesale role change upfront, begin with under-the-radar UX activities and build momentum from positive results. Find the "low-hanging fruit" - those parts of the product everyone knows need improvement - and plan your approach respectfully.
Third, get to know your users. They're the people who will experience the consequences of your design decisions firsthand. Great products become almost invisible, allowing users to achieve flow where they're focused on their goals rather than the interface. Research shows that the amount of face-time teams have with end users directly impacts product quality. As a UX team of one, gather available user data, create proto-personas to humanize users, and conduct guerrilla research even without formal support.
Finally, start designing. People expect UX professionals to produce designs that are undeniably better - lovelier, simpler, more intuitive. This can be challenging for those without formal design backgrounds. The key is understanding user needs well enough to discover elegant solutions beyond the obvious ones. Rather than jumping straight into software tools, adopt techniques from classically trained designers: sketch your ideas first, enlist colleagues to generate design ideas through collaborative sessions, and learn from other successful products by creating inspiration libraries.
Remember that even a little time spent investigating users' needs will lead to insights so important and obvious that they create their own momentum to get you started.
Глава 4
Building Relationships, Not Just Deliverables
Dedicated UX professionals often struggle to get others to support their approach, especially when it conflicts with executive decisions or time and budget constraints. Organizations new to UX may show inconsistent commitment, leaving teams of one with varying levels of support. Success requires handling the "squishier" side of being a UX team of one: navigating the people and organizational issues that impact your work through building trust, setting expectations, and demonstrating progress.
While many UX teams of one crave more process, focusing too much on process can distract from building relationships, which are more crucial-especially when UX is still establishing itself. The most successful teams of one rely on mindset over methods, following key principles of engagement:
1. Invite People In: Overworked UX professionals often isolate themselves, thinking they're being productive, but this can make them seem unapproachable. Daily opportunities exist to invite non-UX colleagues into the world of user experience. Even colleagues with inconsistent support can become UX advocates if you treat them as partners.
2. Make Things Together: Work can become adversarial when meetings lead to endless debates about how to accomplish goals. Break this cycle by making ideas tangible-quickly sketching examples, whiteboarding, or saying "Can we draw that out?" This transforms abstract discussions into constructive evolution of shared vision.
3. Truly Listen: Successful UX teams of one see themselves as facilitators of ideas held by an entire cross-functional team. Their job is creating design solutions that reconcile tensions and produce satisfying user experiences. This requires genuine interest in others' viewpoints and active engagement to understand perspectives.
4. Know When It's Good Enough: UX work is never truly finished-like sweeping a floor, you eventually reach a point of diminishing returns. By accepting imperfection and acknowledging that others will have good ideas for improvement, you develop a sense for what's "good enough" to convey the basic idea or start a productive conversation.
When facing skepticism about UX work, reframe objections as opportunities for honest conversation. Common objections include misconceptions that UX is "just web design" (when it actually impacts all touchpoints), confusion with market research (design research focuses on how rather than what), concerns about cost (prevention is cheaper than correction), worries about timeline impacts (UX can save time by addressing issues early), and territorial concerns from other departments (UX serves as connective tissue between specialized roles).
Remember that designing great products is only half the battle-the other half is managing "people stuff." Building support, addressing objections, untangling competing agendas, and rallying colleagues around new directions are essential skills that require a collaborative, curious mindset rather than defensiveness.
Глава 5
Growing Your Practice and Career
For UX teams of one, establishing personal growth strategies is crucial for maintaining passion and motivation regardless of colleagues' attitudes toward UX. These strategies can develop skills that enhance your practice while advancing organizational commitment to user experience.
Having a community of like-minded professionals provides learning opportunities, mentorship, shared experiences, commiseration, and potential job connections. Professional associations like IXDA (Interaction Design Association), SIGCHI (Special Interest Group of Computer-Human Interaction), the IA Institute, and UXPA (User Experience Professionals' Association) offer benefits like job listings, networking, and event discounts. Discussion lists and online communities provide rich resources of first-hand knowledge from practicing professionals, while local meet-ups create professional connections and opportunities to share experiences.
Continual growth is essential as technology evolves rapidly, requiring adaptability across different interfaces and contexts. Online resources like UX Booth, UX Matters, A List Apart, and Smashing Magazine provide curated content from fellow professionals. Books remain an excellent resource, with publishers like Rosenfeld Media, New Riders, O'Reilly Media, and A Book Apart offering specialized UX titles. Attending at least one conference yearly provides concentrated inspiration, information, and networking in a compressed timeframe.
When you've exhausted learning opportunities in your current position, it's important to take charge of your career direction. Consider whether you prefer to remain a solo practitioner or join a larger UX team, each offering different benefits. Decide if you want to work inside an organization (owning product evolution and navigating organizational politics) or consult with various organizations (tackling diverse challenges without always seeing them through to market). Evaluate whether you prefer steady employment or independence with its freedom and business development responsibilities. With UX skills in growing demand, be deliberate and selective about your career growth.
Глава 6
Practical Methods for Planning and Discovery
The foundation of successful UX work involves getting focused, organized, and establishing agreement with stakeholders on priorities and goals before diving into product changes. Several methods can help practitioners determine what needs improvement, create high-level vision, identify market opportunities, and develop practical work plans.
The UX Questionnaire is a deceptively simple yet powerful tool that helps assess understanding of a product and identify potential issues early. Taking just 1-2 hours to complete, this method involves asking key questions about team structure, project goals, target users, product strategy, core tasks, success metrics, key dates, and potential risks. When product design lacks clear purpose or audience, this questionnaire helps spot red flags before they derail the design process.
A UX Project Plan outlines the specific UX activities needed to design a great user experience, distinct from the broader project plan. This method proves especially valuable for projects spanning more than a few weeks, forcing practitioners to thoughtfully structure their approach. The plan helps set expectations with non-UX colleagues who may be unfamiliar with UX processes and deliverables.
The Listening Tour involves setting up time to gather information about colleagues' priorities and goals to identify opportunities where user-centered design practices might help. Similar to stakeholder interviews, these one-on-one conversations help UX teams of one understand what matters to teammates and formulate how UX can support those objectives. The insights reveal how much people already value human-centered products or what cautions they may harbor.
An Opportunity Workshop helps quickly assess what UX improvements are needed, prioritize them from a business perspective, and determine what will most impact users. This 3-4 hour process brings together a cross-functional team to identify issues in the current product. Participants write problems, missed opportunities, and important product elements on sticky notes, then share them with the group. The team also documents product strengths to maintain balance.
These planning and discovery methods help clarify project goals, improvement opportunities, and how to get started. At their core, they reveal colleagues' expectations for your product while giving you space to consider your own vision for creating a satisfying user experience.
Глава 7
Research Methods That Work in the Real World
When working with a product daily, you risk becoming too familiar with it, accepting all the pragmatic trade-offs that make a complex product possible. However, users have no incentive to apologize for your product's shortcomings-they can simply go elsewhere if it doesn't meet their needs. The best way to provide satisfying experiences is to design with users in mind, investigating what they need, want, and experience.
The key requirement of user research is simple but not always easy: you must actually talk to users. Even just two or three conversations are better than none. Guerilla user research prioritizes learning from users firsthand by whatever means necessary-from phone calls to approaching people in coffee shops. When conducting guerilla research, go into the user's environment whenever possible, documenting with photos or videos if permitted. Use open-ended questions that start with "why" and "how" rather than "did" or "was." Ask about past events chronologically to help users recall specific details.
Proto-personas help you think empathetically about customers without requiring exhaustive research. Unlike traditional personas that demand extensive user research, proto-personas can be created quickly using whatever insights you have available-even well-informed team hunches. They stimulate user-oriented thinking while requiring less investment. To create proto-personas, gather a cross-functional team, discuss what they know about users, and develop personas complete with names, locations, occupations, frustrations, and daily activities.
A heuristic markup helps you understand the user's journey through your product from beginning to end. Unlike formal heuristic evaluations that check compliance with established standards, heuristic markups focus on your gut reactions as you move through the experience. Start at the very beginning of the user journey-whether that's a web search, app store visit, or opening a product box-and work through the entire experience, taking screenshots and recording your thoughts and reactions in real time.
A comparative assessment evaluates products and services your customers likely encounter daily, not just direct competitors. This helps you understand the standards and expectations users bring to your product based on their broader experiences. Focus on overall experience quality rather than mere feature parity, which can lead to bloated products.
If time is limited, prioritize Guerilla User Research above all else. This method not only reveals areas for product improvement but gives you crucial insight into who your users are and what truly matters to them-the foundation of good user experience design.
Глава 8
From Ideas to Implementation: Design Methods That Engage
The design process starts messy before reaching clarity. Designer Damien Newman's "squiggle" illustration perfectly captures this journey from initial uncertainty to focused solution. For UX teams of one, the key is using iterative design with structured activities that engage non-UX colleagues as partners in the process.
A design brief documents working assumptions about the optimal product design and articulates the vision for the user experience. Unlike a project brief that focuses on overall goals, the design brief connects the dots on how that vision will be implemented. It should answer five key questions: the focus of the design work, the target audience, core features and functions, the desired feeling or personality of the product, and any restrictions or expectations that must be addressed.
Design principles articulate the characteristics that should give a product a memorable personality or feeling. They help clarify what personality is right for your product and ensure consistency throughout the design process. Good principles should be specific enough that they wouldn't apply to competitors' products and should go beyond generic statements about being "user-friendly."
Sketching is the point in the design process when you begin exploring different potential forms for your design. Sketches are vital because they're cheap and quick to produce, allowing you to iterate and refine ideas before moving to more time-intensive wireframes or prototypes. They help you explore multiple directions, forestall perfectionism, invite conceptual feedback rather than detailed criticism, engage team members, and can be done by anyone.
A sketchboard is a way to display sketches and facilitate group conversation around them. Think of it as a big poster that assembles your sketches and initial ideas for the system design. Sketchboards help you think beyond individual screens to envision how users will move through multiple parts of a product. They're interesting to look at (drawing people into your process), cheap and quick to assemble, and provide a canvas for layering new ideas and recording notes, questions, and priorities.
Task flows help you envision how people actually use your product-not screen by screen, but through realistic, sometimes erratic journeys. They reveal how the experience unfolds over time and help identify where experiences break down between screens or steps. Keep task flows lightweight and focused on specific scenarios rather than trying to map an entire system at once.
Wireframes are skeletal depictions of what a product should look like-the meat and potatoes of user experience design. Like a skeleton with many bones, wireframes show how the whole system hangs together to create a complete, interconnected structure. They represent black-and-white schematics that detail information layout, navigation, and functionality screen-by-screen.
Глава 9
Testing and Evangelizing Your Work
After designing the user experience, the next crucial phase involves testing and validating your work to ensure it meets user needs and business requirements. Falling in love with your own ideas is a constant risk in design. While being proud of your work is great, you should always remain curious about what isn't working rather than what is.
A Black Hat session provides a structured way to get critical feedback on designs. This versatile method requires minimal preparation-just people, designs, Post-it notes, and time. It can be used whenever helpful, even during difficult design reviews, and you can focus feedback on specific topics like technical feasibility, content, usability, or conversion.
A quick-and-dirty usability test lets you get rapid feedback by showing your design to anyone available, foregoing rigor and perfectionism. While testing with actual end-users is ideal, this method provides a gut check on whether a design works by getting a fresh perspective. You simply find volunteers, ask them how they think the design works for specific tasks, find a few more volunteers to repeat the process, then iterate based on what you learn.
A five-second test quickly assesses information hierarchy by showing users a screen for just five seconds, then asking what they remember. This reveals how clear and memorable a specific moment in the product is, and simulates how people often use products in distracted states.
Beyond designing great user experiences, a UX team of one must build awareness of UX within their organization. Several methods can help create awareness and provoke conversations that identify opportunities, build support, and demonstrate how UX skills can help others:
Bathroom UX builds awareness by posting bite-sized UX information in captive-attention locations like bathroom stalls, elevators, and hallways. This simple technique involves creating flyers that promote UX concepts, showcase recent work, or direct people to resources.
Mini case studies summarize your UX work into compelling, bite-sized stories that are easy to share. By focusing on concise narratives that fit on a single page, you create memorable examples that others can quickly understand.
A peer-to-peer learning community mobilizes support and knowledge among interested colleagues, even when you're the only dedicated UX practitioner. This approach creates a voluntary forum where everyone is a learner rather than an expert, fostering a participatory attitude that welcomes people into UX discussions.
Pyramid evangelism builds relationships at every level of the organizational pyramid-base, middle, and top. Rather than trying to win executives over in one presentation, build a network of supporters throughout the organization.
Глава 10
The Future of UX Teams of One
The UX field has evolved dramatically since this book was conceived in 2008. Web and software design have given way to mobile and app design, with emerging technologies like augmented reality, voice interfaces, and artificial intelligence reshaping how we think about user experiences. Digital experiences now span multiple channels and devices, embedded in our homes, cars, and wearables - from smart thermostats and voice assistants to fitness trackers and autonomous vehicles. The concept of a stand-alone user experience seems outdated as products exist in interconnected ecosystems, requiring practitioners to think holistically about user journeys across platforms and touchpoints.
These changes create more opportunities for UX teams of one who can lead multifunctional teams toward better designs. The complexity of modern digital products demands collaboration across disciplines, including developers, product managers, data scientists, and business stakeholders. UX practitioners must now understand not just interface design but also system thinking, service design, and the business implications of their decisions.
Design thrives on constraints - whether aesthetic, technological, or resource-driven. For UX teams of one, these constraints often come from the people you work with, including budget limitations, technical feasibility, and organizational priorities. Successful practitioners recognize that colleagues not only limit possibilities but also illuminate opportunities and provide complementary perspectives. When handled patiently, these relationships help you make greater impact than you could alone, turning potential roadblocks into stepping stones for innovation.
The secret agenda of the UX team of one is to empower you to engage non-UX colleagues as allies in creating better human-centered experiences. This means developing skills in communication, facilitation, and change management alongside traditional UX capabilities. Beyond methods and tools, the goal is to inspire reflection on the changes you want to make and the future you want to create through your work - whether that's improving product usability, advocating for accessibility, or driving organizational transformation.
Take five minutes to write down 3-5 things you want to be true about your work in five years. Consider what kind of work you want to do (strategic or tactical, specialized or generalist), what team you want to work with (startup or enterprise, remote or local), what products you want to create (consumer or enterprise, digital or physical), what success stories you want to have, who your allies should be (designers, developers, executives), what education you need (formal degrees, certifications, mentorship), how you want to work (collaborative or independent, structured or flexible), and what culture you want to be part of (innovative, user-centered, data-driven). Often, simply acknowledging what matters to you will propel you toward achieving it much sooner than you'd expect, as clarity of purpose drives decisive action.
