Getting in Flow with Your Team
Summary
Key Insights
-
•
Frameworks help non-designers understand design decisions and foster team inclusivity.
-
•
Team flow differs from individual flow by emphasizing interdependence, not independence.
-
•
Achieving flow requires balancing challenge and skills along with clear goals and feedback.
-
•
Open communication and early involvement of all team members strengthen alignment and trust.
-
•
Strong team relationships allow teams to pivot quickly without losing momentum or morale.
-
•
Individual states of flow vary based on personal belief in purpose, scope clarity, and feedback.
-
•
Team flow benefits when members can feed off each other's energy and adapt communication styles.
-
•
Replicating team flow can be challenging with frequently changing teams due to lack of familiarity.
-
•
Respect, trust, and alignment empower teams to balance seriousness and casual connection.
-
•
Developing team flow shares similarities with dating or athletic instincts, requiring intuition and practice.
Notable Quotes
"I am usually the only designer on the team, and it gets difficult to get the information needed for design decisions."
"Frameworks are a team sport; each player brings unique strengths that help create innovative solutions."
"Surgeons say during difficult operations the whole team feels like a single organism moved by the same purpose."
"To get into flow, I need a strong belief in the purpose and the work we’re doing."
"We started with almost nothing and didn’t really know what goal we were trying to achieve."
"Getting everyone involved early helped reduce the need for me to explain why we do things."
"When we pivoted because of business decisions, we felt anxious but kept adapting together."
"Respect, trust, and alignment helped us feel empowered and comfortable talking about anything."
"Flow is different for each person; you have to adjust your style based on who you work with."
"Developing team flow is a lot like dating—you have to nurture it, build instinct, and practice."
Or choose a question:
More Videos
"We all want to design for scale, but empathy alone is sometimes a shortcoming when thinking about scale."
Nancy DouyonWe'll Figure That Out in the Next Launch: Enterprise Tech's Nobility Complex
June 15, 2018
"Interactions are exposed as events on components, so you can define that on clicking a button, a dialog opens."
Jack BeharHow to Build Prototypes that Behave like an End-Product
December 6, 2022
"Politics and ego conflicts are inevitable and separate challenges that seriously impact merger integration."
Jorge ArangoMeeting of the Waters: Designing for Successful Inorganic Growth
August 12, 2021
"We are not just doing research to find stuff out; we need to show a return on investment on everything."
Jon White Erin MayUnsticking Research for Better Information Flow
March 11, 2026
"Give a why of why you’ve made this design decision. It helps your team understand and reduces defensiveness."
Jessamyn EdwardsSurviving Your UX Career in Enterprise Design
December 2, 2021
"Many federal benefit programs face challenges verifying income, causing stress and leaving billions in unclaimed benefits."
Stefanie OwensOptimizing for Outcomes: Transformation Design in Systems at Scale
December 4, 2024
"If you do enough research, you might find 20% of your users are edge cases, so maybe you’re not building for the right people."
Ron BronsonDesign, Consequences & Everyday Life
November 18, 2022
"Slack is growing steadily for us, but it’s hard to moderate and expensive at scale."
Louis RosenfeldThe Rosenbot and the Rosenverse: An AMA with Lou Rosenfeld
June 5, 2024
"Every small initiative can lead to significant change when multiplied across communities."
Ash BrownSilver Linings: What DesignOps Learned in the Shift to WFH
October 23, 2020
