This video is only accessible to conference ticket holders.
Log in Create account
For 90 days after a conference, only paid ticket holders can watch conference videos. After that, all Gold members have access.
Contact Support if you are having any issues.
Summary
Imagine working at a large company where there is no single design organization. Instead, it feels like an archipelago of design islands. Some large islands with an organization of designers and researchers. Others are smaller islands of just one team. And even, UX teams of one floating on rafts in between. Without a map, those islands are only aware of their immediate surroundings. How can we bring the company wide design community of practice together if we don’t even know where to find each other? This was my experience when I did my first design community mapping project. In this talk, I’ll share how we ended up crowdsourcing our design community map, and how it became an invaluable resource for the internal design community of practice. I’ll compare the differences for visualizing and thinking about organizations with a traditional org chart compared to a community map. Further, I’ll share how I brought my cartography skills with me to a new company, where I felt lost without a map, and why this map is my most important DesignOps tool.
Key Insights
-
•
Traditional org charts and HR systems often fail to accurately represent who is on design teams due to outdated or incomplete data.
-
•
Mapping people as circles in a cohesive team layout fosters a stronger sense of belonging than lists or rectangles.
-
•
Crowdsourcing map updates within a design community increases map accuracy and reveals hidden teams or individuals.
-
•
Using component libraries in design tools allows scalable, easy updates to people maps and supports multiple visual models from the same data.
-
•
Maps help new hires orient themselves faster via 'map tours,' accelerating network-building and onboarding.
-
•
People maps create a shared mental model of design teams across the company, aiding cross-team understanding and collaboration.
-
•
Duplicating maps for different use cases enables answering operational questions such as identifying domain experts or assessing org health.
-
•
Ops-managed maps ensure ongoing accuracy when design ops leads actively maintain them, balancing against purely crowdsourced approaches.
-
•
Design ops cartography is a superpower that lifts the fog of organizational complexity, turning hidden knowledge into shared understanding.
-
•
Flexible visual metaphors (circles, rectangles) combined with auto-layout improve efficiency and clarity in visualizing teams and projects.
Notable Quotes
"Who works here anyways? I knew about immediate teams but beyond that, it was a fog."
"Representing a person as a circle feels more right—like we’re all equidistant at the same table."
"I call this an anti org chart because it’s organic, messy, and structures emerge rather than imposed."
"Crowdsourcing the map meant anyone in our community practice could edit, and it worked beautifully."
"These islands of design were close together or far away; our map brought them all closer."
"Publishing a component library means anyone can update titles or roles, and it updates everywhere at once."
"Map tours are my favorite thing—taking a new hire on a guided walk of the entire community."
"Duplicating the map lets me answer ops questions like who are our UX domain experts or how design ops is structured."
"Starting a new job with no map felt lost; so I built a new map as my BYO orientation."
"When we don’t have the people modeling we need, we have to make it ourselves to lift the fog."
Or choose a question:
More Videos
"If executives are responsible for the why and managers are responsible for the what, then directors are responsible for the how."
Peter MerholzThe Trials and Tribulations of Directors of UX
July 13, 2023
"We replaced the exhausting time estimation game with data-driven models that give us more reliable results."
John Paul de Guzman10k Screens Later: How We Became a Data-Driven Design Organization
September 24, 2024
"One ops person to five researchers seems pretty legit, according to Kate Towsie."
Brigette MetzlerScaling ResearchOps: Helping Researchers do Their Best Work
March 30, 2020
"Almost 90% of data science projects do not make it into production—they die on the vine."
Joel BranchHumanizing AI: Filling the Gaps with Multi-faceted Research
March 11, 2021
"Without shared ownership and participation, design systems risk becoming isolated and irrelevant."
Nina JurcicThe Design System Rollercoaster: From Enabler and Bottleneck to Catalyst for Change
October 3, 2023
"Giving senior leadership a shared language for design helped product teams better communicate what needed focus and why."
Chris MosesStretching the Definition of DesignOps with Product Development
November 7, 2018
"You don't want to hide away for six months and try to build the perfect documentation. It won't work."
Gabrielle VerderberDocumentation Your Team Will Actually Use
October 3, 2023
"The incentive structure at a big company is set up to reward people for entirely different stuff than innovation requires."
Laura KleinUnique challenges of innovation in enterprises
April 23, 2020
"A small change in the quarterly business review template led to surfacing eight new collaborative projects each quarter."
Melissa TsangFrom Insights to Action: Driving Business Values through DesignOps
January 8, 2024
