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
"I am swimming in a sea of information, like a little fish, and eating all the stuff."
Sam LadnerHow Research Can Drive Strategic Foresight
March 9, 2022
"The primary way to convene with other attendees is through our Slack channel."
Bria AlexanderOpening Remarks
January 8, 2024
"The only way you’re going to go from good to great is through well-crafted experiences."
Maria GiudiceRemaking the Making Company: Moving from Product to Experience
June 9, 2016
"Asking someone’s origin story gets you their why, not just the what."
Indra KlavinsA Design Ops Girl in a Dev Ops World
October 23, 2019
"Taking time to intentionally create a career strategy helps avoid reactive decisions based on fear."
Corey Nelson Amy SanteeLayoffs
November 15, 2022
"Execution without discipline means no impact."
Laurent ChristophScale the impact of DesignOps in 3D: Diligence, Decision, Discipline
September 17, 2025
"Please don’t delegate hiring to HR—hiring managers must set clear criteria and be personally involved to avoid bias."
Silke Bochat5 Antifragile Strategies for a DesignOps 2.0
September 23, 2024
"AI is pretty good at finding semantic patterns among codes after human researchers have done the initial coding."
Laura KleinHuman vs. machine: Testing AI’s ability to synthesize and analyze research
March 11, 2026
"Activating insights multiple times can be necessary before teams truly internalize and act on them."
Jake BurghardtStop wasting research: Create new value with insight summaries
July 9, 2025
Latest Books All books
Dig deeper with the Rosenbot
Why are some organizations moving away from third-party customer data platforms (CDPs)?
How can teams create lightweight visibility systems that improve workload transparency without reducing productivity?
What are best practices for onboarding and operationalizing UX research tools post-procurement to ensure adoption?