Jazz Improvisation as a Model for Team Collaboration
Summary
Key Insights
-
•
Miles Davis’s 'Kind of Blue' album was mostly recorded in one take without rehearsals, demonstrating the power of spontaneous collaboration within a structured framework.
-
•
Jazz improvisation is governed by an underlying invisible structure, such as a fixed melody (head), harmonies, and form, which enables creative freedom without chaos.
-
•
Jazz musicians follow established rules of engagement, like alternating solos and returning to the head, which parallels agile methodologies in software development.
-
•
Improvisation in teamwork works best when the team agrees on clear frameworks or rituals, such as design sprints or regular critiques.
-
•
Planning for uncertainty is essential in improvisation; teams prepare themselves to respond spontaneously within known boundaries.
-
•
Breakdowns of complex work into smaller cycles (like jazz measures or agile sprints) allow teams to build, measure, and learn iteratively.
-
•
Collaboration and respectful interaction are fundamental principles supporting successful improvisation and team creativity.
-
•
Design systems require substantive collaboration and dialogue to function effectively, just as jazz requires listening and interaction.
-
•
Team rituals and patterned engagement reduce the cognitive load on how to work together, allowing more energy for innovation.
-
•
Jazz improvisation’s universal conventions enable musicians worldwide to play together from minimal cues, illustrating the power of shared frameworks.
Notable Quotes
"Within improv, it’s a combination of listening and not trying to be funny."
"Miles gave them the music as they entered the studio; they didn’t know what they were going to be playing."
"Each first take was the only take, which got pressed on the album."
"We’re focused on the outcome; as soon as we count off the song, it’s going."
"Jazz has those rules of engagement."
"The head means the melody of a song."
"Instead of playing the melody Miles Davis wrote, the soloist creates a melody spontaneously."
"That unit there is kind of like a sprint."
"Design sprints are popular because they give us a format; we don’t have to improvise how we’re collaborating."
"Collaboration is your secret sauce in the end."
Or choose a question:
More Videos
"Status is about microbehaviors like eye contact and gestures that shape how confident or intimidating someone appears."
Cheryl PlatzMerging Improv with Design
March 7, 2019
"Think about what your manager is being rewarded for to figure out how to better support them and your team."
Ellen ChisaThe Values of Design
November 29, 2023
"Make a proof of concept before investing a lot more time and energy into a design system."
Dave Malouf Amy ThibodeauPanel: Design Systems and Documentation
November 7, 2017
"We built a linear aggression model showing direct correlation between design problems and business metrics like referral revenue."
Panel Discussion: Communicating the Value of DesignOps
November 7, 2018
"Design ops can help, but only if we can talk about it in ways that other people can hear."
Adrian HowardSturgeon’s Biases
September 25, 2024
"The outcome of this method really makes the difference between lightning and a lightning bug."
Anne MamaghaniHow Your Organization's Generative Workshops Are Probably Going Wrong and How to Get Them Right
March 28, 2023
"Partner with data scientists to pick and adjust statistical tests because quantitative ethnography requires new assumptions."
Vitorio MilianoDon’t call it AI: Turn words into numbers with quantitative ethnography
March 11, 2026
"Your next design ops peak might actually be beyond the walls of your current design practice."
John CalhounHave we Reached Our Peak? Spotting the Next Mountain For DesignOps to Climb
October 1, 2021
"Jobs to be done can be a catalyst for conversations and change by connecting teams across an organization."
Jim KalbachJobs To Be Done
February 25, 2021
Latest Books All books
Dig deeper with the Rosenbot
What are common organizational or legal challenges when designing for warmth and community connection?
Why is it important for product teams to focus on questions rather than jumping straight to methods?
What is 'vibe coding' and how does it reflect changing expectations for junior design and product roles?