Ruth Jenkins on The ComedySportz Podcast

/

CSz Portland’s Ruth Jenkins appears in Season 3 of the ComedySportz Podcast, discussing applications of improv in Speech Language Pathology, her CSz Nickname, her CSz origins and her personal meet cute story that involves 5 Things!

https://podcasts.apple.com/us/podcast/episode-38-ruth-jumping-jack-jenkins/id1493584575?i=1000673149911

Podcasts featuring CSz Portland - Patrick Short & Ruth Jenkins

/

One of our folks suggested we collect our podcast appearances in one place. We said Yes.

Wool&Prince Founder Finds Value in Applied Improv from CSz

/
13 people from Wool&Prince gathered around CSz Portland's Patrick Short. There are lots of smiles.

Photo by Mac Bishop

Mac Bishop, CEO and Founder of Portland’s Wool&Prince, writes about his company’s experience with our Basic Improv Skills Workshop:

I'd like to share our recent team building experience. We hired an improv coach (Patrick from CSz Portland) to guide us in a workshop. I had a vague idea of the listening and communication games we'd be playing, but didn't know how advanced we'd get in a two hour workshop. Thoughts of "am I or someone on the team going to say or do something embarrassing or regrettable" were running through my mind before we started. However, in our first activity, these fears quickly dissipated and even felt irrational. The game started easy but became hilariously impossible and resulted in everyone making mistakes. The core lesson: we're human, everyone makes mistakes, don't be so hard on yourself. We tend to believe that others notice and care about our mistakes far more than they actually do. If only we could treat ourselves as generously as we treat others when they make mistakes.

By the end of the workshop, my jaw hurt from smiling so much and it ended up being one of the most rewarding Wool&Prince experiences I've had in ten years. Perhaps it was the last two years of minimal group activities due to COVID or that we went into the event with mixed expectations, or what it actually was — just an incredible shared experience of growth, laughter, and team building.

View Mac’s original post (and learn more about the great clothing) from Wool&Prince here.

Let's Fight About Making Mistakes. Or Let's Not.

/

Another mantra in the performance improv world is the celebration of mistakes.

In our classes, we want to get people past the point of editing things, and worrying about their ideas and just get them to go - to make a decision, to make a move. To that end, we "celebrate" mistakes. Participants can take a circus bow, saying, "I Failed!" and everyone will applaud wildly. This comes from a simple need: if we wait for the perfect thing to say, nothing will ever be said. Let's practice on going with our first idea, and if the idea turns out to be terrible, so much the better. We laugh about it and move on.

In our own performance ensemble, we laugh and often roll around on the floor at mistakes made within scenes or games. Even better, sometimes these mistakes result in new ways of doing things and new game ideas. Mistakes are opportunities for laughs and sometimes for growth. We love mistakes!

So, naturally, we carry the concept forward into Applied Improvisation.

Almost everyone who teaches in Applied Improv brings this "celebration of mistakes" forward into their work. This seems like a great fit, especially as people are just figuring out how to work in the games and exercises. It starts to become (or at least seem) less of a fit as our clients think about applying the lessons of the workshop to their work lives. "We can't be making mistakes all of the time," one told me recently.

Paul Z Jackson, President of AIN is trying to get practitioners to ease up on the celebration of mistakes: "People keep telling me they learn from their mistakes.  And I’m pretty sure they are mistaken." Read Paul's blog post here.

I've worked with more than a few clients who bluntly tell me they cannot make mistakes. Some of them, like 9-1-1 operators (that's 9-9-9 to our friends in the UK) and front line employees at a blood-testing laboratory service, are probably right. We don't want avoidable mistakes in their work - the results could literally kill someone.  

In those jobs, the time for making mistakes is in practice (or training).  Once the whistle blows, and we're on the clock, we need precision and error-free work.

I look at mistakes in Applied Improvisation the same way. Our workshops are practice, where people can learn new skills and figure out that errors won't kill them, or even hurt them at all. My teaching is that mistakes are part of the process of learning new skills. You can't learn something new without messing up a lot. Our workshops are a great place to mess up without consequences. "In life, we are the players who live with the consequences of the actions," says Paul Z Jackson, "Context is so important."

When we're afraid to fail, we can become paralyzed.

When we're afraid to fail, we can become paralyzed.

We want to learn to be OK with ourselves for making mistakes, but often, we're still not supposed to make them in real life. Lots of "people and organizations create high stakes environments across the board, rather than leaving room for learning and innovation. It seems like skillful leaders are those who can be purposeful about creating spaces/processes where mistakes are valued." (Jim Ansaldo, Director of Camp Yes And at Indiana University)

When is a mistake not a mistake?

"We've seen numerous scientific and technological discoveries that were the unintended consequences of other pursuits. In the Design Thinking world, the concept of "rapid prototyping" suggests that a trial and error process using stakeholder feedback is the quickest route to operationalizing great ideas." (Jim Ansaldo)

Perhaps the word "mistake" isn't even the right word for every instance of unintended results.

So, what ARE we teaching?

In Applied Improvisation, I think we are actually teaching people to be better to one another. We know mistakes are a part of doing business, so let's minimize their impact on people on our team.

My Five Pillars of the Improv System are:

  • Listening
  • Accepting
  • Supporting
  • Taking Competent Risks
  • Letting Go of Mistakes

Mistakes are going to happen, but are we going to let our team become dominated by them, or could we:

  • Own and accept it
  • Fix it as soon as possible
  • Share it so others learn
  • Move on

If we create a culture where we own it, fix it, share it and move on, we'll spend less time and energy and reduce the paralysis that comes from fear of making mistakes. Wouldn't that be a more pleasant place to work? Wouldn't that also make our customers happier? (In a Design Thinking environment, we might substitute "use it" or "analyze it" for "fix it".*)

The key thing for me in our vendor relationships is what happens when something goes wrong. It's easy to provide "good customer service" when everything runs smoothly. The response when something doesn't go right is what separates great vendors from the rest. Own it, fix it, share it and move on.

In the operational side of our own company, I'd like to be one of those great vendors, providing value and keeping things simple, but when something goes wrong, own it, fix it, share it and move on. 

Of course, we don't want to see the same mistake over and over. We don't want people deliberately messing things up. What we really want is for people to forgive each other easily for mistakes, make the problem right, have the organization learn and move on. We also want to stop the paralysis that fear brings to teams.  The world is changing too fast to let fear hold us back.

Applied Improvisors struggle to get clients to take the leap of faith to work with us. Part of the struggle might be significantly reduced if we stop "celebrating mistakes" and tell you what we're actually talking about.

It's all in the context. It usually is. It's also in the words we use to tell people what we do.

Just to keep the controversy alive, Patrick Short would like to include this list of 40 Things You Can Learn From Mistakes. He would also like to thank Jim Ansaldo for helping to cut to the heart of the matter.

I Was Used For Design Thinking Purposes

/

Shimon Shmueli set me up.

He’s the leader of Touch 360, a “strategy, innovation and design” company; he’s got a high-tech industry resume several times longer than my arm, and he was getting ready to speak at an Applied Improvisation Network regional gathering in Portland.

My contribution was to lead a series of warm-ups to the evening focused on design thinking.

I was walking to the front of the room, and Shimon took me aside and told me he thought I should lead the group in Sun and Moon.

Sun and Moon is a simple and profound activity. Participants stand in a circle, and are asked to pick a “sun” and a “moon” from among the other people. They are not to let on who they’ve picked; it’s a secret. When the game starts, they are to move quickly to “become equidistant” from their sun and moon, as fast as they can, and if their targets move on them, they have to keep moving. Chaos ensues. (There’s also a second round, but it’s not germane to the story.) Shimon had seen me run the game at a Portland State University class he teaches on entrepreneurship.

We ran the game, it was fun, and the very bright group of participants completely got the “jolts” of understanding that Sun and Moon offers.

Following another exercise, Shimon started his presentation, Creativity by Emergence and Leadership.

I can’t completely do his thesis justice, but let me try:

Doing something truly new requires intentional creativity.

Improvisation is great for

  • scenario playing and interaction prototyping
  • brainstorming via emotional uplift and allowing failure
  • demonstrating

But if a new product or service or other innovation is a story, does improvisation do the job?

Improvisation is:

  • Process, not product
  • Limited in its resources
  • Sequential, not parallel

Shimon compared improvisation to the TV show Survivor:

  • no overall leaders
  • simple rules
  • safer in large groups
  • steer toward consensus
  • unpredictable, internally and externally
  • players avoid “visibility” (they don’t want to stand out from the group – publicly)
  • common objectives fall apart fast

For design, and true, intentional creativity, you need a story line – setting the stage, anchor points, climax and the end – along with coloration.

Shimon also compared improvisation to swarm theory, and showed us videos of a very large, very active flock of birds.  If it’s “beautiful” or “cool”, it’s because we (the observers) are applying those values.  There is no creativity in what is happening inside the flock. The birds are each reacting to the moves of a group of birds in their immediate vicinity, and are continuously adjusting to aim for the center of that group.

It’s just like Sun and Moon, said Shimon, where the individual participants where simply responding to a couple of simple rules and the moves of their “sun” and “moon” (the birds in their immediate vicinity).

And that’s why we needed to play Sun and Moon. I was used.

Is he right? Is what we do just a series of responses that do not indicate intentional creativity?

Sometimes, yes. But I like to think there’s more to it than that.

Add a few constraints to improv, including some rules, styles (coloration) and a goal, and you can tell a story.

Even if improv performance is not your goal, accepting an improvisational mindset is a great way to lead to intentional creativity – build a great team and turn them loose – with constraints and a goal.

If all you are doing is reacting to the people nearest you, maybe you are just flying around in a flock. Or playing Sun and Moon. It’s fun, it might look beautiful, but it’s not creating anything.

I was used.