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’re still at a nebula moment where defining what DesignOps truly is remains difficult."
Dave Malouf Patrizia Bertini Jon FukudaThe Past, Present, and Future of DesignOps: a 2-part DesignOps Community Call (Part 2)
April 28, 2022
"Empathy and trust develop through working together, not in isolation."
Christopher Taylor Edwards Valerie RoskeDesign as a Team Practice, A Practical Guide to Cross-functional Collaboration
September 30, 2021
"The absence of feedback during design demos was a red flag — we missed information and had to realign quickly."
Frank DuranPartnership Playbook: Lessons Learned in Effective Partnership
January 8, 2024
"Learning and knowledge management isn’t just about quality of work, it’s deeply tied to retaining people and motivation."
John DevanneyThe Design Management Office
November 6, 2017
"FEMA is not going to stand up a UX department; it’s our responsibility to witness and find ways to help."
Emily Danielson“I mean, I can lift a shovel”: Design Skills in Disaster Response
June 9, 2022
"Make a case to hire people who are product agnostic to connect where products intersect in the rider journey."
Kristin TaylorBuilding Bridges Across Organizational Silos
November 18, 2022
"Stakeholder support is pretty important because if people on your team just don’t have time, they’re not gonna be able to commit to their roles."
Feleesha SterlingBuilding a Rapid Research Program
May 18, 2023
"The moment they begin to shift their thinking and make decisions based on that work, they’re actually giving you a seat."
Dalia El-ShimySo You've Got a Seat at the Table. Now What?
March 31, 2020
"Energy Star appliances generate over a billion dollars in revenue yearly — applying that analogy to Cisco hardware proved powerful."
Amy ParnessScaling Sustainability: Complementary strategies that drive long-term success
May 29, 2025
