Team Building - ST
Team Building - ST
Team Building - ST
Learning Objectives:
By the end of this session, participants will be able to:
Describe the importance of an effective team.
List three characteristics of a highly functioning team.
Identify potential threats to effective team functioning.
List tools for building strong teams.
Identify strategies for leading effective meetings
Introduction
Slide 1
Source:
• Neill, James. Wilderdom: A Project in
Natural Living and Transformation.
http://wilderdom.com/games/description
s/HeliumStick.html
• Ultimate Camp Resource.
http://www.ultimatecampresource.com/si
te/camp-activity/helium-stick.html
Effective Teams
Slide 4
Slide 5
Source: I-TECH.
Animation Clicks: 1Slide 7
Source: I-TECH.
Trust
• Trust must exist among team
members. It is the essence of a
successful team.
Navigate conflict.
• Conflict and disagreement can occur
within teams.
• Successful teams navigate conflict
well, using it as a constructive tool.
• Sometimes, this means agreeing to
disagree.
Tuckman Model:
• The most commonly used framework
Source:
for looking at stages of team
• Stein, Judith. “Using the Stages of Team
Development.” Massachusetts Institute of
development was created in the mid-
Technology (MIT), Department of Organizational 1960s by Bruce Tuckman.
Effectiveness and Change. Retrieved 1-April-2010 • These stages provide a useful frame
from for looking at your own team.
http://web.mit.edu/hr/oed/learn/teams/art_stages.h • They are best used as a starting point
tml. for team dialogue.
• Kenya Family AIDS Care and Education Services • The common stages that teams
(FACES). Nyanza Leadership and Management typically go through are: Form,
Training Initiative. Kenya. 2009. Developed in Storm, Norm, Perform, Transform
collaboration with I-TECH. • It is important to remember that the
process is not always linear!
Generally, teams cycle through
stages over and over depending on
the make-up of the team and the
issues they identify.
Effective Teams
• Communicate openly
• Debate Ideas
• Commit to decisions and plans
• Show accountability
• Focus on results
Make photocopies of the survey for all members of your team. Have each team member
complete their own scoring, and compare team members’ scores for each column.
If the responses show a range of viewpoints about which developmental stage the team is in,
the discussion might focus on the perceptions that lead to that range of viewpoints. The
survey’s answer key connects specific questions with each developmental stage. Discussion
could focus on specific questions, or it might focus on the answers associated with each
stage.
Remember – there are no right or wrong answers, just the variation in perceptions that can
make teams a rich working environment. The point of any discussion is not to force an
agreement about the team’s developmental stage, or to convince someone to change his or her
answers, but to reflect as a team about the team’s development.
Source:
Survey developed by Donald Clark, 2002. (http://www.nwlink.com/~donclark/leader/leader.html).
Accessed via: Stein, Judith. “Using the Stages of Team Development.” Massachusetts Institute of Technology (MIT),
Department of Organizational Effectiveness and Change. http://web.mit.edu/hr/oed/learn/teams/art_stages.html.
We try to have set procedures or protocols to ensure that things are orderly and run
1. smoothly (i.e. minimize interruptions; everyone gets opportunity to have his/her say).
Almost never – 1 Seldom – 2 Occasionally – 3 Frequently – 4 Almost always – 5
We are quick to get at the task at hand, and do not spend much time in the planning stage.
2. Almost never – 1 Seldom – 2 Occasionally – 3 Frequently – 4 Almost always – 5
Our team members feel that we are all in it together and we share responsibility for the
3. team’s success or failure.
Almost never – 1 Seldom – 2 Occasionally – 3 Frequently – 4 Almost always – 5
We have thorough procedures for agreeing on our goals and planning the way we will
4. perform our tasks.
Almost never – 1 Seldom – 2 Occasionally – 3 Frequently – 4 Almost always – 5
Note the value that corresponds with the answer you selected for each number. Total up your
scores in each column. Note: numbers in the scoring tool are not sequential Pay close
attention as you complete the columns below.
The lowest score possible for a stage is 8 (Almost Never) while the highest score possible for
a stage is 40 (Almost Always). The highest of the four scores indicates which stage you
perceive your team normally operates in. If your highest score is 32 or more, it indicates a
clear sense on your part that your team is in this stage.
The lowest of the four scores is an indicator of the stage you believe your team is least likely
to be in. If your lowest score is 16 or less, it is a strong indicator of your belief that your team
is not in this developmental stage.
If two of the scores are close, your team may be going through a transition phase. However, if
you score high in both the Forming and Storming phases, then your team is likely to be in the
Storming phase. If you score high in both the Norming and Performing phases, then your
team is likely to be in the Performing stage.
If there is only a small difference among the four scores, this may indicate one of the
following:
You have no clear perception of the way your team operates;
The team's behaviours are highly variable; or
You are in the Storming phase (this phase can be extremely volatile with high and low
points).
Part 1: Diagnosis
Characteristics of each stage
Forming Storming Norming Performing
Others,
Focus Own objectives Processes Performance
problems
Trust the
Trust Assess leader Trust only leader Trust the people
processes
Relationships None, or distant Conflict Mechanistic Synergistic
Criticism Covert Overt Productive Comfortable
Decision-
Fragmented Thrashing Processed Natural
making
Predictability Politics Volatile Systematic Anticipation
Role
Ignorance Ambiguity Clarity Intuitive
understanding
Products Individual Undesirable Wooden System
Performance Individual effort Working out Following rules Achieving flow
Part 2: Interventions
Types of interventions that leader should make
Forming Storming Norming Performing
Resolve Facilitate
Overview Set Objectives Coach
Conflicts Processes
Direction High High Low Low
Support Low High High Low
People Task Team self-
Leader Focus Individual tasks
interactions interactions development
Persuasion Style Tell, push Sell, consult Listen, advise Observe, support
Team Leader provide Facilitate Facilitate Dynamic
Interaction links relationships team processes grouping
Self-
Summary Individuals Relationships Processes
Development
Source: Team Technology. “Leadership Using the Tuckman Model.” Retrieved 1-April-2010 from
http://www.teamtechnology.co.uk/tuckman.html.
This excerpt from “The 5 Dysfunctions of a Team” by Patrick Lencioni can help you understand
potential threats to team effectiveness.
The 6 activities below can help to build trust and cooperation within teams.
Explain that if teams are to work well together, team members need to get to know each other.
Learning about each other and relating on a personal level helps team members to become open to
each other. And this builds trust.
The first exercise is called the Personal Histories Exercise. On a piece of paper, answer the following
questions:
Where did you grow up?
What was the most difficult or important challenge you faced as a child or teenager?
Other than your parents, who had the greatest positive impact on you? Why?
Starting with yourself, go around the room and have each person share (briefly) their answers. Ask
people to share for only one or two minutes.
Adapted from: Lencioni, P. 2005. Overcoming the 5 Dysfunctions of a Team: Field Guide. San Francisco:
Jossey Bass.
2. Making a Difference
15 minutes
This activity emphasizes that all individuals can and do make a difference to the group.
Divide people into small groups (or do this exercise within a small team).
Ask people to think about what one thing they have done this year to make a difference in the
lives of their co-workers, team, etc.
Instruct each person to share their story briefly with the people at the table.
3. Yes, And…
This activity fosters collaboration, taps into ides, keeps you from getting stuck on obstacles, and helps
people focused on suggestions, idea-building, and problem-solving, rather than only focusing on
problems and frustrations.
Divide participants into small groups of 3-6 people. (Ideally, by the team that they represent.)
Explain that:
o As teams, we represent an impressive array of skills, talents, and experiences.
o A “group CV” is a way to represent our collective strengths.
Give each group a sheet of flipchart paper and markers.
For the first step in the exercise, we get to move around some.
Ask participants to stand up. They are going to each have a card with a value on it. On the back is a
sticky note. I’m going to ask everyone to move around and when I say, “Stop”; find one person to
talk with. The pair should look at both of their cards and decide the value of each. The full value is
“7”, so you have to decide how many points each value gets – might be 0 and 7; 3 and 4; etc., as long
as the total number of points you give to the cards is 7.
Pass out the cards and ask people to move around. Say “Stop” after a few minutes, repeat the
instructions and give people a few minutes to discuss and give a number to each card. Repeat this 5
times. We need 5 numbers on each card.
The final time, ask participants to count the numbers on the back of the card they have. Ask if anyone
has a card with the number 35 on it (that’s the highest possible number a card could have). Continue
counting down to get the cards with the highest total.
Write the top five values on the flipchart. Ask if people agree with this. Is there a value that isn’t here
that should be? Can we agree to these values?
Wrap up by saying that identifying values that we share as a team is an important part of the process
of functioning as an effective team. Creating a shared vision is another part of this process and this is
something we will work on in the future.
Distribute the handout, “My Personal Best Leadership Experience” (note: this is included below.)
Ask participants to spend 20 minutes writing about an experience where they succeeded as a leader.
After 20 minutes, ask participants to stop writing and find one person to share your story with. Take 5
minutes each to share your stories. Remind folks to switch talking after 5 minutes.
After pairs have had a chance to share their stories (10 minutes), ask the full group:
How many people had a story from their work life? How many from their personal life?
Did anyone write about something that happened in the last few months? How about the last
year? How many wrote about something that happened more than 5 years ago?
It can take perspective to realize our accomplishments. Sometimes we can’t see what we have
accomplished recently – but can recognize it after some time has passed (or a lot of time has
passed).
How did it feel to write about this experience? Is it something you think about often?
Often we forget out successes and it’s important to remember and acknowledge what we did.
Think of a time when, in your opinion, you did your very best as a leader. This might have
taken place recently or long ago; while you were the “official” leader or manager of a team or
group, or when you emerged as an informal leader; when you were working for pay or as a volunteer.
The experience might have taken place in the workplace, when you were part of a community group
or professional organization, or when you were a student.
1. Schedule in Advance
Set the meeting date and time in advance, when it is convenient for the largest number of team
members. Ensure that the right people are invited (key decision makers, people whose presence is
essential, etc.).
2. Draft Meeting Agenda
Meeting agendas should be prepared in advance. Put important items first, group related agenda
items together, identify person responsible for leading discussion, and identify the action needed
during the meeting.
3. Get Feedback on Agenda
Ask members to contribute items for the agenda and try to send the agenda out before the
meeting.
4. Start on Time
If you wait for latecomers, it punishes those who were on time.
5. Warm-Up
A brief warm-up introduces members and builds trust. It enables people to unburden other
concerns and mentally direct themselves to the issues at hand.
6. Share Agenda, and Follow It
Clearly state the purpose of the meeting and the items to be covered. People may not have read
the agenda even if you supplied if beforehand! Additional concerns of members should be placed
on the agenda at this time. As agenda items are discussed, take note of action items, follow-up
items, and the people responsible for them.
7. Conclude with Review: What exactly have we decided/agreed to today?
Before the meeting ends, the meeting leader should ask the question: What exactly have we
decided/agreed to today? It can be helpful to write down decisions that the group has made on a
board or flipchart, and ensure that members are in agreement.
8. Set Next Agenda
Ask members for items they think need to be addressed at the next meeting. This brings out ideas
while they are still active and increases their interest in attending the next meeting.
9. End on Time
Include the ending time on the agenda and stick to it. Without set time limits, discussion can drag
on forever. If you need more time, negotiate with those attending. Respect for individual needs
and recognition that meetings are only one part of our lives leads to increased member
commitment
10. Draft & Share Meeting Minutes
Write and distribute minutes to all team members shortly after the meeting, when memory is fresh.
Meeting Agendas
Agendas help participants arrive at meetings prepared, and help to keep discussion focused
and on track.
Team/Meeting: Date:
Agenda Item 1:
Discussion – Key Points:
Adapted from: Microsoft Corporation, Microsoft Office Meeting Minutes Template (http://office.microsoft.com/en-
us/templates/meeting-minutes-TC010173185.aspx).
Ground rules can be useful to clarify standards team members should follow during team
meetings. They serve as a verbal contract regarding the expectations that group members
should follow in their interactions with one another.
Ground rules should be adapted based on the team’s purpose and challenges.
Below is a sample list of ground rules you can consider to support effective team meetings.
A team Term of Reference (TOR) can be a useful tool for teams that meet frequently –
especially for a task force, working group, technical team, or team that cuts across
departments in an organization. The team TOR (also called a “Team Charter”) is a document
that all members agree to, that provides clarity about the “job description” for the team.
A charter should include:
Team name
List of members, roles
Mission/purpose
Objectives
Frequency & duration of meetings
Communication Methods
Ground rules/norms
Agenda
Set at the end of the previous meeting. New items may be added by sending an email to the
facilitator 48 hours before the next meeting
Facilitator sends agenda and relevant documents out to the full ListServe at least 24 hours prior to
the meeting.
Minutes
Notetaker distributes minutes to ListServe within 3 working days
All present review minutes and give feedback within 2 days
Notes posted on Intranet within one week of meeting.
Expectations of Participants
Come prepared – review agenda and read documents
Come on time
Try to protect time for full attendance