Before this series begins, let's start by explaining a concept: team.
To make a long story short, I'll explain later: The team is not simply a collection of people. An organizational structure in which a group of people, with common goals, has an impact on each other.
Let's first explain the first sentence: The team is not a simple collection of people.
First of all, we need to know how to put a few people together, and then do things. This combination cannot be called a "team". They feel more like workers on the line, rather than
Friends who help each other and have strong friendships. Such a combination only uses people as objects. The likelihood of creating innovation is almost 0. Nor can it be called a "team."
The second sentence: (team) is composed of many people, with a common goal, the members of the mutual impact of the organization structure.
Teams must consist of multiple people (greater than or equal to 2), a person cannot be called a team. (PS: Seemingly nonsense)
Team, must have a common goal, otherwise, will inevitably move towards decentralization.
Team members must be able to interact with each other, and if they cannot interact with each other, they will become, in the first sentence, the "collection of people". There is no way to talk about team learning. Mutual help, and
More complex team building up.
After saying what is the team, we should discuss how we should build, yes, it is "building"! a good team is not likely to fall from the sky (unless you have a dog poop). So
I want to combine my own practice with the team and discuss how to build a team in the next blog post.
Preface---What is a team?