Summary
In this session, Ross, Mark, and Ariel address common challenges faced by UX and product teams within large organizations, including government agencies and enterprise companies. Ross discusses creating detailed journey maps and the importance of building shared understanding across multiple departments despite political complexities. He highlights the need for empathy and ongoing dialogue with policy makers and stakeholders. Mark explains how establishing lightweight 'API' processes for design requests improves clarity and manages resource allocation, especially in sales support. Ariel shares experiences building civic design toolkits and fostering design culture through proactive workshops and community building. The group also tackles issues such as integrating design in fast agile cycles via methods like dual-track agile and A/B testing, overcoming siloed teams across global time zones by respecting cultural differences and travel practices, and maintaining continuity amid team changes by emphasizing core design artifacts and thorough handoffs. They underscore the value of involving support teams to surface design-focused feedback and the benefits of incorporating technical writers within UX teams to improve documentation clarity. Throughout, the speakers stress making processes accessible, fostering empathy with stakeholders and economic buyers, and using data-driven arguments to align business goals with user needs.
Key Insights
-
•
Ross created a 75-page detailed journey map document to build shared understanding across government departments, despite political challenges.
-
•
Building empathy with policy makers involves deep knowledge of policy and making it safe for them to discuss challenges and opportunities for change.
-
•
Mark uses lightweight, structured 'API' style requests for design input and sales support to manage resources and provide transparency.
-
•
Ariel's civic design toolkit combines passive materials like stickers and posters with active workshops, creating a community of design-curious participants.
-
•
Respecting time zones and cultural differences is crucial for effective collaboration across distributed teams; rotating meeting inconvenience fosters equity.
-
•
Travel for remote teams should avoid quick visits; extended stays and working alongside local teams build trust and visibility.
-
•
Embedding support team members into design and engineering processes surfaces critical design feedback and reduces support costs.
-
•
Using A/B testing and dual-track agile enables design teams to iterate and validate ideas ahead of development sprints in short agile cycles.
-
•
Maintaining continuity across feature teams requires keeping core design artifacts visible, proactive handoffs, and horizontal roles overseeing consistency.
-
•
Integrating technical writers into UX teams can improve documentation quality and make design knowledge more accessible across disciplines.
Notable Quotes
"The consolidated journey map was a 75-page book with labeled dots and narratives, issued internally to commissioners, staff, and providers to build shared understanding."
"I had to learn a lot about policy so I could have deep discussions and work alongside policy folks as a peer."
"We created APIs so other teams can request design work and sales support with clear response times and status tracking."
"We use stickers, pins, and posters to bring design methods front and center in people’s daily office lives."
"Respect for time zones is the most important thing when collaborating across global teams, and inconvenience should be rotated."
"Don’t do hit and run travel; I try to stay three or four days so I can have pickup meetings and lunch to build relationships."
"Spending a day in support helps designers learn critical user pain points and builds empathy across teams."
"A/B testing allows small design teams to show real value through data when integrated into fast-moving agile processes."
"Make leaving team members write a going away document capturing uncompleted work and lessons learned as a gift to successors."
"Our toolkit uses plain English to avoid jargon so everyone can understand and engage with design tactics."
Or choose a question:
More Videos
"Teaching product managers heuristics took 15 minutes, and now they use that shared language to articulate design."
Standardizing Product Merits for Leaders, Designers, and Everyone
June 15, 2018
"I realized I was just making it up despite the company’s growth."
Simon WardleyMaps and Topographical Intelligence (Videoconference)
January 31, 2019
"The Twitter algorithm favored lighter skin tones when cropping images, reflecting racial bias in tech."
Sandra CamachoCreating More Bias-Proof Designs
January 22, 2025
"By observing, appealing to interests, and promoting accountability, we can build empathy and respect to combat toxicity."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"Timely engagement helps stakeholders make faster, more informed decisions that lead to better business and product outcomes."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"Craft should evolve from making a beautiful final object to serving as a facilitative anchor in enterprise UX."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"What’s so difficult about designing a login? On the surface, it’s simple, but the real challenge was cultural alignment across business units."
Davis Neable Guy SegalHow to Drive a Design Project When you Don’t Have a Design Team
June 10, 2021
"We did a great cleanup of patterns from every decade and deleted anything off brand or untested."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Product managers feel design is a black box; they want visibility, transparency, and accountability on timelines."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
