Basketball court patterns: Weak team, Personal float and Minus moral

Spent half a day on the basketball court. A good workout, and, as the Americans say, “thought-provoking”. I want to share some observations - common, in my opinion, for team sports and team development.

Observation 1: WEAK TEAM

The formation of a team of unfamiliar and unfamiliar players on the court is rapidly rapidly. Crashed three-by-three, more or less fair in growth, in terms of the game and drove off. If after a couple of minutes you realize that you are in a weak team, it is difficult to enjoy the game.

Funny pattern: think “I am in a weak team,” instead of “we are a weak team.” Moreover, regardless of their own level of play. It would seem that both are a statement of fact, but there is a nuance. I tried to repeat to myself several times, to observe the sensations:

• I am in a weak team, I am in a weak team ... I am in a weak team. It feels like something like: “I'm my poor thing,” such an injustice happened to me, what can you do.
• We are a weak team, we are a weak team ... we are a weak team. Initially, a similar annoyance, but with each repetition on the word “we” I start to wind up, a much more active reaction to, in fact, the same fact.

Conclusion:

There are no passive donors in the team. We can change a lot in the original “given” when we take responsibility for teamwork. To think more often “we” when you notice someone else’s or your own weakness.
')

Observation 2: PERSONAL TERKS

I observed such an effect several times: you need to break up into teams, but you really don't want to get into one team with that tip. And of course, you will have to play with him sometime, or worse, programming in pairs. How to be? Quit the game? Change project?

There is such a belief that in a good team, everyone should be friends, practically love their neighbor. But many virtuoso teams of athletes, scientists and musicians prove it is false. If a task is an occasion for a team, then only personal contribution is a reason to play together. Bank robbers gather in teams not for musical and gastronomic tastes, but for good for business. In the overwhelming majority of cases, we have something to appreciate even those people whom we do not love.

Conclusion:

We like people who are like us, and the project is useful for the participants, different in style and skills. Look for reasons to work together instead of reasons to like each other.

Observation 3: MINUS MORAL

Minus morality - so in sports and team games they call actions that undermine the morale of the team, jeopardizing the results, health and even the lives of its members. Regardless of the technique of the game and the star team, often teams that have not learned to recognize and discard such actions lose to those in which the team spirit and sense of support are strong.

The effect of minus morality may not be so obvious in the office, but it is perfectly observed on the sports ground. Often the dynamics of the game, and even the score, change drastically when you get rid of a player who releases stinging comments and reproaches.

The job of an engineer is to solve problems for which there are no ready-made solutions. Technological expertise plays an important but far from decisive role. The fear of experimentation, the inadmissibility of mistakes, criticism from technical leaders are social stoppers blocking the value stream.

Conclusion:

Social context determines team success. We can achieve better results by agreeing on the rules of interaction. Decide what is “minus morality” for us and gradually get rid of such actions.

Software development is a team game. At least I like this way of thinking. But in my opinion, our field lacks good team experience and strong examples associated with it. I would be glad to learn about your experiences and conclusions. And I strongly advise you to try team sports, it's exciting :)