Cartography for Design Communities
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
"Each team should talk about their core values like integrity, accountability, and respect to work together with the same mindset."
Jon Fukuda Amy Evans Ignacio Martinez Joe MeersmanThe Big Question about Innovation: A Panel Discussion
September 25, 2024
"Accessibility is not a shackle; it’s a way to expand our minds and innovate."
Sam ProulxAccessibility: An Opportunity to Innovate
March 9, 2022
"Requesting glossy portfolios up front risks excluding candidates with strong problem-solving skills who may not have had opportunities to showcase visual design."
Anna Avrekh Amy Jiménez Márquez Morgan C. Ramsey Catarina TsangDiversity In and For Design: Building Conscious Diversity in Design and Research
June 9, 2021
"SSML is huge for advancing bot voice; tone and cadence carry more meaning than words alone."
Greg NudelmanDesigning Conversational Interfaces
November 14, 2019
"All our components can be data bound so the developer can point to any data source like CMS or JSON to populate UI elements naturally."
George Abraham Stefan IvanovDesign Systems To-Go: Reimagining Developer Handoff, and Introducing App Builder (Part 2)
October 1, 2021
"I promise chief design evangelism is not religious."
Shipra KayanMake your research synthesis speedy and more collaborative using a canvas
January 24, 2025
"Focus changes are critical to inform screen reader users when dialogs open or content changes."
Sam ProulxDesigning For Screen Readers: Understanding the Mental Models and Techniques of Real Users
December 10, 2021
"We moved from Evernote to spreadsheets, to a giant affinity board in Mirror, then to UserVoice, and finally to idiomatic software with AI."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"Physical therapists see their hands as a golden resource and tend to resist technology that might replace that."
Dane DeSutterKeeping the Body in Mind: What Gestures and Embodied Actions Tell You That Users May Not
March 26, 2024
Latest Books All books
Dig deeper with the Rosenbot
How did puzzles specifically help engineers collaborate more effectively in Feyi’s case study?
What strategies help UX teams translate usability findings into stakeholder-relevant outcomes like cost savings or risk reduction?
How can power imbalances be acknowledged and shared with community members in design processes?