Design as a Team Practice, A Practical Guide to Cross-functional Collaboration
Summary
We believe cross-functional team collaboration delivers value faster for users and organizations. However, it’s not always obvious what exactly cross-functional collaboration actually looks like. What practices are necessary to the team’s success? How do you measure team performance? As a developer and a designer, we have direct experience working together and leading teams on truly cross-functional product design and delivery. In our talk, we’ll provide specific examples of what that kind of collaboration can look like, while sharing some of the values and principles that have motivated us.
Key Insights
-
•
Developers struggled to make trade-offs because they lacked understanding of the broader user context.
-
•
Product strategists became frustrated as their detailed user stories began resembling rigid specifications, yet still failed to meet developers' needs.
-
•
Designers held contextual knowledge valuable to the entire team but lacked a channel to share it effectively.
-
•
Using the BICEPS model helps identify and address team members' psychological needs: belonging, improvement, choice, equity, ability, and significance.
-
•
Reimagining biweekly showcases to visualize how individual work contributes to user outcomes dramatically improved team morale and motivation.
-
•
Pairing, modeled after driver-navigator roles, supports dynamic role exchanges that enhance problem solving and learning within cross-functional teams.
-
•
Empathy and trust grow through working closely together and are foundational for effective collaboration and pairing.
-
•
The roles and responsibilities exercise reveals pairing opportunities by matching what people offer with what they need.
-
•
Pairing is not limited to core roles like developers and designers; it can include quality analysts, product managers, customer support, or even informal interests to foster creativity.
-
•
Leadership must explicitly model and support psychological safety to enable honest conversations that break down barriers to collaboration.
Notable Quotes
"Developers were hungry for the bigger picture, but the only information available to them was a set of user stories."
"It felt like an assembly line where you don't really know what is happening before you or after you."
"The BICEPS model helps understand what our co-workers need to feel supported and purposeful."
"Seeing the dots connected so clearly reminded me why I was doing what I was doing."
"Designing as a team means centering all the humans involved, not just the users."
"Pairing is two people with different roles doing an activity together simultaneously, like a driver and a navigator."
"Empathy and trust develop through working together, not in isolation."
"If you have an unmet need, pairing can help address it by matching offers and needs within the team."
"Pairing isn't about taking away jobs; it's about amplifying everyone's expertise and breaking down hierarchy."
"Psychological safety comes from having hard conversations upfront and requires demonstration from leadership."
Or choose a question:
More Videos
"We’re in this initial stage of tinkering, just trying to make the tech behave the way we expect it to."
Sheryl Cababa Ethan Marcotte Milena PribicDay 2 Panel
June 5, 2024
"Turn capping helps reset the model to prevent drift but introduces new problems around memory."
Katie JohnsonDisrupting generative AI products with just-in-time consumer insights
June 4, 2024
"Our principle is that whatever we build must help researchers avoid becoming a silo."
Sofia QuinteroThe Product Philosophy Behind EnjoyHQ
March 10, 2021
"Typing on a mobile screen reader requires exploring the keyboard and double tapping keys, which can be cumbersome."
Sam ProulxUnderstanding Screen Readers on Mobile: How And Why to Learn from Native Users
March 27, 2023
"Broadening design beyond UX/UI into service and content disciplines reflects growing sophistication in design teams."
Jules MonzaUse These Words and Count These Things
September 25, 2024
"The pressure in design ops is often delivery-first mindset instead of quality and strategic impact - Dave Malu."
Bria Alexander Patrizia Bertini Peter Boersma Jon Fukuda Dave Malouf Theresa Slate Changying (Z) ZhengCharting the future of DesignOps: A community workshop
April 18, 2024
"Please read our code of conduct. Every participant should feel safe, included, and welcome."
Bria Alexander Louis RosenfeldWelcome
September 8, 2022
"We hadn’t really thought about governance up front at all, which is not the ideal way to do something like that."
Dave Malouf Amy ThibodeauPanel: Design Systems and Documentation
November 7, 2017
"Participant recruitment and management is like the spoke in the wheel for research tools."
Jon Temple Kalee Dankner Bruce Falk Lauren GalanterPanel: Stacks, Security, and Stakeholders: The Hidden Work of UXR Tool Procurement
March 12, 2026
