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
"You need strong regional players with negotiation skills to navigate the split loyalties in global teams."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"Knowing your subject matter as a UX leader is just as important as knowing your craft."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"If you don’t tune it properly, sometimes you just don’t get what you want."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"We need to rethink how our cities are designed and function."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"If you forget the individual, you cut out psychological safety, and that’s the foundation of strong teams."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Most organizations are still asking design questions at a global level; we need to be hyper-local now."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"Clusters describing demographics and behaviors alone were not enough; we needed emotional personas to find value propositions."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"Successful operations must have a well-laid-out and transparent process and documentation, but that process must become invisible in its application."
Designing Systems at Scale
November 7, 2018
"The conversion design process creates collective knowledge, which gets reinfused to strengthen future experiments."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
