Search
Collaboration
Lightning Talk: Lessons from Theater and Software
Edit
#teamwork
#collaboration
#software-development
#engineering-culture
#mentorship
Summarized using AI

Lightning Talk: Lessons from Theater and Software

Kevin Stevens • September 25, 2013 • Earth • Lightning Talk

In this talk presented at the Rocky Mountain Ruby 2013 conference, Kevin Stevens, a software engineer and former theater actor, explores the parallels between improvisational theater and software engineering. Drawing from his unique background, Stevens highlights how the principles of theater can enhance collaboration and creativity in software development.

Key points discussed in the talk include:
- The Relationship Between Theater and Software Engineering: Stevens reflects on how his experiences in theater have positively impacted his work as a software developer. He humorously notes that while theater involves more hugs than software engineering, both disciplines share a reliance on collaboration and creativity.
- Principles of Improvisational Theater: He introduces the concept of improvisation which, despite its seemingly chaotic nature, is governed by foundational rules that support creativity. The first rule he emphasizes is to ‘just say yes,’ which is about being open and accepting ideas from teammates.
- Constructive Communication: Stevens addresses the common notion of needing to correct others. He advocates for constructive feedback—embracing and enhancing someone’s idea rather than outright rejecting it. For example, he illustrates this by showing how to guide a junior engineer through a mistake without discouragement.
- Role of Team Members: Every participant in a collaborative project has a role to play, and everyone should feel free to offer ideas, however ridiculous they may seem. He cites that many innovative products arise from seemingly absurd suggestions, stressing the importance of supporting your teammates.
- Equality in Contribution: Stevens emphasizes that collaboration should be egalitarian, where everyone's contributions are valued. He alludes to the cultural notion in improvisation that there is no single star; rather, success relies on the collective efforts of the team. Each member's questions and issues should be treated with the same importance as one’s own.
- Avoiding Rock Star Mentality: He concludes by cautioning against the ‘rock star’ approach to teamwork that values individual brilliance over collective progress. He shares thoughts on how this mentality can lead to feeling undervalued, especially when working purely for financial gain.

Overall, Stevens encourages a shift towards a more supportive and inclusive culture in software development by applying lessons from the theater, ultimately promoting better teamwork and enhanced productivity. He concludes with a reminder that every idea is valuable, regardless of initial perception.

Lightning Talk: Lessons from Theater and Software
Kevin Stevens • September 25, 2013 • Earth • Lightning Talk

Help us caption & translate this video!

http://amara.org/v/FG68/

Rocky Mountain Ruby 2013

00:00:00.480 Welcome to my talk!
00:00:08.420 My name is Kevin Stevens. I'm a software engineer at Engineered. Today, I'm going to talk about my experiences in both theater and as a professional software developer. This is about the briefest bio I can possibly give you. I have a degree in computer science and a degree in acting. I worked for Siegfried and Roy, and I used to spend summers at the Colorado Shakespeare Festival.
00:00:20.460 I've always been amazed at how much I've learned in theater that applies to software engineering. I want to share some insights about that. I'm often asked what the biggest difference is between theater and software engineering. My usual response is that there's a lot less hugging in engineering. However, that perspective changed when I started working with Wayne.
00:00:34.860 Now, I want to talk specifically about improvisational theater. While improvisation can appear chaotic, there are underlying rules that you must follow. These rules are not meant to constrain creativity; rather, they help you open up to the ideas of others, enhancing your teamwork and potentially improving your code. The first principle is 'just say yes.' This means you need to be open, honest, and receptive to the ideas of your teammates.
00:01:06.540 By the way, did anyone get that Prague Rock joke? Ah, it seems everyone here is around my age—AARP cards for everyone! Tina Fey, in her book 'Bossypants', discusses this principle. The first rule of improvisation is to agree. Always agree and say yes. In improvisation, you are required to accept what your partner creates. For instance, if I say this is a gun, you can't respond by saying that's your finger; doing so causes everything to grind to a halt.
00:01:24.580 One common objection I hear about this rule is the belief that we must inform others when they're wrong. While I agree, how you communicate matters significantly. Instead of rejecting an idea outright, embrace it and add to it. For instance, when addressing a junior engineer's mistake, a response like, 'Yes, I see why you might think that, but here's why we need to approach it differently,' is more constructive.
00:01:58.020 Next, everyone plays a role. You, no matter who you are, are entitled to be silly and propose even the most ridiculous ideas. Many excellent products started from someone else's seemingly absurd thoughts. Let's take a moment to think about this idea. Stephen Colbert explains that you are not the most important person in a scene—everyone else is. If they are the focal point, it's your job to support them.
00:02:19.020 The good news is that you are in the scene too, meaning that others will also support you. In improvisational theater, just like in life, there are no winners; everyone is making things up as they go along. If all team members treat each other as equally important, it fosters an environment of support and progress. Practically, this translates to not brushing off someone's questions in favor of a quick Google search; instead, treat their issues as if they are just as important as your own.
00:02:55.319 In conclusion, we should move away from the rock star, ninja, or superhero mentality. Everyone has valid ideas, even if they seem foolish at first. Remember, Johnny Depp playing Tonto was once considered a questionable decision! Finally, if you're working just for the money, you'll likely feel underappreciated.
00:03:06.360 Thank you all for listening!
Kevin Stevens
@KevDog
Explore all talks recorded at Rocky Mountain Ruby 2013
+17