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
"Design leadership needs to be recognized at the executive level to elevate its importance in the company."
Peter MerholzDesign at Scale is People!
June 11, 2021
"Creativity is a metric for resilience, and through that, well-being."
Dr. Karl JeffriesThe Science of Creativity for DesignOps
January 8, 2024
"Helping others to create their own mental map is essential for meaningful change."
Laura WeissThere is No Playbook: Leader as Coach During Challenging Times
April 26, 2024
"You should focus on your strengths and offset them with others' weaknesses."
Greg PetroffDesign is the Differentiator: Bringing New Design Innovations to a Very Antiquated and Very Large Industry
June 9, 2021
"Process can connect folks and help scale projects effectively."
Jennifer KanyamibwaCreating the Blueprint: Growing and Building Design Teams
November 8, 2018
"Latin researchers should embrace discomfort if it leads to meaningful change."
Verónica Urzúa Jorge MontielThe B-side of the Research Impact
March 12, 2021
"We’re not merely fiddling at the edges; these are big structural challenges we’re discussing."
Wendy Johansson Surya VankaDesign at Scale: Behind the Scenes
April 29, 2021
"Words matter and language is foundational to culture."
David ConradThe Feeling of Data
September 14, 2023
"Holding on to your soul in business is more important than ever."
Ryan RumseyBusiness Influence Without Losing Your Soul
January 14, 2021
