Ever thought that a marshmallow could teach you a thing or two about building effective teams?
Tom Wujec, a designer and innovator, presented a fascinating TED Talk in 2010 where he uses the Marshmallow Challenge to reveal profound truths about teamwork and collaboration. By asking teams to build the tallest freestanding structure using spaghetti, tape, string, and a marshmallow, Wujec unearths unexpected lessons on how we work together. In this article, we’ll delve into these lessons and see how they apply to agile practices. Whether you’re an agile coach, a Scrum Master, or a team leader, these insights will help you foster more collaborative and effective teams.
The Marshmallow Challenge: A Simple Yet Powerful Exercise
The Marshmallow Challenge is deceptively simple. Teams of four must build the tallest structure possible with just 20 sticks of spaghetti, a yard of tape, a yard of string, and a single marshmallow that must sit atop the structure. Initially, participants might approach this challenge with a linear mindset, planning meticulously before attempting to build. They often assume that business students, with their analytical skills, will outperform all other groups. Surprisingly, Tom Wujec reveals that kindergarteners often outperform business school graduates. This unexpected result prompts deeper exploration into team dynamics and collaborative processes.
Lessons in Team Dynamics and Collaboration
One of the core lessons from the Marshmallow Challenge is the importance of iteration. Kindergarteners tend to build prototypes immediately, test them, and refine their approach. In contrast, adults often spend too much time planning and less time experimenting. Different leadership styles emerge during the challenge. Effective teams often have a facilitator who guides the process, encourages experimentation, and ensures everyone’s ideas are heard. This leadership fosters a collaborative spirit crucial for agile teams. The challenge underscores the value of embracing failure as a learning opportunity. The teams that excel are those that continuously test and iterate, learning from each small failure to ultimately succeed.
Comparing Team Performance: Business Students vs. Kindergarteners
Business students often focus on finding the perfect plan and executing it flawlessly. However, this approach can lead to failure when the plan doesn’t hold up in practice. Kindergarteners, with their unfiltered creativity and lack of preconceived notions, build, test, and adapt continuously. This comparison reveals that the success of kindergarteners stems from their collaborative approach. They communicate openly, share ideas freely, and aren’t afraid to take risks. Agile teams thrive when they adopt similar behaviors. Continuous communication, iterative development, and a willingness to adapt are key to delivering successful projects.
The Power of Prototyping and Feedback
The iterative process leads to continuous improvement. In Scrum for example, this is akin to regular sprints where teams deliver increments of work, gather feedback, and make necessary adjustments. Regular feedback loops are essential. They allow teams to identify what’s working and what’s not, enabling them to pivot quickly and efficiently. Many successful agile teams implement these principles. For example, software development teams often use prototypes to gather early user feedback, which guides subsequent development phases.
Building Effective Teams: Key Takeaways
Cultivate a culture that embraces experimentation and views failure as a stepping stone to success. This mindset encourages innovation and continuous learning. Effective facilitation is crucial. A good facilitator helps the team navigate challenges, keeps the focus on goals, and fosters an inclusive environment where all ideas are valued. Empower every team member to contribute. When everyone feels their input is valued, collaboration and creativity flourish, leading to more innovative solutions.
Personal Anecdote
In my own experience, I’ve seen teams transformed by adopting these principles. For instance, one team switched from a sequential to an iterative way of working. Where before they produced all documents first, then wrote the features, and only at the end integrated them, they now started showing a working product every week. In their first Sprint Review they proudly announced their new financial calculation feature was done. When I asked them to actually show it in their software, there was a small commotion at first. After 5 minutes the developers had gotten a laptop, hooked it up to the beamer and were about to actually show the new feature. But when they opened the application, they discovered this: While the feature was in there “somewhere”, they had forgotten to add the menu item to actually start it 😅. A small glitch that was easily fixed, but imagine such glitches amass and exploding in your face at the final integration phase!
Next Steps
Try the Marshmallow Challenge with your own team. It’s a fun and insightful exercise that reveals a lot about your team’s dynamics. Start small. Introduce iterative processes and regular feedback sessions into your workflow. Encourage open communication and experimentation. The journey doesn’t stop here. Continue exploring agile practices and look for new ways to enhance your team’s collaboration and effectiveness.
We’ve explored the Marshmallow Challenge and uncovered key lessons about teamwork and collaboration. From the importance of iteration to the power of feedback, these insights are invaluable for any agile practitioner. Remember, the tallest towers aren’t built by those who never fail but by those who learn and adapt from every setback. Embrace the journey of continuous improvement and watch your team reach new heights. Share your thoughts and experiences by replying to this email or commenting below. How has your team benefited from these practices? Let’s continue the conversation and learn from each other!
Let’s get to building those towers! 🏗️🚀
To get more, consider upgrading to a paid subscription. You’ll join our Discord community and get access to all past articles.