Help, blame game

[JaneYoung]

It takes a team to succeed and it takes a team to fail.

That's a very simple statement and one that is often glossed over - especially by those who want to take all the credit for one and give all the credit for another. Dave Lavery made an awesome post about this aspect of team dynamics a while back. I'll do a search and see if I can find it.

In the meantime, think about how much time you spend listening rather than defending the design. The time is short and what is passed is past. As change occurs, see how you can contribute in a positive beneficial manner to help get the job done. If that includes listening and paying attention as change is made - then listen and pay attention.

Edit: I haven't located the post that I'm looking for but I came across another one. This is a post of Dave's that addresses the bigger picture. It's a good one that points out the value of working well in a group situation. I'll look for the other post later after work.

Jane

[Samk]

well lately its seems that the mentor says things just to kind of rub it in or something. Like I'll be working really hard on the robot, and she'll say, "you're two weeks over deadline, I hope the team doesn't fail" or something like that. I tried saying that I couldn't be given all the blame, as it was a team design, but then she responded, "you need to learn to just take the blame"

[johnmaguire2013]

If there are other mentors, I would discuss with one of them, and explain the problems you're having with this specific mentor. Ask them to talk to her for you, or to mediate a discussion between the two of you.

[Samk]

Thanks all for the help, now that the build season is over, I will seek out some mediation, and hope that this hasn't affected my eligibility for the field team