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 main documentation types: process/policy docs created by managers or design ops, and project records created by individual contributors.
-
•
Playbooks organize information by work stages matching the organization's mental model, including detailed plays with instructions and templates.
-
•
Common pitfalls in playbooks include non-actionable info, poor navigation, cognitive overload, and outdated content.
-
•
Teams want documentation specific to their organization's processes, not generic explanations.
-
•
Navigation should align with users' mental models and include searchable content and cross-linking for discoverability.
-
•
Cognitive overload is reduced by using visual hierarchy, headers, lists, and removing unnecessary 'fluff'.
-
•
Regularly reviewing and updating documentation preserves trust and usability.
-
•
Applying a design thinking process—empathize, prioritize, prototype, test, circulate—improves documentation value and adoption.
-
•
Deliver small, complete documentation sections incrementally rather than waiting for a perfect complete playbook.
-
•
Shared ownership and collaboration on documentation fosters greater adoption and accuracy; design ops should avoid sole ownership.
Notable Quotes
"When we say documentation, I think of there being two main types: process and policy docs, and project records."
"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."
"Imagine a team member goes to your playbook and the first link they click lands on a 404 page—this erodes trust."
"You don't want to dictate the process, especially if you're new to an organization."
"Your prototype is going to be imperfect. That's okay. Deliver small but complete sections to provide value sooner."
"I love getting other people in there. Shared ownership means people reference it more often and promote it."
"You should set a usage goal and track adoption metrics to learn why users may not be engaging with the documentation."
"A playbook is not a one hit wonder. You'll need someone to keep it up to date and revisit regularly."
Or choose a question:
More Videos
"We are witnessing the most rapid loss of biodiversity in human history."
Alex Hurworth Bonnie John Fahd Arshad Antoine MarinDesigning a Contact Tracing App for Universal Access
October 23, 2020
"These brand new practitioners can bring fresh perspectives and new ways of thinking to hopefully see current problems in a new light."
Laine Riley Prokay Lisa GordonCarving a Path for Early Career DesignOps Practitioners
September 9, 2022
"TripAdvisor is really nine major business units each thinking like sub companies instead of one end-to-end user experience."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"If your budgets don’t connect to strategy goals, maybe those budget items shouldn’t exist."
Nathan ShedroffDouble Your Mileage: Use Your Research Strategically
March 31, 2020
"You can just pick up your phone and start testing accessibility instantly without procurement or licensing hurdles."
Sam ProulxMobile Accessibility: Why Moving Accessibility Beyond the Desktop is Critical in a Mobile-first World
November 17, 2022
"It’s important to socialize the research program internally so teams get excited and take initiative."
Feleesha SterlingBuilding a Rapid Research Program (Videoconference)
May 18, 2023
"You get to those iconic signature actions when product excellence meets cultural tensions and what people need."
Neil BarrieWidening the Aperture: The Case for Taking a Broader Lens to the Dialogue between Products and Culture
March 25, 2024
"Leadership roles have to evolve depending on whether you’re building awareness, influence, capacity, or measuring impact."
John DevanneyThe Design Management Office
November 6, 2017
"The higher up you go, the more qualities like bravery matter compared to methodology."
Katy MogalBut Do Your Insights Scale?
March 12, 2021