Redr · Study Guide
The User Experience Team of One
A Research and Design Survival Guide
Leah Buley
Unofficial AI-assisted study guide. Not affiliated with or endorsed by the author or publisher. For educational use — supplements, not replaces, the original work.
Contents
- 01UX 101
- 02Getting Started
- 03Building Support for Your Work
- 04Growing Yourself and Your Career
- 05Planning and Discovery Methods
- 06Research Methods
- 07Design Methods
- 08Testing and Validation Methods
- 09Evangelism Methods
- 10What's Next?
- Part 01 · Philosophy01UX 10102Getting Started03Building Support for Your Work04Growing Yourself and Your Career
- Part 02 · Methods05Planning and Discovery Methods06Research Methods07Design Methods08Testing and Validation Methods09Evangelism Methods10What's Next?
Part 01
Philosophy
Ch. 1–4
UX 101
A crash course on what user experience actually is, where it came from, and what "team of one" means. Buley defines UX as the sum of every interaction a person has with a product or service, and frames the solo practitioner as whoever advocates for users inside an organization that has few or no other UX resources.
UX as Cumulative Effect, Not a Screen
User experience is the total of every touchpoint and impression a person has with a product or service. That means UX is much broader than UI — it includes onboarding, support, packaging, tone, and the silence between interactions. Treating UX as "what the screen looks like" misses where most of the experience actually happens.
The Team of One Archetype
A UX team of one is anyone who is the lone (or primary) advocate for user-centered design inside their organization. The role is defined by responsibility, not by headcount or job title — a product manager, an engineer, or a marketer can all play it. What matters is that someone is making sure the user has a seat at the decision table.
The UX Umbrella of Subdisciplines
UX is an umbrella covering interaction design, information architecture, visual/UI design, user research, content strategy, and usability. In a larger team each of these is a specialty; the team of one has to span all of them. Knowing the umbrella helps you decide which hat to wear at any given moment.
Roots in Human Factors and HCI
Modern UX inherits from ergonomics, cognitive psychology, industrial design, and HCI. Understanding that lineage gives you the vocabulary to defend the practice when colleagues treat it as decoration. UX isn't a new fashion — it's a recombination of older, well-established disciplines applied to digital products.
The Economic Case for UX
Fixing a problem in design costs roughly 10x less than fixing it in code, and 100x less than fixing it after release. This multiplier is the business argument the solo practitioner returns to again and again. It reframes UX from "nice to have" into "compounding cost avoidance."
Title Soup
The field is full of overlapping acronyms — UX, XD, UE, IxD, IA — and the label on your business card matters less than the user-centered intent of the work. Don't get stuck arguing titles. Focus on whether decisions in the room are being made with users in mind.
- User Experience (UX)
- The total effect of a person's interactions with and perceptions of a product or service.
- Interaction Design (IxD)
- The design of how a user and product behave in dialogue over time — flows, states, gestures, feedback.
- Information Architecture (IA)
- The structural design of shared information environments — how content is organized, labeled, and made findable.
- User Research
- Learning about users' goals, behaviors, and contexts through qualitative and quantitative methods.
- Content Strategy
- Planning the creation, delivery, and governance of useful, usable content across an experience.
- Usability
- The degree to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction.
- HCI
- Human-Computer Interaction — the academic discipline studying how people interact with computers, one of UX's direct ancestors.
- UI
- User Interface — the surface layer of a product (typography, color, controls) that users directly see and touch.
Multiple choice
According to Buley, what is the most accurate definition of user experience?
Multiple choice
Which of the following best describes a UX team of one?
True / False
Modern UX is a brand-new discipline invented alongside the web, with no meaningful roots in older fields.
Spot the issue
An engineering team finds a usability problem after shipping a feature and decides to wait for the next quarterly release to fix it, arguing that post-release fixes are roughly equivalent in cost to design-time fixes. What's the main issue with this reasoning?
Getting Started
Before charging into work, take stock of yourself, your team, and your organization. Buley walks through self-assessment of skills, sizing up UX maturity where you work, and choosing the right starting moves so that you spend less energy on heavyweight process and more on small wins and relationships.
Self-Assessment of Your UX Skill Profile
Inventory your strengths across research, IxD, IA, visual design, and content. Knowing which hats you wear well and which you'll need to compensate for, learn, or borrow stops you from accidentally over-promising. The team of one's most dangerous bias is pretending to be equally strong across every discipline.
The T-Shaped Practitioner
A team of one needs broad competence across all UX disciplines plus deep expertise in at least one. The breadth of the "T" lets you cover gaps; the stem gives you credibility and a home base. Pure generalists struggle to be taken seriously, and pure specialists can't survive solo.
UX Maturity Assessment
Before picking methods, gauge where your organization sits on a maturity spectrum — from "what's UX?" to embedded user-centered culture. The right next move depends entirely on this starting point. A heuristic review fits a low-maturity org; a strategic workshop fits a high-maturity one.
Start Small, Prove Value, Then Scale
Open with low-cost, high-visibility activities that demonstrate impact in days, not months — a quick heuristic review, a hallway usability test, a one-page persona. Big-bang process rollouts almost always fail when you're alone. Small visible wins compound credibility faster than process documentation does.
If You Can Only Do One Thing
A recurring frame across the book: when time and political capital are scarce, pick the single highest-leverage activity rather than running a full process. This forces ruthless prioritization and protects you from spreading thin across half-finished methods.
Constraints Are a Designer's Friend
Limited time, budget, and headcount force focus. The team of one should treat scarcity as a design constraint to be worked with, not a deficit to be lamented. A six-week deadline produces sharper decisions than a six-month one.
Methods as Trojan Horses
Familiar deliverables — wireframes, project briefs, simple personas — are vehicles for sneaking UX thinking into organizations that aren't ready to "buy UX" as a process. People accept a wireframe; they resist a "design ops transformation." Wrap the practice in artifacts the org already understands.
- UX Maturity
- How developed an organization's UX practice is, from no awareness to fully integrated culture.
- T-Shaped Skills
- A skill profile with broad competence across many disciplines plus deep expertise in one.
- Heuristic Evaluation
- A lightweight expert review of an interface against accepted usability principles.
- Project Brief
- A short shared document capturing goals, users, scope, success criteria, and constraints.
- Stakeholder
- Anyone with a vested interest in a project — execs, PMs, engineers, support, marketing, or users.
- Satisficing
- Accepting a "good enough" solution instead of an optimal one — an essential mindset under constraint.
- Quick Win
- A small, fast piece of work that produces visible value early and builds credibility for bigger UX investment.
- Deliverable
- A tangible artifact (wireframe, persona, prototype, report) that communicates UX decisions.
Multiple choice
What is the T-shape in "T-shaped practitioner" meant to represent?
Multiple choice
Before picking which UX methods to deploy, what does Buley advise the team of one to assess first?
True / False
The best opening move for a solo UX practitioner in a new organization is to roll out a comprehensive, formal UX process across the entire team.
Spot the issue
A new team-of-one designer at a skeptical company proposes a "design ops transformation initiative" in week one. Leadership balks. What's the most likely problem with this approach?
Building Support for Your Work
The biggest pain point of solo UX practice is getting other people to care, buy in, and let you do the work. Buley argues that leverage comes less from process and deliverables than from relationships, and she lays out principles of engagement plus tactics for bringing skeptical colleagues along on the journey rather than fighting them for permission.
Relationships Over Process
Heavy process is a distraction when you're a team of one. The real leverage is the trust you build with stakeholders, not how rigorously you follow a methodology. A respected practitioner gets to skip steps a process-perfect one isn't allowed to take.
Bring Them on the Journey
Don't win arguments — co-create. Stakeholders who help shape research questions and design decisions become advocates for the outcome instead of critics of it. Participation produces ownership; arguments produce resentment.
Invite People In
A core engagement principle: make UX activities open and approachable so non-UX colleagues can participate. Sitting in on interviews, sketching alongside you, or marking up a wall display turns spectators into stakeholders. Closed-door UX work breeds suspicion.
Truly Listen
Before pitching UX, do a listening tour of stakeholders to learn their goals, pressures, and fears. You can't build support for solutions to problems you haven't actually heard. Most resistance to UX is resistance to a perceived takeover, which goes away once people feel understood.
Speak the Language of Your Audience
Translate UX value into the metrics each stakeholder cares about — revenue and risk for execs, velocity and clarity for engineers, conversion and retention for product. "Better usability" doesn't sell; "5% fewer support tickets" does. Translation is half the evangelism job.
The Alternative Close
When you need a yes, offer two acceptable options ("we can do a 5-person test or a 10-person test") instead of asking permission ("can I do research?"). This reframes the conversation from whether to how, and it's almost impossible to refuse without sounding obstructionist.
Pyramid Evangelism
Cultivate allies at every level of the org chart — peers, middle managers, executives — because a champion at one level isn't enough to keep UX work funded and protected when leadership changes. A broad pyramid of supporters is more resilient than a tall stack resting on one sponsor.
- Listening Tour
- A series of stakeholder interviews conducted early to map the organizational landscape before proposing UX work.
- Stakeholder Interview
- A structured 1:1 conversation with someone invested in the project to surface goals, concerns, and constraints.
- Evangelism
- The ongoing practice of building awareness, support, and demand for UX inside an organization.
- Pyramid Evangelism
- Building UX supporters at every level of the org hierarchy, not just at the top.
- Alternative Close
- A persuasion technique offering two acceptable choices instead of a yes/no question.
- Co-creation
- Designing alongside stakeholders and users rather than for them, generating buy-in through participation.
- Black Hat Session
- A structured critique format that invites colleagues to surface problems with a design without it becoming personal.
- Bathroom UX
- A guerrilla evangelism tactic of posting bite-sized UX facts in high-attention low-competition places to raise ambient awareness.
Multiple choice
You need stakeholder buy-in for research and want to maximize the chance of a yes. Which framing does Buley recommend?
Multiple choice
Why does Buley argue against betting all your evangelism energy on a single executive sponsor?
Multiple choice
Buley argues that the real source of leverage for a team of one is not heavy process but ____.
Spot the issue
A team-of-one designer keeps pitching executives on "better usability" and gets nowhere, even though the same execs greenlight engineering proposals framed around uptime and revenue. What principle is being violated?
Growing Yourself and Your Career
Buley closes Part I by zooming out from the current job to the long arc of a UX career. She covers how to keep learning when there's no senior designer to mentor you, how to choose between in-house and consulting paths, how to build a portfolio that travels, and how to plug into the wider community so that being a team of one at work doesn't mean being a team of one in the field.
Combat Isolation Through Community
A solo practitioner without colleagues to learn from will plateau. Deliberately joining UX meetups, professional groups (IxDA, UXPA), conferences, and online communities is professional development, not a perk. The most reliable predictor of stagnation as a team of one is having no peers outside the office.
Find a Mentor (or Several)
Because you likely don't have a senior UX person at work, source mentorship externally — former colleagues, conference contacts, or peers slightly ahead of you on the path. One mentor is good; a small portfolio of mentors covering different facets of the craft is better.
Build a Portfolio That Tells a Story
A UX portfolio isn't a gallery of screens — it's a set of case studies showing problem, process, decisions, trade-offs, and outcomes. Polish on a single final mockup means little. Hiring managers and clients want to see how you think, which means showing the messy middle.
In-House vs. Consulting vs. Agency
Each path offers different trade-offs: depth of context vs. breadth of exposure, stability vs. variety, ownership vs. independence. The team of one should consciously pick a setting that matches their growth goals at this career stage rather than drift into one by default.
Specialist vs. Generalist Trajectory
At some point you'll choose whether to deepen into one craft (research, IxD, content) or stay broad as a generalist. Both are valid, but drifting into one by accident is the failure mode. Periodically audit which way the work is pulling you and decide whether you want to go there.
Personal Brand and Visibility
Writing, speaking, and sharing work publicly grows your influence inside your company and across the industry. It also creates an external safety net when internal politics turn against UX. A visible practitioner finds the next role; an invisible one waits to be found.
Know When It's Time to Leave
Career growth sometimes requires changing organizations. Leaving is a normal, even healthy move when the current role no longer offers room to grow. The team of one is especially prone to outgrowing their environment — recognize the signal instead of suppressing it.
- Community of Practice
- A group of professionals who share a craft and learn from each other through ongoing interaction.
- Mentor
- A more experienced practitioner who provides guidance, feedback, and perspective on your work and career.
- Portfolio
- A curated collection of case studies that communicates how you think and work.
- Case Study
- A narrative portfolio piece showing problem, approach, key decisions, and outcome — not just final visuals.
- Generalist
- A practitioner with broad competence across multiple UX disciplines, typical of the team-of-one role.
- Specialist
- A practitioner with deep expertise in one UX subdiscipline (research, content strategy, IA, etc.).
- Professional Association
- Industry bodies such as IxDA and UXPA that offer events, publications, and community.
- Personal Brand
- The reputation you cultivate as a practitioner through public work — writing, speaking, side projects, shared portfolios.
Multiple choice
According to Buley, what does a strong UX portfolio actually consist of?
Multiple choice
What does Buley say is the most reliable predictor of stagnation as a team of one?
True / False
Once you're a team of one, you should pick generalist or specialist as your trajectory once and stick with it for the rest of your career.
Spot the issue
A team-of-one designer has done excellent work for three years but never written about it, spoken about it, or shared a portfolio publicly. When internal politics shift against UX, they struggle to find their next role. What did they miss?
Part 02
Methods
Ch. 5–10
Planning and Discovery Methods
Part II opens with the up-front work the solo UX practitioner does before any design begins: surfacing what the team already knows, mapping a realistic project plan, and aligning stakeholders on a shared vision. Buley frames these methods as conversation-driven rather than artifact-heavy — the goal is shared understanding and political traction, not long deliverables.
UX Questionnaire
A structured set of questions you ask the team to surface existing assumptions about users, goals, success metrics, and constraints. It exposes knowledge gaps and gives the team of one a baseline before deeper research starts. The questionnaire itself often shocks the team into realizing how thin their shared understanding actually is.
UX Project Plan
A lightweight, tailored roadmap of which UX activities will actually happen on this project, scaled to time and budget. It substitutes for the heavyweight project plans that full UX teams produce, focusing on phases and key checkpoints rather than exhaustive deliverables.
Listening Tour
A round of informal one-on-one conversations with stakeholders across the org to learn what they care about, fear, and see as opportunity. It doubles as relationship-building and political reconnaissance for a solo practitioner. The listening tour is where you map who will help, who will block, and who will sit on the fence.
Opportunity Workshop
A facilitated group session that inventories possible UX improvements and ranks them by business priority. It produces a shared list of "what's worth doing" that the team owns collectively. The collective authorship is the point — it short-circuits later arguments about whether the work matters.
Project Brief
A short document — ideally one page — that captures the project's focus, audience, success criteria, constraints, and timeline. It anchors later decisions and gives non-UX colleagues a reference for scope conversations. When scope creeps, the brief is the receipt.
Strategy Workshop
A cross-functional working session held early — before design begins — that uses the collective wisdom of the team to articulate a UX vision and strategy. Done at peak optimism, when "what could be" energy is highest. Trying to run it after schedules slip is too late; the room is no longer hopeful.
- UX Strategy
- The high-level vision for how a product will deliver value to users and the business.
- Discovery
- The early phase of a project focused on learning context and constraints rather than producing design output.
- Facilitation
- Leading a group through a structured collaborative activity so the group, not the facilitator, produces the output.
- Project Brief
- A concise framing document capturing scope, audience, goals, and constraints before work starts.
- Alignment
- A shared understanding among team members of goals, priorities, and definitions of success.
- Lightweight Deliverable
- A purposely brief artifact (one page, sticky-note wall) chosen because it can be made and consumed quickly.
- Opportunity
- A specific user-facing problem or improvement candidate worth investing UX effort in.
- UX Questionnaire
- A short survey for the team that surfaces existing assumptions and knowledge gaps.
Multiple choice
A team of one wants to run a single early session to articulate a shared UX vision with cross-functional partners. Buley specifically recommends doing this while team energy is high, before schedules slip. Which method is she describing?
Multiple choice
What is the primary purpose of a UX Questionnaire in the discovery phase?
Spot the issue
A solo UX practitioner kicks off a project by spending three weeks producing a 40-page project plan listing every conceivable UX activity, with detailed Gantt charts and exhaustive deliverable specs. The team rarely opens it. What's the main problem?
True / False
A Listening Tour is purely a research activity and has no political or relationship-building function for the team of one.
Research Methods
The core research chapter and the heart of the book's team-of-one philosophy: do real user research even when you have no budget, no recruiter, and no lab. Buley pairs scrappy primary-research tactics with desk-research and expert-review tactics so the practitioner can ground every design decision in evidence.
Learning Plan
A short document that lists what you need to learn about users — needs, motivations, behaviors — and rates your current confidence in each assumption. It tells you where research effort should be concentrated. High-stakes, low-confidence beliefs are where to spend your scarce hours.
Guerrilla User Research
Fast, low-budget interviews and observations done in cafes, hallways, or public spaces with people who roughly match your target user. You trade statistical rigor for speed, recency, and the ability to do it without approval or budget. Five informal sessions next Tuesday beat a thirty-person study you'll never run.
Proto-Personas
Stripped-down personas built from existing knowledge, secondary research, and team assumptions rather than fresh field research. Created collaboratively in roughly 90 minutes with 4-12 colleagues, they include a name, photo, motivations, behaviors, and needs. They are explicitly first drafts to be validated against real research later — the value is in the shared act of creation.
Heuristic Markup
Buley's informal version of expert review: walk through the product end-to-end while a proto-persona "uses" it, marking up screens with sketches and notes about problems and opportunities. Lighter and more narrative than a formal Nielsen-style heuristic evaluation, and far more shareable.
Comparative Assessment
Pick roughly five comparable products — competitors and analogues — and evaluate them on content, design, features, flow, intuitiveness, strengths, and weaknesses. Output is annotated screenshots and a pattern library, not a feature checklist. Analogues from other industries often teach you more than direct competitors.
Content Audit
A systematic inventory of the existing content of a product or site, classifying what exists, what's missing, and what recurring structural patterns are in use. It informs IA, content strategy, and reuse opportunities. Audits sound tedious but typically expose surprising structural problems that no one had noticed.
- Persona
- A fictional but research-grounded character representing a target user segment, used to guide design decisions.
- Proto-Persona
- A first-draft persona built from team assumptions and secondary data, refined by later research.
- Heuristic Evaluation
- Reviewing a product against a list of usability principles (e.g., Nielsen's 10) to spot problems without users.
- Guerrilla Research
- Low-cost, low-ceremony field research run by the practitioner directly, typically without formal recruiting.
- Secondary Research
- Reusing existing research, analytics, support tickets, and market reports instead of generating new primary data.
- Recruiting
- Finding and scheduling participants for research sessions.
- Comparative Assessment
- A structured review of how comparable products solve similar user problems.
- Content Audit
- An inventory and classification of all the content in a product or site.
Multiple choice
Buley describes a roughly 90-minute collaborative session with 4-12 colleagues that produces a first-draft persona — including name, photo, motivations, behaviors, and needs — built from existing knowledge and team assumptions rather than fresh field research. What method is this?
Multiple choice
According to Buley's Learning Plan, where should a team of one concentrate scarce research hours?
Spot the issue
A team-of-one designer keeps delaying user research because she can't get HR to approve a participant recruiting budget or a formal screener process. Six months pass with zero user contact. What's the missed move?
Multiple choice
When doing a Comparative Assessment, Buley recommends including which kinds of products?
Design Methods
Move from learning to making. Buley emphasizes inclusive, sketch-driven techniques that pull non-designers into the design process, so the team of one is multiplying their hands rather than working alone. The chapter favors deliberately rough artifacts over polished ones so the team contributes ideas instead of just reacting.
Design Brief
A short statement of the design problem that names focus, audience, key features, desired tone, constraints, and success criteria. It is the design counterpart to the project brief and frames every later sketch. A design without a brief drifts; a design with one defends itself.
Design Principles
A list of no more than five short statements describing how users should experience the product and what personality it should have. Often posted physically on the wall so the team references them during critique. Principles only work when they're specific enough to rule a choice in or out.
Sketching as a Thinking Tool
Treat fast, low-fidelity drawing — many alternatives per screen — as cognitive scaffolding, not artwork. Pencils or simple pens defer perfectionism and surface a wider option space. Buley's framing: the worse it looks, the more honestly people will critique it.
Sketchboards
A large brown-paper wall display of sketches that the team annotates with sticky notes, ties back to personas, and uses to converge on directions. Makes design progress visible and participatory. The wall replaces the closed file on your laptop.
Task Flows
Visual diagrams of the steps a user takes to accomplish a goal, including decision points, edge cases, and non-digital touchpoints. They expose gaps before wireframing. Most "we forgot the empty state" failures would be caught here.
Wireframes
Schematic screen layouts that work out hierarchy, navigation, and content placement without visual design treatment. Buley keeps them grid-based and informal enough to revise quickly. The goal is to make structural decisions cheap to change.
- Design Brief
- A short framing document capturing the design problem, audience, and constraints.
- Design Principles
- Short directive statements that guide design decisions toward a consistent product personality.
- Low-Fidelity (Lo-Fi)
- Deliberately rough artifacts (sketches, paper) that invite critique and revision.
- Sketchboard
- A wall-mounted collection of sketches the team uses to review and converge on direction.
- Task Flow
- A diagram of the steps and decision points a user takes to complete a goal.
- Wireframe
- A schematic screen layout focused on structure and hierarchy rather than visual design.
- Information Hierarchy
- The visual and structural ordering that signals what is most important on a screen.
- Participatory Design
- A practice that involves non-designers (stakeholders, users) directly in design activities.
Multiple choice
Why does Buley advocate for deliberately rough, low-fidelity sketches over polished mockups during early design?
Multiple choice
According to Buley, how many design principles should a team aim to define, and what makes them effective?
Spot the issue
A team-of-one designer jumps straight from a project brief into wireframes for a new checkout flow. After two weeks of wireframing, an engineer points out that nothing has been thought through for the abandoned-cart edge case, expired-coupon path, or offline state. What should have come first?
Multiple choice
What is the purpose of a Sketchboard?
Testing and Validation Methods
Cheap, fast ways to put designs in front of users and critical eyes before committing to build. Buley's testing methods are deliberately scaled down — five users, fifteen minutes, paper instead of code — so a solo practitioner can run them repeatedly throughout a project rather than once at the end.
Prototypes
Artifacts at varying fidelity — paper, clickable, coded — used to probe specific design questions. Fidelity should match the question being asked, not be maximized for its own sake. Paper answers "is the flow right?"; code answers "does the interaction feel right?" — picking the wrong fidelity wastes time.
Black Hat Session
A team workshop where participants deliberately try to find weaknesses, risks, and failure modes in a design using sticky notes on wall-mounted printouts. Borrowed from De Bono's Six Thinking Hats. Surfacing problems explicitly removes the social cost of personal critique — everyone is hatting up to be a critic.
Quick-and-Dirty Usability Test
Roughly 15-minute sessions with a handful of unfamiliar participants attempting realistic tasks while the practitioner observes friction. Trades statistical rigor for speed and frequency. Done weekly, it produces a steady stream of design fixes the team can ship.
Five-Second Test
Show a participant a single screen for five seconds, hide it, then ask what they remember and what they think it's for. Gauges first impressions, clarity, and information hierarchy. If users can't tell what the screen does after five seconds, no amount of micro-interaction polish will save it.
UX Health Check
The team rates sections of the product against benchmarks (often competitors or a prior version) to spot the weakest areas and prioritize them. Functions as a recurring temperature read. Run quarterly, it tracks whether UX investment is actually moving the product.
Iterate-Then-Validate Cadence
Testing exists to feed the next design loop, so methods should be chosen for speed of insight rather than completeness. Five users this week beats fifty users in two months. The cadence — not the rigor of any single test — is what compounds into a better product.
- Prototype
- A working stand-in for a design used to test ideas before full implementation.
- Fidelity
- How closely a prototype matches the look, feel, or behavior of a finished product.
- Usability Testing
- Observing real users attempt realistic tasks to find friction in a design.
- Black Hat Thinking
- Deliberately critical, risk-finding mode of thought (from De Bono's Six Thinking Hats).
- Five-Second Test
- A first-impression test where users see a screen for only five seconds before being questioned.
- Task Scenario
- A realistic goal given to a test participant so behavior is observed rather than opinion solicited.
- Validation
- Confirming with evidence that a design solves the intended problem for real users.
- Benchmark
- A reference standard (often a competitor or prior version) against which current performance is compared.
Multiple choice
A teammate insists on building a fully coded, pixel-perfect prototype just to check whether users can find the right entry point in a navigation flow. According to Buley, what's the core principle they're violating?
Multiple choice
You want to surface design weaknesses without anyone feeling personally attacked in critique. Which method does Buley recommend, and what's its origin?
Spot the issue
A team-of-one practitioner schedules one big usability study at the end of the project: 30 carefully recruited participants, full lab, polished prototype. They plan to publish a comprehensive report after launch. What's wrong with this plan in Buley's framing?
True / False
A five-second test is mainly used to measure how quickly a user can complete a multi-step task.
Evangelism Methods
Techniques for spreading UX culture through an organization where you are the only practitioner. Buley argues a team of one's long-term survival depends as much on advocacy and storytelling as on craft, and she offers methods for building a coalition of supporters at every level — not betting everything on a single executive sponsor.
Bathroom UX
Posting flyers, newsletters, or research recruiting pitches in high-traffic spots — literally including bathroom stalls — so colleagues encounter UX content in passive moments. A cheap, persistent visibility tactic. The point is ambient awareness, not direct conversion.
Mini Case Studies
One-page write-ups of a UX project — problem, what was done, evidence, outcome — used to demonstrate impact and ROI to stakeholders. They make abstract UX work concrete and shareable. A folder of mini case studies is the team of one's most portable credibility asset.
Peer-to-Peer Learning Community
Internal UX book clubs, brown bags, or "UX days" that turn other employees into informed allies. Spreads vocabulary and methods beyond the practitioner, which is what real organizational UX maturity looks like. Allies who can run a guerrilla test themselves are far more valuable than allies who just nod at your presentations.
One-on-One Engagement
Personal conversations with specific colleagues to gather support, gather information, and convert skeptics. More effective per minute than broadcast announcements. A skeptic converted in coffee is worth a dozen who applauded politely in the all-hands.
Show, Don't Tell
Demo visible work products — wireframes, prototypes, test clips — rather than explaining UX abstractly. Tangible artifacts persuade better than definitions. Five minutes of watching a real user struggle ends the debate that thirty slides on "user-centered design" could not.
The Four Engagement Principles
Buley's anchors for evangelism work: Invite People In, Make Things Together, Truly Listen, and Know When It's Good Enough. They distinguish evangelism from sales — the goal is participation, not persuasion. Followed consistently, they make UX feel inviting rather than threatening.
- Evangelism
- Active advocacy for UX practices and value inside the organization.
- Mini Case Study
- A one-page narrative documenting a project's challenge, approach, and outcome, used persuasively.
- ROI
- Return on Investment — the business value gained relative to effort spent, often what stakeholders demand to justify UX.
- Grassroots Support
- Bottom-up backing built across peers and middle layers, not top-down executive mandate.
- Lunch-and-Learn
- An informal teaching session held over lunch to spread skills or concepts inside the org.
- Champion / Sponsor
- A senior ally who advocates for UX work in rooms the practitioner isn't in.
- Lightweight Artifact
- A small, shareable deliverable (one-pager, sketch, short video) designed for fast circulation.
- Adoption
- The degree to which UX practices and outputs are actually used by the broader team or organization.
Multiple choice
You have one hour to spend convincing a skeptical engineering lead that UX research matters. Based on Buley's evangelism methods, what's the highest-leverage use of that hour?
Multiple choice
Buley names four engagement principles that distinguish UX evangelism from sales. Which set captures them?
Spot the issue
A team-of-one practitioner wants to prove the value of their last six months of work to leadership. They prepare a 45-slide deck filled with definitions of UX terminology, abstract diagrams of the design process, and a long bibliography. They hand it out at the next all-hands. What's the most important thing they got wrong?
True / False
According to Buley, training other employees to run their own UX activities — via book clubs, brown bags, or "UX days" — is wasted effort because only specialists can do real UX work.
What's Next?
Buley closes by zooming out from tactics to the trajectory of the UX field and the meaning of being a team of one inside it. She sketches where the discipline is heading, why design's underlying value is durable even as tools and titles churn, and what she calls "the secret agenda" — the quiet, cumulative cultural work that solo practitioners do every day.
The Evolution of UX
A short historical arc showing how UX absorbed and recombined disciplines (HCI, IA, visual design, research) and a projection of where it's heading — more strategic, more embedded, more cross-functional. Knowing the arc helps you bet on durable skills instead of trendy tools.
The Endurance of Design
Specific tools, deliverables, and even job titles change, but the underlying craft of understanding people and shaping experiences is durable. Betting on the craft beats betting on any one method. Wireframes will be replaced by something else; the discipline of structuring screens for human comprehension will not.
The Secret Agenda of the UX Team of One
Buley's framing that solo UXers are doing more than shipping features — they are seeding a user-centered worldview inside organizations that didn't have one. The shipped feature is the visible output; the cultural shift is the real one. That cultural shift is the field's actual growth engine.
Boots on the Ground
The team of one is the most consequential practitioner in the field because they bring UX to companies that have never had it. Famous UX teams at famous companies matter less for the field's spread than ten thousand quiet solo practitioners winning small fights inside ordinary companies.
Permission to Start Small
Incremental, visible wins matter more than sweeping transformation programs, especially when you're alone. The team of one's correct mode is patient accretion. Pushing for a "UX transformation" when you're solo is usually a way to get fired before any UX actually ships.
The Continuous Practice Mindset
UX work, like any craft, rewards consistent practice over heroic effort. A small habit (sketching every day, reading one paper a week, running one guerrilla test a month) compounds further than occasional grand pushes. The closing message is to treat the work as a long career-spanning practice, not a series of projects.
- UX Maturity
- A measure of how deeply user-centered practices are embedded in an organization's culture and process.
- Human-Centered Design
- A design approach that starts from the needs, behaviors, and contexts of the people who will use the product.
- Practitioner
- Someone who actively does the work of a discipline, as distinct from researching or teaching it.
- Craft
- The accumulated, embodied skill of a practice — durable even as specific tools change.
- User-Centered Worldview
- The mental habit of starting from user needs and context when making product decisions.
- Manifesto
- A short declarative statement of beliefs and intentions for a field or movement.
- Discipline
- A bounded field of practice with shared methods, vocabulary, and standards.
- Secret Agenda
- Buley's term for the cumulative cultural shift toward user-centered thinking that team-of-one practitioners drive over time.
Multiple choice
A junior UXer worries that wireframes will be obsolete in ten years and asks Buley what to invest in. Based on the chapter's closing argument, which answer best matches her framing?
Multiple choice
What does Buley call the "secret agenda" of the UX team of one?
Spot the issue
Fresh in a team-of-one role at a low-maturity company, a practitioner announces a sweeping "UX transformation program" in their first month. They propose a new design system, mandatory research before every feature, and a redesigned product roadmap built around personas they haven't created yet. What does Buley say is the core problem with this approach?
True / False
According to Buley, famous UX teams at famous companies matter more for the spread of UX as a field than the countless solo practitioners working inside ordinary companies.
Key Takeaways
UX is the cumulative effect of every touchpoint, not just the screen — and a "team of one" is anyone advocating for users no matter their title.
Relationships beat process — invite people in, listen first, and bring stakeholders on the journey instead of fighting for permission.
Lightweight beats heavyweight — proto-personas, guerrilla research, paper prototypes, and 15-minute tests beat polished artifacts you'll never finish alone.
Constraints are a feature, not a bug — scarce time and budget force you to pick the single highest-leverage move ("if you can only do one thing").
Evangelism is craft — mini case studies, pyramid evangelism, and ambient visibility convert skeptics more reliably than heroic presentations.
Career growth comes from outside the building — community, mentors, and a portfolio of case studies guard against isolation when you're the only UX person at work.