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
-
•
Documentation should focus on actionable and clear instructions rather than generic content.
-
•
Easy navigation is crucial; if people can't find the information, it becomes useless.
-
•
Cognitive overload can be minimized by breaking down information into digestible parts and using visual hierarchy.
-
•
Regularly updating content is necessary to maintain trust and usability of the playbook.
-
•
Empathizing with team members helps identify their actual needs and biggest frustrations with existing documentation.
-
•
Incremental delivery of documentation ensures teams can provide feedback early, improving the final product.
-
•
Utilizing design thinking principles can enhance the documentation creation process.
-
•
Involving team members in content ownership fosters collaboration and increases documentation utilization.
-
•
Tracking adoption metrics and understanding content usage is essential for refining documentation.
-
•
Documentation should be continuously iterated upon as processes and tools evolve.
Notable Quotes
"Documentation must be actionable and reflect your organization's practices, not just generic information."
"If folks can't find the information, it doesn't matter how well it's written."
"You need to understand how people are working and what they need help with."
"Leave out generic content and focus on what your team needs."
"Imagine if team members find broken links in your playbook – it erodes trust."
"Empathize with your team to ensure the documentation meets their needs."
"Don't hide away for six months trying to build the perfect documentation."
"Deliver small complete sections to get feedback sooner rather than waiting for a finished product."
"A playbook is not a one-hit wonder; it needs ongoing maintenance and updates."
"Encourage team adoption by sharing documentation widely and pinning it in accessible channels."
More Videos
"Today's topic is around researchers thriving in the organization."
Bria AlexanderOpening Remarks
January 8, 2024
"Doing research with kids can be some of the most fun work you'll get to do."
Mila Kuznetsova Lucy DentonHow Lessons Learned from Our Youngest Users Can Help Us Evolve our Practices
March 9, 2022
"The change management component is lengthy and requires best practices to guide teams."
Dave Malouf Patrizia Bertini Jon FukudaThe Past, Present, and Future of DesignOps: a 2-part DesignOps Community Call (Part 2)
April 28, 2022
"The gap between theory and practice in prioritization is often where teams struggle the most."
John Cutler Harry MaxPrioritization for designers and product managers (1st of 3 seminars)
June 13, 2024
"Design always has a seat at the table at Pinterest because our co-founder is a designer."
Meredith BlackScaling Design Culture
November 6, 2017
"I'm incredibly proud of each of you for the effort you put into the curation process"
Bria AlexanderTheme Two Intro
September 8, 2022
"What would you do if info sets said you can't use this tool?"
Holly ColeUnderstanding Experiences: When you have to do more than work
November 8, 2018
"It’s less about interaction and more about integrity."
Ron BronsonDesign, Consequences & Everyday Life
November 18, 2022
"Companies need to consider the entire end-to-end user journey, not just isolated product features."
Kit Unger Jackie Ho Veevi Rosenstein Vasileios XanthopoulosTheme 2: Discussion
January 8, 2024
