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
"The more experienced you are, the more satisfied you tend to be with your salary; it can almost be double compared to beginners."
Marc FonteijnFirst Insights from the 2025 Service Design Salary(+) Report
December 4, 2024
"Say it until someone says it better back to you."
Jacqui Frey Alison RandSetting the Table for Dynamic Change
October 24, 2019
"Design is open source; everybody participates, but you need facilitation to make good on that promise."
Bob Baxley Sara Asche Anderson Sharon Bautista Frank Duran Jamie Kaspszak Abbey Smalley Sylas SouzaTheme 4: Discussion
January 8, 2024
"Sponsor sessions are optional but incredibly high quality content, not sales pitches."
Bria AlexanderDay 2 Welcome
September 24, 2024
"We should feel empowered to propose research initiatives that stakeholders aren’t explicitly asking for."
Joanna Vodopivec Prabhas PokharelOne Research Team for All - Influence Without Authority
March 9, 2022
"AI isn't good at context yet; it may insist it's a B or a 13, but not that it could be both depending on view."
David ConradThe Feeling of Data
September 14, 2023
"DPM loneliness and siloing happen because of wearing too many hats and inheriting mismatched responsibilities."
John Calhoun Rachel PosmanTwo Sides of the DesignOps Coin: Teams Ops and Product Ops
January 8, 2024
"If you want your users to trust you, you need to share openly and be transparent about your research."
Amy Brana StuartRest in Peace Fly-in-fly-out Design
June 9, 2022
"The Quality Experience score helps executives make confident decisions by summarizing digital experience quality in a single number."
Rima Campbell Amrit S BhachuIncrease Productivity and Drive Business Impact
September 24, 2024
