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? rbrenNmUIemfhKUwobeOsner@ChaclfouBrcmqSnukrRooCanyon.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:
- When we steer the discussion away from issues to attack the credibility, motives, or character of our
debate partners, we often resort to a technique known as the ad hominem attack. It's unfair, it's unethical,
and it leads to bad, expensive decisions that we'll probably regret.
- If Only I Had Known: II
- Ever had one of those forehead-slapping moments when someone explained something, or you suddenly realized
something? They usually involve some idea or insight that would have saved you much pain, trouble, and
heartache, if only you had known.
- Ten Reasons Why You Don't Always Get What You Measure: I
- One of the "truisms" floating around is that "You get what you measure." Belief
in this assertion has led many to a metrics-based style of management, but the results have been uneven
at best. Why?
- How to Make Good Guesses: Strategy
- Making good guesses — guessing right — is often regarded as a talent that cannot be taught.
Like most things, it probably does take talent to be among the first rank of those who make conjectures.
But being in the second rank is pretty good, too, and we can learn how to do that.
- Hill Climbing and Its Limitations
- Finding a better solution by making small adjustments to your current solution is usually a good idea.
The key word is "usually."
See also Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
- Coming June 28: Tackling Hard Problems: I
- Hard problems need not be big problems. Even when they're small, they can halt progress on any project. Here's Part I of an approach to working on hard problems by breaking them down into smaller steps. Available here and by RSS on June 28.
- And on July 5: Tackling Hard Problems: II
- In this Part II of our look at solving hard problems, we continue developing properties of the solution, and look at how we get from the beginning to the end. Available here and by RSS on July 5.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrennsPfxEMUfJGAhtoTner@ChacPRAakdkLeeWlljmZoCanyon.com or (617) 491-6289, 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, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
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 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. Here are some upcoming dates for this program:
- Creating High Performance Virtual Teams
- Many people experience virtual teams as awkward, slow, and sometimes
frustrating. Even when most team members hail from the same nation or culture, and even when they all
speak the same language, geographic dispersion or the presence of employees from multiple enterprises
is often enough to exclude all possibility of high performance. The problem is that we lead, manage,
and support virtual teams in ways that are too much like the way we lead, manage, and support co-located
teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and
supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance.
Read more about this program. Here's an upcoming date
for this program:
- Baci Grill, 134 Berlin
Road, Berlin, CT 06416: September 19,
Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- Baci Grill, 134 Berlin Road, Berlin, CT 06416: September 19, Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- The Race to the South Pole: Ten Lessons for Project Managers
- 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. Lessons abound. Read
more about this program. Here's an upcoming date for this program:
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- CTCPA, 716 Brook Street, Rocky Hill, CT 06067: September 20, Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- 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.