<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Richard Kasperowski on Medium]]></title>
        <description><![CDATA[Stories by Richard Kasperowski on Medium]]></description>
        <link>https://medium.com/@rkasper?source=rss-8de0ae241122------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*EaR3QIvJbe-nSeL4HfIm3g.jpeg</url>
            <title>Stories by Richard Kasperowski on Medium</title>
            <link>https://medium.com/@rkasper?source=rss-8de0ae241122------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:39:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rkasper/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to Make Your Current Team Your Best Team]]></title>
            <link>https://rkasper.medium.com/how-to-make-your-current-team-your-best-team-6e21afd5bd50?source=rss-8de0ae241122------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e21afd5bd50</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[friendship]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Richard Kasperowski]]></dc:creator>
            <pubDate>Sun, 10 Apr 2022 19:21:56 GMT</pubDate>
            <atom:updated>2022-04-10T19:21:56.867Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Richard Kasperowski and Catherine Louis conversing on With Great People: The Podcast for High-Performance Teams" src="https://cdn-images-1.medium.com/max/739/1*l3yQEtTBKKhAsQkVGM7SLg.gif" /></figure><p>Last week, I had a great conversation with <a href="https://www.linkedin.com/in/catherinelouis/">Catherine Louis</a>. Catherine is a coach, trainer, and consultant helping people like their customers, create high-performance teams, optimize value, innovate and learn together. But it is Catherine’s unique experience as a K9 handler and a search and rescue technician that brings valuable new perspectives on rapid deployment, dynamic teams, and quick team cohesion. <a href="https://kasperowski.com/podcast-81-catherine-louis/">We captured our conversation in an episode of my podcast, With Great People: The Podcast for High-Performance Teams.</a></p><p>Here’s the full interview:</p><p>Richard:</p><p>Hi friends, welcome back to With Great People. The podcast for high performance teams, I’m Richard Kasperowski, and our special guest today is Catherine Lewis. Catherine is someone who knows a lot about a lot of different kinds of teams, she’s a coach, trainer and consultant. She helps people delight their customers, create high performance teams, optimize value, innovate, and learn together. To support this podcast, visit my website, Kasperowski.com.</p><p>Hello, Catherine. It’s so great to see you again.</p><p>Catherine:</p><p>Hey Richard, thanks for inviting me.</p><p>Richard:</p><p>Oh my pleasure. I’ve been looking forward to this for a long time. We’ve been trying to set a date and one or the other of us has been busy and I’m so happy we can finally do this. Is there anything else you would add on to that introduction? What else would we about you?</p><p>Catherine:</p><p>I really enjoy helping teams solve wicked problems. And perhaps one thing folks don’t know about me is I’m a canine handle handler, a search and rescue technician, I help find missing people using my little doggy right there that’s Vega and we get called out by emergency management in North Carolina. So it’s a something I’ve been doing over 20 years.</p><p>Richard:</p><p>Cool, cool. And it’s interesting and unusual. It’s not for most of us, it’s not a normal thing we think about or talk about or of course do so it’s really cool.</p><p>Catherine:</p><p>Yeah, I don’t have a picture here, but I have one in the kitchen of my grandmother who used to import German shepherds and train them for the Chicago Police Department. And I was the one year old baby that they put in the tree for those dogs to learn and find. So I’ve kind of been handed down this work with animals to find missing people thing.</p><p>Richard:</p><p>Wow, so this has been in your family for generations.</p><p>Catherine:</p><p>Little bit, yeah.</p><p>Richard:</p><p>That’s so cool. So this podcast is about teams and you work with a lot of teams. You do a lot of interesting things with a lot of different kinds of teams. What’s your single best team ever? Work team, a search and rescue team, any kind of team at all, any group of two or more people who have a common goal, what’s your best one of those?</p><p>Catherine:</p><p>I’m going to answer this from what I’ve learned with Search and Rescue and what I’ve learned in my tech career. And I’ve been in tech since I was 17. The best team ever is the team that I have at the moment.</p><p>Richard:</p><p>Okay. And okay, I need you to expand on that. What do you mean, the best team is a team you have in the moment?</p><p>Catherine:</p><p>I think there’s a tendency for folks to look outside of their team, to find somebody else to improve the team before looking at what the team, where the team wants to go themselves and how can we help them as a team together, help each other grow. And if we focus there, you’ll get the best team.</p><p>Richard:</p><p>Okay. Now I want to make this concrete, is there a team of the moment right now, or a recent team of the moment that we could talk about.</p><p>Catherine:</p><p>The last search I went on, that could be the last search I went on, I got a brand new team. Don’t know these people, meet the team, figure out what skills we have, how can we help each other, what our mission is, how we’re going to run the mission, how we collaborate in this mission and how we find the person.</p><p>Richard:</p><p>Yeah. Yeah, there’s so much there. I’ve got a lot I want to say. And I’m sort of at the same time, like stunned and shocked that it it’s hard to get the words out. It’s like an instantaneous team. It’s a spontaneous team. Heidi Helthen would call it a dynamic team. You, you always have a new team, They’re the short lived, they have a very specific mission and purpose.</p><p>Catherine:</p><p>Yeah, and search over search, you see some of these same people again and get to go out with them again. But you know, there’s a lot that we have in common. You know, we have the bug, we want to find that missing person. So we’re all out there. We believe in it, we believe in the mission.</p><p>Richard:</p><p>Yeah.</p><p>Catherine:</p><p>So imagine a team that you’re on and a tech team, and you start out just assuming everybody believes in the mission, isn’t really a good thing to do.</p><p>Richard:</p><p>Or that we even know what the mission is.</p><p>Catherine:</p><p>Yeah, we could perhaps just work and not know why we’re working.</p><p>Richard:</p><p>Yeah, I mean, I just love writing code. Just loves walking in the woods, I don’t know.</p><p>Catherine:</p><p>Yeah.</p><p>Richard:</p><p>But it would really good to get that out, right? And, and so you have, I don’t know, some techniques, do you have like a checklist you go through to spin up, to connect together as a team quickly.</p><p>Catherine:</p><p>You are probably familiar with this market of skills exercise we do with agile teams. It’s a great one to do with the team. You know you say, hey, what skills do we have to offer one another? I’ve got pets at home, for example, I could help you watch your dog. They ask, what does your dog do when they find sent? And I explain to them, now I have a flaker, you know, somebody who can help me watch my dog or somebody else says, you know, I’ve been in Orient Hearing Club for 20 years. Okay, you’re our navigator, you know? So you have, what are the skills people have? And then you do another round of that and say, what’s maybe one skill that you have under the table that you want to share, that might not be related to search at all. And I used to be, I was in combat and I was a medic, oh, okay. There’s somebody who can help us if somebody gets hurt. And then you ask, what do you want to learn from one another? And you get this collaboration. Yeah. Also check for what’s in everybody’s backpack. We share what’s in our backpack. Do you have enough water? If you don’t have enough water, get the water that you need so that we can go out for 12 hours. What do you need that you don’t have, that somebody else could supply? You know, so you’re instantly cover for one another, even before you start.</p><p>Richard:</p><p>All right. So that’s a great way to put up a team really fast and connect with each other. And actually, I usually admit this, when I say this is what a team is, I define the word team, but you’re actually figuring out how to depend on each other, right. ’Cause that’s what a team really is. When you can’t do it without each other. So you’re really connecting with that.</p><p>Catherine:</p><p>Yeah, yeah. I mean, I have asthma. I want to make sure everybody knows where my inhaler is because you know, I might not be able to reach it when I need it, you know? So you show your own vulnerabilities too.</p><p>Richard:</p><p>Oh that too. Yeah, I’m taking little notes as we go. So this most recent search and rescue team, another thing I always ask is if you could take the experience of being on that team and the way it felt to be there, the way it felt within you, what’s one word you could use to describe the feeling of being together with that team.</p><p>Catherine:</p><p>Two words, fluidly, collaborative.</p><p>Richard:</p><p>Fluidly collaborative, and what do you mean?</p><p>Catherine:</p><p>So we’re collaborating and not just, you know, two people collaborating, the whole team is collaborating and it’s not planned. It’s fluid.</p><p>Richard:</p><p>Yeah, what’s an example of that?</p><p>Catherine:</p><p>We have an area and I have somebody near me who’s helping me watch my dog. And then somebody on the other end notices that we are actually in the middle of an Angus beef ranging area. And these are not nice animals. So everybody, let’s head and we give them a coordinate that’s on the other side of a fence, so it’s something that we can handle, you know? Yeah. I don’t know if that’s a good example, but it’s what it feels like. You know, it’s a complex thing search. There’s the environment. There’s the animal that has good days and bad days, the search dog, people have good days and bad days, the weather conditions, because the scent is on the wind and this complexity is just like software development complexity.</p><p>Richard:</p><p>Okay, that’s interesting. And okay, so there’s a lot of complexity, including with the search dog. And you told me something that I joke about with my wife sometimes when we’re walking our little dog who is not a search and rescue dog, she’s just a little, you know, little dog. But even sometimes she does this, you told me something like training a search and rescue dog. Basically what you’re teaching the dog and I’m going to mangle what you told me. But the way I say is, when you’re training a search dog, you’re teaching the dog that there are these slow animals who can’t hear well, who can’t smell well, who can’t see well, they walk on two feet instead of four feet and you just have to be patient with a humans, dear search dog. And even our little house dog is like this with us sometimes, she’s like looking back at us, like why can’t you keep up?</p><p>Catherine:</p><p>Yeah.</p><p>Richard:</p><p>Or why didn’t you hear that? Why can’t you smell this? Why aren’t you fascinated by this scent on the ground?</p><p>Catherine:</p><p>They get to communicate very elaborately. I mean, sometimes she’ll smell like the sock of the missing person, and do you see it? Do you see it, and then jump on me? Like there it is. Do you get it, do you get it again? And again, because I’m the dumb one at the end of the leash.</p><p>Richard:</p><p>Right, it’s a funny way to think about dogs and humans. Funny way to think about humans. We’re the dumb ones at the end of the leash.</p><p>Catherine:</p><p>We are.</p><p>Richard:</p><p>This most recent search and rescue team subjectively, how do you know that it was a great team?</p><p>Catherine:</p><p>I kind of alluded to it earlier. We really care about what we’re doing. And there’s a feeling of giving and receiving trust. We operate like a team, so if somebody is in need of help, we slow down and help the slowest person on the team because we’re only as fast as the slowest person on the team. And we all want to get better at what we’re doing. So we want feedback. We all want feedback all the time.</p><p>Richard:</p><p>All right, there’s a couple things in there I want to hear more about, this idea about as a team, we’re only as fast as the slowest person on the team. Is that generalized to all teams? Is it specifically or only for search and rescue teams?</p><p>Catherine:</p><p>So let’s take it to a tech team where some director says that for every five developers, we need one tester. How fast do you think that team is going to be able to go?</p><p>Richard:</p><p>That team is going to be as fast as that one tester, I mean, if they care about product quality.</p><p>Catherine:</p><p>Yeah, exactly, yeah. So it’s the same thing. There’s multiple skills on the team and we experiment to try to do, so normally there’s one handler per dog, and I’ve been playing with this idea of, so let’s say you’re on the team. You’re searching further away. And then I send my dog to you to search with you a little bit and then come back to me. So I’ve expanded my coverage area with the dog helping between. And then when I come back to incident command, I show them the map that has the dog trail, your trail and my trail. And we can eliminate that search area it’s covered.</p><p>Richard:</p><p>Yeah. Got it, and what about, you mentioned feedback, all of you want feedback, what is that about?</p><p>Catherine:</p><p>Let’s just take last weekend’s training. I have my partner’s dog I was working ’cause he has a broken wing. He had rotor cuff surgery and working his dog. I need help with different angles reading his dog, so I don’t work him alone. I make sure I have the missing subject recording on video and then two other people recording on video. And then I take these washers and I put flagging tape on the washers and I give them to everybody. And I say, when you see something, just toss that where you saw it, toss the washer. And then when we finished the problem, we debrief, looking at all the washers and getting the feedback from everybody. What did they see?</p><p>Richard:</p><p>So interesting.</p><p>Catherine:</p><p>And I learned so much about reading the dog with that kind of feedback.</p><p>Richard:</p><p>Okay, okay, what a great technique. I want to do that with people teams.</p><p>Catherine:</p><p>Yeah, you can, I’ve done it. Here’s what I do with my search team. I’ve pull out the flagging tape with all these washers. Just drop the washer where you need to give some feedback. And then at the very end of whatever activity is, we’ll just look at all the washers and get the feedback.</p><p>Richard:</p><p>What a cool tool, what a great technique for learning.</p><p>Catherine:</p><p>Yeah, I like it because you can pull one out of your pocket and throw it towards a wood line where that thing happened. It’s kind of almost necessary in the woods. It would be a little dramatic in the classroom.</p><p>Richard:</p><p>I’ve used something like that in real work. But it was like only as a joke or only for negative feedback. We had like an NFL yellow flag that we would throw. It was actually, it was actually the TMI flag, the too much information flag. If somebody was like oversharing, which in retrospect, there is no oversharing. That’s like connecting with each other more. But in that team, our norm was if somebody was sharing too much, we would throw the flag.</p><p>Catherine:</p><p>That’s funny.</p><p>Richard:</p><p>But if we could have used that for like maybe a green flag or something, or just a neutral flag, anytime something interesting happens, we could have used it.</p><p>Catherine:</p><p>Yeah, I think it would have to be something that doesn’t make as much noise as a washer.</p><p>Richard:</p><p>Or as dramatic as an NFL referee flag.</p><p>Catherine:</p><p>Yeah, yeah.</p><p>Richard:</p><p>So this idea of the feedback technique with the washers, that’s something, that’s a technique you were doing. That’s a behavior that you were doing and that’s something that somebody from outside the team could have observed. Is there anything else objective about the team that we could use to know that this was a high performing team.</p><p>Catherine:</p><p>Objective versus subjective. Lots of laughter, lots of laughter. And we have this. So the variables are huge. You know, there’s the search area that has stuff in it that we don’t know what’s in there. ’Cause it’s a brand new area, the dog, the human, the weather, and plus your own personal emotions at the time on that day. And you want to set up these experiments playing with all of this. So go to Lowe’s Garden Center and put somebody in one of those closed containers and see if your dog can find the person that’s in a place where cushions should be, but make sure they have air. If you’re putting somebody in there, put somebody at some inaccesible places, just think about all the things that could, the Angus beef example, there’s so many things that can happen and you want to be experimenting all the time. So experimentation happens all the time. And because of that, you need to make sure there’s a safe to fail environment because you know these experiments are not going to work. The dog’s going to be afraid of stuff. The human’s going to be afraid of stuff. The wind’s going to be the wrong direction. That’s the same with tech teams. You need to make it safe to fail. Objectively, you hear lots of peer recognition. And I think peer recognition is so much more powerful than recognition from above and so much more appreciated than recognition from a above. And you know, you hear a lot of thanks a lots. That’s great, as well, you get a lot of feedback, so that’s great. Next time, try da, da, da, da. So it’s not taken with a hard, what are you giving feedback for? All of us network outside of the team. So lots of learning, lots of networking with other professionals. And I do that with search, I do that with technology, you know, try to block time to learn. And we mentioned feedback, but if I don’t get feedback, I start getting uncomfortable. So getting itchy and uncomfortable. So those are all objective. I think another one would be when we’re not aligned as a team, it’s obvious, like instantly obvious, but that’s okay, we just stop and address it.</p><p>Richard:</p><p>How is it obvious?</p><p>Catherine:</p><p>Real good example, the searchers go like that, you know, we’re actually supposed to be searching this area.</p><p>Richard:</p><p>Yeah. Literally not aligned, yeah.</p><p>Catherine:</p><p>Yeah, and I think teams, tech teams should feel the same. You know, what are we building? Are we building two different things? So just take that time to get that alignment back.</p><p>Richard:</p><p>All right. Is there a concrete behavior for getting that alignment back or what are some of the concrete behaviors for this search and rescue team that make them so great?</p><p>Catherine:</p><p>Oh, we make sure that experiments are big and visible. You know, here’s my hypothesis. Here’s what I want to try. Here’s where I want folks to be for feedback. And at tech teams, I find the strategizers test card is a really great way to make experimentation big and visible and safe to fail. You know, the test card has what’s the hypothesis, what’s the test, what are we going to measure? We are right if whatever criteria is met and you could just have a backlog of these test cards. So you’re just continually experimenting.</p><p>Richard:</p><p>Is this strategizers test card something I could find somewhere.</p><p>Catherine:</p><p>I’ll send it to you, yeah.</p><p>Richard:</p><p>Okay, I want to want to make sure people listening to us or watching us can get some of this, goodness.</p><p>Catherine:</p><p>Yeah, is there a way when you post the podcast, you can put the link in it, yeah.</p><p>Richard:</p><p>Yeah, for sure.</p><p>Catherine:</p><p>We’ll make sure you have it.</p><p>Richard:</p><p>Great. So I get how to do that if I’m working with a tech product development team, make it big vis, make these hypotheses, these experiments safe, big, visible, safe to fail. How are you doing that with the search and rescue team? Are you documenting these on paper and like waving the paper around while you’re outside? Or how does it happen?</p><p>Catherine:</p><p>There’s a GPS collar on the dog. There’s a track on my watch. There’s a GPS colla on team members. And then the washers with the flags, you know, and the debriefing. And then each of us personally have like how we’re writing it up and what’s the next experiment that we want to do.</p><p>Richard:</p><p>Okay, so you’re pausing, like sort of reconvening with each other, reviewing what happened, getting realigned, setting the next experiment, is it like that?</p><p>Catherine:</p><p>Yeah, well, each handler would have the track for their experiments for their dog. So we have to do our own work. And then we come back to the team saying, hey, can you help me with the next thing I want to work on?</p><p>Richard:</p><p>Okay, okay, cool. Cool, and everybody gets aligned and on that same experiment together.</p><p>Catherine:</p><p>Yeah, yeah. And we try to set up problems so that team members can use the same, having missing people as hard to do. So can we use same problem to run everybody’s experiments ’cause it’s like we’re training for finding missing people.</p><p>Richard:</p><p>Right. So you need somebody to pose as a missing person while you’re doing this.</p><p>Catherine:</p><p>Yeah, yeah. I think if we just ran problems and we didn’t see any feedback, it would be pretty much worthless. And in tech teams, you went real feedback, feedback from customers, not just from a stakeholder who wants the button orange, we want the real feedback.</p><p>Richard:</p><p>I’m like, that was such a weird laugh. But I’m thinking about having customers that would give us feedback that was like, we want that screen to look a little sexier. And we’re like, what are you talking about? How do we do that? We need something more concrete.</p><p>Catherine:</p><p>Yeah, concrete behaviors. I think another one is that everybody has a voice. You’ve been on teams where like only one person is talking, telling everybody what they have to do, collaboration actually has a healthy buzz and the buzzing has come from all of the team members. This is more than three, but I think another concrete behavior is you can really see that people are taking time for learning, whatever it is, going to a class or going to looking at webinars or presenting at a conference, you can see the time that’s taken out for learning.</p><p>Richard:</p><p>Yeah, all right, so, okay. People can copy some of these ideas, these concrete behaviors. What else could people do to reproduce the success of a team like this?</p><p>Catherine:</p><p>I’d say the first thing is talk to your team. What is currently missing that they need? And you know, the daily scrum, do you have any impediments that you have? No, no, no, no. Instead of asking that, say, what’s one thing that you really could have used that would’ve made today better? And somebody might have answer, well, I have really bad headache ’cause my screen is so small. Order bigger screens, you know like, so maybe ask that question differently, instead of do you have an impediment, what’s going to make your day better?</p><p>Richard:</p><p>That’s such a good way to phrase that, yeah. The impediment is I have a headache, but I don’t think of it as an impediment.</p><p>Catherine:</p><p>Yeah, and it could be because of your equipment or it could be because of your lighting or whatever. Take the time to really see how you can help and ask the team, are you the one causing them stress? You know, you being there could be, you know, get out of the way if you need to get out of the way. Another thing is I meet so many teams that have just never been given the time to gel as a team. Like I mentioned, when I start with the SAR team, I do this market of skills and we’re vulnerable with one another saying what we want to learn from another.</p><p>Richard:</p><p>Okay, so there’s a concrete way to be more vulnerable. And this is one of those things. People say be more vulnerable, but we don’t know how to do it. Here’s a way to do it. You tell other people what you want to learn or you know, like, which is a way of saying, it’s a positive way of saying there’s a gap in my skillset and that’s definitely a vulnerability.</p><p>Catherine:</p><p>Yeah, or I need to be able to search this area and I have asthma. I could have an asthma attack, my asthma thing is here. Does anybody have my back? You know, who can actually help me in this situation? And it opens the door for other people to say, yeah, I have a allergy to bees and my EpiPen is over here. So you really need to know that on a search. So let your team lead where they want to grow and then support them and get out of their way.</p><p>Richard:</p><p>All right, any other advice for people to have a super successful team like that?</p><p>Catherine:</p><p>You may find the team that you already have as the best team if you give them space to get there.</p><p>Richard:</p><p>All right. What a lovely potential episode title.</p><p>Catherine:</p><p>That’s right.</p><p>Richard:</p><p>Now, there’s so much stuff going on. You and I, have collaborating on things for a couple of conferences. Is there anything else you want to add? Anything that’s been on your mind, search and rescue is big in your mind, training and coaching teams is big on your mind. Anything else you want to, you want to add on?</p><p>Catherine:</p><p>Well I would like to plug the conferences that we’ve may be doing Scrum Alliance and Agile Alliance. And it’s on this topic. So if you are interested, we will follow up this podcast with a link to conferences.</p><p>Richard:</p><p>Hope so.</p><p>Catherine:</p><p>Me too.</p><p>Richard:</p><p>Definitely our goal.</p><p>Catherine:</p><p>Me too.</p><p>Richard:</p><p>Is there a way for listeners or viewers to get in touch with you?</p><p>Catherine:</p><p>Yeah, on Twitter @CatherineLewis, all one word or linkedin.com/INCatherineLewis. All one word.</p><p>Richard:</p><p>Perfect, perfect. Well, gosh, Catherine, thank you so much for the conversation. It’s been so great to reconnect and thank you so much for being here.</p><p>Catherine:</p><p>Thank you, thank you. You’ve given me more ideas for things we can do at the next conference.</p><p>Richard:</p><p>Oh good. I can’t wait. And dear listeners and viewers, remember to support this podcast, just visit my website, Kasperowski.com.</p><p><em>Join the community of high performers — </em><a href="https://kasperowski.com/?utm_source=linkedin&amp;utm_medium=blog&amp;utm_campaign=good-feedback"><em>subscribe to Richard’s newsletter</em></a><em> today.</em></p><p><em>Originally published at </em><a href="https://kasperowski.com/intentional-about-meetings/?utm_source=linkedin&amp;utm_medium=blog&amp;utm_campaign=good-feedback"><em>kasperowski.com</em></a><em> on March 29, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e21afd5bd50" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Saying ‘Yes’ Can Take You Anywhere You Want]]></title>
            <link>https://rkasper.medium.com/how-saying-yes-can-take-you-anywhere-you-want-38f20b3567a?source=rss-8de0ae241122------2</link>
            <guid isPermaLink="false">https://medium.com/p/38f20b3567a</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[authors]]></category>
            <category><![CDATA[podcast]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[interview]]></category>
            <dc:creator><![CDATA[Richard Kasperowski]]></dc:creator>
            <pubDate>Tue, 15 Feb 2022 13:05:16 GMT</pubDate>
            <atom:updated>2022-02-27T23:37:00.180Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/670/0*OMKSu_EfdOQ4F7z-.png" /></figure><p>In <a href="https://kasperowski.com/podcast-78-arie-van-bennekum/">this episode of With Great People: The Podcast for High-Performance Teams</a>, I interview <a href="https://www.linkedin.com/in/ariev3/">Arie van Bennekum</a>. Arie is a co-author of the <a href="https://agilemanifesto.org/">Agile Manifesto</a> and an Agile thought leader at <a href="https://wemanity.com/">Wemanity Group</a>. Arie tells us how accepting new challenges, even when doubting ourselves, opens new opportunities and truly makes us the architects of our own life.</p><p>When you finish listening to the episode, connect with Arie on <a href="https://www.linkedin.com/in/ariev3/">LinkedIn</a> and visit his website at <a href="https://arievanbennekum.com/">https://arievanbennekum.com</a>.</p><p>Richard:</p><p>Hi, Arie, thank you so much for joining us today.</p><p>Arie:</p><p>My pleasure Richard, my pleasure.</p><p>Richard:</p><p>Hey, is there anything else you would add on to that introduction?</p><p>Arie:</p><p>Oh yeah, of course, family man. I have two children, a daughter-in-law. I have a beautiful girlfriend. Two wonderful bonus children as we say these days. I have a granddaughter. I love my motorcycle, my bike. I live in the countryside in the Netherlands. Wind mills, cows, wooden shoes, they’re real. In case people think it’s joke, no, it’s not. Where I live is in the Netherlands in Europe. Of course, I live, for those who know the Netherlands a bit, 20 kilometers straight east from the beautiful city of Rotterdam. And I live very close to the tourist attraction of Kinderdijk where you have those whole row of wind mills forming a beautiful, extremely smart, water management system designed hundreds of years ago. Yeah, so that’s where I am and who I am.</p><p>Richard:</p><p>That is amazing. I love that term that you you all have in not exactly Northern Europe, but in Europe, you have this term, bonus children. I love that term.</p><p>Arie:</p><p>Yeah, yeah, yeah.</p><p>Richard:</p><p>I have two bonus children of my own. I really love that term.</p><p>Arie:</p><p>Yeah, yeah. Then you know what I’m talking about, right?</p><p>Richard:</p><p>Yeah, exactly. Let’s see. So this part podcast is about teams. I love to ask people about the best team they’ve ever been a member of in their life. And this could be any kind of team. A work team, a non-work team, a creative team, some university project team, you and your girlfriend, you and your family, you and your bonus children. Any group of two or more people aligned with common goals, that’s how we define team here. You could define team any way you want. What’s the best team of your life? What’s the best team that you are ever a part of in your life?</p><p>Arie:</p><p>This is, whoa, this is such a difficult question because you have all the different areas in your life. Because I like the way that I was a team with my parents and my brother when I was young, really. And actually, yesterday evening, with my brother because he lives downtown. Had my drink and we do that on a regular basis. Maybe I would say that I liked the way my parents were a team. I also think that when I was writing the manifesto, when we were writing the manifesto in 2001, I was working for a company in the Netherlands called SoulVizion. And we had this very steep growth curve. We would go from 24 to 700 in two and a half years autonomous growth. And it was not about all being perfect, but there was this very shared, and you have to imagine in writing the manifest, when you see things like, “Trust people to get the job done and maximizing the work not done.” My part of the contribution was in that part, based on how we worked in there, we were self organizing teams to the max. And that was amazing. You know, we did everything from innovation and business development to sales and contract management and delivery and HR and hiring, firing, and evaluation and rewarding. Everything except for sending invoices to customers. And that was amazing. Not only that all organization SoulVizion as a whole, but also the team that I worked in around the time that we wrote the manifest. So, yeah. Awesome. But there are many more beautiful.</p><p>Richard:</p><p>What was the name of the organization again?</p><p>Arie:</p><p>SoulVizion with an S, yeah. Doesn’t exist anymore.</p><p>Richard:</p><p>All right.</p><p>Arie:</p><p>Has been bought by one of the larger consultancy firms. But that was an absolutely massive experience. I worked there for 10 years.</p><p>Richard:</p><p>Okay. So subjectively, you just shared some of the experience with us about this huge, rapid scaling, from a few people to hundreds of people, trusting people to get the job done. You basically did everything it took to get the job done and make your customers happy. How do you know it was a great team? What did it feel like? Subjectively, what was it like to be part of that group of people or any particular subteam in there? What did it feel like for you? How do you know it was such a great team?</p><p>Arie:</p><p>I always, because people very all often ask me questions in this direction, right? So, what was it like? And I think one of the most important characteristics for me is I cannot recall in those days that I ever got out of bed being out of bed, being unhappy. And people would ask me, “How many hours a week do you work?” I said, “How should I know, I don’t know.” You know? And was doing at the same time, also in the evening, I was lecturing at the Rotterdam University. I was at one time lecturing at one evening at Rotterdam, one evening at Amsterdam at the university, doing my SoulVizion consulting during the day. We were supporting each other and the innovation was amazing. The new ideas, the buzz. The people that I am connected with, and that I really interact with still on the professional level every now and then because, hey, this person might help you or this person might help you, she knows this, very often are from this organization still, yeah.</p><p>Richard:</p><p>Tell me more about this idea of there was a lot of innovation, there were new ideas, there was a buzz. What was that like?</p><p>Arie:</p><p>So it’s March, 1997, and I talked to a gentleman and he and two friends of his, and also colleagues by the way. And I knew him because I did quote unquote, Agile Delivery projects for him in 1995, 1996. And he knew me and he said, “You know, I started this new company and maybe you heard about the book, it’s called the “Semco Style from Ricardo Semler.” And that was the idea of self organizing teams getting the max out of people, also making people responsible, right? And taking the benefits, but when it’s not really good, also you know the effects as well. And the idea was that you have a group of people anywhere from five to what, 20, 25 or so, working on a specific product or a service or whatever. But the way you interact together within that group, at one moment in time, there will be a subgroup saying, “Now, we have this idea.” And they would start talking about this idea and if they would really want it. Within weeks, they could have the business plan, just an outline set. They would select some people from the organization, had a couple of iterations on the plan and they would split off and start a new team. So when I joined in 1997, we had three teams. And when the company was bought by a consultancy firm in 2003, I think it was, I think we had like between 25 and 30 teams. Really interesting. Yeah. So you get that innovation as, I mean, one of the things, especially these days with the pace of innovation and technology that we have in the world, you cannot rely when it comes to innovation, on proof of concept processes or that kind of the old school way. Innovation has to be part of your daily operations, I always say. You have to continuously help trigger, motivate people to look in different angles. I hate the phrase out of the box, right? To get so much going, that kind of stuff. And man, it was unstoppable. One of the biggest concerns we have, we didn’t have a lot, but the biggest concerns that we have is people not getting any burnout. Because everybody was working during the day, at the client site, in the evening at the office, working with people and that kind of thing. Yeah, it was amazing.</p><p>Richard:</p><p>So, what about this idea of, I don’t know if you’re saying, or if you’re implying or I’m just hearing it this way, that you can’t have a process for innovation. Did you just create this atmosphere and innovation happened or what was it that fomented all of this activity?</p><p>Arie:</p><p>Yeah, I think it’s not binary, but, you cannot plan innovation. You cannot say, “Oh, we have this new, brilliant product ready on May one.” Right? It’s not going to, So, in the days that we live in, where we are, 2022 with a pace of innovation on the tech side, where the technology is offering so fast, new opportunities, right? So you have technology that is not only helping you in the way you work, but it’s disrupting entire business models sometimes in months, right? And that means that you have the next one, the follow up of your brilliant product or service that you put in the market, you have to have it ready. If you’re a governmental organization, the knowledge that laws have to change because of new developments, what technology offers to maybe competition, threatening your own national market, terrorism, whatever. You have to understand, you have to respond fast, you have to have solutions ready. You have to have integrated change of development, from your organization to suppliers, to your clients or the people that are using your services if you’re government. You to have different dynamics, closer collaboration and the one thing that is your beautiful, brilliant product today, might be obsolete on July one. So you have to continuously work. If you continuously work part of your time on innovation, you will have a lot of things that will fail, will not get there, but you will always have those things that are going to help you out also already and they’re there to help you strive. And I think that’s the reason why innovation is so important these days. And that pace of innovation will only go up and will never slow down so you better be ready.</p><p>Richard:</p><p>Right, yeah. Now, let’s go back to SoulVizion. I don’t know, could we talk about one particular team there? Like is the founding team or some of other team at SoulVizion? Is there a particular team?</p><p>Arie:</p><p>Yeah, let’s just take my own team, right? So I joined in March, 1997 and we had three teams and I was asked to be in the team that was, let’s say, in the software development kind of working. And I was asked to take more or less the lead. We didn’t have any management and every team did it in its own way. You could have someone having the lead. You could have that position every three months changed. You could have two people having the lead, the way you wanted, right? And I remember that one moment in time, I split off with a colleague of mine, and we said, we are going to work explicitly on DSDM, dynamic systems development method, because in 1994, I started working with mostly rapid application development, I would say. In the late eighties, I was doing in hindsight, what you would call pairing, just trying to experiment what would really help. And then into reification development kind of way, working and I got connected to the DSDM consortium, with that guy, by the way, because he joined the team that I was leading at the time. And we got a connection with the DSDM consortium. We did the certification. I remember the moment that the DSDM started the chapter here in the Benelux, Belgium, Netherlands, Luxembourg, and we got into the chapter right away. Knowledge sharing, right? That’s what it’s all about. And what is very important to me is of course, you have to focus on your revenue because your revenue has to be there. Because if you don’t have the revenue, you cannot do the other stuff that’s important for the company. Such as innovation, for example. We started growing, we started recruiting people, they joined us. Most people are still in contact with me. Every now and then, somebody from the team will ask me, “Arie, can you do a talk at the client where I am? Can you do a talk at whatever.” And very often, I go there and I do this, and we were completely in, so let’s say in what we did, we were completely, you know, free to choose what kind of a delivery we did. So, when it comes to what we call Agile transformations today, I remember sitting down with the vice president of a big bank, one of the top three banks in the Netherlands at the office of SoulVizion, with my friend Corey and talking about the transformation of that bank, this is 1998. And it was masterclass, it was talks, it was coaching. The word “Agile Coach” didn’t exist at the time, right? But that was what we did. And the people that founded the organization had one thing only, if you need our help, let us know. And if there were things not going well and of course, it wasn’t all beautiful and roses and wonderful. So things went wrong. They would give a call and know what’s going on because we can see some things are not going well and they would try to help out. And that meant that, for me, what is very important in that specific team, is that we could rely on each other. Still, I am in contact with Helt. Corey is a little bit less because he has his own area. He’s not in my area working at the time. Ali is still in my contact list and you try to reconnect sometimes with him. So you have those people around. Maybe, you know, like when you’re a child, right, you have this time in your life when a lot of things are settled in your brain and this is how you perceive life. This is your starting point. And I think in hindsight, because I joined SoulVizion when was 33. And I left when I was 43. But I think especially the first six years, they set the scene. And one of the most remarkable things for me is when you talk about self organizing teams, I’ve never been in an organization when I’ve seen it working like this. People struggle. People always start at the beginning. Oh, you’re self organizing team. And they will start talking about how do we do it with the shares? And we start talking about the people on the team. And we said, “Okay, what do we put in the market? Where do we start? What do we think that we like to put in the market? And who would be nice to work with with us on this? Or do you know someone?” And that kind of thing, you know, that was amazing. And I remember that one of the guys that I work with and later on, I returned working with him. He said, “Arie.” He passed away sadly two and a half years ago, I think two and a half years. And sadly, he said, “Arie, I think if you want to have success, you need to be able to like each other or maybe be friends.” And of course, you’re not friends with 700 people and you don’t know even all 700, but the teams that are close to you and similar to you, you know, still today, I have people from that time said, “Arie, I think I have a job for you.” And I was ask someone, “Hey, I think I have someone for you.” Because you know each other, you’re in each other’s frontal cortex, right? And I think that’s.</p><p>Richard:</p><p>I love that idea of you like each other, you’re you’re friends. You can’t be friends with everybody in the whole company, but there’s people who are near you for sure. And you also started off by saying, you said a couple things like you never got out of bed unhappy. And you never kept track of how many hours you worked per week. And it was definitely a lot, especially when you had on all the extra teaching you did. How about objectively? Are there any measurements? Anything that somebody from the outside could observe objectively? How would somebody that this was a great team or these were great teams?</p><p>Arie:</p><p>Two things I would say. I was in the DSDM community. That was a large community. And the back office, Mary Hansen was responsible at the time at the DSDM consortium and she gave me a call. And she said, “Arie, do you want to come?” I said, “Yeah, I think so.” And actually, I can point it because there is church two kilometers away and I was driving exactly there. And I said, I’m home in a couple of minutes. And I can tell you, I was married at the time still. I can tell you. And then people would say, “Oh yeah, but before they called Arie, they called me.” And one of the things that you will see in those successful companies is that it’s not about who get the call, it’s about who says yes, right? People say yes. You only get somewhere when you say yes, right? When you would’ve walked into that office, the office, Richard, you have to imagine, the city of Delft, close to the Hague. Beautiful, I think 150 year old house, a mansion and it was the old mayor’s house actually. And at the ground floor, there was a big pub. Because the founder said, “Best ideas are born in a pub, not in office rooms.” And you would walk in and there would always be that buzz. And it was not that we drank alcohol during the day, don’t get me wrong, right? But we had to say, it’s just a pub, right? Wooden floor, brass mirrors, bottles of booze, tables, sitting there, you know? Beautiful, beautiful design on the inside. And we would sit there and if you would walk in, you would say, “Man, this is a good place here. Here, I’d like to sit. Give me a cup of coffee, man. Let me sit down.” And people gave that back to as well, right? Because you invite people to your office obviously. And I think that buzz, that was really cool. Yeah, absolutely. You would notice that instantly.</p><p>Richard:</p><p>Love it. That buzz, this idea that it’s like someplace really warm and inviting and where you want to be.</p><p>Arie:</p><p>Yeah. And especially where you don’t have ideas that are rejected. You know how it works. “Oh yeah, well, that’s a great idea, but it doesn’t work for us.” No, no, no, no. Oh, you have an idea? Let’s sit down, tell me about the idea. Oh, if you talk about this kind of thing, I’m not maybe the most logical guy to talk, but just go to Richard. Maybe Richard can help you out. And if Richard doesn’t, maybe somebody else. Instead of saying, no, you help people forward.</p><p>Richard:<br> All right. So there’s an example of a concrete behavior that maybe you used on these teams. Not saying no to each other, like actually opening it up to people’s new ideas. What are some other concrete things that you did? Some other concrete behaviors that helps these teams be so amazing?</p><p>Arie:</p><p>Let me tell you that as an outcome of this group, a lot of people have got to really good positions in business. And I also mean governmental. They really got into good positions. Very wide thinking, creative brains, right? But I can also give you a down side of that because we were working day and night because it was so fun. I think we had a serious number of burnouts. And I remember one the, at that time, young ladies. You’re just getting out of university, joining us. Awesome, you can do whatever you like. And I go on with it. And she’s living now in the north of the country and I remember her saying to me at one moment in time, she said, “Arie, I want an office. I want a desk where I can put the photograph of my boyfriend and a plant and my computer so I can work.” And we didn’t have desks, our founders didn’t didn’t have a room. We didn’t have parking places. The space was for those who were there, period. And nothing else. That’s another behavior. And I remember when we changed to, when we were bought by one of the consultancy firms, during 2003, I got a team full of project managers. And instantly, we got it back into old silos. And one of the guys, and at this time, I am 39 years old. And this guy is for 55, 56, 57, I don’t know. And he calls me it’s May. And he says, you know, in the Netherlands, we have 20 to 25 days that you can take off for holidays or whatever, right? A minimum at full time is 20, we had 25. And he gave me a call and he said, “Arie.” You know, he auditioned this date in August, “Can I go on holiday?” And I was baffled. I was like, what? What? Are you asking me if you can go on holiday with your family? What’s this? What’s this? And the only thing I asked, I said. He said, “Yeah, you’re my manager now.” And he was coming from the other side of the organization. He was not part of the organization SoulVizion. but from that consultancy firm. He was just blended into my team. And I said, “Fear not, listen, man, it’s very simple. What I like is that your client knows and is okay with the fact that you go. And the fact when you’re out, is that one of your colleagues that is available will cover your behind while you’re out so the work can go on and nobody drops to a standstill.” And so that kind of thinking is I remember, sometimes you get in those situations, people are asking you, “When are you going on holiday?” And I got into situations where I was collaborating with people and people have to ask me if they can go on a holiday. I said “Well, I’m going to tell you something. I will not spend my time on judging if adult people with highly educated people can go on holiday or not. They know that they have to make sure that the client side everything is okay. They know that they have to make sure that the work goes on. I’m not going to interfere with it. I have other things to do.”</p><p>Richard:</p><p>Right.</p><p>Arie:</p><p>That’s the kind of thinking. That’s the self organizing model.</p><p>Richard:</p><p>You don’t have to give them permission. You’re not their dad. You’re a coworker who happens to be a little bit more senior.</p><p>Arie:</p><p>Yeah. And I mean, so you have highly educated people and they need to ask you for permission to go on holiday. Oh, come on, come on. And this is what I like. I think the phrase is from Steve jobs where he said, “I don’t hire highly educated people to tell them what to do. I hire them to tell me what to do.” Right? And that’s where it’s supposed to be. And I like, before SoulVizion, I was working for a consultancy firm, so this was teams of up to 50. Like with their own profit and loss across the Netherlands. I don’t know how many of those teams. And he was young, he was 30 years old when he was running, totally responsible. Like a managing director. And he told me that he came back from one of those managing directors meetings. So there’s maybe like 40 managing directors and some of them were complaining to him. Oh, so busy man. Oh, over time. And my wife is complaining and blah, blah. He said, “Arie, I don’t understand this.” I said, “We’re a consultancy firm. If I have people available on the bench, that means I have people look and do the work for me. And if I have everybody working at the client site, there is no reason to do overtime. So I just don’t get it.” And that’s the way you’re thinking that you need to have. Man, people get so in those rigid processes and it’s like, get out of there, get out of there. Now make sure that the business runs properly instead of running a to prescribe processes and stuff.</p><p>Richard:</p><p>Right, right. All right. So how about advice for listeners and viewers? How can they take some of these practices and these ways of thinking and reproduce this success with their teams?</p><p>Arie:</p><p>Yeah, so, I’m going to show you something. I want to show you something. And I know it’s a podcast, so the people will not be able to see it, right?</p><p>Richard:</p><p>Oh, we’re going to do, this will be video too. So some people will see this.</p><p>Arie:</p><p>Yeah, yeah. Very good. One of the things in Agile working is that we do the retrospective, right? And a retrospective can be a little bit painful because you’ve been working for a sprint and maybe something didn’t go the way you want it. And then, if you don’t point out what really happened, you cannot improve it, right? So that might be on the table that we have to say, “Arie, you know, man, you messed up here. You really messed up.” And what people tend to do is point other people. Oh, I know it wasn’t me. It was the bridge that was open, that’s why I’m late. And it was the whatever. And I think people should understand that you are the architect of your own life and that’s about taking responsibility. And what I mean to say is, you’re not controlling what’s coming over you, forget about it, there will always be things happening. I remember the weekend that we wrote the manifesto, we didn’t expect that the manifesto would be so impactful in the world. Secondly, that same weekend, my wife decided to divorce me. And thirdly, the house was on fire when I was in Salt Lake. So if you want to talk about life changing events that you don’t control, there you go, right?</p><p>Richard:</p><p>It’s quite a weekend.</p><p>Arie:</p><p>Yeah, yeah, exactly. So the point is, you don’t control what’s coming to you, but you decide how you handle it. And walking away from things, denying things, blaming others, being suspicious to others, having bad intentions, it doesn’t work. See what you can do yourself and make that happen. And then you wake up every morning being happy. I mean, sorry man. That’s how I perceive life. And yes, I have my bad days too. Especially when I visit my brother. Like we talked before the recording started and we have one of those evenings that you think, okay, I should have gone home earlier, right? But I love my life because I know whatever is happening in my life, I decide on what’s going on there. And if things aren’t, because things happen to me that I don’t like, of course. But then I take them on, I only worry about the things that I have an impact on, the things I don’t have an impact on, I just accept or I leave. I go out, that’s also, then I change places, it’s also possible. But that makes your life easier, right? I focus on the things that I want to do.</p><p>Richard:</p><p>All right. And is there anything else you’d like to add? Anything you you’re thinking about recently, working on recently? Anything at all?</p><p>Arie:</p><p>Yeah. Yeah. Oh man. Actually, now we can do another podcast of 24 hours, right? But one of the things I was just before we did, we started our video conference here, I was talking to a business colleague friend from Germany, Sebastian. And he calls me, he says, “Arie, I’m doing this masterclass, agnostic agile. Would you drop in for half an hour or an hour or so to talk to the team? And, I said, “Yeah, sure. If I have the time I will.” So I just dropped in, I helped him out. There from a big, well known car manufacturer, the team that he was training and I helped him forward. I’m not charging money. I’m just this because Sebastian is my friend. And he said, “Arie, you know.” And I think instead of translating everything into money all the time, I mean, you have to have a decent living, don’t get me wrong. But what about spending your wealth, whatever your wealth is, a little bit with somebody else in the world who maybe needs it in that moment? And I had a friend who was in financial, very difficult positions all the time. I never threw clothes away. You know, I would say, “Hey man, you need anything. And if we would go to the pub, I would pay the bill for the couple of beers that we did. Helping, when my boys were growing, the clothes would be okay, that doesn’t fit you anymore. I would just checkout and I would know this family that doesn’t have a lot of money, they have children that are just below mine, right in the size. And I would give them the clothes, right? Helping people out is what we don’t do very often. And help means that you give without asking anything in return. That’s when you help. And we should do it a little bit more.</p><p>Richard:</p><p>That is great advice. Thanks so much for sharing what.</p><p>Arie:</p><p>Not money, right? Helping people, not money.</p><p>Richard:</p><p>Yeah. All right and how could listeners and viewers contact you?</p><p>Arie:</p><p>I think the easiest way is LinkedIn. I always say, when you connect to me in LinkedIn and in the direct message of LinkedIn, you ask me a question nine out of ten within a day, you have an answer. It might be short. And if it’s really too long, we will find 15 minutes to do a little video conference. And then we be good, right?</p><p>Richard:</p><p>And it’s the truth. That’s how you and I connected.</p><p>Arie:</p><p>Yeah. I mean, you, then are the living proof of what I just said. And of course, you can find me on Twitter and on Instagram, on Facebook. And I have arievanbennekum.com and I should update it, I know. But I’m always so busy doing stuff. Yeah, yeah.</p><p>Richard:</p><p>All right. We’ll make it easy for people to find you. Digitally, not like in this house where you are.</p><p>Arie:</p><p>Well, if people are ever in Hardinxveld-Giessendam, they’re very welcome to send me that message and saying, “I’m in this and this pud, do you want to come over for a beer?” And then I’ll join you for a beer.</p><p>Richard:</p><p>All right, I’m going to keep that in mind. And maybe I’ll be there someday.</p><p>Arie:</p><p>Yeah, yeah, exactly. Yeah, you feel free to do so.</p><p>Richard:</p><p>All right, all right. Thank you, thank you so much for joining me today for joining all of us today on the podcast. It was really great getting to know you, getting to meet you. Built up a little bit of friendship here. I really, really appreciate it. Thanks so much.</p><p>Arie:</p><p>My pleasure, Richard and maybe we’ll meet in the future. There’s there’s a globe in between us, but you never know, right?</p><p>Richard:</p><p>Yeah, yeah. Okay. Thanks so much. And listeners and viewers, remember to support this podcast, visit my website, kasperowski.com.</p><p><em>Join the community of high performers — </em><a href="https://kasperowski.com/?utm_source=medium.com&amp;utm_medium=blog&amp;utm_campaign=good-feedback"><em>subscribe to Richard’s newsletter</em></a><em> today.</em></p><p><em>Originally published at </em><a href="https://kasperowski.com/podcast-78-arie-van-bennekum/"><em>https://kasperowski.com</em></a><em> on February 15, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38f20b3567a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Does It Take to Have a Great Agile Team?]]></title>
            <link>https://rkasper.medium.com/what-does-it-take-to-have-a-great-agile-team-5fd29241aff0?source=rss-8de0ae241122------2</link>
            <guid isPermaLink="false">https://medium.com/p/5fd29241aff0</guid>
            <category><![CDATA[finance]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[safety]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[performance]]></category>
            <dc:creator><![CDATA[Richard Kasperowski]]></dc:creator>
            <pubDate>Tue, 21 Dec 2021 21:45:13 GMT</pubDate>
            <atom:updated>2021-12-21T21:45:13.652Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W3JWCbjXn3PkrF2DBooTqg.png" /></figure><p><strong>An interview with Richard Kasperowski on High-Performance Teams</strong></p><p><strong>Stephen Harrison</strong>: Let me introduce Richard Kasperowski. Richard and I worked together a while back and have been friends ever since. Along the way, Richard has become a recognized expert in an interesting and relevant field.</p><p><strong>SH</strong>: Richard, welcome. Thanks for taking time to chat.</p><p><strong>Richard Kasperowski</strong>: Thank you — I’m happy to be here!</p><p><strong>SH</strong>: What’s your elevator pitch?</p><p><strong>RK</strong>: I’m an author, teacher, coach, and consultant. I focus on teams, helping people build and maintain teams in a state of high performance. Some of the tools I use include <a href="https://thecoreprotocols.org/">the Core Protocols</a>, <a href="https://en.wikipedia.org/wiki/Agile_software_development">Agile software development</a>, and <a href="https://en.wikipedia.org/wiki/Open_Space_Technology">Open Space</a>. And I teach a couple of courses: one at Harvard University called <a href="https://agilesoftwarecourse.org/">Agile Software Development</a> and one at Boston University called <a href="http://www.bu.edu/spark/">Spark!</a>. Spark! is an innovation program for teams of students creating awesome new products together.</p><p><strong>SH</strong>: You’re one of the best presenters I’ve seen at workshops. What’s your secret?</p><p><strong>RK</strong>: What a funny question because the first time I spoke at a conference I really sucked! This was about 25 years ago. I decided to speak at a conference because I thought it was something that, I don’t know, cool people did, smart people did, successful people did. And I got into this conference and I showed up wearing a suit and a tie because I thought that’s what you did when you went to a conference. So I stood there in my suit basically reading the slides in a monotone voice. I sounded like a robot — I was so scared of being in front of the audience! The feedback I got at the end was that you had good material, but you looked liked you were really nervous: You might want to try changing the tone of your voice once in a while. :-)So, Stephen, I know you use a lot of the practices that I call Agile, like continuous integration, continuous delivery, and so on. Maybe my “secret” is this old idea from Extreme Programming: If it’s hard, then you do it all the time so it becomes easier. So I just do it a lot now — I do a lot of public speaking and teaching. At first, it was hard. But I still liked it, so I did it more. Practice, practice, practice. Now I don’t feel so scared talking in front of an audience, and at least a little bit of my personality comes through.</p><p><strong>SH</strong>: Staying with workshops for a moment. I notice you get people to engage in your exercises and overcome their initial reluctance. Tell us how to do that too.</p><p><strong>RK</strong>: I think this is all about people feeling safe. And by safe I mean the opposite of a fight-or-fight response. So how do people feel safe? Here’s a really common facilitator technique to help people to feel safe: it’s called solo-pairs-quads-all. You do an activity, and you ask people to do it solo. That’s totally safe: you can do the activity in your head, on a piece of paper. Totally safe, nobody sees what you wrote, nobody hears what your idea was. The next level up is to pair together on an activity that’s the same or similar. And it’s easy and safe because people basically have their answer written down and just read their answers to each other. But they’re together in these small groups, and they end making a new friend — they feel safe in their group of two. And the next level up … it’s pairs of pairs, and people feeling safe in groups of four. And then you expand the activity to the entire group.</p><p>This scaffolding helps people feel safe. Whatever you’re doing, find some scaffolding, some framework in which people can feel safe with each other. Find a way to avoid that fight-or-flight response. When people are experiencing fight or flight, there’s all this cortisol and adrenaline in their bodies. They can’t think, they can’t be creative, they can’t participate, they can’t learn. They can’t even hear what you’re saying. They’re just worried about themselves, trying to defend themselves. What we get from this safety scaffolding is serotonin, dopamine, oxytocin. These are the chemicals in your body that make you feel good, help you connect with each other, put you in a state of flow and high creativity. That’s what we want for the people we work with and care about.</p><p><strong>SH</strong>: In your travels around the world helping people build high-performance teams, what have been some of the consistent and challenging themes?</p><p><strong>RK</strong>: Continuing on this idea of safety, you can’t just tell people to “do more safety with each other at work.” People have some idea of what that means, but nobody has an in-born idea of how to “do safety.” So psychological safety is this idea that relates to high-performing teams. We feel safe when we’re together. We’re in a state where we’re not experiencing that fight-or-flight response. What are the practices to feel safe together? <a href="https://thecoreprotocols.org/protocols/pass.html">The first practice is everything is opt-in. And it’s totally OK to opt out.</a> So invitation. And the second step is <a href="https://thecoreprotocols.org/protocols/checkin.html">share how you’re feeling with each other</a>. Yeah … that’s crazy stuff!</p><p>That first idea — it’s OK for anyone to opt out at any time — as soon as I share it with managers, they’re like, “Wait a minute, if I don’t command people to come to a meeting, or I don’t tell them what to do, they won’t do anything. That won’t work.” And the second idea, to share how you’re feeling with each other, folks will say, “No! I just want to write code. We don’t do feelings here.”</p><p>But if you look at the science and the research of the behaviors of high-performing teams, they do these things. They opt in to their team, their project, their way of working together. They do the things because they want to do the things. They solve problems the way they want to solve them. And they share how they’re feeling with each other. When they’re happy they say so, when they’re mad they say so, when they’re sad they say so. They connect with each other better. They become friends.</p><p>And you and me, Stephen. We worked together on a team once, and I talk about that team as one of the best teams in my life. And I say we got lucky. We didn’t really know what we were doing. If we look back at that, we became friends. Could a random team do that again on purpose? How do people become friends? For starters, you decide you want to. Nobody makes you do it. It’s opt-in, and you share with each other — things about yourself, including how you’re feeling.</p><p><strong>SH</strong>: Are there some occupations, industries that push back the most on these ideas? How do you work around peoples’ skepticism in a tough crowd?</p><p><strong>RK</strong>: I think the profession we’re in, the techie business resists the most. And I joke about when I work with finance companies. Stephen, you’re working at a techie finance company…</p><p><strong>SH</strong>: [awkward silence]</p><p><strong>RK</strong>: … I mean like Wall Street stock trading companies. They don’t believe in sharing feelings.</p><p>Many of us who do this kind of work, this techie kind of work or this finance kind of work, we’re really good at numbers, and we’re really good at logic. And this is part of why we think we don’t need emotion at work. Because we’ve been so successful at work with just numbers and logic. Like me: why did I get into working with computers? Because I sucked at people. But I totally understood numbers and logic. That was easy.</p><p>I share with folks the science and research on teams and team performance. The literature and the evidence is that teams who have high group emotional intelligence outperform other teams. I make this case as a “hook.” If you believe in evidence-based thinking, if you’re a numbers and logic person, then you more or less believe well-done research. Now, if you believe in evidence-based research, and you want your team to be high performing … well, gosh, you have to have high emotional intelligence in the team because that’s the logical case.</p><p><strong>SH</strong>: Who are your greatest influences and why?</p><p><strong>RK</strong>: Jim McCarthy with his work on the Core Protocols and with an assignment that he uses in his signature course.</p><p>I have been teaching technical skills classes recently, so influences like Llewellyn Falco, Tim Ottinger, and Arlo Belshee come to mind. They are three leaders in writing amazingly good code.</p><p>I learned Mob Programming from Llewellyn, which is like Pair Programming, but with more people.</p><p>I learned an idea called “pin-down tests” from Tim. Imagine you want to refactor some legacy code. You want to make sure you don’t break anything. But it’s legacy code, so it doesn’t have any tests that tell you what the code does. First, you write tests that tell you how the code works, so when you refactor it, you know you didn’t break anything. “Pin-down testing” is a metaphor from high school biology class. You don’t just take the frog in one hand and the scalpel in the other hand and cut it open — you would hurt yourself with the scalpel. Instead, you take the frog and pin it down to the table. You make it safe to examine its insides. In the case of software, pin-down tests make it safe for you to open up the code and put it back together without hurting yourself.</p><p>Arlo has this idea of “provable refactorings.” Because of the rules of your programming language and runtime, you can prove that your refactoring is bug-for-bug compatible with the original code.</p><p>So these are some really important ideas for clean code and technical agility. You can’t arbitrarily change code — even if you think it will fix a bug — when you refactor. What you think is a bug might be someone else’s feature. If you change the code’s behavior, their code will break, and your business will lose money.</p><p>Arlo is also the one who first popularized “Promiscuous Pair Programming,” where pairings change every morning and afternoon. So you’re always writing code with other people on your team. They were working on this in the early 2000s where, as a rule of thumb, they’d pair the most knowledgeable person with the least knowledgeable person on the team to amplify the learning and the creativity. The most knowledgeable person teaches the less knowledgeable person, and the less knowledgeable person will have the freshest ideas. This makes the solutions great and brings the team up to speed quickly.</p><p><strong>SH</strong>: We’re not all familiar with some of the terms you frequently use: Core Protocols, Open Space, and so on. What are they?</p><p><strong>RK</strong>: Core Protocols is this: if you watch high-performing teams working together, creating products, you would notice they have a set of behaviors in common. If you factor out those success behaviors that they have in common, write them down, and share them with other people, you can intentionally reproduce success on your team. One of those behaviors of high-performance teams — and this is weird for techie people like us — is sharing your feelings with each other. There is solid science to support that sharing makes better teams.</p><p>Open Space is a great way to hold a meeting for 5 to 2,000 people to creatively solve a really important problem we needed to have solved yesterday.</p><p><strong>SH</strong>: How do you know when you’re really making a difference?</p><p><strong>RK</strong>: There are objective metrics: We have a valid and reliable diagnostic for high-performing team behaviors. We have measures of technical team performance.</p><p>But even better than metrics, you can tell you’ve made a difference when people show up to work with their team and want to be there, are happy and energized, and they’re creative with each other.</p><p><strong>SH</strong>: Thank you so much agreeing to do this. Richard, this has been wonderful.</p><p><strong>RK</strong>: My pleasure, Stephen! Always great to spend some time with you.</p><p>— <a href="https://www.linkedin.com/in/stephenharrison/"><em>Stephen Harrison</em></a><em>, Venmo SRE</em></p><p><em>Join the community of high performers — </em><a href="https://kasperowski.com/?utm_source=medium.com&amp;utm_medium=blog&amp;utm_campaign=good-feedback"><em>subscribe to Richard’s newsletter</em></a><em> today.</em></p><p><em>Originally published at </em><a href="https://kasperowski.com/intentional-about-meetings/?utm_source=medium.com&amp;utm_medium=blog&amp;utm_campaign=good-feedback"><em>kasperowski.com</em></a><em> on April 15, 2021. A version of this interview appeared on the </em><a href="https://venmo.dev/"><em>Venmo Technology Blog</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5fd29241aff0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Richard Could You Win a Nobel Prize for Slacking Off?]]></title>
            <link>https://rkasper.medium.com/richard-could-you-win-a-nobel-prize-for-slacking-off-2b39b3f506df?source=rss-8de0ae241122------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b39b3f506df</guid>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[flow]]></category>
            <category><![CDATA[creativity-tips]]></category>
            <category><![CDATA[nobel-prize]]></category>
            <dc:creator><![CDATA[Richard Kasperowski]]></dc:creator>
            <pubDate>Tue, 21 Dec 2021 21:30:11 GMT</pubDate>
            <atom:updated>2021-12-21T21:30:11.593Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*-ViTeaKjA9nw9U-L2gRUHg.gif" /><figcaption>Richard playing piano. Yes, it’s really me! Yes, I really can play piano and sing at the same time! Wow! No, I couldn’t do that before Covid kept me home instead of my previous normal: always traveling for work.</figcaption></figure><p>Before it was an app, “slack” was already a useful word.</p><p>As a verb, it meant to take things easy and even be a bit lazy, but the noun hints at its more exciting possibilities: an empty piece of time or space where unknown things can occur. A bit of surplus time in your schedule, a liminal buffer zone between two states of business. The place where interesting things happen.</p><p>When I look at how I spend my time now and compare it to the “before days,” there’s a lot more slack in my life. I am not travelling, dashing from one lecture to another in different cities or continents — gone are the 10 to 15 speaking gigs a month in addition to my regular classes. I am not over-scheduling, not feeling a need to pack my days with outcomes and achievements.</p><p>In these strange in-between days while the world remains in flux, my days are very different from what they used to be. I am meditating. I am making music. I am walking.</p><p>I am noticing what’s going on in the wider world and in my internal world.</p><p>Back when I was hurrying from one keynote to the next, I didn’t always have time to feel my thoughts and think my feelings, and integrate the synergy between them. That was OK because the work before me was clear. I thrived on the energy. The world was evolving and changing at a pace I could handle just fine.</p><p>When everything turned upside down, I had to rethink the ways I had been teaching and training people. I had to dig into first principles and the real lessons those decades of experience had brought, to find resilience. Without overanalyzing it, I changed my pace and slowed things down, until I found the right rhythm for the new normal — which is why my days are now so different.</p><p>I am playing piano — reactivating long forgotten skills and learning new styles. I am singing. I am meditating. I am walking. And I <em>am</em> working, creating at the same time… So why do I sometimes stop and wonder why it feels like I’m not working enough?</p><p>To a casual observer, a lot of what I do certainly <em>doesn’</em>t look like work. And it’s true, I have the great privilege of being able to work creatively using my mind. I don’t always have to trade my time for money — I’m at least a little bit free of those handcuffs (almost all of us creative people have to work for someone else at least some of the time).</p><p>Despite the great peace of mind this pattern of activity brings me, there is a twinge of guilt underlying it all. I was programmed by my parents and peers, by my education and career, to equate being busy with being effective, that getting things done is the most important thing in the world. And that the more I get done, the better.</p><p>But creativity does not happen in a vacuum. With the stimulation and space that my music and other activities provide, I am inspired. I actually do generate more and better in the time that I spend doing what most people would recognize as real work. It’s as if I am taking time for sharpening the saw, and suddenly I find new edges on the saw or better ways to use it.</p><p>I am not alone in this. It turns out that the world does not divide people into strictly artsy types and science types. The greatest minds of history were multitalented polymaths. Look at Da Vinci, Ramon y Cajal, Einstein and his violin…</p><p>It turns out that this has been known for decades. I love reading research papers. So I did what I do when I’m curious about something: I found some research on slacking off from the 1990s. The research shows that there is a correlation between science and arts, and the necessity of developing both aspects of creative thinking for success. The more research I read, the more I let go of my guilt. The creative stimulation of the arts enhances our technical work. By embracing downtime, I’m following in the footsteps of Nobel Prize winners. (According to research in the <a href="https://www.researchgate.net/publication/247857346_Arts_Foster_Scientific_Success_Avocations_of_Nobel_National_Academy_Royal_Society_and_Sigma_Xi_Members?enrichId=rgreq-a479570aa0256cff08b7109caf176555-XXX&amp;enrichSource=Y292ZXJQYWdlOzI0Nzg1NzM0NjtBUzoxMTc3OTQ1NDA2MjU5MjFAMTQwNTA5NTgxNjE5OA%3D%3D&amp;el=1_x_2&amp;_esc=publicationCoverPdf">Journal of Psychology of Science and Technology</a>, Nobel winners are more likely to have artistic pastimes.)</p><p>The combination of the technical and the artistic so often yields transformative breakthroughs. Having the scientific ability to solve a problem is not enough without the artistic competence to bring the vision to life. This applies to <a href="http://edq.sagepub.com/content/27/3/221">economics and innovation too</a>. So many of the world’s greatest challenges today, which seem to be related to dry technical questions, demand complex solutions drawing on multiple disciplines and kinds of thinking.</p><p>I wonder if this is related to the true <a href="https://en.wikipedia.org/wiki/Flow_(psychology)">flow state (as defined by Mihaly Csikszentmihalyi back in the 1970s)</a>. I get into this state of flow when I play the piano, where it feels like anything is possible, and I am reactivating a connection between my brain and my fingertips I haven’t exploited for decades — and finding it’s all still there. It’s a highly meditative frame of mind, that is also similar to the mental state I used get into with taekwondo, practicing a <a href="https://en.wikipedia.org/wiki/Kata">kata</a>/form over and over and over. Letting go of the guilt, relaxing into this state of mind.</p><p>A complex piano exercise is like a kata, demanding concentration that is simultaneously intense and delicate — continuously stretching my attention and focus, with immediate feedback and perpetual possibility. Whenever I stop to think, I make a mistake — I don’t know which note to play next. But when I relax my attention into the right space I can go on for hours and hours.</p><p>Like all deliberate practice, with enough repetition it physically rewires your brain and becomes your natural state — the same with practicing <a href="http://thecoreprotocols.org/">the Core Protocols</a> in your team communications, the teaming skills we develop to be emotionally open to one another, to the point we can forget that not every team is naturally like this.</p><p>Or <a href="https://www.agilealliance.org/glossary/tdd/">test-driven development</a>. With deliberate practice, it becomes the only way you’d ever write code — because of that immediate feedback when you hit a wrong note.</p><p>And the music gets better. You write better code, you play more advanced scores. You get to the point you can riff and jam and experiment, extending things this way or that to create something brand new. It doesn’t always work perfectly, but this is where you get the serendipity of outcome.</p><p>You only get to this state when you have some slack. To doodle, to play around.</p><p>So I’m going to try not worry that I am putting in more time on my piano keyboard than on my computer keyboard right now.</p><p>And I challenge you to do the same: if you think you’re slacking, if you’re taking time out for self-care and creativity from your professional work, then recognize the good it is doing you, and the good it’s doing in the world enabling you to make better art — or code, or bread, or marketing copy, or whatever it is you do to keep the lights on.</p><p>Let your brain work in parallel, use its circuitry creatively, and light up all its different pathways. It will reward you by solving your problems while you’re out for a mountain walk or deep in a yoga session, and you might become the Einstein or Da Vinci of your niche.</p><p>Oh, and don’t make your kids choose between science and arts either. Let them learn the joy of fulfilling their creative potential and finding things to do with their own slack time.</p><p><em>Join the community of high performers — </em><a href="https://kasperowski.com/?utm_source=medium.com&amp;utm_medium=blog&amp;utm_campaign=good-feedback"><em>subscribe to Richard’s newsletter</em></a><em> today.</em></p><p><em>Originally published at </em><a href="https://kasperowski.com/intentional-about-meetings/?utm_source=medium.com&amp;utm_medium=blog&amp;utm_campaign=good-feedback"><em>kasperowski.com</em></a><em> on July 13, 2021</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b39b3f506df" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Psych Safety and Team EI: The Antidote to the Five Dysfunctions of a Team]]></title>
            <link>https://rkasper.medium.com/psych-safety-and-team-ei-the-antidote-to-the-five-dysfunctions-of-a-team-f25fa33dfa5?source=rss-8de0ae241122------2</link>
            <guid isPermaLink="false">https://medium.com/p/f25fa33dfa5</guid>
            <category><![CDATA[teaching]]></category>
            <category><![CDATA[emotional-intelligence]]></category>
            <category><![CDATA[teaching-and-learning]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[trust]]></category>
            <dc:creator><![CDATA[Richard Kasperowski]]></dc:creator>
            <pubDate>Sun, 12 Dec 2021 21:43:14 GMT</pubDate>
            <atom:updated>2021-12-12T21:43:14.983Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iAE1MT6fnK7JhWFIKPlEbg.jpeg" /><figcaption>Photo by Joshua Hoehne on Unsplash</figcaption></figure><p>My students are my best teachers. In a recent <a href="https://kasperowski.com/high-performance-teams/">High-Performance Team Building™ class</a>, my students asked some great questions. I had to pause, ponder, learn something new, and get back to them after class. Here’s one of those great questions, along with my response.</p><p><em>In the book The Five Dysfunctions of a Team, the author says that “Trust” is the most important skill for the team to work on. But Richard, you say Psychological Safety and Team Emotional Intelligence are the most important skills. What do you think about Trust?</em></p><p>My student was referring to Patrick Lencioni’s book, <a href="https://amzn.to/3FhvUjL"><em>The Five Dysfunctions of a Team: A Leadership Fable</em></a>, which is a brilliant story-based learning tool. (<a href="https://amzn.to/31jzbQS">Check out the graphic novel version</a> — I actually like it better than the original.). Whatever your learning style, you’ll find this book engaging. It contains memorable insights into the way people work together — or fail to work together — in business.</p><p>However, <a href="https://en.wikipedia.org/wiki/The_Five_Dysfunctions_of_a_Team#Criticism">the book has been criticized by some</a>, including Gordon Curphy and <a href="https://en.wikipedia.org/wiki/Robert_Hogan_(psychologist)">Robert Hogan</a>. Curphy and Hogan are organizational psychologists and leadership researchers. They criticize <em>The Five Dysfunctions</em> for its lack of evidence-based validity and rigor in their book <a href="https://amzn.to/3Eezlr3"><em>The Rocket Model: Practical Advice for Building High Performing Teams</em></a>.</p><p>Trust, or its absence, is the first dysfunction addressed in <em>The Five Dysfunctions</em>. It’s obvious that if we don’t trust each other, we won’t work well together. We won’t make ourselves vulnerable to each other, and we won’t grow our team emotional intelligence — two more important traits of great teams. Lencioni suggests activities to help teams build higher trust, including a series of personal disclosures. Curphy and Hogan point out that there is little empirical evidence for “sharing personal disclosures” as an isolated technique, and that it’s the kind of activity which would need to be handled with great care if the team were in any way dysfunctional or mistrusting.</p><p>Let’s keep in mind that <em>The Five Dysfunctions</em> is a work of fiction — its subtitle, after all, is <em>A Leadership Fable</em>. The team’s personal disclosures build excellent dramatic tension within the story. But according to Katzenbach and Smith in <a href="https://amzn.to/31kVK7A"><em>The Wisdom of Teams: Creating the High-Performance Organization</em></a>, <strong>the only effective method for teams to build trust and cohesion is to do real work together</strong>. A stand-alone “team building” activity outside the real work, like a Myers-Briggs Type Indicator activity, is not the “real work.” It might help build mutual awareness, but it won’t instantly create mutual trust. <a href="https://en.wikipedia.org/wiki/The_Five_Dysfunctions_of_a_Team#Criticism">[paraphrased from the Criticism section in the Wikepedia article on The Five Dysfunctions]</a></p><p>Trust takes time and is built in increments of behavior and outcome, none of which is great for a fictional narrative trying to illustrate a point rapidly. Trust is also fragile, and it can be damaged rapidly, which is one reason that anyone who feels insecure about trust in their team is likely to resist any activity that forces them to make disclosures that they’re not ready for. When these exercises are performed in an unengaged, arms-length way, they can even make things worse. For example, if it seems like one team member is just “checking the box” by being present in the workshop, but isn’t sharing anything particularly meaningful, another team member who is disclosing something deeply personal now feels vulnerable to a point of being naked — the trust level is worse than before.</p><p>Another important point to consider is that in the story, <strong>the company leaders don’t identify the leadership team as their <em>primary team</em></strong>. This insight is critical. Each of them manages a specialty skill area, like Marketing or R&amp;D. They identify with their specialty area as their primary team, rather than with the leadership team as their primary team. But to foster the organization’s best performance, the leadership team is where the trust needs to begin. In <a href="https://en.wikipedia.org/wiki/Lean_thinking">Lean</a> terms, we would say the leaders are sub-optimizing: they seek to optimize their specialty area instead of optimizing the whole organization.</p><p>To be most effective, they should adjust their definition of “primary team.” They should identify with the leadership team as their primary team; and they should think of their specialty areas — the group of people they manage — as the people who execute specialty skills on their behalf, for the benefit of the leadership team and of the organization as a whole. For example, the marketing leader’s primary team is the leadership team. She aligns with the rest of the leaders and offers to do marketing-related work for the leadership team. She executes the work using her marketing organization. The marketing organization is her execution team, doing the work for her, in the service of her primary team: the company leaders.</p><p>It’s a common problem for senior leadership in many organizations. By nature, the leadership team is composed of experts from each specialty department, who each see themselves as competing for budget and other resources, and who each have different priorities when they make decisions. They spend most of their time in their specialty subteam, and thus they build stronger personal relationships there. They each come to the boardroom on behalf of “their” team. It takes a deliberate shift to start to see the C-suite or senior management team as the <em>primary</em> unit in which they act.</p><p><a href="https://thecoreprotocols.org/corecommitments.html"><strong>The Core Protocols</strong></a><strong> are an antidote to the “five dysfunctions” problem.</strong> When the leaders come together as a cohesive primary team, they perform better — as individuals, as a leadership team, as specialty area subteams, and as a whole organization. Everything in the Core Protocols starts with action — behavior — bringing teammates together in a safe way. Deliberately adopting these practices at the top is a great way to begin cascading these behaviors throughout the entire organization.</p><p>Once you optimize the leadership team, the rest of the teams follow their example. The leaders model the optimal behaviors in all their interactions. This is what fixes trust issues at every level: everyone participates consensually and transparently, safe to be creative and effective within guide rails that shape the way they interact with each other.</p><p>The Core Protocols have a strong relationship to the science and research on great teams. We know from the science and research that great teams have skills for freedom and autonomy, self-awareness, connecting with each other, productivity, and error handling. The skills are universally applicable, in whatever industry the organization is engaged with, and in whatever operational area each team member is responsible for.</p><p>Above all, <strong>the Core Protocols are a way to transform a leadership team into a really great team</strong>. The steps we go through in class help individuals form together as a strong primary team and give them the skills to maintain that strength together.</p><p><em>Join the community of high performers — </em><a href="https://kasperowski.com/?utm_source=medium.com&amp;utm_medium=blog&amp;utm_campaign=good-feedback"><em>subscribe to Richard’s newsletter</em></a><em> today.</em></p><p><em>Originally published at </em><a href="https://kasperowski.com/intentional-about-meetings/?utm_source=medium.com&amp;utm_medium=blog&amp;utm_campaign=good-feedback"><em>kasperowski.com</em></a><em> on December 2, 2021</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f25fa33dfa5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Want to Know More About High-Performance Teams?]]></title>
            <link>https://rkasper.medium.com/want-to-know-more-about-high-performance-teams-18ce87bbff41?source=rss-8de0ae241122------2</link>
            <guid isPermaLink="false">https://medium.com/p/18ce87bbff41</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[high-performance-team]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[agile-coach]]></category>
            <dc:creator><![CDATA[Richard Kasperowski]]></dc:creator>
            <pubDate>Fri, 19 Feb 2021 15:57:42 GMT</pubDate>
            <atom:updated>2021-02-19T15:57:42.514Z</atom:updated>
            <content:encoded><![CDATA[<p><em>(Originally recorded as a podcast: </em><a href="https://kspr.co/Podcast57"><em>https://kspr.co/Podcast57</em></a><em>)</em></p><p><strong>Want to Know More About High-Performance Teams?</strong></p><p>Hi, friends! Welcome back to With Great People, the podcast for high-performance teams. I’m Richard Kasperowski.</p><p>Way back in 2020, we did a <a href="https://kasperowski.com/event/scrumalliance/">webinar on high-performance teams </a>in conjunction with the Scrum Alliance. (Thanks, Scrum Alliance friends, for hosting me!). In case you missed it, we’ll include a link to that webinar in our podcast notes.</p><p>We had a ton of questions after the event — people wanted to learn more. I want to make sure we answer everyone’s questions, so that’s what this episode is about: questions and answers about high-performace teams, psychological safety, team emotional intelligence, and the Core Protocols.</p><p>Here’s our first question:</p><p>Q: When you talked about positive bias as the foundation for great teams, you defined it partly with the phrase “no negation.” But what if a teammate makes a suggestion that is a hard NO — like, what they propose is illegal. How do you handle that with “no negativity”?</p><p>A: The foundation of positive bias, including the idea, “no negation,” is a reminder to make space for a wide diversity of ideas, to include everyone on your team in every conversation. It’s not permission for illegal or unethical behavior. You are responsible for always doing the right thing, consistently modeling the desired behaviors for your teammates, and <a href="https://thecoreprotocols.org/corecommitments.html">not doing anything dumb on purpose</a>.</p><p>Q: Can “Checking Out” be irresponsible?</p><p>A: When you <a href="https://thecoreprotocols.org/protocols/checkout.html">check out</a>, it is usually the most responsible thing to do: if you should be somewhere else doing something more valuable, do it! However, if you notice that you’re checking out most of the time, you should probably <a href="https://thecoreprotocols.org/protocols/investigate.html">investigate</a> yourself or <a href="https://thecoreprotocols.org/protocols/intentioncheck.html">check your intentions</a>: do you really want to be part of that team?</p><p>Q: Based on what I understand, self-awareness is a behavior that leads to high performance. So, is this a trait to cultivate, or is this a characteristic you look for when deciding who should join a team?</p><p>A: I would recruit people who have at least some self-awareness and a demonstrable growth mindset. The minimum self-awareness would be their knowledge that they want to be part of the team. They would be aligned with our goals, and they would be passionate about achieving our mutual goals together.</p><p>Q: What is the website reference for Check In?</p><p>A: You can find all the Core Protocols at <a href="https://thecoreprotocols.org/">https://thecoreprotocols.org/</a>. Check In is documented at <a href="https://thecoreprotocols.org/protocols/checkin.html">https://thecoreprotocols.org/protocols/checkin.html</a>. It’s all GPLd, and it’s all free. (And for the geekier among us: welcome! This version of the Core is a Git repository, genuinely open source. We welcome your comments, and we invite you to do whatever you want with it, like any other open source software.)</p><p>Q: In the emotion check-in protocol, we respond to our teammates by saying, “welcome.” What is the specific reason for saying “welcome”? Are we merely trying to let the person know we are listening, or is there more?</p><p>A: In the script for the <a href="https://thecoreprotocols.org/protocols/checkin.html">emotion check-in</a>, teammates say, “Welcome,” after the person checks in. Most people report that “welcome” helps them feel acknowledged and heard. This tiny bit of positivity triggers a feel-good sensation in the body: the body releases serotonin, dopamine, and oxytocin. We feel more relaxed, connected, and focused. Saying “welcome” is a simple connection behavior that binds us together more firmly.</p><p>Q: Is any of this based on VIA Institute character strengths? I’m noticing similarities, so I am curious.</p><p>A: There’s no explicit connection between the Core Protocols and VIA Institute. I wouldn’t be surprised if there were similarities: there’s more than one way for people to build high self-awareness, <a href="https://thecoreprotocols.org/protocols/personalalignment.html">aim for what they want</a>, and have great experiences together. <a href="https://thecoreprotocols.org/">The Core Protocols</a> are one way — there are others.</p><p>Q: How do you practice “passion”?</p><p>A: What a great question! Is Passion your <a href="https://thecoreprotocols.org/protocols/personalalignment.html">Personal Alignment</a>? Then I would turn that question back to you: What does passion mean to you — how would you define it? What would it look like if you were practicing it? How could someone observe that you’d been practicing it — what evidence would there be? You might want to fill in the <a href="http://teamtransformationcanvas.com/">Team Transformation Canvas</a> and see if it helps you with ideas.</p><p>Q: Most of us are working from home these days — we no longer work together in physical space. Have you looked at how to implement the Core Protocols in a virtual environment successfully or how we could modify them for virtual environments?</p><p>A: Yes! Every one of these behaviors works in a virtual environment. I wrote the blog piece <a href="https://kasperowski.com/stay-amazing-together/">“Stay Amazing Together When Life Is Hard”</a> to help with this. Take a look at the article’s sidebar, which includes ten tips for remote teams. For example, here’s what <a href="https://thecoreprotocols.org/protocols/decider.html">Decider</a> and <a href="https://thecoreprotocols.org/protocols/resolution.html">Resolution</a> might look like in an asynchronous online environment:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gNY8S5-ymtTDgj7m" /></figure><p>Q: As a Scrum Master, if you see someone who is distracted in a stand-up meeting, how do you let them know they can Pass or Check out?</p><p>A: I like to model these behaviors as a way to invite people to try them — without even telling them that it’s a behavior with a name. I would intentionally model <a href="https://thecoreprotocols.org/protocols/pass.html">Pass</a> or <a href="https://thecoreprotocols.org/protocols/checkout.html">Check Out</a> at the next stand-up: when it’s my turn, I’d just say, “I pass.” Or if I were distracted, I would check out. I also might <a href="https://thecoreprotocols.org/protocols/investigate.html">investigate</a> my teammate to try to understand what that distraction is about.</p><p>Q: How would you encourage a new team, composed of people who just met, to be open to sharing information about each other, to “investigate” each other? Since they just met, people might be more reticent to share information on personal aspects.</p><p>A: <a href="https://kasperowski.com/a-great-team-in-one-day/">I have a real-life story about this.</a> I was a member of a criminal jury. I wanted us to be a great team in a day, despite that we had just met. I simply modeled the behaviors, starting with <a href="https://thecoreprotocols.org/protocols/checkin.html">emotion check-in</a>. Everything flowed from there. Try it!</p><p>Q: Can ‘error handling’ be used as part of our Retrospectives?</p><p>A: Absolutely! The error handling behavior (<a href="https://thecoreprotocols.org/protocols/protocolcheck.html">Protocol Check</a> in <a href="https://thecoreprotocols.org/">the Core Protocols</a>) is an example of how to safely raise an important issue with our teammates: that we had made an agreement with each other, but we didn’t honor it. Being able to confront each other safely is a characteristic of great teams.</p><p>Q: At which stage of team development would you suggest we implement the Core Protocols? Would you recommend applying some of them before others?</p><p>A: Use the Core Protocols any time you want your team to be more effective, and use them immediately if you want your team to be more effective immediately. 😀</p><p>Q: What do you use to evaluate team “friendship” — other than the team’s performance level?</p><p>A: We think friendship — connection, general — is one of the most vital indicators of a high-performance team. We’ve been researching metrics for friendship. The research suggests that teammate interconnectedness is a good heuristic for friendship and that we can objectively measure it by looking at the frequency of communication between teammates. We plan to introduce Slack and email tools to help people measure their interconnectedness — to measure the level of friendship in a team. Meanwhile, <a href="https://kasperowski.com/diagnostic/">take a look at our team diagnostics tools</a>.</p><p>Q: What to do when the person that is looking at the cellphone is your leader/boss? Is there a safe way to suggest that they either stay engaged or Check Out?</p><p>A: When any teammate is disengaged, the first thing I consider whether they are “in” on <a href="https://thecoreprotocols.org/">the Core Protocols</a>. If they are “in,” I <a href="https://thecoreprotocols.org/protocols/protocolcheck.html">protocol check</a>: dear teammate, are you checked in, or should you check out? I <a href="https://thecoreprotocols.org/protocols/investigate.html">investigate</a> and <a href="https://thecoreprotocols.org/protocols/intentioncheck.html">intention check</a> if they’re open to it. Even if they’re not “in” with the Core Protocols, I check in, protocol check, investigate, and intention check. On the other hand, if the person is not “in” on the Core Protocols, well, we’ll just have to settle for a lesser-performing team. 🙁</p><p>Q: How do you deal with cultural differences based on people’s upbringing or background? For example, some folks are very shy/introverted and very reluctant to share/participate.</p><p>Q: How do we break past real cultural programming that has molded teammates into shy/introverted individuals? Sometimes they complain that they don’t want to engage more with each other. How can I help them come out of their shells?</p><p>A: I know what you mean — I’m one of those shy people who grew up in a family culture where we don’t share our feelings, in <a href="https://www.nature.com/articles/s41562-017-0240-0.epdf">a region that is less emotionally open</a>. Freedom is the foundation of high-performance teams: everyone gets to decide for themselves whether they want to opt-in. <a href="https://thecoreprotocols.org/protocols/pass.html">If someone opts out</a>, that’s fine. (And if they are familiar with <a href="https://hbr.org/2001/03/building-the-emotional-intelligence-of-groups">the research on team emotional intelligence</a>, they know that they are settling for a lesser-performing team.) Also, emotional intelligence isn’t a fixed trait; instead, it’s an ability that you can grow if you choose to. (Proof: despite growing up in a low EI culture, I have developed my emotional skills.) So if someone wants to improve their EI skills, they can.</p><p>Q: The company I work in comprises three teams; in my team, there are two of us: my boss and me. Because my teammate is my boss, I feel like I have no psychological safety, and we’re not an emotionally intelligent team. How do I bring this up with my boss?</p><p>A: It depends. Would your boss respond to numbers and logic? You might try sharing the research on psychological safety, including its correlation to high team performance (for example, <a href="https://www.researchgate.net/publication/309233109_Learning_from_Mistakes_is_Easier_Said_than_Done_Group_and_Organizational_Influences_on_the_Detection_and_Correction_of_Human_Error">Amy Edmondson’s seminal paper on the topic</a>).</p><p>Q: Let’s say you have a group of four people, and you’re pairing people up to connect and team together. Do you then swap the pairs around to team with each other, or leave them alone and let it happen organically?</p><p>A: You’re suggesting a practice called <a href="https://csis.pace.edu/~grossman/dcs/XR4-PromiscuousPairing.pdf">promiscuous pairing</a>. Try every possible combination of people. You might even try <a href="https://en.wikipedia.org/wiki/Mob_programming">mobbing</a>. The more teammates connect with each other, the better.</p><p>Q: How do you manage poor performers?</p><p>A: I start with an open mind. <a href="https://thecoreprotocols.org/protocols/checkin.html">I share how I’m feeling.</a> <a href="https://thecoreprotocols.org/protocols/investigate.html">I investigate</a> what I think I’m observing. <a href="https://thecoreprotocols.org/protocols/intentioncheck.html">I ask them what their intended outcomes are.</a> I ask them about their <a href="https://thecoreprotocols.org/protocols/personalalignment.html">biggest goals in life</a>. I offer them feedback, and if they’re up for it, <a href="https://thecoreprotocols.org/protocols/perfectiongame.html">we use Perfection Game to explore how well they’re doing</a>, what are some positives about their performance, and what they could do differently to be awesome at their role. It usually becomes evident that there’s something wrong with the team or organization — and we try to fix it. Or that the individual lacks some critical skill — and we make it possible for them to try to learn it. Or that they realize they don’t belong on the team — and they leave this team and find a team that fits them better.</p><p>Q: How can we engage with teammates who don’t want to engage? They just want to keep their heads down and work.</p><p>A: The research on the correlation between psychological safety and team performance is solid. It goes back more than 20 years. Would your teammates respond to numbers and logic? You might try sharing the research on psychological safety, including its correlation to high team performance (for example, <a href="https://www.researchgate.net/publication/309233109_Learning_from_Mistakes_is_Easier_Said_than_Done_Group_and_Organizational_Influences_on_the_Detection_and_Correction_of_Human_Error">Amy Edmondson’s seminal paper</a> on the topic or <a href="https://www.nytimes.com/2016/02/28/magazine/what-google-learned-from-its-quest-to-build-the-perfect-team.html">the famous news story about Google</a>).</p><p>Q: What are some tips for applying some of these learnings within a large organization that lacks the right mindset?</p><p>A: You could start with your team or your team-of-teams. Create a bubble within which there is high psychological safety, high emotional intelligence, and high performance. Protect the people within that bubble of awesomeness from the rest of the large organization.</p><p>Q: When offering a “pass,” would you do it as part of a Scrum event, or would you reserve it for a one-on-one? I fear that doing it in the Scrum event would look judgmental.</p><p>A: <a href="https://thecoreprotocols.org/protocols/pass.html">I just say, “I pass,”</a> at the right time. I don’t make a big deal out of it. There’s no ritual — it’s just two words.</p><p>Q: How can we encourage our leaders to use these ideas? They’re not “sold” on the idea that psychological safety is necessary for high-performing teams.</p><p>A: The research on the correlation between psychological safety and team performance is solid. It goes back more than 20 years. Would your leaders respond to numbers and logic? You might try sharing the research on psychological safety, including its correlation to high team performance (for example, <a href="https://www.researchgate.net/publication/309233109_Learning_from_Mistakes_is_Easier_Said_than_Done_Group_and_Organizational_Influences_on_the_Detection_and_Correction_of_Human_Error">Amy Edmondson’s seminal paper</a> on the topic or <a href="https://www.nytimes.com/2016/02/28/magazine/what-google-learned-from-its-quest-to-build-the-perfect-team.html">the famous news story about Google</a>).</p><p>Q: I am a new person on a team that has been working together for years. What would you suggest as a good start to get them to be a high-performing team?</p><p>A: I would try three things. First, I would simply model some of the behaviors. <a href="https://thecoreprotocols.org/protocols/checkin.html">Try an emotion check-in</a>; you might explain what it feels like to be a new member of this long-standing team. <a href="https://thecoreprotocols.org/protocols/pass.html">Pass on something.</a> Suggest <a href="https://thecoreprotocols.org/protocols/decider.html">a better way to make decisions</a> and <a href="https://thecoreprotocols.org/protocols/resolution.html">resolve conflict</a>. If someone asks you what you’re doing, explicitly explain it to them. Next, I would share the decades of science and research on teams and team performance. <a href="https://www.researchgate.net/publication/309233109_Learning_from_Mistakes_is_Easier_Said_than_Done_Group_and_Organizational_Influences_on_the_Detection_and_Correction_of_Human_Error">The highest performing teams enjoy measurably high levels of psychological safety</a> and <a href="https://hbr.org/2001/03/building-the-emotional-intelligence-of-groups">emotional intelligence</a>; if we want our team to be one of the highest performing teams, <a href="https://www.nytimes.com/2016/02/28/magazine/what-google-learned-from-its-quest-to-build-the-perfect-team.html">the science and research tell us that we’ll need high safety</a> and high EI. Finally, <a href="https://kasperowski.com/training/">consider taking a class or getting some coaching on the behaviors that can get your team into a state of high safety, high EI, and, thus, high performance</a>.</p><p>Q: If you have a team stuck in the “storming” phase, how would you propose getting them past this phase?</p><p>A: You’re talking about <a href="https://en.wikipedia.org/wiki/Tuckman&#39;s_stages_of_group_development">Tuckman’s model of team formation</a>. I notice that <a href="https://kasperowski.com/training/">when we run a class or workshop</a> on <a href="https://thecoreprotocols.org/">the Core Protocols</a>, we traverse the stages of team formation super fast — from forming to storming to norming and performing in as little as one day. You could try it yourself, or <a href="https://thecoreprotocols.org/protocols/askforhelp.html">you could ask for help</a>.</p><p>Q: How can you keep these values alive after a reorganization? Do you need to start from scratch with Tuckman?</p><p>Q: How do you deal with unstable teams during organizational change?</p><p>A: In the most successful cases, leaders learn and practice these behaviors first, before anyone else in the organization. When leaders do something first, we call it leading — we call them leaders. Leaders go first, right? 😉 They might <a href="https://kasperowski.com/training/">take one of my classes and participate in regular coaching to practice and master the behaviors of high-performance teams</a>. The leadership team becomes the first high-performing team in the organization, and they openly model the behaviors so everyone else can learn by imitating them. In one organization I worked with, the leadership team held their daily stand-up in an open physical space, and everyone in the organization was invited to observe. They began their daily meeting with an <a href="https://thecoreprotocols.org/protocols/checkin.html">emotion check-in</a>. They modeled <a href="https://thecoreprotocols.org/protocols/decider.html">good decision making</a> and <a href="https://thecoreprotocols.org/protocols/resolution.html">conflict resolution</a>, and all the other behaviors of high-performing teams. They were true leaders — they went first — and they genuinely tried to be a great team. They made it safe for everyone else in the organization to learn and practice the behaviors of high-performance teams. They cultivated an environment of high psychological safety and <a href="https://hbr.org/2001/03/building-the-emotional-intelligence-of-groups">team emotional intelligence</a>, critical ingredients for high-performance. When teams got shuffled to achieve organizational goals better, team members had the skills to reteam quickly. They already had <a href="https://thecoreprotocols.org/corecommitments.html">norms</a> they could use to spin up into well-performing teams rapidly.</p><p>Q: How do I encourage my teammates to have the courage to be honest about how they feel?</p><p>A: Try modeling it. <a href="https://thecoreprotocols.org/protocols/checkin.html">Share your emotions</a> with them, and invite them (but don’t pressure them) to do the same.</p><p>That’s it for today’s questions! If you have a question about anything you think I might be able to help with, just ask. We’ll include a link to my website’s Contact page — just type your question there, and I’ll get back to you.</p><p>Thanks for joining us here on With Great People, the podcast for high-performance teams. We’ll be back soon with another episode. And remember, to support this podcast, visit my website, kasperowski.com. Thanks for listening!</p><p><em>Join the community of high performers — </em><a href="https://kasperowski.com/?utm_source=medium.com&amp;utm_medium=blog&amp;utm_campaign=good-feedback"><em>subscribe to Richard’s news letter</em></a><em> today.</em></p><p><em>Originally published at </em><a href="https://kasperowski.com/intentional-about-meetings/?utm_source=medium.com&amp;utm_medium=blog&amp;utm_campaign=good-feedback"><em>kasperowski.com</em></a><em> on January 11, 2021</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18ce87bbff41" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your Remote Team Actually Can Be Awesome]]></title>
            <link>https://rkasper.medium.com/your-remote-team-actually-can-be-awesome-2e339e94b6cc?source=rss-8de0ae241122------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e339e94b6cc</guid>
            <category><![CDATA[agile-coaching]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[remote-work]]></category>
            <category><![CDATA[miro]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <dc:creator><![CDATA[Richard Kasperowski]]></dc:creator>
            <pubDate>Tue, 02 Feb 2021 16:45:26 GMT</pubDate>
            <atom:updated>2021-02-02T16:45:26.545Z</atom:updated>
            <content:encoded><![CDATA[<p>Cue the piano:</p><blockquote>If you don’t want to see me…<br>I did a full one-eighty, crazy<br>Thinking ‘bout the way I was<br>– from <a href="https://genius.com/Dua-lipa-dont-start-now-lyrics">Dua Lipa’s “Don’t Start Now”</a></blockquote><p>I did a full one-eighty in my teaching, coaching, and consulting work. As recently as March, I advised clients that if they care about the product they’re building together, they need to be collocated and working together in real-time. If they’re working on a less important product, then at least try to work together in the same time zone. And if they’re maintaining an end-of-life product, then it doesn’t matter, do whatever you want.</p><p>This advice is obviously bogus. So what should we do today?</p><p>These days, I still advise people to maximize connection — individuals interacting together really well. Think about the people you work with and how to amplify your ability to connect with each other. Do everything possible to have an awesome team, and an awesome product will follow as a side effect (<a href="https://www.devopschat.net/2017/07/13/team-product/">inspired by Jim and Michele McCarthy when they say, “Team == Product”</a>). Then, and only then, choose the tools to amplify your team’s awesomeness. As the <a href="http://agilemanifesto.org/">Manifesto for Agile Software Development</a> guides us:: “… we have come to value individuals and interactions over processes and tools.”</p><p>Despite that, of course we need to use tools to do great work together. Which tools should we use to amplify our teams’ awesomeness? In this article, I’ll focus on tools to enhance real-time collaboration.</p><h3>Video: Cameras On!</h3><p>Collaborating via video is practically a given. It’s the next best thing to being together face-to-face in physical space. And I mean real video meetings, with cameras and microphones turned on so we can see each other, hear each other, and engage in authentic communication. Communication is more than the words we speak or write; real communication includes vocal inflection and body language. <a href="https://www.psychologytoday.com/us/blog/beyond-words/201109/is-nonverbal-communication-numbers-game"><strong><em>We don’t know precisely what percentage of communication is nonverbal.</em></strong></a> Still, when we limit ourselves solely to voice — or worse, to asynchronous text chat — we lose a great deal of information and connection.</p><p>When I arrive in a video meeting and people have their cameras turned off, I feel disconnected from them. If it were a face-to-face physical space meeting, would they have shown up with a paper bag over their head? That’s what camera-off feels like to me in online space: as if they’re embarrassed to be there, they don’t want anyone to know they’re there, they refuse even to try to connect with anyone else present. I feel like they’re disengaged, that they’re not “<a href="https://thecoreprotocols.org/protocols/checkin.html"><strong><em>in</em></strong></a>” with the team, that we’re wasting our time together, and that they should <a href="https://thecoreprotocols.org/protocols/checkout.html"><strong><em>check out</em></strong></a>.</p><p>So I invite everyone to turn on their cameras. I remind them that feedback is one of the most critical aspects of our work, and that faster and more information-rich feedback will help us connect more strongly and help us get better results together. The fastest form of feedback we have as humans is our facial expressions. It’s so easy to see from someone’s face whether they understood what we said, whether it made sense, or whether they disagree a little or a lot. We use that feedback to make adjustments to what we’re saying and how we’re saying it to ensure there are no misunderstandings and that we achieve our goals together. (Hmmm, that last sentence includes my definition of a protocol: a shared agreement that helps us avoid misunderstandings and accomplish our shared goals. Perhaps “Video Cameras Turned On” could be one of your team’s protocols.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/445/0*aiLKKkxMudVuQY6h.jpg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/445/0*8xdRMgTpDwVpK46U.jpg" /></figure><h3>The Simplest Tools that Work</h3><p>Faces and voices — video and audio — are a great start. To enhance the conversation, most of us need tools to visualize the conversation, the collaboration, and the ideas we are creating together. The best idea is to use the simplest tools that work: easy tools that everyone already knows how to use, and that are accessible to everyone everywhere in the world.</p><p>For most collaborations, a shared text editor is the best tool for the job. Most people know or can quickly learn <a href="http://docs.google.com/"><strong><em>Google Docs</em></strong></a>, so that’s my default recommendation. Just create a new document, click the Share button, change the Share settings to “Anyone with the link” — “Editor,” and share the link with your teammates. They open the shared document, and you all take notes and record ideas together in real-time. Easy!</p><p>Typing text into a shared document is a great start, and we can amplify that goodness with tools that are more visual. <a href="https://jamboard.google.com/"><strong><em>Google Jamboard</em></strong></a> is a virtual whiteboard with make-believe pens and post-its, and it’s super easy to use. It works well in the web browser, and it’s easy to add hand-written content on a tablet with your finger or an electronic pen. (I use it on my iPad with a Pencil.) I’ve used it for everything from everyday collaboration with teammates to Open Space breakout sessions. Sometimes when traveling for work (pre-Covid-19), I use it to help my stepson with his homework. Zoom + Jamboard is almost like being in the same room together.</p><h3>Miro for Awesomely Rich Collaboration</h3><p>For my <a href="https://agilesoftwarecourse.org/"><strong><em>Agile Software Development course at Harvard</em></strong></a>, I needed to recreate the in-classroom learning experience without being in the classroom. Pre-Covid, almost every learning module included face-to-face hands-on learning activities. In Covid times, face-to-face is impossible. The challenge was to recreate highly interactive collaborative learning activities without being in physical space together.</p><p><a href="https://miro.com/"><strong><em>Miro</em></strong></a> is the best tool for a challenge like this. I successfully transformed the entire course — and all of the other learning and work activities I use with clients — to work online.</p><p>I encourage you to add Miro to your toolset for online classes and work meetings. Here’s a set of my pre-made Miro templates. Just log in to your Miro account, open one of my canvases, and make your own copy of any template you want to use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/445/0*qCSfjEI3bo5UkiIo.jpg" /></figure><h3>Team Transformation Canvas</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*G7v6-sgCc2sFa1cb.jpg" /></figure><p>Want an easy tool to help you start building the best team of your life?</p><p>That’s what the <strong>Team Transformation Canvas</strong> is: a practical worksheet to help you and your teammates discover the best in each other and put it into action.</p><p>The canvas facilitates individual self-awareness of your current emotional state and desired personal outcomes. It helps you develop a deepened understanding of what drives your behaviors and actions. By identifying and owning these intrinsic motivations, you align your future actions with your most inherent needs, creating your unique pathway to professional and personal self-actualization. Finally, the canvas facilitates deep emotional and supportive connections with each other — the building blocks of a high-performance team.</p><p>You can find the <a href="https://miro.com/miroverse/category/team-building/team-transformation-canvas"><strong><em>Team Transformation Canvas in Miro’s Miroverse</em></strong></a>, or you can <a href="https://miro.com/app/board/o9J_kse2iYY=/"><strong><em>make a copy of my Team Transformation Canvas template</em></strong></a>.</p><h3>Product Inception Canvas</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*toXvuvFUWL_iGqfw.jpg" /></figure><p>Want an easy tool to help you start building great products that people love?</p><p>That’s exactly what the <strong>Product Inception Canvas</strong> is: a practical worksheet to help you, your business people, your stakeholders, and everyone else on your team discover exactly what to do next as you build and extend your product.</p><p>The <strong>Product Inception Canvas</strong> facilitates alignment among business people, product development teams, and stakeholders. We begin by identifying, discussing, and aligning on our company vision and product vision: Who are we? Why do we exist? How will the world be different and better because of the work we are doing? Next, we identify stakeholders and bring them to life as user personas: Who cares about the work we are doing? Who are they, really, including all their details? Finally, we put it all together into a product backlog — an ordered to-do list of everything we want to be true about our product in the future: What are the wants and needs of our stakeholders? What problems will we solve for them? Which problems should we solve first to maximize their joy?</p><p><a href="https://miro.com/app/board/o9J_kr3H3pQ=/"><strong><em>To use the Product Inception Canvas, make a copy of my template.</em></strong></a></p><h3>Doggy Estimating: Online</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*q0jNKTAbVLUKPITg.jpg" /></figure><p>Given a product backlog and an agreement about what it means to get backlog items done, our next step is to estimate the size and complexity of the user stories on the backlog. I use the following two templates to help agile teams learn estimation techniques. The first learning activity is <strong>Doggy Estimating: Online</strong>. This is a 100% online version of the old Doggy Planning game from Tasty Cupcakes. I use this activity to help people learn how to estimate product backlog items one-at-a-time using Planning Poker.</p><p>You can find <a href="https://miro.com/miroverse/category/agile-workflows/doggy-estimating-online"><strong><em>Doggy Estimating: Online in Miro’s Miroverse</em></strong></a> or <a href="https://miro.com/app/board/o9J_krBjy6I=/"><strong><em>make a copy of my Doggy Estimating: Online template</em></strong></a>.</p><p>Are you a teacher or coach? <a href="https://kasperowski.com/contact-me/"><strong><em>Ask me for a copy of the companion board, Doggy Estimating: Online — for Facilitators.</em></strong></a></p><h3>Perfection Game Retrospective: Online</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*Lcj4dtGwB0BoTWPZ.jpg" /></figure><p>My favorite retrospective activity is <a href="https://thecoreprotocols.org/protocols/perfectiongame.html"><strong><em>Perfection Game</em></strong></a>. Perfection Game is the single best activity to give or receive feedback about anything. It’s an excellent tool for teammates to reflect on their performance as a team and agree on the most important improvement to make together.</p><p><a href="https://miro.com/app/board/o9J_kq2e7vE=/"><strong><em>To use the Perfection Game Retrospective: Online, make a copy of my template.</em></strong></a></p><h3>Lean Coffee</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*DXpSaUTfXB5F2fJs.jpg" /></figure><p><a href="https://kasperowski.com/open-space-technology-and-lean-coffee/"><strong><em>Lean Coffee is another great way to facilitate a productive meeting.</em></strong></a> I often use <strong>Lean Coffee</strong> to host conversations with groups of eight or fewer people. This <strong>Lean Coffee</strong> template includes all the instructions and tools you need to facilitate a great discussion.</p><p><a href="https://miro.com/app/board/o9J_kjETAHU="><strong><em>To facilitate a Lean Coffee, make a copy of my template.</em></strong></a></p><h3>Agile Point Game</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/274/0*I-Pk5EOqIhM9HnJw.jpg" /></figure><p><strong>Agile Point Game</strong>: It’s like the Ball Point Game, but it’s 100% online.</p><p>Are you an Agile trainer, coach, or scrum master? Do you want an easy way to help your students learn the foundations of Agile software development? Then the <strong>Agile Point Game</strong> is for you.</p><p>The Agile Point Game is a 100% online version of Boris Gloger’s famous Ball Point Game. By playing this simple game together, your students learn about teamwork, collaboration, iterative work, forecasting, retrospectives, empirical process control, diversity and inclusion, the Tuckman model of team formation, continuous improvement, experimenting, inspect and adapt, Agile principles, psychological safety, and trust.</p><p>Best of all, they have fun! That means they really learn together. They think of Agile as something fun. They look back at your Agile training class as an enjoyable experience that brought them together as a team.</p><p>I use the <strong>Agile Point Game</strong> as the opening activity of every online Agile class I teach, including my courses at Harvard University and in industry. We reference this learning activity throughout the rest of the course: every element of the game is a stepping stone to deeper learning.</p><p>Enjoy this Agile learning game!</p><p>You can find the <a href="https://miro.com/miroverse/category/workshops/agile-point-game"><strong><em>Agile Point Game in Miro’s Miroverse</em></strong></a> or <a href="https://miro.com/app/board/o9J_ks-mwgM=/"><strong><em>make a copy of my Agile Point Game template</em></strong></a>.</p><h3>User Story Template</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*qcmnLJWHfGZy-lLS.jpg" /></figure><p>Now that your team knows what they are building, who they are building it for, why it’s important, and what’s on the initial product backlog, it’s time to elaborate those initial product backlog items as user stories. Fill in the blanks on this user story template, and you’ll be on your way.</p><p><a href="https://miro.com/app/board/o9J_kr3M4C0=/"><strong><em>To use the User Story Template, make a copy of my template.</em></strong></a></p><h3>Animal Estimating: Online</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*jqJeMxwb23nJH8kN.jpg" /></figure><p>The other activity I use to help people learn estimating is <strong>Animal Estimating: Online</strong>. I use this one to help people learn how to estimate a large product backlog all-at-once using affinity grouping.</p><p>You can <a href="https://miro.com/miroverse/category/agile-workflows/animal-estimating-online"><strong><em>find Animal Estimating: Online in Miro’s Miroverse</em></strong></a> or <a href="https://miro.com/app/board/o9J_krCbE0Q=/"><strong><em>make a copy of my Animal Estimating: Online template</em></strong></a>.</p><h3>User Story Mapping Workshop</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/243/0*XWrwR-txu04otQGR.jpg" /></figure><p><a href="https://www.jpattonassociates.com/user-story-mapping/"><strong><em>User story mapping</em></strong></a> is a way to explore exactly what to build. It is precisely the right tool for everyone involved in building a product — customers, business people, developers, and everyone else — to get all their great ideas out there, prioritize them, and get aligned with each other about exactly what to build next. This <strong>User Story Mapping Workshop</strong> template makes it easy for remote teams to go through all the steps to learn user story mapping and then apply the technique to their future amazing product.</p><p><a href="https://miro.com/app/board/o9J_kkHUKOw="><strong><em>To use the User Story Mapping Workshop, make a copy of my template.</em></strong></a></p><h3>Course Creation Canvas</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/255/0*NpBopOn7uL_EgP0k.jpg" /></figure><p>Delivering training is easy. But will your students remember it next week? And will they still be practicing their new skills months from now?</p><p>Chances are the answer is “no.” <a href="https://hbr.org/2016/10/why-leadership-training-fails-and-what-to-do-about-it"><strong><em>Most corporate training fails</em></strong></a> at its goal of effecting organizational change, and most training of any kind fails because of something called the <a href="https://en.m.wikipedia.org/wiki/Forgetting_curve"><strong><em>Forgetting Curve</em></strong></a>. Without regular practice at new skills and concepts, people can’t remember what they learned in a class. It’s not their fault — it’s merely a human trait. So how do we facilitate effective learning? How can we support learners with effective courses, skills practice, and learning environments?</p><p>I spend a lot of time creating learning material and helping students learn and acquire all the knowledge and skills they want. Every time I create a new short course or learning module, I follow a pattern based on <a href="https://bowperson.com/"><strong><em>Sharon Bowman</em></strong></a>’s <a href="https://amzn.to/3m4cCoz"><strong><em>Training from the Back of the Room!</em></strong></a>. I created the <strong>Course Creation Canvas</strong> to make it easy for me — and more importantly, for you — to create great learning sessions. It works every time. It’s an easy way to create a great course for your students.</p><p><a href="https://miro.com/app/board/o9J_ko3mXos=/"><strong><em>To use the Course Creation Canvas, make a copy of my template.</em></strong></a></p><h3>Build Your Own Scrum: Online</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/286/0*nVxMaJRYf8ckkWHN.jpg" /></figure><p>After playing the <strong>Agile Point Game</strong>, my students are ready to learn Scrum. We use my online adaptation of <a href="https://weisbart.com/byos"><strong><em>Adam Weisbart’s Build Your Own Scrum</em></strong></a>. BYOS is, without a doubt, the best Scrum learning activity.</p><p>If you’d like a <a href="https://kasperowski.com/contact-me/"><strong><em>private preview of my Build Your Own Scrum: Online adaptation, send me a message</em></strong></a>. Meanwhile, I’ll be updating it to match the new <a href="https://scrumguides.org/"><strong><em>Scrum Guide 2020</em></strong></a>.</p><h3>Definition of Done &amp; Ready</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*Td54QHGssDmHgAqa.jpg" /></figure><p>Yay, we have a product backlog! Next step: let’s agree with each other on what it means to have a high-quality finished product increment — let’s create our <a href="https://kasperowski.com/is-it-done/"><strong><em>Definition of Done</em></strong></a>. And to help us make sure we really understand what we’re about to build, let’s also define what it means for us to be <a href="https://kasperowski.com/get-ready-to-get-done-definition-of-ready/"><strong><em>Ready to start the work</em></strong></a>. I use these templates to teach the concepts of Definition of Done and Definition of Ready, and to create real Definitions of Done and Ready with the teams I work with.</p><p><a href="https://miro.com/app/board/o9J_krCXXJ4=/"><strong><em>To use the Definition of Done &amp; Ready board, make a copy of my template.</em></strong></a></p><h3>PlusDelta Retrospective: Online</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*idn5yMglrNUGDFNV.jpg" /></figure><p>Whew, we made it to the end of the sprint! What’s the thing we do at the end of the sprint to inspect-and-adapt on ourselves as a team, to make our team the most amazing team that has ever existed in the history of the universe, building the most incredible highest quality product ever? That’s right, it’s time for a retrospective!</p><p>I have two retrospective templates that I like to share with my students and real work teams. The first is a simple <strong>PlusDelta Retrospective: Online</strong>. This is the activity where you and your teammates collectively identify the things that went well (“pluses”) and the things that you’d like to change (“deltas”). Then, together as a team, you use those data to guide the massive improvements you’ll make right away.</p><p><a href="https://miro.com/app/board/o9J_kqgECqk=/"><strong><em>To use the PlusDelta Retrospective: Online, make a copy of my template.</em></strong></a></p><h3>Open Space: Online</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*kILIa-SMqtWopTdy.jpg" /></figure><p><a href="https://openspaceworld.org/"><strong><em>Open Space</em></strong></a> is a great way to hold a productive meeting for anywhere from 5 to 2000 people who have an important problem that they wanted to solve yesterday. If you want to help all those caring people combine their individual brains into a super-creative problem-solving machine, then Open Space is probably the right tool for you.</p><p>I’ve probably facilitated more Open Spaces than anyone else in the world, including <a href="https://kasperowski.com/open-space-technology-pushing-the-limits/"><strong><em>an Open Space that lasted six weeks</em></strong></a>. I’ve taken all that experience and put it together into an <strong>Open Space: Online</strong> template that you can use to facilitate an OS event for any group of people. And when we get back to face-to-face events in physical space, you can <a href="https://openspaceproceedings.com/"><strong><em>use my Open Space Proceedings website to augment your Open Space event</em></strong></a>.</p><p>The <strong>Open Space: Online</strong> template is a work in progress. <a href="https://miro.com/app/board/o9J_krR6QKI=/"><strong><em>To use Open Space: Online, make a copy of this example and customize it for your event.</em></strong></a></p><h3>Live Class with Hand-Drawn Posters</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*LNOGROcr38Net5M9.jpg" /></figure><p>My physical-space classes are typically zero-PowerPoint fiestas. Yay! Instead of lecturing over slides that quickly disappear from the screen, I hand-draw notes on large poster paper. The learning benefits are myriad. For one thing, it ensures that I, as the teacher, go at human pace — not too fast for learners, and not too slow, either. When a teacher reads from pre-made PowerPoint (or Keynote or Google Slides) slides, they go so fast that it feels like they are assaulting their students with so much information so quickly that it hurts. Instead, I draw posters while I’m talking, guaranteeing that I’m going at the same pace that they can absorb the material.</p><p>The other significant benefit is that all the class material is visible to learners all the time. We stick the posters to the classroom walls, basically wallpapering the room with information. If someone wants a little reminder about something, all they have to do is look at the right poster on the right wall, and there it is; they’re all set. This contrasts with ephemeral PowerPoint slides that disappear into the ether, leaving students bewildered about what happened earlier in the course.</p><p>To reproduce this in my online classes, I use my <strong>Live Class with Hand-Drawn Posters</strong> template. Before class starts, I make a copy of the template and customize it for the class I’m about to teach. I share the Miro link with my students so they can navigate around the notes and zoom in on whatever they want to see at the moment. I screen-share what I’m live-drawing to help them focus on that moment’s learning segment, but they’re free to refer back to whatever content they want to see whenever they want to see it. And they can keep that copy of the classroom visuals as their notes forever.</p><p><a href="https://miro.com/app/board/o9J_le0g5EU=/"><strong><em>To use Live Class with Hand-Drawn Posters, make a copy of my template.</em></strong></a></p><h3>What’s Next for You?</h3><p>I’m hopeful these Miro templates will be great starting points for you, your learners, and your colleagues. Let me know what works for and what improvements we could make to these templates. If you want any help, just ask.</p><p><em>Join the community of high performers — </em><a href="https://kasperowski.com/?utm_source=medium.com&amp;utm_medium=blog&amp;utm_campaign=good-feedback"><em>subscribe to Richard’s news letter</em></a><em> today.</em></p><p><em>Originally published at </em><a href="https://kasperowski.com/intentional-about-meetings/?utm_source=medium.com&amp;utm_medium=blog&amp;utm_campaign=good-feedback"><em>kasperowski.com</em></a><em> on December 3, 2020</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e339e94b6cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Build Super-Cohesive Teams and Work with Joy]]></title>
            <link>https://rkasper.medium.com/how-to-build-super-cohesive-teams-and-work-with-joy-f67194b55a76?source=rss-8de0ae241122------2</link>
            <guid isPermaLink="false">https://medium.com/p/f67194b55a76</guid>
            <category><![CDATA[work]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[joy]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Richard Kasperowski]]></dc:creator>
            <pubDate>Tue, 26 Jan 2021 13:08:04 GMT</pubDate>
            <atom:updated>2022-01-10T19:34:01.527Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/739/1*rbFmMeZEfFhIaLL_ayCpLg.gif" /></figure><p>In case you missed it, James Shore and I had a chat last January about amazingly great work teams. James is an Agile software development teacher, writer, and consultant. He is the co-author of the book <a href="https://click.mailerlite.com/link/c/"><em>The Art of Agile Development</em></a>, a seminal work in the Agile community. He also co-created with Diana Larsen the <a href="https://click.mailerlite.com/link/c/">Agile Fluency Model</a>, a highly-regarded guide for Agile adoption.</p><p><a href="https://click.mailerlite.com/link/c/"><strong>We captured our conversation in an episode of my podcast, With Great People: The Podcast for High-Performance Teams.</strong></a> During the podcast, James tells us about his first encounter with <a href="https://click.mailerlite.com/link/c/">Extreme Programming</a>, what he learned from that experience, and why he has been on the mission ever since to recreate the joy he felt with this team:</p><p><em>And I would say that in a way, my career has been about reproducing that experience. Because when you work with a great team, with a jelled team, there’s this experience of every day you’re excited to go to work and every day you’re looking forward to working with these people. I mean, there’s some good days and bad days, like anything, but overall you’re really looking forward to working with people. And eventually these teams always break up for some reason. And there’s this model called the Tuckman Model of Team Formation, you’ve probably heard of it, it goes like this forming, storming, norming, performing, …</em></p><p><strong>Here’s the full interview:</strong></p><p>Richard Kasperowski:</p><p>Our guest today is James Shore. Hi James. Welcome to the podcast.</p><p>James Shore:<br> Thanks for having me. I’m happy to be here.</p><p>Richard:<br> Yeah. Great. I’m really happy to have you here. Can you introduce yourself to our listeners?</p><p>James:<br> Yeah, I’m a software developer turned consultant. I’ve been doing this consulting in the agile space for about 20 years. And what I do is I help companies figure out software development effectiveness. So particularly smaller companies that are growing that are finding that as they grow, it’s harder and harder to develop software the way they know, they used to know how to do, I help them out with that. I also wrote a book called The Art of Agile Development and I co-created the agile fluency model and co-founded the agile fluency project with Diana Larson.</p><p>Richard:<br> All right. And I’m hoping we’ll hear more about that as we go, the agile fluency model, the agile fluency project, I’m very familiar with. I’ve known about it for a, I don’t know, I think since you guys started it.</p><p>James:<br> Yeah. We started it back in 2011, 2012 is when the article first came out.</p><p>Richard:<br> Yeah. All right. Now this is a podcast about teams and best teams, the best team of your life. As you reflect on yourself and your life, what’s your best team ever, and this is not constrained to work, this could be any group of two or more people you’ve been part of, what’s the best one of those of your life?</p><p>James:<br> Yeah. Well, as a consultant, particularly one who does a lot of embedded immersion consulting, I’ve worked with a lot of teams. And so when you sent me this question in advance, I had to really think about it because there I have worked with a lot of teams and the best one ever is kind of a big ask, but I would say that the best team I’ve worked with was at a company on the East Coast that developed a financial software. And they brought me in because they wanted to do a rewrite and they were going to do it right this time, that’s what everybody says when they do a software rewrite. And it ended up being a really … it was a great team to work with. I loved working with them. They sent me a nice gift afterwards actually, Guitar Hero, I don’t know if you remember that game.</p><p>Richard:<br> Cool. Not only do I remember it, but I’ve been dreaming about it so much lately. I want to get some Guitar Hero controllers again.</p><p>James:<br> Yeah, I actually just last year gave them away, like gave away the old PS2 and I regret it now, but yeah. So we got along really well and they were also just really successful afterwards. When I joined the team, there was maybe six, seven people. I don’t remember the details now, and after we worked together, their product was really successful, they grew. They grew to being about four or five teams, all working very closely together and eventually were bought out by IBM who I think killed them, but it was a great experience. And I think of all the teams I’ve worked with, they’re the ones who I think were the best. Although it’s a tough call.</p><p>Richard:<br> All right. And now that this is, I don’t know, this is interesting. It’s a little different, most people are sharing with me stories about a team that they were in sort of like a first-class member of, they were all peers. So this is a special one that we’re talking about today. This is where they hired you to help them be an excellent team.</p><p>James:<br> That’s right. Well, they didn’t hire me to help them be an excellent team, they hired me to help them do excellent software development. And like I said, I’ve been doing consulting for 20 years, so all my stories are going to be stories where I was a consultant brought in because 20 years ago, I didn’t know hardly nothing. And I know a little bit more now, but maybe still hardly nothing.</p><p>James:<br> But the thing is, is my favorite way to work, my first experience, so I don’t know how much your listeners know about software development and agile development and so forth, but I first got into agile development through something called extreme programming. And that was a team that I was actually hired in as a contractor, but I was still a member of the team. And that was not necessarily the best team I’ve ever worked with, but it was my favorite team experience of my life. And it sort of ruined me for doing work in any other way.</p><p>James:<br> And I would say that in a way, my career has been about reproducing that experience. Because when you work with a great team, with a jelled team, there’s this experience of every day you’re excited to go to work and every day you’re looking forward to working with these people. I mean, there’s some good days and bad days, like anything, but overall you’re really looking forward to working with people. And eventually these teams always break up for some reason. And there’s this model called the Tuckman Model of Team Formation, you’ve probably heard of it, it goes like this forming, storming, norming, performing, and then mourning or-</p><p>Richard:<br> Ajorning.</p><p>James:<br> Or ajorning.</p><p>Richard:<br> What do you say with the writing accent?</p><p>James:<br> Yeah. Sort of that Shakespearian ajorning.</p><p>Richard:<br> Ajorning.</p><p>James:<br> Yeah. And so when that team breaks up, there’s this period of regret. And I’ll always remember that first team. And that was my second choice, when you asked me for my best team, but I don’t think they were actually the greatest team I’ve worked with, but it was a great experience for sure. I mean, that was 20 years ago and I would say in my consulting career, what I really just wanted to do is reproduce that experience. And unfortunately I can’t really, because I’m brought in to help a team really become great and do great work. And then by the time they’re there it’s time for me to leave.</p><p>James:<br> But the work I do is my favorite type of work is where I’m joining a team and I’m embedding with them and I’m there as a peer. And I’m a peer who knows something that the other people on the team don’t, but they also know things I don’t and really being successful and really doing great work requires that we all act as peers. And that’s actually, I would say one of the lessons I have about being on a great team is that you can have people with different levels of experience, but you’re all there as peers, you’re all working together to create a great result.</p><p>James:<br> So for this team on the East Coast, yeah, I was brought in because I had special knowledge about extreme programming and software development. For those of your listeners who are not familiar with agile development, extreme programming was invented in the nineties and that’s where the name came from and I’ll just leave it at that. But it’s actually a really, really nice way of developing software despite the name, not because of the name, but despite the name. So, yeah, I had some special knowledge, but that’s not what made the team great.</p><p>Richard:<br> All right. Well, let’s go back to this team, if you can take yourself back to it, sometimes people close their eyes and sort of re-dream of being a part of this team. If you took yourself back to those people and the activity you were doing together, is there one word that you could use to describe the sensation of being part of that team?</p><p>James:<br> I would say if I had to choose one word, I’m going to choose two words to answer this in two different ways. One word would be open-minded and another word would be comfortable. The second word, that’s what I’ve seen, I’ve had the blessing to have been on several teams that were just really good teams and that comfortableness is the common factor in all of them. This one team I’m thinking of in the East Coast, I would say open-mind was what made them great. But being part of a great team, it’s this comfort and a sense of belonging and a sense of really being happy to be part, be working together on this.</p><p>Richard:<br> Okay. So this East Coast team that we keep telling, we’re going to call them at the East Coast team.</p><p>James:<br> Yeah. I don’t want to say the name of the company, because I don’t know if somebody might be offended.</p><p>Richard:<br> That’s cool. Subjectively, how do you know it was a great team?</p><p>James:<br> Subjectively, it’s really hard to say. It’s one of those things like, you know it when you see it, but it’s hard to describe. But I would say one of the things was that everybody got along really well. Some of the people on the team, I don’t know if this was true before they were members of the team or not, but some of the people in the team were friends, but they were also very welcoming to everybody else on the team to join them. And this is how I ended up with a set of Guitar Hero because we would occasionally go over to one of the team member’s houses and play Guitar Hero and so forth. Now that doesn’t mean that you need a team where everybody is interested in video games or ping pong or drinking or whatever the team activity is, but it wasn’t just that everybody got along, it’s that everybody was trying to bring the others into the group and not excluding anybody. They were really focused on creating a good result together, they cared about creating a good result. And subjectively the way I knew they were a good team as they stuck together longer than average, I think they stayed together until IBM bought them and killed them or killed the company even, I’m not sure.</p><p>Richard:<br> Just so listeners are clear on those, IBM did not kill the people on the team.</p><p>James:<br> I suppose. Yeah. Yeah. We should probably clarify that. To my knowledge most of them are still alive, yes. Yeah. So they stick together. So there’s another sort of subjective metric, but most of all, it’s the way it felt being on that team. And that’s, I think nearly impossible to describe.</p><p>Richard:<br> I love the way you’re talking about that, the way it felt. I’m also curious about curious about the, you mentioned the Tuckman model, you just mentioned something about, they stayed together longer than the average team. What do you think about this? What is the average team lifespan? How much longer was this team’s lifespan?</p><p>James:<br> Yeah, I don’t, that’s why it’s subjective because I don’t have numbers around it. But in software development people tend to hop jobs quite frequently. It’s rare to be in a job more than two to three years. And the folks on this team, they were still together when I went to visit them again, five years later.</p><p>Richard:<br> Wow.</p><p>James:<br> They had grown, but I think all or nearly all the people who were part of that core team are still there and still playing a leadership role.</p><p>Richard:<br> Yeah. All right. So that is unusual and special. And this is an objective thing, some sort of objective indicator that this was a special team.</p><p>James:<br> It is objective in a way, yeah.</p><p>Richard:<br> Are there any other objective signs that this was a really great team?</p><p>James:<br> I don’t have any concrete metrics. I’m not a big believer in metrics to begin with, which would be a whole nother conversation, but they tend to lead to dysfunction. But I would say that some objective measures or signs is that the team was very successful. I mean, they did grow. They grew into from one team to four or five teams. I think they had, I mean, I started out, there were five or six people on the team and when I went back to visit them again, five years later, I think they had 20, or maybe 30 people. They were acquired by IBM and their team developed product, this was a small product oriented software company. So their team, they were acquired by IBM on the strength of the product that they had built.</p><p>James:<br> And several of the team members, I still, I just gotten a bunch of them actually, coincidentally, all independently contacted me last year. So I’ve recently talked to a bunch of the people that were on that team, 10 years later and they’ve all disbanded, but they’ve gone on to become leaders in their community, leading software development meetups, and so forth and leaders in other organizations. And what they’re doing is they’re teaching people how to do what they did on that team. So I would suspect, I haven’t talked to them about this, but I suspect they are probably all regretting that that team no longer exists. Just as I regret my first team no longer exist.</p><p>Richard:<br> Exactly. And maybe they’re on this quest again to reproduce that, the specialness of that team.</p><p>James:<br> Yeah. Yeah. I mean, I think that’s one of the ways you can tell that you were really part of a great team as if 10 years later you find yourself thinking, man, I just want to create that team again.</p><p>Richard:<br> Yeah. I think we’ve discovered something right here. How do you know it was a great team, because we want to reproduce that.</p><p>James:<br> Yeah. Yeah.</p><p>Richard:<br> What were some of the concrete behaviors that this team engaged in that, that led to their success?</p><p>James:<br> One of the ones that I think was non-obvious was that they had a really good manager and that manager allowed the team to self-organize. Some managers sort of hold themselves apart or above the team and they’re there to tell the team what to do or to judge the team members and decide who’s deserving of what. And to a degree that is the job of a manager, but what this manager did was he really allowed the team to self-organize. He engaged as a member of the team, he wasn’t hands-off, he was a member of the team. He was focused on the product outcomes that the team working on. So he didn’t develop software with the team, although, and I don’t know if he had a software background or not, a software programmer background, but he was definitely a full-time member of the team, engaging full-time with a team, thinking about where’s this product going and what do we want out of it? But he did that as a peer. And he did that as somebody who respected what the team was creating in terms of their team dynamics. So that’s one.</p><p>James:<br> Another one was that the team members really took ownership of their process, so the way they worked, and the outcomes, the success. Again, now they didn’t necessarily have the domain expertise that the manager did, but they really cared about creating a good result. And they were all dedicated to working together to create that result. And I think that’s one of the things you see from a really solid team is they’re not a bunch of people working in vicinity all on their own projects, they were working on one thing together.</p><p>James:<br> And then the third thing is, and this is maybe a little egotistical of me, but I came in with all these disruptive, extreme programming ideas, not only were they disruptive ideas, they had a silly, stupid name and they agreed to try them and withhold judgment for six months, which is something I always ask the teams that I’m going to work with in this sort of immersive way. So they agreed to do this and they did it without a lot of, if we must or what I see with some other teams, as they say yes, when they cross their fingers behind their back and the next six months is pulling teeth to get them to actually try it. Now, they said, “Yeah, we want to experiment with this. It’s a little out there. It’s a little weird. We don’t know if it’s going to work and yeah, let’s do it.” And then they really did. And that sort of, when earlier you asked me what is one word? And I said, open-mindedness, and I think that wasn’t the only reason for their success, but it was really a reflection of what made them successful, may not have been caused it, but it was certainly correlated.</p><p>Richard:<br> All right. Now you’ve been on this quest to reproduce this best team that you were a member of from way back, your first extreme programming team. I’ve been on the same quest with similar experience, an extreme programming team. What do you think listeners could do? What’s your advice to listeners to reproduce the success of this team or any of the excellent teams you’ve been on in your life?</p><p>James:<br> Yeah, that’s a good question. It’s funny that you said that you had been on a similar quest and your first and that experience was an extreme programming team. So somewhat tongue in cheek, maybe the answer is everybody just needs to do extreme programming.</p><p>Richard:<br> Everybody has to go back in time to 20 years ago and do extreme programming.</p><p>James:<br> Yeah. And you got to get the nineties haircuts and the surf boards.</p><p>Richard:<br> All right, mullets and the white extreme programming book.</p><p>James:<br> Yeah, that’s right. More seriously, although it’s funny, I talked to people who were involved in that early XP movement, and I hear a lot of people saying, “Wow, that was a great experience.” So maybe there’s something to that.</p><p>James:<br> But if I were to separate it from the specifics of software development, I would say that if you want to reproduce that success, first thing I would do is I would pay attention to team dynamics and specifically what people in the biz call psychological safety. So make sure that everyone is safe to express their opinion, but not only that, to also experiment and to fail, because if it’s not safe to fail, it’s not safe to experiment. If it’s not safe to experiment, you can’t make things better because you can’t make things better by only doing sure things, you can make things, or at least you can’t make things great. I imagine you can make it better, but you can’t be great if you’re not willing to experiment and try new things and fail. And if it’s not safe to fail, then it’s not going to happen.</p><p>James:<br> And I think that’s one of the things that the manager on this team was really good at. Like I said, he was part of the team, not over the team and he made it safe for people to take ownership. And as you’re doing this, if I’m laying down advice from upon high, as you’re doing this pay particular attention to making it safe for people with non-traditional backgrounds. So people who have different demographics or went through a different college or non-college experience, or some of the great programmers have music degrees and or history degrees or psychology degrees. Or most of the programmers sadly are white males, so you might have people on your team who aren’t white males. Those folks are going to have, likely are going to have different experiences, whether it’s educational or demographic and what is makes it safe to fail for people who are, don’t have a common experience with the rest of the team is different than what’s makes it safe to fail for the people who are sort of in the mainstream of the team’s experience.</p><p>Richard:<br> Right. All right. Thanks for that.</p><p>James:<br> And I did have another one.</p><p>Richard:<br> Okay.</p><p>James:<br> Another one was, and I think this does sort of get back to the XP ideas, whatever industry you’re in, prioritize learning, skill and ease. This team on the East Coast that I worked with, they set aside half a day for research every week where people could work on anything they wanted, as long as they were going to be able to present on it the next day at lunch and it wasn’t anything related to their day job or not anything related to the production work. So typically people would do coding research, but it could not be checked in, it couldn’t be part of the software that was being built.</p><p>James:<br> And they also worked really hard on their software fundamentals. And this is what I came to help them with, software fundamentals are things like if you’re in software test driven development, evolutionary design, communicating through code, they really worked on being very skillful in those areas. And in software these days, if you want to get a job in software, you have to go study something called Leet Code and do all these puzzles, these coding puzzles, but that’s not what this team was good at. They were really good at the fundamentals of communicating well, not the puzzles that people do to get hired. And I think learning and skill are two of the things that any team needs in order to be really great.</p><p>James:<br> And then third is ease. They were constantly looking at how could they improve the way they worked as a team to reduce overhead, to make the things that were important less friction to do and less time spent on what folks in software call yak shaving. That’s where, when you want a blanket, but you realize that you’ve loaned it out to somebody and now you’ve got to do this, now you got to do that and next thing you know, you’re in Cambodia, shaving a yak, trying to get yak hair to get your blanket. Reducing that sort of friction is also something that I would recommend for anybody trying to create a great team. So the team can focus, the team really focuses on reducing that friction so they can spend the majority of their time doing what matters.</p><p>Richard:<br> Beautiful advice. Is there anything else you’d like to add, James? Anything you’re passionate about lately? Anything you’re working on lately? Anything at all?</p><p>James:<br> No, I don’t think so. Other than maybe a little bit of shameless self promotion, which is that I love doing this sort of work. I just love working with teams. I love helping companies figure out how to solve the problems that are preventing their teams from growing and being more successful. And I tend to work with the smaller companies and it’s rare to get the opportunity to really embed with a team. So if anybody’s listening to this and would like that, I would love working with you because it’s just so much fun.</p><p>Richard:<br> All right. And I can tell, I have an objective or subjective, I don’t know which point it is, way to gauge that you really love this. As we talk to each other, I have this sort of like feeling in my belly that I just am enjoying this conversation so much that just because of the passion that I can feel sort of coming through the screen as we talk to each other. And if listeners would like to get in touch with you, maybe take you up on that. How would they do that?</p><p>James:<br> My website, world’s ugliest website is Jamesshore.com. You can tell a programmer built it. And I guess I’ve just been lucky enough to have been too busy to make any changes for it. So Jamesshore.com will, there’s a contact me link, you can find out more information. Or if you want to email me directly, it’s Jshore@Jamesshore.com. I only work with software teams. If you’re in the software world and you’re not necessarily ready to take the leap of contacting me directly, but you’re interested in some of what I’ve learned from building software, check out the agile fluency project at agilefluency.org and all kinds of insights there that Diana and I came up with about how software teams tend to grow and change over time that I think you might find pretty useful and interesting.</p><p>Richard:<br> Definitely. I’ll second that I love the work of the agile fluency project. Thank you for sharing that with the world chance.</p><p>James:<br> My pleasure.</p><p>Richard:<br> All right, James Shore, thank you so much for joining us today. It’s been a lot of fun for me.</p><p>James:<br> Yeah. It’s been an absolute pleasure. Thanks for having me on.</p><p>Richard:<br> Hi friends. Thanks again for listening. And remember to support this podcast, visit my website kasperowski.com.</p><p><em>Join the community of high performers — </em><a href="https://kasperowski.com/?utm_source=medium.com&amp;utm_medium=blog&amp;utm_campaign=good-feedback"><em>subscribe to Richard’s newsletter</em></a><em> today.</em></p><p><em>Originally published at </em><a href="https://kasperowski.com/podcast-58-james-shore/"><em>kasperowski.com</em></a><em> on January 26, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f67194b55a76" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wicked Problems, Wicked Opportunities: Mindset and Perspective]]></title>
            <link>https://rkasper.medium.com/wicked-problems-wicked-opportunities-mindset-and-perspective-cef90f3730b8?source=rss-8de0ae241122------2</link>
            <guid isPermaLink="false">https://medium.com/p/cef90f3730b8</guid>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[work-from-home]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Richard Kasperowski]]></dc:creator>
            <pubDate>Fri, 16 Oct 2020 18:24:38 GMT</pubDate>
            <atom:updated>2020-10-16T18:24:38.711Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.linkedin.com/in/joanne-stone/">Joanne Stone</a> and I recently had a great conversation about wicked problems. I love the word wicked. <a href="https://www.merriam-webster.com/words-at-play/wicked-adverb-intensifier-usage">It’s a wonderfully positive word in my native New England vernacular.</a> We use it to amplify or express the superlative of an idea: a wicked good movie, wicked awesome lobster dinner, a wicked nice day at the beach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*Noc-b4AnkbXIJ2PnnmZSVQ.jpeg" /></figure><p>The idea of a <a href="https://en.wikipedia.org/wiki/Wicked_problem">wicked problem</a> comes from the realm of social planning in the 1960s. It describes any problem that is too complex to just solve — where there are innumerable challenges, there’s no obvious end-point, there are incomplete data or contradictory or changing circumstances. In this sense, the word wicked means neither evil (its usual meaning) nor awesome, the way I use it. It means resistant to resolution, and it embraces the idea of a problem that is extreme and huge, practically unsolvable.</p><p>Joanna asked, “What’s the most wicked problem you can think of?” My answer: the <a href="https://www.developgoodhabits.com/fixed-mindset-vs-growth-mindset/#:~:text=In%20a%20fixed%20mindset%2C%20people,and%20effort%20is%20not%20required.">fixed mindset</a> that seems to be driving so much of the <a href="https://pcl.stanford.edu/research/2015/iyengar-ajps-group-polarization.pdf">fear and polarized thinking that’s damaging the world today</a>. And my wicked big question toward a solution: how can we cultivate <a href="https://hbr.org/2016/01/what-having-a-growth-mindset-actually-means">growth mindset</a> in all people?</p><h3>Fixed by fear</h3><p>This certainly meets the criteria of a wicked problem. There are multiple factors, there’s no yes/no answer, and there are many ways of expressing and defining the problem. I’ve been mulling this over since the pre-COVID era (remember back then?). Fixed thinking manifests in a lack of personal mobility and choice, driven by fear: fear of the unknown, the distant, the “other.”</p><p>For example, why do people who live in economically depressed areas stay there? Why do they suffer? Why don’t they just learn a new trade or move somewhere else where they can find a decent job? I get it that they were born there, that they feel strong ties to the place, but it’s so easy nowadays to move somewhere else and get a job. Or to retrain yourself, to <a href="https://www.khanacademy.org/">learn something new</a>, or to find a job that lets you work remotely. We’ve never had so many choices. Why are there people who get stuck in <a href="https://en.wikipedia.org/wiki/Victim_mentality#:~:text=Victim%20mentality%20is%20an%20acquired,contrary%20evidence%20of%20such%20circumstances.">victim mentality</a> or stick with a dying profession that doesn’t make economic sense anymore? Their grandparents or great-grandparents moved to that place back when the factory opened — their ancestors were growth mindset pioneers, willing to move to wherever there was work, ready to discover new places and learn new skills. How and when did the grandchildren and great-grandchildren lose that spirit? Why don’t they move and seek job opportunities someplace else, now that the town is closing down?</p><p>This closed mindset also blinds people to <a href="https://www.library.uwa.edu.au/__data/assets/pdf_file/0006/989007/Thinking_Science_paper_in_SCIOS_.pdf">evidence-based thinking</a> about things like <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7151371/">pandemic control</a> or the ability to do any meaningful kind of risk assessment. For some of us, our minds get shut down by fear of the unknown — for example, <a href="https://www.vox.com/science-and-health/2017/1/28/14425658/fear-of-refugees-explained">fear of immigrants</a> — even though our great-grandparents probably were immigrants (mine were!). Today’s immigrants, who successfully moved themselves and their families out of terrible danger and hardship, represent <a href="https://hbr.org/2016/10/why-are-immigrants-more-entrepreneurial">some of the most enterprising, creative, and determined people in the world</a>. But instead of their new homeland embracing what they bring to it, these people are too often shunned and rejected instead.</p><h3>Embracing change for growth</h3><p>We see more growth mindedness in people who have made deliberate changes in their life, like moving to a new area or being in a relationship with someone from a different culture. That’s a chicken-and-egg issue and another wicked problem in itself: do people with a growth mindset seek out a more diverse and enriching set of life experiences, or does that exposure unlock the potential for growth mindset?</p><p>By definition, wicked problems don’t have easy answers. But for me, there’s a great deal of hope in education. I wish we could get important stuff like <a href="https://amzn.to/2Icd6tH">emotional intelligence, critical thinking, and growth mindset classes into children’s school curriculum</a>. It should be standard for kids to grow up thinking like this, with curiosity and enthusiasm about the world and their future. Our <a href="https://mashable.com/article/how-to-burst-social-media-filter-bubble-election/#:~:text=Realize%20you&#39;re%20in%20a,re%20curating%20our%20own%20feeds.">social media bubbles</a> are reinforcing our fixed mindsets; we need to learn that we have agency, that we are in control of our personal outcomes before fixed mindset manifests.</p><p>If we could just make all learning more self-directed, more rewarding, more joyful… Surely people would see the connection between effort and growth and the satisfaction they bring, whether it’s getting better at math, mastering a musical instrument, learning a new trade, or whatever you’re motivated to find a path in.</p><p>This approach is what I love about <a href="https://en.wikipedia.org/wiki/Agile_software_development">agile software development</a> and creative work in general. It’s a contrast to the <a href="https://www.investopedia.com/terms/s/scarcity.asp#:~:text=Scarcity%20refers%20to%20the%20basic,many%20additional%20wants%20as%20possible.">scarcity economics</a> management model from the industrial era. In the industrial age, scarcity thinking made sense: if I had a ton of coal and a ton of iron, then you didn’t have those same raw materials, and my company would make steel and yours couldn’t — my company would win. But in creative intellectual problem-solving work, <a href="https://en.wikipedia.org/wiki/Post-scarcity_economy">abundance thinking</a> is more apt: if I have a good idea, it doesn’t prevent you from also having a good idea. There’s an abundance of good creative ideas — in fact, the more ideas, the better! We’re better off when we encourage each other and share with each other.</p><p>This growth mindset abundance thinking is a long way from the small town in western Massachusetts, where I grew up. It was safe, for sure — as long as you were one of us: white, Christian, English-speaking. My mind shifted and opened when I moved to Boston, a much more global, open, and creative city, to study, participate in big-city arts and culture, and work in tech companies. (Or did I move to Boston because I was more growth-mindset oriented? That chicken-egg question again…) I was suddenly surrounded by people who were different from me. They looked different; they thought differently; they challenged me and helped me grow. It was great!</p><h3>Protocols for change</h3><p>Perhaps my <a href="https://en.wikipedia.org/wiki/Commodore_VIC-20">childhood passion for playing with computers</a> led me to be more open and move on from smalltown thinking. Ultimately, it all led me down the road to <a href="https://thecoreprotocols.org/">the Core Protocols</a>, informing so much of my teaching today. The framework encourages <a href="https://thecoreprotocols.org/protocols/personalalignment.html">awareness of what we really want</a> and need, along with the ability to <a href="https://thecoreprotocols.org/protocols/askforhelp.html">ask for help</a> and continually grow and improve; the ability to <a href="https://thecoreprotocols.org/protocols/checkin.html">share what we’re feeling</a> and connect with others has an impact way beyond working as a team to build a wicked awesome product.</p><p>And don’t get me wrong, we still have limits on our abundance thinking, even in the world of software development. We still have problems with <a href="https://hbr.org/2020/05/diversity-and-inclusion-efforts-that-really-work">diversity and inclusion</a>. Some of us excuse ourselves from the issue by saying, “there aren’t enough qualified women / black people / etc. in the pipeline — that’s just how it is.” Well, that’s simply unacceptable. The pipeline that we have is the pipeline we created. To change it, all we have to do is notice that there are wicked smart people who aren’t white dudes, that <a href="https://www.theguardian.com/lifeandstyle/2016/dec/08/gendered-toys-deter-girls-from-career-engineering-technology">technology-based toys aren’t just for boys</a>, that if we want more amazing people in the world to have the same opportunities as us, it’s up to us to make that happen.</p><p>For example, at <a href="https://cacm.acm.org/magazines/2019/2/234346-how-computer-science-at-cmu-is-attracting-and-retaining-women/fulltext">Carnegie Mellon University, they made a strategic decision to remove coding experience as a prerequisite for first-year students entering the Computer Science program</a>. They realized that they were excluding women and people who weren’t rich enough to have easy access to computers when they were growing up. They also hired amazing CS teachers who aren’t white dudes, giving students more diverse role models and showing them that all kinds of people are welcome in the program. The result: more than 50% of CS graduates at CMU are women — and you can bet that anyone coming out that program isn’t afraid of learning new things in the future too.</p><p>One of my small contributions is that I help run and mentor at a <a href="http://charlesrivercoderdojo.org/">CoderDojo for kids</a>. I subtly embed a bit of critical thinking and growth mindset into their lives alongside the technical learning, encouraging a creative and co-operative approach to finding solutions together. We make sure the kids aren’t all boys, aren’t all white, aren’t all rich. We actively seek mentors who aren’t white dudes. We model inclusivity and enjoy the benefits of fresh perspectives and inputs. (I also like to program and mentor diverse groups of speakers at conferences and <a href="https://agilenewengland.org/">event series</a>. It’s so easy to make small contributions like this!)</p><p>But by definition, I can’t solve wicked problems on my own, and neither can you. We have to work together, each person bringing what we can to the issues in front of us. We have to chip away at the calcified thinking and the structural inequalities. We have to destroy the belief that things can never be different.</p><p>Because things can be different. We can grow, we can change, we can fulfill our potential — and change the world.</p><p>What are you doing to change, cultivate growth mindset in the people you influence, and make our world better?</p><p>he tools are there. The protocols are there. As a result, we’re pulling through it together.</p><p><em>Join the community of high performers — </em><a href="https://kasperowski.com/?utm_source=medium.com&amp;utm_medium=blog&amp;utm_campaign=good-feedback"><em>subscribe to Richard’s news letter</em></a><em> today.</em></p><p><em>Originally published at </em><a href="https://kasperowski.com/intentional-about-meetings/?utm_source=medium.com&amp;utm_medium=blog&amp;utm_campaign=good-feedback"><em>kasperowski.com</em></a><em> on October 13, 2020</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cef90f3730b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Collaborate Better and Save the World]]></title>
            <link>https://rkasper.medium.com/collaborate-better-and-save-the-world-11eccf3c65b2?source=rss-8de0ae241122------2</link>
            <guid isPermaLink="false">https://medium.com/p/11eccf3c65b2</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[work-from-home]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Richard Kasperowski]]></dc:creator>
            <pubDate>Wed, 26 Aug 2020 18:30:42 GMT</pubDate>
            <atom:updated>2020-08-26T18:30:42.217Z</atom:updated>
            <content:encoded><![CDATA[<h3>Team Communication in Times of Crisis</h3><p>Once upon a time, a very long time ago — also known as “February 2020” — my personal and professional life consisted of being together and communicating with other people face to face.</p><p>I gave talks at conferences, business coaching sessions in my clients’ offices, and professional training in their classrooms and in universities. I traveled all around the United States, my home country, and around the world, working to bring teams together so that they could collaborate and perform at their best. I served them as a teacher and facilitator by going to where they were, physically drawing them into a room with each other, helping them create the magic that teams can achieve together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*kpbzGff8iZJV6zlF.jpg" /></figure><h3>1 week, &gt;40 hours face-to-face, 7373 miles</h3><p>The week of February 18, 2020, back in these olden times, was particularly hectic, I realize, as I look back at my calendar. I started with some on-site coaching with a client near Boston — Agile software development coaching, leadership consulting, and a hands-on software coding dojo. It was a busy day, but I wasn’t done yet: I had <a href="https://kasperowski.com/event/agileri/">a talk to deliver for a professional group in Providence, Rhode Island</a>, that night.</p><p>The next day I traveled to Seattle for an afternoon of agile training at the <a href="https://www.gatesfoundation.org/">Bill and Melinda Gates Foundation</a>. The day after that, I taught an all-day <a href="https://kasperowski.com/high-performance-teams/">High-Performance Team Building™ class</a> for the same group.</p><p>It was great working with the Foundation! They were collaborating with another consulting company to build a better website for their stakeholders — donors, medical researchers, healthcare workers, and so on.</p><p>At the time, they were planning for future projects, looking at problems they could solve in the world proactively, unaware of the impact the brewing global health crisis would have on the Foundation’s priorities and plans. And while it seems crazy now that I traveled 3000 miles to teach a class face to face, it was how I worked and what I did — indeed, it was what we all felt the project deserved, to help the new team gel around a vision of what they wanted to accomplish together. We were looking forward to creating something great.</p><p>I finished up that busy week in Arizona, with a day of <a href="https://kasperowski.com/agile-product-owner-skills/">Agile business skills training</a>, and a red-eye flight home to Boston. I traveled over 7,000 miles that week, in total, and while it was quite fragmented in terms of location, it wasn’t that unusual. I always want to give my best energy, attention, and focus to the clients I work with, which means being there with them, in their office, anywhere in the world.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*69Rge4Ks8m1vR0g1zY4ohA.jpeg" /></figure><h3>Getting into team flow together</h3><p>It also meant sharing that conviction with them and persuading people to get together in a room to collaborate face to face as the default. That if you care about the outcome of a project, if you’re creating something new and innovative, you need to look each other in the eye — literally in the eye, not through a webcam and a screen. The value this added was worth the costs and inconvenience of travel.</p><p>That buzz and synergy that gets you into that beautiful state of group flow only happen when you share physical space. You don’t need any special tools or technology or training. Just grab a pen and some post-its and a supply of good strong coffee. Get someone to orchestrate the conversation and shepherd it along, and collaboration just happens naturally.</p><p>It’s what we humans do best when we get aligned around a common goal: what we say or do inspires others’ thoughts and remarks. The creativity wells up. Each person builds on the others’ ideas. With a little intentionality in team behavior, like assuming positive intent and communicating respectfully, each person’s ideas amplify everyone else’s.</p><p>It wasn’t that I thought and taught that this could not take place remotely. It was just that being separated inevitably introduced friction and barriers to the flow of the process. I’d seen too many remote teams become disconnected in terms of mood and emotion, or find their activities limited by poor choices in remote collaboration tools. I’d never seen it done well. It was never a good alternative to face-to-face.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*JeGUT65fLTrDHRh0.jpg" /></figure><h3>The new normal</h3><p>But that was then. Not that long ago, but it feels like a lifetime.</p><p>Because right after that, everything changed for all of us. <a href="https://en.wikipedia.org/wiki/Coronavirus_disease_2019">COVID-19</a>. Every country and region in the world began shutting down, and eventually, we were all staying at home for the foreseeable future.</p><p>Everyone who could work from home was going to be doing so. We couldn’t collaborate face to face, even with our closest colleagues. Most of us didn’t know whether our job or business could be done that way — completely at home,</p><p>Many of us were afraid about the future of our careers, or more simply about our survival — fear of the virus itself. I grew up during the end of the Cold War with its dystopian dramas about nuclear war, fallout shelters, and nuclear winters. It was easy to start visualizing the virus as a threatening cloud of infection hanging in the air around us, silently spreading, lingering on surfaces, following us back into our homes if we allowed anything to penetrate our family safety bubbles.</p><p>As the world comes out of lockdown restrictions as unevenly as it went in, people are still afraid, still confused about what’s safe. The long-term mass psychological impact is yet to be seen. The world population is at risk of PTSD.</p><p>The COVID-19 health crisis made us all look at things differently, from new perspectives. We put aside petty squabbles. Families learned new ways of cooperating in close quarters. Neighborhoods rallied to support one another’s most vulnerable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*ul8Th4n-02ajasfB.jpg" /></figure><h3>A time that reframed everything we had thought was important</h3><p>Basic human fear and basic human connection: these primal sensations called into question so much of what many of us did for a living. Helping a marquee client’s team build a better website — was that even important right now?</p><p>Well, it turned out that it was important.</p><p>The work of organizations like the Gates Foundation has never mattered more to the future of the world. And getting back to normal, working, earning money, and putting food on the table are not abstractions; they are survival. After the initial shock, we all had to pick ourselves up and find new ways of doing things.</p><p>For me, that means some fundamental reflection and reframing of what collaboration means and how I teach it. Collaboration is more than what it looks like on the surface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*0bX9HprvD9q3x5lp.jpg" /></figure><h3>Keeping the world working and moving forward</h3><p>To understand the essence of great teamwork, and then to be able to share and evangelize the behaviors of great teams… It turns out that great teamwork is more about what we do, how we do it, and who we are — and not at all about where we do it.</p><p>And you know what? It worked. These teams — the ones I’ve been visiting in physical space, all around the continent and all around the world, helping them work together seamlessly in one physical place — actually functioned just fine as remote collaborators. We just needed to redefine and re-present a few things, facilitate things differently. We all got back to work.</p><p>How did that happen so smoothly for ours and so many other great teams? How did they so easily swing into action in new ways?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*FGCtirG6982sqtAG.jpg" /></figure><h3>Protocols</h3><p>We had protocols that we could apply. Protocols: clearly defined behaviors and patterns that ensure we communicate clearly and accomplish our goals together.</p><p>We knew what to do because we’d been doing it all along. We’d been practicing the behaviors and activities and ways to communicate as a team, to the point that we internalized and understood them. We’d developed and normed these methods of acting when things were calm, and we could draw upon them to serve us in our hour of need.</p><p>When you have protocols in place, everyone knows what to do. People feel safe. They can focus 100% on their role and their locus of responsibility because they trust the others around them to play their part.</p><p>You realize that the place — like that collaboration space at the office with all the whiteboards — is much less important than the interpersonal interactions. And you can hang on to those interaction protocols and use them to serve you when things get weird. They provide comfort and familiarity when everything else is falling apart.</p><p>Most of my work is with high-tech teams, but this works for all groups in all kinds of work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/0*oV8xDGQTCOzbWtJc.jpg" /></figure><h3>Watching a practiced team perform their protocols is a joy</h3><p>Many professions use strict protocols to manage their work, so that the things that matter get done flawlessly, regardless of external pressure and stress.</p><p>Emergency medical teams have admissions protocols for each patient: to triage patients, to figure out who each patient is, share medical history, update treatment records, and so on.</p><p>Emergency departments have protocols for each of the many different kinds of major incidents that might occur. They invoke these particular protocols when something apparently unexpected happens — like an airplane crashes. For situations where you can’t predict when the stressful situation might occur, but you know that it could, these protocols are mapped out and drilled in advance. When the heat is on, there’s no time to waste deciding who will do what, or in what order things need to happen. People just apply the behaviors they practiced and get on with responding.</p><p>Surgical teams are another kind of healthcare team where the stakes are high — literally life and death. They have such strict protocols for surgical operation rooms that a new surgery team can form at a moment’s notice. There’s no room for error. Everyone knows their role and the group procedures, and they collaborate flawlessly the first time they work together. They perform and deliver the expected result. And it’s the same in the military, in aircraft cockpits, and so many other workplaces.</p><p>Less life-threatening emergencies can be tackled the same way, such as a team fixing urgent software bugs when there’s a crisis in a live production system. When everyone on the team feels secure in their roles and tasks within the team and knows the process and framework for resolving the emergency together, they deliver solutions in record time.</p><p>Teams like this work effectively in times of high stress. That stress is muted by the familiarity of their practiced behaviors and the ways they interact with each other. It yields creativity and confidence.</p><p>It happens in international diplomacy, too — there are protocols for the behavior of representatives from various countries — like how to greet or interact with a head of state. Because the stakes are so high, you can’t risk having war break out because someone was over-friendly or misbehaved in any way.</p><p>(And a quick side note — here’s an example of a world leader not following protocol. <a href="https://www.nytimes.com/interactive/2019/11/02/us/politics/trump-twitter-presidency.html">Imagine the leader of a powerful country waking up in the morning and posting rambling tweets about whatever is on his mind, threatening and bullying people who disagree with him.</a> <a href="https://www.nytimes.com/2020/05/29/technology/trump-twitter-minneapolis-george-floyd.html">The result is chaos.</a>)</p><p>So we resort to ceremony, to ritual — to protocol. Not for its own sake, but because it is effective.</p><p>We even do it on our own when working solo. I used to practice martial artists — I’m a second-degree black belt in taekwondo. We drilled our moves over and over. We used the English word forms to describe these sequences of movements. Many people know the Japanese word, kata, for this type of intentional practice in martial arts. A kata is a sequence of moves performed in a controlled and systematic way, practiced over and over until your brain doesn’t have to think about the steps anymore. You build muscle memory. Your body just knows what to do. So when you’re under the stress of a sports competition or a real fight, your moves just come out, and you defend yourself successfully.</p><p><a href="https://www.jacoboapito.com/">My son</a> tells a story about defending himself against a bully in elementary school. His martial arts skills appeared like magic. He didn’t hurt the other kid, but no one ever bothered him again.</p><p>So that’s the power of protocols: they let you transfer skills from the learning environment — in this case, a martial arts dojo — to wherever you need to use them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/0*cjsfr7ytgvhZ1_Qz.jpg" /></figure><h3>Taking your protocols into new territory</h3><p>This year almost all of us knowledge workers had to do this to some extent. We had to decouple the things we do from their original environment and apply them in new ways.</p><p>For me, the challenge was enormous. No one was waving a knife at me, but for my training and consulting company and most creative intellectual business, the threats were on the horizon. Everything I did in terms of training, coaching, and facilitation was optimized for face-to-face interaction in physical space.</p><p>I had to change my behaviors. I had to strip my practices down to the bare bones of their protocols and work out their essence.</p><p>How could I help my clients continue learning, connecting, delivering joy and value to the customers and stakeholders who care about their work? How could we figure out the essence of the work — the protocols — and do it in non-physical space?</p><p>We did it, and you can do it, too. But first, you need to identify and practice the protocols. They are your secure foundation, your resilience against future upheaval. It’s never too late to start.</p><p>You already have some protocols. No, trust me, you do, even if you haven’t thought about them this way and labeled them with names. It’s the routine stuff you do without even noticing. Like a fish in the water — the fish doesn’t know there’s anything special about breathing water and swimming all day — you need to step outside of your work and observe it from afar. You have to flip your perspective a little bit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*3OG0KckJ2lmrcex5.jpg" /></figure><h3>Observe your team’s work from an outside perspective</h3><p>Don’t do it alone. <a href="https://thecoreprotocols.org/protocols/askforhelp">Ask for help</a>. Talk to your team. How do we do such-and-such? What happens when the so-and-so problem occurs? Perhaps you can even get an outsider, an independent observer, to watch you and help you nail it. (We call these independent outsiders “coaches,” and everyone should have one!) We so often internalize the most critical nuggets of our success behaviors and overlook them.</p><p>An outsider quietly observing the behaviors of successful teams — this is how <a href="https://thecoreprotocols.org/">the Core Protocols</a> were first developed, the protocols I use all the time in training and coaching high-performance teams. Jim and Michele McCarthy studied successful teams’ actions, encoding the success behaviors they observed as reproducible behavior protocols. The McCarthys didn’t intervene in the activities of the groups they studied — that would have influenced and changed the team behaviors they were observing. They just sat and watched. You can do the same kind of observational research with yourself, your teams, and your organization.</p><p>Once you have codified your protocols, then you can examine them, investigate them, respectfully, positively, and generatively, as a team. Ask yourselves: “Do we really need to do this? Yes, and this is why… What happens when we do X instead of Y, what is the outcome down the line?”</p><p>How could we still do that, if the environment or context changed overnight?</p><p>It’s a fantastic process. It will teach you so much about yourself and your team. It will let you celebrate and recognize what makes your team unique. It will connect you strongly. As a result, you’ll be both happier and more effective together.</p><p>You’ll know together what your success behaviors are. You’ll be able to practice them, review them, acknowledge them, improve them. Notice if you deviate from one of your success protocols — what happens? Revisit your protocol and see what’s going on. Has the situation changed? Did you get lazy? Or does the protocol need updating? Would this protocol still serve us if the context changed?</p><p>You probably know how it feels when your team is in perfect flow, when you’re working at your best together. Draw on your past experiences, the times you’ve collaborated, gotten stuff done, and how amazing it felt.</p><p>Imagine being able to channel that feeling and that effectiveness, when things are at their worst, when the sky is falling, when the world is in crisis.</p><p>That’s why we practice the things that work, over and over, before a crisis. It’s because you don’t have time to learn new behaviors and routines when shit happens, you don’t even have time to think about it. You already have to know what to do.</p><p>I’ve learned a lot during these exciting times, including new ways to do things I’d been doing for years.</p><p>I learned that the Core Protocols, as an operating system for high-performance teams, are truly universal and location-independent. The protocols for great teams are presence-independent: they work when you are face-to-face, and they work when you are continents apart.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*watZyN1vj8y22fFA.jpg" /></figure><h3>Checking in — glad, sad, mad, afraid</h3><p><a href="https://thecoreprotocols.org/protocols/checkin.html">Checking In</a> — sharing your emotions with your teammates — and <a href="https://thecoreprotocols.org/protocols/checkout.html">Checking Out</a> — letting your teammates know that you’re having trouble staying present with them — these two simple protocols transfer easily to remote work. The emotion check-in helps us establish our presence within the team and connect. It’s even more important in online space to be present and connected, to say that we’re here and share how we feel. It tees everyone up to be on the same page, to be present together, ready to be creative and effective, even if we’re thousands of miles apart in physical space.</p><p>These simple protocols make us strong. Having these shared practices bonds us together as a team.</p><p>From that strength comes greatness and resilience. A better Us. More creativity. More invention. More productivity. More joy. More humanity. We thrive through a crisis, and we come back better.</p><p>There’s a long way to go for the world to get well, grieve its losses, and recover economically and humanly. But history teaches us that after each crisis, whether it’s war or depression or pandemic, a wave of innovation and development follows, a boom of creativity and progress.</p><p>The things we learn when times are unbearably hard are the things that will help us surf this wave with style. They help us build resilience for the next “black swan” event.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*i12CTXcz_MpR4WAI.jpg" /></figure><h3>Collaboration will save the world</h3><p>With the same technologies and tools that I am using for online teaming, teaching, and coaching, the same way you are reading this right now, the brightest minds of the world are collaborating — across cultures, continents, and languages. A problem like this will never be solved by one person, one local collocated team, or one country or one government’s best brains.</p><p>Scientific communities are working together remotely, online, to develop vaccines, to find cures, to share data and learning, to pool their knowledge for the greater good. We’re collectively keeping supply lines open and feeding people the world over. We’re doing all this globally and without borders.</p><p>The tools are there. The protocols are there. As a result, we’re pulling through it together.</p><p><em>Join the community of high performers — </em><a href="https://kasperowski.com/?utm_source=medium.com&amp;utm_medium=blog&amp;utm_campaign=good-feedback"><em>subscribe to Richard’s news letter</em></a><em> today.</em></p><p><em>Originally published at </em><a href="https://kasperowski.com/intentional-about-meetings/?utm_source=medium.com&amp;utm_medium=blog&amp;utm_campaign=good-feedback"><em>kasperowski.com</em></a><em> on August 18, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11eccf3c65b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>