Getting in Flow with Your Team
Summary
A design process is only as good as the people who run it, no matter how "efficient" the process claims to be. This talk will cover the circumstances of a case study and the strategies that took place to establish and maintain momentum on a product that didn't have a direction. With the collaboration of a team in "flow," the work seemed (sometimes unbelievably) natural, enabling and empowering everybody not only to trust each other, but also to trust themselves in their own decision making and their own exploration of their craft and strengths with mutual trust and respect.
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
"If you need to cross a dangerous river, you don’t paddle straight into it; you use the opposing force of the river to move forward."
John CutlerOxbows, Rivers, and Estuaries: How to navigate the currents of change (without burning out)
December 3, 2024
"When fellow co-workers label an individual as difficult, it's hard not to treat that individual as a problem."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"We’re all in this together and figuring it out — making it up as we go along."
Dave GrayGroup Activity: Making Sense of DesignOps
November 7, 2017
"These aren't linear; every circle or box has multiple lines into it—our work does not fit neatly into trees or pyramids."
John CutlerThe Alignment Trap
November 29, 2023
"Simplicity is not always the answer to complexity, but understanding often is."
Abby CovertStuck? Diagrams Help
October 27, 2022
"Small micro changes every week add up — ask your team what tiny improvements they’ve made recently."
Mark InterranteCollaboration Flows in Product Development
June 9, 2017
"Naming things like the 'vibe shift' is powerful in shaping the narratives around future developments."
Devon PowersImagining Better Futures
March 9, 2022
"Researchers want designers to help them with the research because there aren’t enough researchers in the world."
Prayag NarulaHow to Empower Your Designers to Do Good Research – And Why You Want To
June 10, 2022
"Skills are like onboarding material for the model; you write them as simple markdown files that describe workflows or tools."
Peter Van DijckHands on AI #3: Claude Code for UX people
October 22, 2025
Latest Books All books
Dig deeper with the Rosenbot
In what ways can AI tools accelerate value delivery in design operations, and what pitfalls should be avoided?
What are the benefits of using Rosenbot for both UX students and instructors?
How can research and operations teams collaboratively evaluate new UXR tools for usability and operational fit?