Summary
Picture this: You spend weeks writing up your UX Playbook. Your Playbook covers every design and research method your team might use, when to use it, and how. It’s PERFECT. And... no one reads it. I’ve been there! I’ve led or contributed to 4 Playbooks, 2 toolkits and uncountable miscellaneous “how to” docs in my 8 years as a UX Designer and Operations Manager. In this talk, we’ll cover how to: avoid common pitfalls in documentation, discover what your team needs most, apply a design process to your documentation efforts and deliver incremental value through documentation your team will actually use.
Key Insights
-
•
There are two primary types of documentation: process and policy documents, typically made by managers or design ops, and project records created by individual contributors.
-
•
Playbooks streamline organizational design practices by organizing actionable content into stages and plays reflecting the team's mental model.
-
•
Common pitfalls in documentation include unactionable generic information, difficult navigation, cognitive overload from excessive detail, and outdated content that erodes trust.
-
•
Teams overwhelmingly rely on numerous tools (13 on average in UX research), making accessible and clear playbooks essential especially for new hires and junior designers.
-
•
Applying a design thinking process to documentation—empathize, prioritize, prototype small sections, test, and circulate—helps create valuable, user-friendly resources.
-
•
Empathizing means understanding how your team currently accesses information, avoiding top-down imposed processes, and discovering real pain points through interviews, surveys, and desk research.
-
•
Delivering incremental, usable sections instead of waiting to complete the entire playbook increases adoption and feedback opportunities.
-
•
Shared ownership of playbook sections by contributors encourages more frequent referencing and greater relevance.
-
•
Tools like Coda offer useful analytics such as page views and video engagement metrics that help track documentation adoption and identify pain points.
-
•
Regular review and content updating, ideally on a quarterly or semiannual cadence, is critical to maintain trust and ensure documentation relevance.
Notable Quotes
"Our folks are not looking for information about what are wireframes. They want information specific to your organization."
"If folks can't find the information, it doesn't matter how well it is written."
"Avoid walls of text and create visual hierarchy to ensure scanability by using headers, sections, lists, and images."
"Outdated content will erode trust and make folks question whether other information is worth their time."
"You should not try to deliver your playbook from the ivory tower of design ops. It just will not be successful."
"Start with the biggest pain points your team is experiencing and find the biggest potential impact."
"You don't want to hide away for six months and try to build the perfect documentation. It won't work."
"Encourage adoption by sharing documentation in relevant channels, referring team members to it, and including it in onboarding."
"I love getting other people in there. Shared ownership means people are going to reference it more often."
"Use whatever information is available in the tool. Views, downloads, and links in Slack channels are all helpful adoption metrics."
Or choose a question:
More Videos
"Slow and intentional communication allows you to be fully present rather than distracted by constant notifications."
Marc Fonteijn Ru ButlerIncrease your confidence, influence, and impact (through a Professional Community)
December 3, 2024
"Universities in Latin America are doing a very bad job providing practical UX research training."
Victor M. GonzalezPracticing Learners and Learning Practitioners
March 10, 2021
"It’s less about empathy and more about building an understanding of barriers and user needs."
Elana Chapman Li Wen Huang Divyen Sanganee Annabel WeinerGetting started with accessibility research
February 20, 2025
"Most employees take at least 90 days to onboard and another 90 days to become productive — that’s half a year before you see impact."
Karen PascoeDeveloping Experience Teams and Talent in the Enterprise
June 8, 2016
"Widgets are more than UI; they combine front end code, back end services, and analytics into a reusable package."
Dawn ResselFull-Stack User Experiences: A Marriage of Design and Technology
June 9, 2016
"Invite yourself to the table by bringing actual deliverables, like storyboards and prototypes."
Gretchen AndersonScaling the Human Center
June 8, 2017
"Power dynamics exist in every session. People don’t want to be embarrassed or feel put on the spot."
Mila Kuznetsova Lucy DentonHow Lessons Learned from Our Youngest Users Can Help Us Evolve our Practices
March 9, 2022
"Diverse teams create diverse products because we each only understand our own needs."
Sam ProulxAccessibility: An Opportunity to Innovate
November 16, 2022
"Building a design system is really about breaking big problems into smaller parts that have real value."
Nathan CurtisDesign Systems for Us: How Many One-Source(s)-of-Truth Are Enough?
January 17, 2019
