Skip to main content
Home
  • Agile
  • Manage
  • Test
Register
Log In
  • Membership
  • Feedback
  • Contact Us

When Is a Team Player Not a Team Player?

Blog Post

When Is a Team Player Not a Team Player?

Blog Post by Naomi Karten | Comments: (6) | Thu, 11/19/2009 - 10:30pm
  • Login or register to post comments
  • Print

It may seem like a contradiction, but you can view yourself as a team player and still impede your team's ability to succeed. Consider one team that I observed during a four-hour problem-solving session.

Moments after the group gathered, Jonathan, a personable, outgoing fellow volunteered to facilitate the group's efforts. At that, he positioned himself at the flipchart, marker in hand, ready to take notes. Jonathan had previously told me with pride that he was a team player and he truly saw himself as one. He wanted his team to succeed and was highly motivated to contribute to their shared effort.

But once at the flipchart, Jonathan did as much to obstruct the team's effort as to support it. For example, he dismissed several ideas that differed from his own, and discounted some suggestions without trying to understand the reasoning behind them. He seemed unfazed when several people spoke simultaneously. As the effort proceeded, he failed to notice expressions of annoyance on the faces of some team members - or if he noticed, he did nothing about them.

Jonathan's heart was in the right place. He was a team player. How could it be otherwise, given how strenuously he wanted the team to succeed? Yet from the way he worked, it was as if he'd been directed to do all he could to make the problem harder to solve than it actually was.

The same was true of other participants—team players all. For example, one team member said she was good at listening to many simultaneous speakers; then moments later, she misstated a key point one of them had just made. Another said he'd support any solution as long as the session ended quickly. Then he continually inserted ideas that prolonged the discussion.

None of them seemed aware of how their behavior was counteracting the very success they wanted the team to achieve. Under the pressure of time, they acted in a manner that ensured their effort would need more time rather than less.

Partway through the session, with the team's energy plummeting, I asked them to describe their reactions to the team effort. Several said they were frustrated, impatient, or disappointed. Yet they said nothing until explicitly asked.

Did they solve the problem by their deadline? Yes, they did. But they could have solved it with fewer frayed nerves and ruffled feathers if they had built a foundation of respect and caring as their starting point. When time isn't spent up front building a strong foundation for working together, even more time is inevitably needed to repair the foundation when it cracks. The mark of a successful team is not just that it achieves a successful outcome, but that team members enjoy working together and would like to continue doing so.

A team that destroys itself in the course of accomplishing its mission is no team at all. Even if everyone is a team player.

  • Project & Team Management
About The Author: Naomi Karten

Naomi Karten is a highly experienced speaker and seminar leader who draws from her psychology and IT backgrounds to help organizations improve customer satisfaction, manage change, and strengthen teamwork. She has delivered seminars and keynotes to more than 100,000 people internationally. Naomi's newest books are Presentation Skills for Technical Professionals and Changing How You Manage and Communicate Change. Her other books and ebooks include Managing Expectations, Communication Gaps and How to Close Them, and How to Survive, Excel and Advance as an Introvert. Readers have described her newsletter, Perceptions & Realities, as lively, informative, and a breath of fresh air. She is a regular columnist for StickyMinds.com. When not working, Naomi's passion is skiing deep powder. Contact her at naomi@nkarten.com or via her Web site, www.nkarten.com.

View More

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

#1 Submitted by on Thu, 12/17/2009 - 2:59am.

Re: When is a team player not a team player?

Kenneth, you've raised an interesting and important point. Too often, management uses "team player"(as in "you're not one") to suppress behavior they don't like or don't know how to handle. In my post, I was focusing on behaviors that were well-intended, but that led the team in a direction that was counterproductive. But I agree with you about the potential for group-think when there's too much team-playing, and I like your notion of "controlled contention" as the middle ground between too much team playing and too little. Very thought-provoking. ~Naomi

  • Login or register to post comments

#2 Submitted by on Thu, 12/17/2009 - 2:52am.

Re: When is a team player not a team player?

Richard, yes, exactly right. Each team player has strengths and weaknesses, and viewing yourself as a team player doesn't mean your weaknesses suddenly become strengths. ~Naomi

  • Login or register to post comments

#3 Submitted by on Fri, 12/18/2009 - 10:16pm.

Re: When is a team player not a team player?

Kate, thanks for your comment. I agree. People use the term "team player" because it sounds good and it's something they want to see in themselves. But often, they don't appreciate what being a team player entails. ~Naomi

  • Login or register to post comments

#4 Submitted by on Wed, 12/16/2009 - 10:43pm.

Re: When is a team player not a team player?

"You're not being a team player" is one of those coded bits of exclusionary speech meant to message that "you" are not being a compliant. It's Dubya's, "You're either with us or you're with the terrorists" ploy. There are times (and I believe often), when being a "team player" does a disservice to the organization. Too much "team playing" and you have nothing more that groupthink. BTW, too little team playing and you find chaos-- there is a middle ground... I use the term "controlled contention" to describe that magic spot where there is a balance of team cohesion, but a clear willingness of participants to speak up and challenge the group to think a different way.<br><br><br><br>

  • Login or register to post comments

#5 Submitted by on Wed, 12/16/2009 - 8:37pm.

Re: When is a team player not a team player?

The real issue is that Jonathan was not a very good facilitator. Just because he wants to be a team player does not imply that he can then play a role he is not well trained for.

  • Login or register to post comments

#6 Submitted by on Wed, 12/16/2009 - 8:37pm.

Re: When is a team player not a team player?

Oh so true Naomi -- people using the phrase "team player" yet not truly clear on what that means. The first example you mentioned -- power of the pen -- was in full swing it would seem. The second, listening skills, is often missed as a key element of teaming. Great post that will take all teams to a new level of discovery.<br>Kate Nasser

  • Login or register to post comments

More like this

  • When is Done Really Done?
  • When Should You Start Project Overtime?
  • When to Step Up, When to Step Back
  • When Trust Goes AWOL
  • How to Improve Meetings When You're Not in Charge

Welcome to TechWell!

With an ever-expanding library of content by industry experts, TechWell is your source for software knowledge. The site is still growing, so please pardon our dust. If you see anything that requires our attention, please CONTACT us.

Not a member? REGISTER to join our community.
Already a member? Log In

Hot Topics

  • Most Read
  • Most Discussed
  • Most Shared
  • New Downloads

Management Myth #1: The Myth of 100% Utilization

Article by Johanna Rothman | Comments (17)
 A manager took me aside at a recent engagement. “You know, Johanna, there’s something I just don’t understand about this agile thing. It sure doesn’t look like everyone is being used at 100 percent... Read More

Edit Those Epics

Article by Johanna Rothman | Comments (23)
 I've been working with folks making their transition to agile. One of the hardest transitions is for the managers and technical leaders.Managers are accustomed to working in timeboxes. To them, the... Read More

Matt Heusser and Company Discuss "Testing is Dead"

Blog Post by Jonathan Vanian
 Do you think testing is dead? Matt Heusser recently put up a great podcast over at Software Test Professionals discussing this blasphemous topic. Read More

Passing the Baton

Article by Rinku Sahay | Comments (1)
 I was watching a relay race recently. A relay is where members of a team take turns to perform and complete a certain action or activity. In a relay race, one team member passes a baton to another... Read More

The Future Is Mobile Technology

Article by Heather Shanholtzer | Comments (3)
 A thought leader in mobile application testing, Jonathan Kohl has been a pioneer in applying effective software testing, business analysis, and design and project management on mobile application... Read More

Management Myth #1: The Myth of 100% Utilization

Article by Johanna Rothman | Comments (17)
 A manager took me aside at a recent engagement. “You know, Johanna, there’s something I just don’t understand about this agile thing. It sure doesn’t look like everyone is being used at 100 percent... Read More

Considering the Modern Technology Career

Article by Matthew Heusser
 Software development is a young field, at least compared with established professions like law and medicine. The choice to work in software is likewise a different choice. It is often made in youth... Read More

Testing Tradeoffs and Project Risk: A Case Study

Article by Payson Hall
 The project had issues. It was a two-year project intended to swap an aging legacy application for a commercial product. The vendor’s off-the-shelf software required some customization and extension... Read More

The ROI of Learning for Testers

Article by Lisa Crispin
  During my software career, I’ve spent a lot of time and effort learning new thinking and technical skills. I’ve encouraged my peers to do the same. The series that Janet Gregory and I wrote on... Read More

The Top 5 Frustrations for Project Managers

See how you can avoid management swoop-in at the eleventh hour, or creating and sending around a dreaded 200-page plan that no one has time to read once, let alone every time a change occurs. We've... Read More - Get this content

Follow Us On...

Follow us on Twitter
Twitter
Follow us on Facebook
Facebook
Follow us on LinkedIn
LinkedIn
Follow our RSS feed
RSS Feed

Sponsors

  ASTQB
  HP Software
  Microsoft
  Neustar
  SQE Training
  SmartBear Software
  Tricentis


Our Bloggers

Johanna Rothman is a management consultant and a regular StickyMinds.com and Better Software magazine columnist.

Steve Berczuk is an engineer and ScrumMaster at Humedica where he's helping to build next-generation SaaS-based clinical informatics applications.

Naomi Karten is a highly experienced speaker and seminar leader who draws from her psychology and IT backgrounds to help organizations improve customer satisfaction, manage change, and strengthen teamwork.

Lee Copeland has more than thirty years of experience in the field of software development and testing.

Lisa Crispin has worked as a tester on agile teams for the past ten years, and enjoys sharing her experiences via writing, presenting, teaching and participating in agile testing communities around the world.

Claire Moss has been testing software for 8 years. Although authoring a testing blog and articles are new for her, Claire has always had a passion for writing, which might be a strange trait for a Discrete mathematician.

Site Contents
Back To Top
  • » My Page
  • » Communities
    • - Agile
    • - Manage
    • - Test
  • » Solution Central
    • - HP Solution Center
  • » Interact
    • - Blogs
    • - Forums
  • » Resources
    • - Articles
    • - Better Software Magazine
    • - Download Center
    • - News Center
    • - Podcasts
    • - Videos
  • » Events
    • - Web Seminars
    • - Conferences
    • - Training



Techwell

  • Terms of Use
  • Privacy Policy
  • RSS
  • Site Feedback
  • Subscription Services