Summary
Design groups are no longer fringe in large corporations. We’ve grown up, and our numbers have multiplied; which is exactly what we wanted. However, we now face the challenge of integrating—at scale—with our organization’s cultural and operational fabric. Understanding which stakeholders are most needed to support our DesignOps ambitions is a great place to start garnering influence and yielding intended outcomes. Relationship maps are a powerful tool to humanize the process and chart the course.
Key Insights
-
•
Design has evolved from individual craftsmanship to system design with greater collaboration and communication across companies.
-
•
Relationship maps go beyond org charts by focusing on necessary interpersonal and cross-functional relationships rather than formal reporting.
-
•
Design leaders act as translators and managers of relationships between designers and other departments to facilitate design at scale.
-
•
Creating purposeful relationships with mutually beneficial outcomes sustains volunteer task forces in large organizations.
-
•
Leveraging executive support, such as from Maria Gideese and finance partners like Kim, helps facilitate company-wide tool adoption.
-
•
Single sign-on integration reduces barriers to adoption and increases cross-disciplinary participation in design platforms.
-
•
A manageable relationship map with clear roles (e.g. program manager Christina as captain) helps coordinate complex initiatives.
-
•
Expressing gratitude publicly and privately maintains morale and encourages continued contribution in a thankless environment.
-
•
Decentralized design teams can still provide centralized services and influence through networked relationships rather than direct authority.
-
•
Quantitative business cases focusing on cost savings and broad user adoption are crucial to convincing stakeholders to invest in design tools.
Notable Quotes
"We are outnumbered by engineers maybe a dozen to one, but things are improving all around."
"Designers are now represented in executive leadership, which was unheard of five years ago."
"An org chart is about formal reporting; a relationship map is about networking and collaboration across silos."
"Relationship maps help you get stuff done with people who don’t report to you and aren’t accountable to you."
"Design is frequently misunderstood; sometimes it’s just about explaining why it’s important to get others involved."
"Single sign-on was going to be really important because I didn’t want any barrier entry for people."
"Mutual benefit and agreement on the definition of success upfront are critical to long-term team effectiveness."
"Expressing gratitude publicly and privately gives people a sense of purpose and acknowledges their contributions."
"I worked through a volunteer task force of 15 people across the company to drive radical design collaboration."
"Not a single person on this relationship map reported to me. That’s how I affect design at scale at Autodesk."
Or choose a question:
More Videos
"People want to grow in a bushy way, not just in a linear ladder fashion."
Peter MerholzThe Mysterious Case of the Missing UX Career Path
August 25, 2022
"MJ Broadband saves our fingers some pain and some stress because we don’t have to take notes."
Louis Rosenfeld Bria AlexanderOpening Remarks
March 27, 2023
"The state of the UX profession just totally sucks, doesn't it?"
Louis RosenfeldCoffee with Lou
January 11, 2024
"The effect you have on others is the most valuable currency there is."
Melissa Eggleston Maya Israni Florence Kasule Owen Seely Andrea SchneiderPractical People Skills for Building Trust on Teams and with Partners
December 9, 2021
"I don't want a component library for the account home. I want a system for all of that."
Nathan CurtisBeyond the Toolkit: Spreading a System Across People & Products
June 9, 2016
"Learning scientific domain knowledge requires humility—being willing to say ‘I don’t get it, can you explain differently?’ and asking dumb questions."
Victor Lombardi Ted Booth HK Dunston Andrew OtwellBridging Design and Climate Science
February 14, 2024
"Disruptive innovation doesn’t happen overnight; you have to practice, fail, learn, and have patience."
Jeff GothelfInnovation Studios: the Engines of Enterprise Experimentation
May 14, 2015
"You need someone human deciding what information is good enough and tagged well for AI to surface it."
Kate Towsey Jake BurghardtResearchOps AMA with Kate Towsey & Jake Burghardt
October 16, 2025
"The community of practitioners is the way we carry each other through difficult moments."
Bria AlexanderTheme Two Intro
September 8, 2022
