Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
Summary
In this talk, Kim Annex, leader of ZenDesk's product design organization, draws from over two decades of experience in distributed teams to explore the challenges and strategies of managing a global design team spanning eight countries and multiple time zones. Kim recounts early experiences with distributed work from the 1990s to today’s improved technological environment, highlighting how tools like video conferencing, Slack, and Google Docs enable better collaboration. She details ZenDesk's evolution from siloed product teams to an integrated Omni Channel approach, requiring greater cross-team collaboration and co-location. Kim stresses building trust through strong partnerships, aligning on shared values, and fostering open communication. She outlines tactical approaches such as asynchronous communication, setting clear responsibilities, limited routine global calls, and shared documentation to bridge distance. The talk also covers managing acquisitions, integrating new teams thoughtfully over time, and the importance of design specialists including design systems, research, and operations. Kim emphasizes the cultural diversity at ZenDesk and the role of off-sites and social time to build lasting bonds, while her leadership style prioritizes empowering creative technologists over just shipping products. The session concludes with insights on maintaining design quality through recurring critiques, co-located workshops, and adopting an experience-first mindset across products. Questions address remote work models, integration post-acquisitions, team structures, and how ZenDesk balances remote flexibility with a culture that values office presence.
Key Insights
-
•
ZenDesk’s product design spans eight countries with over 50 people, requiring complex coordination across 17-hour time zone differences.
-
•
The core of ZenDesk’s success lies in the Triad leadership model: product design, engineering, and business founders collaborating closely.
-
•
Acquisitions are managed with a hands-off first 100 days approach, focusing initially on IT and HR normalization before design integration.
-
•
Trust and strong partnerships underpin effective distributed team collaboration and are actively built through off-sites and social interactions like shared meals.
-
•
Asynchronous communication is critical; ZenDesk employs shared docs, Slack, and staggered meetings to accommodate global time zones.
-
•
Design systems at ZenDesk evolved into a product managed collaboratively by designers and engineers, crucial for cross-product consistency.
-
•
Cultural empathy is actively cultivated, recognizing that ZenDesk’s offices have highly diverse populations often not native to their office location country.
-
•
Leaders and team members share explicit communication about their work styles, hours, and availability to respect boundaries and maximize overlap.
-
•
Global design critiques and leadership reviews are scheduled by time zones with asynchronous commenting to maintain design quality.
-
•
ZenDesk fosters a shift from siloed product thinking to an experience-first mindset considering cohesive multi-product user journeys.
Notable Quotes
"Nothing can get done without fostering and building trust."
"Sharing meals is a really critical part of building trust which seems kind of strange but breaking bread together makes a difference."
"Design is really a team sport, and we are investing in specialists to help with design systems, operations, research, and content strategy."
"Instagram is so important for me to see what my team is doing outside of work; it builds stronger bonds."
"We have a Chief Creative Officer who leads design but also brand and workplace experience, giving design a seat at the executive table."
"Asynchronous communication means you’re not going to get an answer quickly, and you have to embrace that."
"We set expectations for who is owner and who is contributor in asynchronous work so decisions can move forward."
"The telephone game scenario happens with distributed teams all the time and when that happens, customers suffer."
"We try to limit routine global calls and break large meetings into three regional meetings so people don’t have to join at impossible hours."
"I don’t want people to do a 6 AM call — I can do a 10 PM call to brainstorm but not a design critique."
Or choose a question:
More Videos
"More ways to contact support—chat, email, phone—are essential because different disabilities require different options."
Sam ProulxOnline Shopping: Designing an Accessible Experience
June 7, 2023
"We want to build consultants who can solve problems across a variety of projects and clients."
Ignacio MartinezFair and Effective Designer Evaluation
September 25, 2024
"Transformation is new ways of thinking and eventually doing; we won’t have all the answers at the start and that’s okay."
Sarah Kinkade Mariana Ortiz-ReyesDesign Management Models in the Face of Transformation
June 8, 2022
"The Shakers’ principled approach to design was a precursor to Bauhaus’s form follows function and today’s user-centered values."
Daniel GloydWarming the User Experience: Lessons from America's first and most radical human-centered designers
May 9, 2024
"AI systems can present speculative connections as established facts, so confidence ratings are critical."
Patrick BoehlerFishing for Real Needs: Reimagining Journalism Needs with AI
June 10, 2025
"How do you build in the context of what you specifically need rather than having tools drive the research process? That’s the future."
Andy Barraclough Betsy NelsonFrom Costly Complexity to Efficient Insights: Why UX Teams Are Switching To Voxpopme
September 23, 2024
"The future of our technology cannot and should not rest solely on the ethics of individual designers."
Alexandra SchmidtWhy Ethics Can't Save Tech
November 18, 2022
"The Etsy postmortem is not about blame, it’s about open-ended discovery and learning to do better next time."
Louis RosenfeldDiscussion: What Operations can teach DesignOps
November 6, 2017
"The product is the reflection of how well teams communicate. Without clear communication, success is impossible."
Mitchell BernsteinOrganizing Chaos: How IBM is Defining Design Systems with Sketch for an Ever-Changing AI Landscape
September 29, 2021
Latest Books All books
Dig deeper with the Rosenbot
How can national development agencies strategically manage their innovation portfolios to balance risk and impact?
How do competing AI agents within an enterprise environment require new design approaches for prioritization and control?
What are the main requirements of the EU AI Act for product teams designing AI systems?