Rosenverse
Documentation Your Team Will Actually Use

This video is only accessible to Gold members. Log in or register for a free Gold Trial Account to watch.

Log in Register

Most conference talks are accessible to Gold members, while community videos are generally available to all logged-in members.

Documentation Your Team Will Actually Use

Gold
Tuesday, October 3, 2023 • DesignOps Summit 2023
Share the love for this talk
Documentation Your Team Will Actually Use
Speakers: Gabrielle Verderber
Link:

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 primary types of documentation: process and policy documents, typically made by managers or design ops, and project records created by individual contributors.

  • Playbooks streamline organizational design practices by organizing actionable content into stages and plays reflecting the team's mental model.

  • Common pitfalls in documentation include unactionable generic information, difficult navigation, cognitive overload from excessive detail, and outdated content that erodes trust.

  • Teams overwhelmingly rely on numerous tools (13 on average in UX research), making accessible and clear playbooks essential especially for new hires and junior designers.

  • Applying a design thinking process to documentation—empathize, prioritize, prototype small sections, test, and circulate—helps create valuable, user-friendly resources.

  • Empathizing means understanding how your team currently accesses information, avoiding top-down imposed processes, and discovering real pain points through interviews, surveys, and desk research.

  • Delivering incremental, usable sections instead of waiting to complete the entire playbook increases adoption and feedback opportunities.

  • Shared ownership of playbook sections by contributors encourages more frequent referencing and greater relevance.

  • Tools like Coda offer useful analytics such as page views and video engagement metrics that help track documentation adoption and identify pain points.

  • Regular review and content updating, ideally on a quarterly or semiannual cadence, is critical to maintain trust and ensure documentation relevance.

Notable Quotes

"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."

"Outdated content will erode trust and make folks question whether other information is worth their time."

"You should not try to deliver your playbook from the ivory tower of design ops. It just will not be successful."

"Start with the biggest pain points your team is experiencing and find the biggest potential impact."

"You don't want to hide away for six months and try to build the perfect documentation. It won't work."

"Encourage adoption by sharing documentation in relevant channels, referring team members to it, and including it in onboarding."

"I love getting other people in there. Shared ownership means people are going to reference it more often."

"Use whatever information is available in the tool. Views, downloads, and links in Slack channels are all helpful adoption metrics."

Ask the Rosenbot
Dave Malouf
The Past, Present, and Future of DesignOps: a 2-part DesignOps Community Call (Part 1)
2022 • DesignOps Community
George Zhang
UX Research Excellence Framework
2021 • Advancing Research 2021
Gold
Dianne Que
Real Talk: Proving Value through a Scrappy Playbook
2019 • DesignOps Summit 2019
Gold
Adam Cutler
Discussion
2016 • Enterprise UX 2016
Gold
Melinda Belcher
Insider preview of Enterprise Experience 2020
2020 • Enterprise Community
Sarah Auslander
Insights Panel
2022 • Civic Design 2022
Gold
Chris Govias
Perspectives on Civic Design
2021 • Civic Design Community
Michael Land
Establishing Design Operations in Government
2021 • DesignOps Community
Maria Rosala
Research Repositories
2026 • Advancing Research 2026
Gold
Sahibzada Mayed
The Politics of Radical Research: A Manifesto
2023 • Advancing Research 2023
Gold
Theresa Marwah
How Atlassian is Operationalizing Respect in Research
2020 • Advancing Research Community
JJ Kercher
A Roadmap for Maturing Design in the Enterprise
2018 • Enterprise Experience 2018
Gold
Samuel Proulx
Invisible barriers: Why accessible service design can’t be an afterthought
2024 • Advancing Service Design 2024
Gold
Changying (Z) Zheng
From prototype to production: Vibe coding design for real engineering systems
2026 • Designing with AI 2026
Conference
Kritika Sony
Moving AI offscreen: Exploring failures, constraints, and recovery in physical game design
2026 • Designing with AI 2026
Conference
Jemma Ahmed
Theme Three Intro
2023 • Advancing Research 2023
Gold

More Videos

John Cutler

"A story lets people assign the meaning that's powerful to them and then think about the decisions they need to make and align."

John Cutler

The Alignment Trap

November 29, 2023

Jemma Ahmed

"Participation rates are falling, engagement rates are falling — this is a data quality crisis."

Jemma Ahmed Robert Fabricant Sean McKay Llewyn Paine Kate Towsey Noah Bond

Theme Panel

March 11, 2025

Jon Fukuda

"You can’t escape existential matters; you need to confront them head on to unleash the power of storytelling."

Jon Fukuda

Storytelling for DesignOps

August 17, 2023

Kristin Skinner

"The future of education lies in collaboration and adaptation."

Kristin Skinner

Five Years of DesignOps

September 29, 2021

Christopher Taylor Edwards

"Pairing isn't about taking away jobs; it's about amplifying everyone's expertise and breaking down hierarchy."

Christopher Taylor Edwards Valerie Roske

Design as a Team Practice, A Practical Guide to Cross-functional Collaboration

September 30, 2021

Amy Paris

"Government forms need to represent identity and respect privacy so we can better serve all people."

Amy Paris Danielle Thierry

Delivering Equity: Government Services for All Ages, Languages, Sexual Orientations, and Gender Identities

December 9, 2021

Julie Gitlin

"Having a designated buddy for new hires proactively soliciting questions creates a supported partnership and eases onboarding."

Julie Gitlin Esther Raice

Design as an Agent of Digital Transformation at JPMC

June 9, 2021

Louis Rosenfeld

"MJ Broadband saves our fingers some pain and some stress because we don’t have to take notes."

Louis Rosenfeld Bria Alexander

Opening Remarks

March 27, 2023

Davis Neable

"Investing time in people, relationships, and collaboration pays off in stronger teams and better user experiences."

Davis Neable Guy Segal

How to Drive a Design Project When you Don’t Have a Design Team

June 10, 2021