About Cheri Baker

  • Cheri Baker is the owner of Emergence Consulting LLC, an Organizational Development Consulting firm based near Seattle, WA.

Enlightened Events

Network with Cheri

  • Biznik - Business Networking

Notice

  • All rights reserved by Cheri Baker. Individual readers may print one copy of materials for personal (non-commercial) use.

Team Effectiveness

Five Followership Tips

I'm sitting at Uptown Espresso in Seattle catching a breath between meetings and playing catch up on my weekly blog posts.  Today I'm going to write on Followership, which is the flipside of Leadership.  In the situations when we are not the recognized leader in a situation, how can we contribute to the effectiveness of our teams?  Here are five quick tips to consider.

1.  Balance out the leader's strengths.   If you work for a highly directive leader, one way to balance their strengths would be to ask good questions and strive to create a balance of advocacy and inquiry in the group.  Or if your leader is a big picture thinker, you might contribute some of the detail-oriented bits that the team needs, to create a well rounded approach to issues.

2. Observe and learn.  Learning from your own mistakes and triumphs is powerful.  Learning from the mistakes and triumphs of others can be even better.  Rather than sitting and making judgments of the leader, use your follower time to make observations about the whole team.  "Whenever Jane says "As you all well know..." she shuts down the conversation" is one example observation.  Be a keen observer of human nature - an organizational anthropologist!

3. Boost your Leader Up.  Leading teams can be tough, so when you see your leader making a good point or trying to lead a necessary but difficult conversation, offer your support both verbally and with your body language.  "As much as I hate to have more meetings, Joe is right.  We really do need to figure this thing out.  I'll bring coffee."  Your validation isn't sucking up to your boss unless it is effusive or inappropriate.

4. Practice your Challenging Skills.  Challenging the group might include sentences that start "I'd like us to look at this from another angle..."  or "I think there is something we are overlooking...." or even "I'm worried that we're making a mistake."  When something is not going right in your eyes, you can still challenge the team as a non-leader, and doing this with style will take some practice.

5. Relax a little.  For those of you in leadership roles, it can be draining at times.  When you are in situations when you are a regular-ole-participant, kick your feet up a bit (at least mentally) and enjoy a brief respite from the demands of leadership.  Strive to be the employee that you would like to have on your team. 

I hope you enjoyed these tips.  More and more, the concept of leadership is being redefined from a specific "role" to a set of behaviors anyone can and should use.  Even when you are part of the pack, you still have a great deal to offer.

Do you have tips to add?  Leave a comment!

Better Teambuilding Through Metaphors: Part II

This post is an update on last week's post about using organizational metaphors to enhance teambuilding.  In that post, I was wondering if using the metaphor or "story" that an organization lives by in a teambuilding session would enhance the effectiveness of the learning.

I think the answer is yes.

Here is the situation.  I was preparing a series of team effectiveness sessions for a healthcare team, and I put the work in the context of healthcare.  For example:

Healthy teams vs Unhealthy teams
The "symptoms" of unhealthy teams vs. the root causes.
Good communications habits as the "lifestyle changes" to improve team health.

The non-healthcare language for these same topics would have been:

Setting the right environment for team effectiveness.
Assessing the effectiveness of your own team - and identifying root causes.
Understanding the habits that create an environment where team effectiveness can emerge.

The group seemed to really "get it" and to be pleased that the concepts were in the language they use every day.  I'm going to continue building on this idea - and I'm happy it has turned out well.   People like to learn in the language they use every day.  Using organizational/functional metaphors is one way to do this.

Neat-O eh?

The Surprising Power of Organizational Resilience

I'd like to open today's post with a quote from one of my favorite authors: Margaret Wheatley.  She says:

"In my own work I am always constantly and happily surprised by how impossible it is to extinguish the human spirit. People who had been given up for dead in their organizations, once conditions change and they feel welcomed back in, find new energy and become great innovators."

This quote represents a fundamental truth that I experience firsthand in my teambuilding work.  Inevitably teambuilding starts when someone is deeply concerned about the relationships within a team.  Often this begins as a series of problems.

"We don't communicate well."
"People simply don't care."
"People backstab each other"
"Everyone is afraid to speak up."

Like Meg Wheatley, I am also happily surprised by what I see in organizations.  Once people are put in a relatively safe space to talk, they tend to open up rather quickly and speak with great courage and compassion.  Employees who may have been "checked out" a few days ago suddenly speak up with new fervor about what matters to them.  Once people feel "welcomed back" so to speak, everything changes.  I've seen these transformations take six weeks or twenty minutes, but in all cases the result feels like a loosening of old bonds - a kind of freedom.

I tell you, dear readers, there are days when I honestly can't believe that I get paid to do this kind of work.  Walking into a room (and they are all different) full of strangers and seeing that lightbulb switch on when they realize that they are empowered to make things better - it just lights up my life.

I admire the everyday courage and kindness I see in organizations everywhere I go.  And while I tend to be an optimist when it comes to the human spirit, like Meg Wheatley, I find myself surprised over and over again.

It is a distinctly pleasant kind of surprise.  I don't mind it at all.

We're All In This Together: Strategies for Cross-Functional Cooperation

Team_responsibility_2_2A fair number of the phone calls I get have to do with cross-team cooperation.  In short, this means that accounting is focused on accounting's goals, and engineering is focused on engineering's goals, and production cares only about production.  This kind of shortsightedness is unfortunately common, but it is very fixable.

Personal development guru Tony Robbins likes to say "your focus determines your reality" and this is some of what is going on here.  When our departments focus on "their piece" and don't spend time looking at "the big picture" of the organization, it is easy for people to think that if their department is doing well then everything else is fine.

Here are a few concepts that I share with my clients when teams are not all pulling together:

The Importance of Shared Vision

For many people (I used to be one of them) this concept of "Shared Vision" sounds like fluffy bunny nonsense.  Most of us have been exposed to enough meaningless "vision statements"  that this whole notion of Vision makes us leery.  We don't need to be so apprehensive.  Shared Vision simply means that the leadership team (or perhaps an even wider circle of participants) has come together and crafted a shared sense of what the organization is, and where it is going.  Shared vision means that everyone has a similar sense of what the organization does, what the goals are, and how they can contribute to the big picture.

There are a lot of ways to build shared vision, and in general the more of the organization you involve, the more durable the vision is.  I like the Appreciative Inquiry approach because it involves not only leaders, but also employees, vendors, customers, etc.  Out of AI, a wide variety of stakeholders can become champions of the vision.  For organizations who either cannot or don't want to involve such a broad circle, there are a number of strategic planning approaches that can bring shared vision to life.

The Importance of Effective Teams

Many times, leadership teams come together regularly but they are not doing the right kinds of work to create organizational momentum.  Departments are siloed, or separate, and cooperation is limited to tactical problems.  ("I need accounting to pull some files for *my* project.") 

CEOs or Leaders who are caught up in their own importance can exacerbate this problem.  I've been in staff meetings where CEOs lecture the team and where sharing information results in "getting in trouble."  I've also been in staff meetings where the CEO acts like the font of all knowledge, and the executives swarm around him or her like curious children asking "what do you think about this."  and "what is your opinion on this." and "how should we handle that."   Neither role (speech maker or expert witness) is terribly helpful in building an effective leadership team.   

What does build effective teams?  Having a leader who focuses on creating organization-wide goals and helping each leader see their role in that goal is a start. (For those who are interested in learning more about how to do this I recommend the work of Patrick Lenconi, in particular his books Silos, Politics, and Turf Wars, and The Five Dysfunctions of a Team.)   Setting the norm in a team that problems belong not to one department, but to the whole team is another.  Ensuring that the team has sufficient skills to function together is also a good first step.  When I work with teams that are not pulling together I often start with skill building in communication, conflict management, group process, and goal setting.  These skills when used in tandem can give a team a big push forward.

And lastly, for a team to operate as part of the whole, it is also a good idea for team members to have an understanding of and an appreciation for the work done by their peers.  This is part of the reason why organizations like Microsoft and GE take high potential individuals (future leaders) and rotate them through various functions in the company.  If such rotation is impractical in your organization, look for other ways to build shared appreciation for the roles of everyone on the team.

It's All About Perspective

I have a former employee who raised a group of kids by telling them "when one of you is in trouble - you're all in trouble."  There are probably some downsides to this notion of parenting, but one of the upsides was that her kids were adept in keeping each other in check.  "No, you are not going to sneak out because you'll get us all in hot water."   This notion of shared destiny is one that I think that leadership teams would benefit from keeping in mind.   Too many of us in organizations are willing to let another department flounder.  "It's not my problem" we might say.  Heck, with the prevalence of "forced ranking" performance review systems out there we even set up a system where a certain number of people are required to fail!  How much sense does that make?

If we can get to the point were we view ourselves not as "Engineering" or "HR" or "Customer Service" but as one whole organization, we can create a reality where where a problem belongs not to a department, but to the whole.  When there is a hole in the bottom of the boat, let's not stand around and watch.  Let's all pick up our tools with energy and take our place on the line to fix the ship.  We may yet get to the point where we see any hole in our ship as a threat to our collective survival.  I hope we get there because this notion of shared destiny is not only helpful, it is also absolutely true.

Credit: The drawing above was created by Simon Baker. (creative commons license)

 

Effective Meetings: A Case Study

Today I'm going to share a consulting story with you.  One of the things I love best about my work is being able to experience the incredible variety of organizational cultures that I interact with.  Sharing some of these experiences is one of the things I particularly enjoy doing here on this blog.

So today I was facilitating a discussion about organizational improvement in an organization here in Seattle.  The company decided to do this work in the context of a regular staff meeting, so I was able to sit back and observe how people interact.  I've been to a lot of staff meetings in my life but this one was particularly impressive.  Here are some of the factors that stood out:

They had Rotating Leadership
One thing this company did is to rotate the responsibility for facilitating the meeting.  Each session, someone new comes up and runs the meeting with the support of the HR executive.  This has the effect of building up the facilitation skills of the workforce while it encourages everyone to share in the leadership of the team.

They Laughed Often
Another element of this team is that they used humor to bond the team together.  The facilitator was a funny guy to begin with (Think starting off your staff meeting with wisdom from Homer Simpson) and there was plenty of laughter and gentle self-deprecation in the meeting.

They all Chipped In Without Complaint
The team also demonstrated a habit of helping each other out as a matter of course.  For example, when the team convened there were large stacks of mailing materials on the tables.  As people sat down, they automatically began stuffing envelopes.  By the time the meeting was five minutes in, an incredible amount of "busy work" had been completed.  No one seemed to find this kind of work demeaning or bothersome.

They Planned for Gratitude
This one impressed the heck out of me.  Shortly after the meeting started, the facilitator invited everyone to express any thanks that they had.  Suddenly, team members began to speak up.  These are the kinds of comments I heard:

"I'd like to thank Joe for helping me by filling in while I was on vacation."

"I'd like to thank Maggie for pulling me out of the fire last week when my computer broke down - she helped me get my reports printed when I was stuck."

"I want to recognize Accounting for pulling all those customer reports for my group - it was a lot of work and they were very thorough."

Was this series of "thank you's" a special event?  No, this time takes time for gratitude at every staff meeting.  Saying "thanks" to members of the team is a routine part of how they operate.

They Reported Successes
During the meeting, there was special attention paid to successes.  "These three employees referred new clients" and "We sold all the tickets to the conference." for example.  Each success was met with appreciation and smiles.

They Kept it Brief
No one at this meeting provided a laundry list of what they were working on, listed status reports for the sake of status reports, or rambled.  The meeting was brief, on target, and lighthearted.  To keep the meeting relevant, individual teams (HR, Customer Service, etc) each met *after* the main meeting to talk about departmental issues.  The whole team meeting focused on what applied to the whole team.

To walk into the room with this team was to feel that you were in the midst of a group of people who genuinely respect and enjoy each other.  No team is perfect, and I don't doubt that there are sometimes challenges or hard moments, but the overall tone was one of positive action.

And I admit that I'm especially entranced by that idea of taking time each meeting to recognize and thank others.  What a powerful action!  What would your team be like if they took the time to say "thank you" on a regular basis like this? 

I hope you enjoyed this 'case study' into effective meetings.  If you have a response to this post or your own stories to tell, leave a comment below. 

When is Team building not Team building?

Today's post will be brief, but I wanted to take the opportunity to say something about team building that has been bugging me for a while.

A pizza party alone is not team building.
A potluck is not team building.
Taking the team for drinks after work is not team building.

These are morale events.  They can be fun.  They may even bond people.  But they are not team building.

What are some examples of team building?

A pizza party coupled with a discussion about "how good are we at giving and receiving feedback in this group?" can be team building.

A workshop on communication done with a real work team can be team building.

An informal presentation on conflict management followed by discussion can be team building.

Bringing together a group of unconnected employees, teaching them about communication, then sending them back to different parts of the company is not team building.

So what makes Team building?

* There is an actual work team involved together.  (not strangers, not a random assortment)
* There is some kind of learning associated with how the team functions.
* Participants actually engage with the topic and each other - not just listening to a lecture.
* Participants learn tools or techniques that they can apply with the team when they leave the event.

I'm writing this today because I get lots of comments from people about how they do Team building because they have free donuts once a week in the break room.  Don't get me wrong, I think bringing people together to talk and form relationships is important.  But I'll offer this. If you really want to build a team - be very intentional about it.  Don't just assume that if you bring donuts that everyone will work effectively together.  You're more likely to contribute to giving employees diabetes than giving them job skills.

That is my 2 cents anyway.  What is yours?