Most team friction isn't about the work - it's about unspoken expectations around how people work together. In this Scrap Yard episode, Diane and Erich dig into two habits that separate high-performing teams from ones that just get by: understanding how your teammates like to receive (and offer) help, and knowing how to give and receive feedback that actually lands. When those two things click, teams stop losing energy to misread signals and start building the kind of trust that makes everything else move faster. Whether you're leading a sprint team or running a nonprofit program, these aren't soft skills - they're the infrastructure your team runs on. Evolving your work, accelerating your impact
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
SPEAKER_00Things look a little bit different around here today, don't they? Indeed they do. It's just me. Well, and our dog, Ollie, has joined us today, but yeah, my co-host Eric isn't joining us for this one. Don't worry, he still loves y'all, and he's gonna be here talking about agile ways of working with me next time. But this is a topic that I'm super passionate about, and uh yeah, talking about feedback actually involves some stories that are a whole bunch easier to talk about, I think, sometimes when you're by yourself.
SPEAKER_00Hey, and welcome back to Agile Driven Impact. So let's dig in. Here's what I want you to think about. What it looks like when there's two teammates who genuinely want to help each other. One who probably is ready to jump in and solve a problem, the other who just wants to be given a little bit of space to try and figure something out on their own. Hear how those don't sound the same? Yeah, that probably means that both walk away a little bit frustrated. Okay, so that's about offering help.
SPEAKER_00What about feedback? Asking for feedback, giving feedback, receiving feedback. Something similar could happen. Someone could give feedback that they think is candid and helpful, the other person might shut right down. Not because the feedback was wrong, but because of how it was landed. So the reality is that when we think about teams and how to create these awesome high-performing teams in any workplace setting, for-profit, nonprofit, volunteer-driven, doesn't matter, most teams assume that everyone gives and receives help and feedback the same way that they do personally.
SPEAKER_00The reality is they don't. So today we're gonna look at some simple skills that help high-performing teams build this agreement, this understanding amongst each other early, knowing how to help each other, knowing how to give each other feedback, that's really gonna help move the needle. So when we think about expectations related to how people work together, if people feel that they're being helped or tried to have help provided to them in the wrong way, even when the intent is good, it's likely that they're gonna disengage.
SPEAKER_00Maybe you've been in that situation yourself. Today is not just about learning how to work with other people. Spoiler alert, it's gonna involve some self-reflection. So if you're driving, don't grab something to write down with. Just think about these items. But if you're sitting somewhere or have a piece of paper handy, it might be helpful to jot down some notes for what your answers are to some of these questions. So when we think about how people are engaging or maybe disengaging related to receiving help, offering help, giving feedback, receiving feedback, these are unfortunately common points of conflict in teams.
SPEAKER_00So let's be clear. When I talk about trying to have agreement or understanding about what this might look like, it's not that we're trying to create a team environment that is totally conflict-free. That feels like too much of a pie in the sky type moment. The reality is high-performing teams, I'm not saying that they're conflict-free. Rather, they're teams that know each other well enough that they can work through it. So when we're thinking in a team setting, uh it might be people feeling comfortable to say something like, you know, that's not how I'm gonna work best, or that's not how I receive feedback in the best way.
SPEAKER_00So it's gonna be about creating a psychologically safe space to share how you like to offer help, how you like to receive help, how you like to offer feedback, how you like to receive feedback. It's not a mandate, it's not the only way it will happen. It's not that everyone will always remember your preferences, but having the answers and a little bit of deeper understanding about your team members on this topic, how to give and receive help, how to give and receive feedback, we feel pretty confident that that's gonna help make your team even stronger than it is today.
SPEAKER_00So here's the question I want you to think about for yourself. When you're stuck on whatever the project might be, what does helpful actually look like for you? Yeah, I'm guessing that there's a slightly nuanced, different answer for each and every one of you today. But if I were to, I'm gonna create some buckets, let's say two broad buckets, in fact. So a lot of you probably thought, oh, I really want somebody who's gonna think through the problem with me.
SPEAKER_00And on the other hand, that second bucket might be more like, give me a little bit of space, and then I might want like for you to be uh a thoughtful ear, a sounding board, someone that can maybe I can bounce some ideas off of it after maybe I've tried something. Both of those are great. Neither's right, neither's wrong. But the well-meaning mistake that many team members, unfortunately, will make is that they might jump right in with a solution when what their colleague really needs is a collaborator.
SPEAKER_00Or they might be hovering a little too close in the office or digitally, uh, maybe in the chat channel, when what someone really needs is just a moment to kind of work it out on their own. So, how do we learn which one really fits for our team? So there's some questions that you might ask. In fact, the team working agreement, if that's something that your team utilizes, might be a spot where you might be able to ask questions like this, when it's not in the moment needing help or wanting to offer help, but rather at a neutral time.
SPEAKER_00To find out from your colleagues, something like, hey, uh, if you're struggling with something, do you want me to jump in or do you prefer that I wait to be asked? Hearing everyone on the team, hearing their answer, if they're willing to share. Maybe in fact, you give them a little bit of notice that you're going to ask the questions so that they don't feel like they've been put on the spot. But understanding that, maybe even documenting those preferences in the team working agreement so that folks remember that. It's a lot to remember all your team members' preferences.
SPEAKER_00But that might be some way that would make it more than a one-time quick conversation, but rather can become a habit of understanding just a little bit deeper your team members' preferences. And I'm talking about this in a way that, yeah, it works in all settings, whether we're talking about an engineering team, whether we're talking about a software team, whether we're talking about a development team in a nonprofit organization, a group of boards of directors for nonprofits, it doesn't matter. All teams could follow exactly the same idea.
SPEAKER_00This is industry agnostic, folks. So there's how your teammates like to receive help. But you should also be thinking about you, right? Then I first asked you that question when you're stuck, what does helpful actually look like for you? So that's one side of the equation. Now we need to think about what it's gonna feel like and how it's gonna interact when, well, you're the one that needs help and your colleague wants to give help.
SPEAKER_00Or you're the one offering help and your colleague needs help. So as we think about what that's gonna be like, there's what your natural style was, what you want to have happen for you. But there's three common ways that people are gonna offer help. And we've got fun little titles for what they might be. So the first one, the fixer. Somebody that's gonna dive right in, take over. They're like, I can help you with this, let's get this done. The second one is the coach, someone who's gonna ask uh curious, not judgmental questions, won't give clear, directive answers, but try to help someone see what an answer might be that's best for them.
SPEAKER_00The helper, the person who needs the help, I should say, not the person who's asking the questions. And then third, the supporter. Someone who's gonna focus first on validating how somebody's feeling, and second, on trying to solve a problem. So the fixer, the coach, and the supporter. Now here's where we've got to talk about my awesome co-host Eric. Uh, we don't have the same styles for how we offer help. Some of you might know us personally and might have a feeling that you could guess which is his style and which is my style.
SPEAKER_00Doesn't matter if you get that right or not. What's important is to know that they are not the same. And we've been married for more than 23 years. You would think that we would know this difference, and we do, but sometimes it could lead to conflict when we forget what each other's styles are. So I am a fixer. Yep, I want it. All right, we can get that done. I've got ideas, I know people, I can make a phone call, we can fix it.
SPEAKER_00That is my natural inclination for how I'm gonna offer help. I'm not saying that's the only way I offer help, but that is my go-to path. Eric, on the other hand, you probably guessed, yeah, he's a coach. He wants to ask thoughtful questions. He wants to try and see what different options might get you excited, what feels like maybe the path of least resistance. Coach all the way through. Maybe with a side of supporter. Not the same, not at all the same.
SPEAKER_00But they can be really great superpowers to have different people in a team that offer help in different ways. But if we forget, which sometimes we might, whether it be about a work-related thing or something related to just what's happening in the family or in the household, if we forget that we have different styles for how we offer help, conflict could ensue. And none of these help offering styles are universally right.
SPEAKER_00None of them are close to wrong. No, not even at all. They're all amazing and can be exactly what somebody might need. But we have to remember in a team setting that the mismatch between how someone offers help and some how someone wants to receive it, that's where the friction can lie in teams. So the more that we can have our team members give a name to or give some verbal description about their natural help style, the smoother the road should be, not always, not guaranteed, but should be for our team.
SPEAKER_00So something like having a team member say, well, okay, I'll just make it about me, right? I might say, I tend to jump in with solutions, with ways to fix things. Be sure to let me know if you'd rather I ask questions first. So I'm empowering the person to consider something different. I'm also flagging my natural tendency. There's a lot of other ways you could try and wordsmith that as you're sharing. But what you're trying to develop is the uh ability in the team to self-regulate. So if we each recognize our own instincts, great.
SPEAKER_00That makes us aware of how sometimes that might not be right. And if we know our colleagues' preferences, that gives us the opportunity to support them and to work with them in a way that uh is gonna be best for their preferences. Hopefully, combined those two levels of awareness in the team members, the person who needs help and the person who wants to give help, hopefully that's gonna bring about some fantastic impact in whatever the work is that you're trying to do together. So, help, asking and giving, is one part of the equation for how we work together, regardless of our industry, that's gonna make our teams better and stronger if we're transparent about it and can self-regulate.
SPEAKER_00The second is about giving and receiving feedback. Now, giving and receiving feedback as a topic, this is one of the most highly requested and highly attended uh webinar topics that I've been looking at this last year as I've been writing my book, Playbook for Changemakers. This has been a hot topic. And it's not that it's anything new, it's that it's something that I think a lot of us realize is constantly a work in progress, especially because it seems like there are more tools and tech that can help us with feedback and require more human-in-the-loop interaction related to feedback.
SPEAKER_00Uh, but that's just my working theory. But it is, it's an entire chapter in Playbook for Changemakers when it comes out in December. So super excited about this particular part of today's episode. And so if we think about giving and receiving feedback, well, we've got the same problem as with giving or asking for help. We could have really different personal preferences that might, if we're not careful, cause friction in our team. So there are three things that can really help feedback land well and be productive.
SPEAKER_00I would say in any setting, but we're talking workplace teams today. So three things: timing, specificity, and knowing how the person receives it. So by timing, I mean that feedback uh that's given in a moment of stress, it's rarely gonna land well. Uh in my day-to-day life, uh, if I'm just quick grabbing a salad because I've got 15 minutes for lunch, that's not the time to give me feedback on anything because I'm like thinking about what I just finished and where I just am headed, but I'm also really focused on getting some good nutrition because I'm hungry after my workout from that morning.
SPEAKER_00So having instead someone say, like, hey, is now a good time? That always gives me the opportunity to say, actually, like, could we talk in two hours? Okay, I know I'm making it about me, but that's the only thing that seems fair in terms of transparency. But I'm sure that you have similar situations where you're like, oh, if someone asks me a question before I've had my first cup of coffee at my desk, not the right time. Or if someone asks me something 10 minutes before I'm getting ready to shut down for the day, not the right time.
SPEAKER_00So asking, is now a good time? It'll mean something different for each of us for why you might say yes or no. That's what timing's about. All right, specificity. Saying, oh, you did a great job. Hey, high five, gold stars, or saying, that didn't really seem to work. Useless. They're so generic we don't know really what happened, what was the positive or the space that needed improvement, what was the impact, what could have been better.
SPEAKER_00No. So we want to be really specific in the way that we provide our feedback. Uh, I like actually Kim Scott's book, Radical Candor, and the hip feedback framework that's included in there when I think about what it looks like to offer feedback, so it's not just about timing and how it lands, but when I think about the specificity part, uh I often refer back to the that hip feedback framework from Kim Scott and Radical Candor. But then the third part is knowing how they receive it. So some people they want direct feedback.
SPEAKER_00Don't sugarcoat it. Tell me what it is. Others want a little bit of some positive stuff, some rooms for improv areas for improvement, and then some more positive. They might say, but Diane, like the sandwich, even if it's something positive, well, then it's all positive, I guess, right? We've got a sandwich that is full of positive, but understanding the preferences for how people are going to receive it increases the chance that it's gonna be worth our time to share and potentially make our team stronger.
SPEAKER_00So if someone needs affirmation first before you provide the candid feedback on whatever the work product is, a new design idea for a product, a new application that was written for grant funding, doesn't matter what it is. If someone needs affirmation about the work before they hear what needs to be improved, not that it will always happen, but the awareness of team members and especially the awareness of leaders for those preferences increases the likelihood that the feedback will move the team as a whole forward.
SPEAKER_00So giving feedback, well, who's it really for? Right? Uh it people will say feedback is a gift, but we want to make sure that it's a gift that like the other person can open, wants to open, maybe we'd say. But if we're receiving feedback, you might be handed something that looks like a gift and you're like, I'm not real sure. I don't know if I want it, I don't like surprises. So receiving feedback, well, it's also a skill and one that once we have formed a team, it's rarely one that teams practice.
SPEAKER_00Uh, maybe individually you had some coaching on it, or maybe you worked on it in a different team setting. But the minute you're in a new team, different folks, different makeup, yep, it's a skill that we have to think about again because we have different people, different preferences. And part of what's so hard for folks, myself included, is separating the message itself from the delivery. When it's delivered, right? The timing of it. Uh, if I if I'm in the middle of that salad, please don't deliver feedback.
SPEAKER_00I've got to focus for what I've got for these 10-15 minutes. So the delivery really will impact what is probably really well-intentioned feedback. Uh, I'm not saying all feedback is valid, absolutely not. We need to know when we dismiss feedback as thank you for providing the feedback, I'll take it into consideration, and when we move on. So, you know, what we really are looking for is not just to understand the structure and how we want to give or receive feedback ourselves, but to help each other think about ways we can hear our well-intentioned colleagues.
SPEAKER_00Hopefully, not be too defensive, but rather maybe ask some clarifying questions. Something like, could you say a little bit more about what you mean? We want to try and normalize asking follow-up questions after we have received feedback, which means if we're giving feedback, we need to be ready that someone might ask some follow-up questions so that both sides make it more of a dialogue. This in itself can help normalize the act of feedback, help make it feel so like it's less of an attack, and again, rather something that's going to help move the entire team and our impact forward.
SPEAKER_00We're trying to build trust, we're trying to build psychological safety, and I know those feel like buzzwords, but whew. By asking about preferences related to feedback, giving and receiving feedback in advance, we we have that potential for the same overall team enhancement, the stronger high-performing teams, as one I just talked about, giving and receiving help. The reality is high-performing teams, they do not happen on accident. Nope, not at all.
SPEAKER_00So, what we want to think about is not that we're gonna have a perfect team. I mean, if you have one, amazing. I'm so happy for you, but usually that we're we're moving towards progress as a team together, being stronger and better together today than we were yesterday, tomorrow than we were one week ago. So, to help you do that, I've got our normal challenge structure. Yep, I know folks love our challenges that we put forward. And so today it's a two-parter because we talked about help and we talked about feedback.
SPEAKER_00So you are welcome to take both challenges. Or if you're more excited about the help part, take that challenge. If you're more excited about the feedback part, take that challenge. Feel? All right, here's the scoop. The challenge related to help. This week I would challenge you to please ask one teammate. At least one if you want to ask more than one. Yeah, I'll give you gold stars. That's fine, happy to do it. Uh, but at least one teammate, ask them, please, when you're stuck on something, what does helpful look like for you?
SPEAKER_00See what they say, see what you learn. Think about how you want to remember that. Are you gonna jot it down somewhere for yourself so that you can remember you took the time to ask, they took to the time to answer. Now, how are you gonna take that learning and remember it? All right, challenge part two on the feedback side. This is still about asking a colleague something. If you take on both challenges, it could be that you ask the same colleague both questions. If you want to split it up, also great, make it your own. I want you to ask one teammate what's one thing that I could do differently that would make it easier for you to give, to receive, to hear my feedback, to think about how we work together.
SPEAKER_00Wordsmith these questions as you want. You're not gonna solve everything. It's not gonna make for the perfect team tomorrow if you ask these questions, but you're gonna have started the conversation. You're gonna start a deeper understanding among team members about preferences related to giving and receiving help and giving and receiving feedback. And we think that's a pretty strong formula for making awesome, high-performing teams. All right, we got to give a shout out to our season two sponsor, Agile in Nonprofits, www.agileandonprofits.com.
SPEAKER_00Free templates and guides and trainings for mission-driven teams. Uh really grateful for their support. Now, don't forget to subscribe, to share, maybe share it with somebody that you know, a team leader who wants to focus on how to make their teams stronger together. Yeah, this might be exactly the episode for them. But uh, we'll be back next time. You'll see both of us here again, ready to talk with you about more agile ways of working. And so as you're thinking about these skills related to giving help, giving feedback, these aren't just soft skills.
SPEAKER_00I know that's what they sound like. That's what you I know that's what they get talked about a lot, but what they really are infrastructure that high performing teams are built on. So keep that one in mind. All right, thanks for joining us for this episode of Agile Driven Impact. Can't wait to see you next time.
Most teams only celebrate the finish line - a habit that is leaving your team behind. In this Pit Stop episode, Diane and Erich make the case for a small but powerful shift: celebrating ALL milestones (not just the big...
In this Co-pilot episode of Agile Driven Impact, hosts Diane and Erich are joined by Rob Hatch - executive coach, trusted advisor to CEOs and senior leaders, and author of Attention! and Success Frames - to challenge...
In this Pit Stop episode of Agile Driven Impact, hosts Diane and Erich tackle one of the most common challenges facing teams with big missions: you have an important goal, everyone is working hard, but nobody really...
In this Co-pilot episode of Agile Driven Impact, hosts Diane and Erich are joined by Dr. Jessica Crowley, Co-Founder of Agileon and Registered Scrum Trainer, to explore why making work visible isn't just a best practice...
Most teams treat the product backlog like a to-do list. JJ Sutherland, CEO of Scrum Inc. and co-author of Scrum: The Art of Doing Twice the Work in Half the Time, says it should be so much more. In this episode, JJ...