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."
Dig deeper—ask the Rosenbot:
More Videos
"If you think about it, the theme is you — the 613 people from around the planet bringing so much energy and diverse experience."
Bria Alexander Louis RosenfeldWelcome
September 8, 2022
"The essence of strategy isn't painting a grand vision of the future, it's deciding what not to do."
Mike OrenWhy Pharmaceutical's Research Model Should Replace Design Thinking
March 28, 2023
"We should think of AI as our ancestor encountered fire: managed well it’s a force for good, deployed recklessly it will burn us."
Jodi ForlizziDesign and AI innovation
June 5, 2024
"Our sponsors bring so much color and light into the community; the conference really would not happen without them."
Bria AlexanderOpening Remarks
October 3, 2023
"Marketing is psychology; to sell, you need to know how people think and feel."
Michael WeirMixed Methods and Behavioural Science (Videoconference)
May 26, 2023
"The definition of UX research is something we revisit and share regularly so it remains evergreen and aligned with our growth."
Molly FargotsteinMultipurpose Communication & UX Research Marketing (Videoconference)
September 12, 2019
"Emotions are not universal at all; emotions and behaviors are constructed by the culture and society where they come from."
Verónica Urzúa Jorge MontielThe B-side of the Research Impact
March 12, 2021
"How is information stored, found, and used? What systems turn data into actionable context-rich knowledge?"
Husani OakleyTheme Two Intro
June 6, 2023
"Unlike tools like XD or Figma, we don’t just show specs, we ship actual components with hooks and accessibility built-in."
George Abraham Stefan IvanovDesign Systems To-Go: Reimagining Developer Handoff, and Introducing App Builder (Part 2)
October 1, 2021
