Summary
The session includes several UX and product experts, including Ariel, Ross, Mark, and others, sharing rich insights on cross-organizational collaboration and design practices. Ariel details a comprehensive 75-page journey map he developed for a city government project, emphasizing the importance of creating shared documentation and safe spaces for policy conversations. Ross shares his transition from engineering to UX driven by user stories and empathy, while Mark explains how APIs help coordinate requests for design resources across large teams, ensuring that workload is manageable and transparent. The group discusses techniques for empathizing with higher-level stakeholders, including understanding how they’re measured and aligning design goals with their success metrics. They tackle maintaining continuity as teams and members change by recommending thorough handoff documents and horizontal roles overseeing core experiences. Agile challenges are addressed through dual-track agile methodologies and A/B testing, allowing iterative design in short sprints. The importance of including support teams in design feedback loops is highlighted, with suggestions for tagging support tickets for visibility. Ariel also speaks about building an internal community of practice and design kits to encourage civic service design culture. Additionally, small human gestures like sending thank you cards across silos prove effective in fostering empathy. The panel underscores making documentation accessible and integrating technical writers within UX teams. The conversation weaves in practical examples and cultural tactics from companies like Honeywell, HP, and government agencies, all focusing on bridging organizational silos to deliver better user-centered products.
Key Insights
-
•
A detailed journey map for government services can span 75 pages and serve as a critical shared internal document to build understanding across commissioners, staff, and providers, as Ariel described.
-
•
Successful collaboration in government requires designers to learn enough policy to engage as trusted peers, creating safe spaces to surface real issues and invite constructive change.
-
•
Ross transitioned from engineering to UX by discovering inspirational user stories in product feedback that generated empathy and motivation to improve user experience.
-
•
Mark’s team created lightweight 'APIs' for other teams to request UX resources, including tracking states like accepted, in progress, or rejected, helping manage demand and transparency.
-
•
Empathizing with stakeholders higher up the org involves understanding how they are measured and what success means for their role, enabling better alignment of design goals.
-
•
To maintain continuity across feature teams with turnover, special onboarding sessions and 'going away' documents are critical handoff rituals that save time and preserve context.
-
•
Dual-track agile separates design and product discovery (one track) from development sprints (another), giving designers more runway to iterate and validate ideas.
-
•
Including support teams in scrums or regular meetings improves visibility of design-related customer issues; tagging support tickets enables focused review of design feedback.
-
•
Simple gestures like sending physical thank you cards across organizational silos can foster empathy and build cross-team relationships beyond technology.
-
•
Making documentation and toolkits in plain language, avoiding jargon, broadens access for cross-disciplinary teams and elevates the value of information design within UX.
Notable Quotes
"The consolidated view is really the invitation in to help get people excited and also help them see that we've created documentation that didn't exist previously."
"As a designer and leader in this space, I've had to learn a lot about policy so I can come in and have really deep discussions with policy folks as a peer."
"I started just searching for product name to look for bugs, but then found inspirational stories that helped me build empathy for users."
"We created APIs so people can submit ideas or resource requests in a simple structure, and then track their status from accepted to rejected."
"When I talk to stakeholders, I try to understand how they are measured and what success means for their role in the company."
"When someone swaps out on a feature team, that event needs a special onboarding: briefings and whiteboard sessions to transfer knowledge."
"Dual track agile means you have the dev sprint track and a separate design/product track that leads the dev track by several cycles."
"Invite support people to scrums or monthly engineering reviews so design can get visibility into common customer issues."
"Sending real physical thank you cards across silos surprises people and builds empathy and openness beyond what technology can do."
"We wrote our toolkits in plain English so people understand the tactics without getting lost in jargon—they can learn the jargon later."
Or choose a question:
More Videos
"Many companies start with vision accessibility because of legal risks, but accessibility should be broader."
Lija HoganPractical Principles of Inclusive Research
March 27, 2023
"Excel is a little bit outdated; more advanced cloud tools help us co-create and collaborate in real time."
Scott StephensThe Next Generation in DesignOps Toolsets
July 28, 2022
"Consistent, gentle support over time creates deeply loyal adopters."
Rachael Greene Alison DavisBuilding a Design Ops Practice that Really Works (Most of the Time)
October 2, 2025
"Not everyone using machine learning is your user; think also about the people labeling the data feeding these models."
Brian T. O’Neill Maria Cipollone Luis Colin Manuel Dahm Mike OrenDoes Designing and Researching Data Products Powered by ML/AI and Analytics Call for New UX Methods?
February 18, 2022
"Organizational information models need to grow and be managed, not treated as static deliverables."
Bram WesselEnterprise Information Architecture
January 10, 2020
"Change is the reason we keep paying attention to stories; without it, there is no story."
Jon FukudaStorytelling for DesignOps
August 17, 2023
"We’ve been taught to build fast and break things, and we often play accessibility on the back burner."
Alexis LucioScaling Accessibility Through Design Systems
June 9, 2022
"Being data informed is not data driven—blindly following data can kill you, like the Challenger explosion."
Adam ThomasSurvival Metrics – Making Change in a Fast, Data-Informed, and Politically Safe Way
December 6, 2022
"Evergreen content needs a strong perspective on why the topic matters along with practical examples on how to apply it."
Louis RosenfeldCoffee with Lou: Should You Write a (UX) Book?
March 7, 2024
Latest Books All books
Dig deeper with the Rosenbot
How can designers identify which parts of a system they can influence or should monitor using affordance mapping?
What advice does Mary Lynn give to UX professionals unsure about staying in the industry?
What role does visualizing funding distributions (like 'sausage' diagrams) play in improving portfolio management?