It was the end of the team-building training, and as everyone politely applauded, Maria began gathering her things. The binder. The picture of her with Diane holding the eight-foot paper elephant. Her certificate. And of course her notes, which included long lists of to-dos that came to her during the times she was zoned out. Feeling both energized and depressed, she turned to her left to look at Diane.
Diane looked back, saying nothing. They were both tired. Finally Diane said, very quietly, "Two days. What a waste." Maria nodded and they both stood and walked silently out of the room, among the first to leave.
Back in Diane's office, door closed, Maria kicked it off with, "And how long will it be till we forget this?"
Maria's impish side triumphed: "Forget what?" They both laughed. A needed laugh.
"You know what I mean," Diane said. "Will we ever use this stuff?"
Maria and Diane are experiencing some of the letdown that frequently follows team-building training. It's a common reaction, but it needn't be. Here are some simple ways to make team learning last longer.
- Think of it as "learning" rather than training
- It's amazing how powerful the words are. Learning is the real goal, so let's call it learning. Training is for puppies.
- Inflicting education rarely works
- Give the team a choice. Allow budget and schedule for team learning, if they want it. Mandating it instead of supporting it produces different and inferior results.
- Structure learning in short bursts
- Is it "team training"
or "team learning"?
Words do matter
- Unless air travel is involved, even two days of education is usually too long. Leaving space between "modules" gives people time to practice and integrate new ideas into their work.
- Limit turnover on the team
- Changing the composition of a team is disruptive. The new people often didn't attend the recent team learning experience, and more important, change entails Chaos (see "Now We're in Chaos," Point Lookout for September 19, 2001). You might get more out of a team by keeping its members in place than you would by cycling in an expert for a short-term specialized task.
- Leave some slack for experimentation
- After a team goes through a team learning experience, we hope they'll apply what they've learned. They'll be a bit clumsy at first — it's like learning to walk. Give them the slack they need to experiment with the new methods they've learned.
Most important, follow up. Setting an actual date for a "post-graduate" follow-up to any educational experience makes actual application of the learning much more likely. Setting a date creates an expectation that we'll be reviewing the results of applying the methods we've learned.
A year later, what will people remember from the team learning experience? Will it be the important lessons that were so difficult and valuable to learn? Or will it be the eight-foot paper elephant? Top Next Issue
Are your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!
Your comments are welcomeWould you like to see your comments posted here? rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.comSend me your comments by email, or by Web form.
About Point Lookout
Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.
Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.
Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.
More articles on Personal, Team, and Organizational Effectiveness:
- Email Antics: II
- Nearly everyone complains that email is a time waster. Yet much of the problem results from our own
actions. Here's Part II of a little catalog of things we do that help waste our time.
- On Virtual Relationships
- Whether or not you work as part of a virtual team, you probably work with some people you rarely meet
face-to-face. And there are some people you've never met, and probably never will. What does it take
to maintain good working relationships with people you rarely meet?
- I've Been Right All Along
- As people, we're very good at forming and holding beliefs and opinions despite nagging doubts. These
doubts lead us to search for confirmation of our beliefs, and to reject information that might conflict
with our beliefs. Often, this process causes us to persist in believing nonsense. How can we tell when
this is happening?
- The Limits of Status Reports: II
- We aren't completely free to specify the content or frequency of status reports from the people who
write them. There are limits on both. Here's Part II of an exploration of those limits.
- Contextual Causes of Conflict: I
- When destructive conflict erupts, we usually hold responsible only the people directly involved. But
the choices of others, and general circumstances, can be the real causes of destructive conflict.
See also Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
- Coming October 23: Power Distance and Teams
- One of the attributes of team cultures is something called power distance, which is a measure of the overall comfort people have with inequality in the distribution of power. Power distance can determine how well a team performs when executing high-risk projects. Available here and by RSS on October 23.
- And on October 30: Power Distance and Risk
- Managing or responding to project risks is much easier when team culture encourages people to report problems and question any plans they have reason to doubt. Here are five examples that show how such encouragement helps to manage risk. Available here and by RSS on October 30.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout are available in six ebooks:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, )
- Get 2003-4 in Why Dogs Wag (PDF, )
- Get 2005-6 in Loopy Things We Do (PDF, )
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
- Get 2009-10 in The Questions Not Asked (PDF, )
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )
Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500 words in your inbox in one hour. License any article from this Web site. More info
- The Race to the South Pole: Lessons in Leadership
On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. But to organizational leaders, business analysts, project sponsors, and project managers, the story is fascinating. We'll use the history of this event to explore lessons in leadership and its application to organizational efforts. A fascinating and refreshing look at leadership from the vantage point of history. Read more about this program.
Here's a date for this program:
- Baldwin-Wallace University, 275 Eastland Road, Berea, Ohio
44017: November 7,
Kerzner Lecture Series/International Project Management Day, sponsored by Baldwin Wallace University and the Northeast Ohio Chapter of the Project Management Institute.
- Baldwin-Wallace University, 275 Eastland Road, Berea, Ohio 44017: November 7, Kerzner Lecture Series/International Project Management Day, sponsored by Baldwin Wallace University and the Northeast Ohio Chapter of the Project Management Institute. Register now.
- The Power Affect: How We Express Our Personal Power
Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.
- Your stuff is brilliant! Thank you!
- You and Scott Adams both secretly work here, right?
- I really enjoy my weekly newsletters. I appreciate the quick read.
- A sort of Dr. Phil for Management!
- …extremely accurate, inspiring and applicable to day-to-day … invaluable.