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? rbrendbTtLLSVlUPPCNkAner@ChacthFxWKdRwnLylOCDoCanyon.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:
- The Mind Reading Trap
- When we think, "Paul doesn't trust me," we could be fooling ourselves into believing that
we can read his mind. Unless he has directly expressed his distrust, we're just guessing, and we can
reach whatever conclusion we wish, unconstrained by reality. In project management, as anywhere else,
that's a recipe for trouble.
- Heavy Burdens: Should, Always, Must, and Never
- As a leader you carry a heavy burden. You're accountable for everything from employee development to
meeting organizational objectives, and many of these responsibilities conflict. Life is tough enough,
but most of us pile on a load of over-generalized rules of work life — a load too heavy for anyone
- Risk Management Risk: II
- Risk Management Risk is the risk that a particular risk management plan is deficient. Here are some
guidelines for reducing risk management risk arising from risk interactions and change.
- Speak for Influence
- Among the factors that determine the influence of contributions in meetings are the content of the contribution
and how it fits into the conversation. Most of the time, we focus too much on content and not enough on fit.
- Risk Creep: I
- Risk creep is a term that describes the insidious and unrecognized increase in risk that occurs despite
our every effort to mitigate risk or avoid it altogether. What are the dominant sources of risk creep?
See also Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
- Coming October 5: Downscoping Under Pressure: I
- When projects overrun their budgets and/or schedules, we sometimes "downscope" to save time and money. The tactic can succeed — and fail. Three common anti-patterns involve politics, the sunk cost effect, and cognitive biases that distort estimates. Available here and by RSS on October 5.
- And on October 12: Downscoping Under Pressure: II
- We sometimes "downscope" projects to bring them back on budget and schedule when they're headed for overruns. Downscoping doesn't always work. Cognitive biases like the sunk cost effect and confirmation bias can distort decisions about how to downscope. Available here and by RSS on October 12.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendbTtLLSVlUPPCNkAner@ChacthFxWKdRwnLylOCDoCanyon.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-1000 words in your inbox in one hour. License any article from this Web site. More info
- 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.