Summary
Trying to plan and collaborate across different teams whilst creating a cohesive culture can sometimes feel like a pipe dream. This is especially true as we start to work with more distributed teams and as we add more and more specialised functions to the mix, such as Design, Research, Content Strategy, Product Management, Engineering, Data Science…oh my! There are also a few common myths which are just not true in today’s modern team environment. Come along for a few laughs as we explore a few popular myths, debunk them and arm you with a few practical tips and ideas to help you build world-class products.
Key Insights
-
•
Rigid roles and responsibilities create us-versus-them mentalities and blame games rather than solving collaboration problems.
-
•
Starting projects by defining outcomes and responsibilities rather than roles fosters adaptability and clarity.
-
•
Teams perform best with autonomy, mastery, and purpose, which rigid processes often undermine.
-
•
Co-creation and joint accountability break down discipline silos and improve project alignment and engagement.
-
•
Trust does not happen automatically, especially in remote teams; it requires deliberate effort and relationship building.
-
•
Raising communication bandwidth—in-person or video calls—is crucial to resolving misunderstandings and maintaining trust.
-
•
Involving all disciplines early and continuously, with broad participation and transparent updates, leads to better outcomes.
-
•
Understanding the history and context of a product is as important as aligning on future goals to avoid repeating mistakes.
-
•
Sharing work early and often, such as via walls, brown bags, or workshops, fosters customer empathy and team cohesion.
-
•
Measuring team health through self-assessment of key attributes helps guide productive conversations and project focus.
Notable Quotes
"Solid roles and responsibilities will solve everything is a myth that leads to blame games and ignores team diversity."
"Teams constantly bicker over turf blaming the various disciplines for their inability to meet deadlines – Alan Cooper."
"You have to know when to raise the bandwidth and jump on a video call if slack threads exceed 10 concurrent comments – Mike Nup."
"Who is not in the room is just as important as who is – Aubrey, head of diversity and belonging at Atlassian."
"Effective teamwork is about being adaptable, messy, and having a clear purpose."
"Process is neither necessary nor sufficient for great design – Mark Parnell."
"Sharing research and design work early fosters empathy and stops the ‘big reveal’ failures."
"Great teams want autonomy, mastery, and purpose — guard rails, not rigid process."
"Showing you care by asking colleagues how they are and actually listening builds trust."
"Trust is fundamental; when trust is high, speed goes up and costs go down – Stephen Covey."
Or choose a question:
More Videos
"I have to triangulate socially because Yorkshire folks are quite reserved; they won't openly admit issues."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"UX directors often feel like this poor person in the middle here getting pulled in all these directions."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"If you haven’t designed who your teams are and who your players are, expecting people to comply with standards won’t work."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"Every small action contributes to a larger impact in the fight against climate change."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"Psychological safety was far and away the key ingredient for teams being effective."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Thick data is the opposite of big data; it’s stories, qualitative, and crucial during moments of rapid change."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"If you don’t bring stakeholders into the research journey, they won’t believe or use the data."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"Our brains are terrible at operating only on one type of information, whether object-oriented or context-oriented."
Designing Systems at Scale
November 7, 2018
"Conversion design means to create intentional change."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024