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
"We gave away the recipe with no fee for entry – immediate value first, then learning the process."
Matt StoneScaling Empathy, A Case Study in Change Management
June 11, 2021
"This work does not fit our product program."
Aditi Ruiz Christian Crumlish Farid SabitovA PM State of Mind: Empathy Mapping Your Product Manager, Pt. 1
December 6, 2022
"Educating design leaders on setting expectations for Design Ops roles is critical to avoid 'teams of one' who are expected to do everything."
Dave Malouf Meredith Black Farid SabitovThe Past, Present, and Future of DesignOps: a 2-part DesignOps Community Call (Part 1)
February 17, 2022
"Assistive technology has to communicate with the destination, that’s your website or product."
Sheri Byrne-HaberAccessibility at Scale
June 9, 2021
"I think of a journey map as a suggestion, not a rule, and I might take parts of it to fit the context and people."
Nidhi Singh Rathore Amber DavisEmbracing participation to unlock deeper truths in commercial research
March 12, 2025
"Adding inclusivity to the career ladder took three years and this is still a living document with room for change."
Laine Riley ProkayHow DesignOps can Drive Inclusive Career Ladders for All
September 30, 2021
"People were taking vacation days just to homeschool or take care of a loved one."
Ariba JahanTeam Resiliency Through a Pandemic
January 8, 2024
"From an engineer's perspective, we don't have to talk about the engineering but talk about the value, including usability, and that is what builds trust."
Noreen Whysel Katie SaindonShort Take #4: UX/Product Lessons from Your Industry Peers
December 6, 2022
"Buttons should be sized 48 pixels and above to avoid fat finger errors for seniors."
Rittika BasuAge and Interfaces: Equipping Older Adults with Technological Tools
February 23, 2023
