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
"Senior designers are subject matter experts, staff designers navigate ambiguity, and principal designers create business impact."
Catt Small Micah Bennett Brian Carr Jessica HarlleeWhat's Next for ICs: Exploring Staff and Principal Designer Roles (Videoconference)
February 22, 2024
"We released several incremental but imperfect pilot solutions to inform usability and strategy rather than relying on typical prototyping."
Jennifer Kong[Case study] Journeying toward AI-assisted documentation in healthcare
June 5, 2024
"Our stakeholders and colleagues are users too, and the product we’re sharing is the research and learnings."
Sara LogelYour Colleagues are Your Users Too
March 29, 2023
"I showed teams tips and templates to organize and analyze raw data so insights could be shared and reused beyond one project."
Veevi RosensteinBuilding for Scale: Creating the Zendesk UX Research Practice
January 8, 2024
"Our culture means if someone publishes something questionable, there’s a transparent discussion."
Michelle Bejian Lotia Anne-Marie MorellRolling Out a Repository: How Zapier Centralizes Insights from Across their Organization
March 28, 2023
"Multitasking is a myth; I invite you to turn your video on to help focus and connect."
Tutti TaygerlyVideconference: How to Work with Difficult People with Tutti Taygerly
June 25, 2020
"We transitioned designers embedded on low priority projects to higher priority ones within three weeks."
Patrick CommarfordDesign Staffing for Impact
January 8, 2024
"Today’s speakers will guide us towards defining, measuring, and growing our impact with the people, processes, practices, and products we steward."
Frances YllanaTheme 2 Intro
September 24, 2024
"Edward Tufte says, the act of arranging information becomes an act of insight."
Mujtaba HameedFrameworks for Excellence: Using Visual Thinking and Communication to Elevate Your Research
March 26, 2024