In this capstone project class, you analyze a real-world case provided by N2Growth, a global firm that helps clients create a culture of leadership through practice areas like strategy, cultural transformation and organizational design. Based on the N2Growth case, you are expected to identify and diagnose organizational issues, select a senior leader and make recommendations in a culminating PowerPoint or Prezi presentation.
Diagnosing Problems in Groups and Teams
Loading...
来自 University of Pennsylvania 的课程
Culture-Driven Team Building Capstone
4 个评分
从本节课中
Week 2
与讲师见面
Derek Newberry, Ph.D.Lecturer
Organizational Dynamics
Dr. Aviva LegattAffiliated Faculty
Organizational Dynamics
Welcome.
Welcome to our second module of our course on Continuous learning in teams.
I'm Dana Kaminstein in Organizational Dynamics here at
the University of Pennsylvania.
>> Hi, I'm Ramya, delighted to be here with you again today.
>> Thank you Dana and Ramya.
It's good to have you again with us.
This is Amrita Subramanian.
>> Hi, Alan Barstow,
also Organizational Dynamics here at the University of Pennsylvania.
Welcome.
>> In our first module, we covered framing, reframing, and systems thinking.
These are very important aspects of understanding teams and groups.
Today, we're going to focus in on diagnosis.
I'm sure all of you have been in groups or teams that got stuck, or
weren't working quite insufficiently or effectively as you wanted them to.
Today, we're going to focusing on how you understand what's going on,
which is the first step in terms of addressing those issues.
>> Yes, more often than not, we tend to think that we can bring
together a group of very successful, intelligent, creative people,
and voila, we have the perfect recipe for a high performing team.
It's not true most of the cases, is it?
And what if they are wonderful people, but they cannot work together as a team?
Why is it so very important to understand what's happening in teams?
And if the team is not firing on all cylinders, what could be happening?
How can we identify those?
That's a central theme of today's module.
Let me start off with an example.
I was once consulting with a team, a steering committee on an organizational
development initiative and I observed some very interesting patterns.
Every time this team met in person, they were very amicable, laughing, joking.
They were agreeable on most anything that was discussed during the meeting.
But later, they will send these emails to each other raising numerous issues and
concerns about what they discussed in the very same meeting.
Emails flew back and forth, emotions run high, work got delayed and
the next time when they meet, and that's the most interesting part,
none of these issues ever get raised.
It's all back to hunky-dory.
What then is happening in these teams?
What is going on?
>> It's very interesting.
So what is going on that makes me when I'm in front of you.
And then I send all my emotions over the email and
the consequence is that, the team is not happy for me.
Even though that, that doesn't take away from us how competent the team might be.
You know, this is, this is just a repeating pattern, so true.
For instance, a quick example that comes on top of my mind, is I went for
a coaching assignment, and
this is the first time a woman is getting promoted as a vice president.
It's largely male dominated.
Here's the scenario.
The boss is quitting in three months, he's retiring.
She's getting promoted in three months,
the team knows they will have a new boss in three months.
But they no know what to do about it.
So they're all waiting for something completely stuck and
I thought maybe this is a unique pattern.
But then I found out that this has always been the case in the company.
Always classic, this is how we are.
This is how we do things.
This is just the way we've always been.
>> So they keep repeating the same thing.
>> They keep repeating the same thing.
There is no reframing.
>> I see two things going on here and I know I've been in these meetings as well.
The first is the culture of politeness.
We're interfacing with each other face to face, we're going to be polite.
Learning and
dealing with real issues, that's sort of secondary to just being polite.
Being polite gets in the way of learning and
organizations often times, it's part of the culture.
When we do repeat these patterns, I'm also aware of the fact that
even when people do put issues out on the table, and explain their point of view,
or advocate their view, what others do is they turn away,
they're self absorbed in their own thoughts, they're thinking other things.
Yeah, they're sort of listening to you,
but they're not wanting to signal agreement or disagreement.
So you're sitting there wondering, well geez, have they heard me?
I'm going to say it again, and when I say it again, I tend to say it louder.
>> [LAUGH] >> And a little more exuberance,
try to make sure I get your attention.
And that's this pattern of just repeating, not breaking frame,
not stepping back, not taking some sort of a time out and
getting people to think about what's actually happening, sort of a diagnosis.
But just trying to push ahead and saying it louder or again.
I'll do it again and they'll get it this time.
That's pattern that we see in many, many groups.
>> And it's not just being polite that's a very good point,
but also sometimes what happens is there is no culture of dealing with conflicts.
So that could be one of the reasons, as well.
Either they don't want to confront each other in person and
publicly or they don't feel the need to confront each other.
Maybe it's an accountability issue.
Maybe they're just not comfortable dealing with conflicts.
>> So we're sure that you've run into similar issues in groups or
teams that you've been on.
Sometimes these problems can go around and around for weeks at a time.
And one of the things we want to work with you on is how to
interrupt that cycle, and figure out what's going on.
Ramya, I was particularly struck by the example you gave,
because often times, I've been on teams where, as you say,
things seem to be fine during the meeting and then everybody goes out to lunch and
complains for 3 hours about what didn't work.
This is particularly problematic, because you're taking what needs to
be discussed in the team outside of it, you're draining energy out of the team.
And your setting up a norm that we don't really discuss conflicts in here,
e discuss them over lunch or over a beer.
So that's one situation that we imagine you've run into as well.
We want to talk a little bit about how to begin
doing some diagnostic work in your team.
The first thing is to step back or pause and to
raise the question of what's going on here and try to identify what the issue is.
Maybe it's an issue of the team is having a hard time focusing and
they're getting off on tangents.
Maybe it's that the team only starts talking about the important issues
five minutes before the meeting is over, whatever it is.
Try to identify where the team is getting stuck.
And thirdly, collect a little data.
And that can be done simply by asking everybody on the team for
their thoughts about what's going on, what's working well, what isn't.
You can even take it to a slightly different level and
do a little anonymous survey if people aren't
comfortable talking in the open about what the issues are.
But it really helps to not just make assumptions and
to try to figure out how people are seeing what's happening.
>> That's very interesting, Dana,
because it's almost as if when I start doing a diagnosis.
I am figuring a way out of the stuckness.
So, you said three things, right?
First, is to recognize that something is not right, or
needs to be looked at differently, needs to be recognized differently, perhaps,
the goals we are attaining, or not attaining, or the way we are attaining.
You also mentioned that we have to sort of agree, what the problem is.
Different stakeholders at the table, I need to know, Alan, what's your view,
how do you understand it, Dana what do you see, and of course, collect data.
So when we are getting into this, and I was really,
really stuck about the pause button and I recall Alan, you and
I were talking about something a while back, say a little more about the pause.
>> Well I think there's a need for ground rules.
And when you're going to sort of say, stop, hold on a second, there almost
needs to be a trigger people recognize as that's what you're asking them to do.
So it's ground rules.
And we are usually so intent on our own view.
Advocating, making sure other people understand what we're saying.
Not so much about listening to other people's views,
as making sure they understand our own.
That we tend to be very focused.
>> Mm.
>> And to be able to step back >> And call sort of a time out, or
a pause is an important aspect of effective groups.
And it's one of the things that I think can help us reframe and refocus.
But it needs to be sort of a deliberate activity.
An agreed upon activity in a group.
>> So if I were to try doing that in tomorrow's meeting and
if you ever tried to do that, what would be the good way?
>> Well, I think you need to setup some groundrules before you do it.
When someone is in the situation.
Work teams in factories can stop the whole production line.
No one wants to do that, because there might be consequences.
But there's permission to do that.
The leader oftentimes, the senior person in the room, has to help
establish that that's an effective and acceptable practice in the team.
>> Effective.
Well that's a perfect segue, Allen, to the next thing that we are about to see.
Just like the last module, in this module you're going to meet a group of
actors who are going to play out a scenario for you.
So watch it.
Have your notes and pens ready, and
this emphasizes, what you heard all of us talk about.
So you're going to see a team that is completely stuck.
Really, really stuck, and they're not getting anywhere.
And you will sense that.
As you watch it, notice what you do watch.
Notice what they say.
And, of course, make a lot of notes.
We'll be doing the same.
We're now going to turn it over to Quinn.
Our narrator to take us to that scene.
