HR-Glossar
Teamentwicklung (team development)
How teams develop, what phase models do and do not deliver, and which conditions actually carry collaboration.
1. What is Teamentwicklung (team development)?
Team development means deliberately improving collaboration in a group working towards a shared result – by settling objectives, roles, rules and how people deal with one another.
The term is frequently equated with team building, that is, with shared activities outside work. That equation is the most common weakness in practice: a shared outing improves the mood but settles neither objectives nor responsibilities – and that is where most of the friction sits.
The most effective starting points are unspectacular: a shared objective everyone understands the same way, clear responsibilities, binding agreements about how to work together, and a way of dealing with conflict that makes it workable. That is work on the frame, not on the people.
2. Origin and development
Team development draws on group dynamics. What became best known is a four-phase model dividing a group's development into forming, storming, norming and performing.
Placing it fairly requires saying: that model is a description, not a law. It dates from the 1960s, is empirically less well founded than its currency suggests, and teams pass through the phases neither necessarily nor in a fixed order. Its usefulness lies elsewhere – it makes the conflict phase expected and therefore discussable. Someone who knows that friction belongs to development does not read it as failure.
More recent work has shifted the view: away from phases and personality types, towards the conditions under which collaboration succeeds – a shared objective, clear responsibilities, reliable agreements, and the safety to voice mistakes and objections without fearing disadvantage.
That shift has a practical consequence: team development is less a question of events than of leadership in daily work.
3. Core principles and how it works
The shared objective first
Without an objective everyone understands the same way, a group is not a team. Most apparent relationship conflicts are unsettled conflicts about objectives.
Settle roles and responsibilities
Who decides what, who is consulted, who is informed. Uncertainty here produces friction that gets read as personal.
Agree rules for working together
Availability, how mistakes are handled, decision routes, how conflict is dealt with. A few binding agreements work harder than a mission statement.
Conflict belongs to development
The contest over roles and influence is not a disturbance. Teams that avoid it stay on the surface.
Phase models describe, they predict nothing
They help to place friction. As a schedule they are no use – teams do not pass through the phases necessarily or in a fixed order.
Safety to raise objections
Where mistakes and dissent bring disadvantage, both are avoided – and with them the information that matters.
Leadership works harder than events
What is tolerated, rewarded and modelled in daily work shapes collaboration more than any workshop.
4. Who is Teamentwicklung (team development) relevant for?
- Newly assembled teams – early clarification pays off most with them. - Teams in changed ways of working – self-organisation demands explicit agreements. - Managers – they shape the conditions under which collaboration succeeds. - Distributed teams – less arises incidentally for them, more has to be agreed. - Teams after conflict or changes of staff – clarification is more urgent here than a shared experience.
5. How it differs from related terms
- Team development and team building – one settles objectives, roles and rules, the other fosters a sense of belonging. Both have their place, but the second does not replace the first. - Team development and organisational development – one starts with the group, the other with the structures and procedures of the organisation. - Team development and conflict mediation – mediation works on a concrete conflict; development creates conditions under which conflicts become workable. - Team development and personality diagnostics – type tests create a shared vocabulary but do not explain collaboration. Their value is frequently overestimated. - Team development and leadership – the manager is part of the team, not its observer. A development that leaves them out falls short.
6. Variants and adaptations
Starting points by occasion:
- Start-up clarification for new teams – objective, roles, rules, decision routes. The most effective step and the most frequently skipped. - A retrospective on a fixed rhythm – a regular look back at the collaboration; from agile practice, but usable independently of it. - Role clarification – where friction hangs on responsibilities, which is more often the case than assumed. - Facilitated conflict work – for entrenched disputes; needs impartiality and usually external support. - Shared activities – strengthen relationships but replace no clarification. - Clarification for distributed work – availability, response times, choice of channels. What arises incidentally in an office has to be agreed here.
7. Advantages and challenges
Advantages
- Settles causes of friction that otherwise get read as personal conflict
- Improves results, not only the mood
- Early clarification is cheaper than late conflict work
- A regular look back makes adjustment a habit
- Particularly effective in distributed work, where less arises incidentally
Challenges
- It gets reduced to team building and then misses its purpose
- Phase models are misunderstood as laws
- Type tests produce labels that harden into attributions
- Without the manager's involvement the effect stays limited
- One-off events with no follow-up evaporate
- Where the cause lies in the organisation, work on the team does not help
8. Best practices for implementation
Begin with the objective, not with the people
Most apparent relationship conflicts are unsettled conflicts about objectives or roles. The question of what the team is jointly measured on settles more than any exercise.
Do not skip the start-up clarification
New teams almost always start straight into the work. Half a day for the objective, the roles and the rules saves months of friction.
Keep the rules short and make them binding
Five agreements that are kept work harder than twenty nobody knows.
Involve the manager
Developing a team while leadership stays outside moves the problem. They are part of the system, not its observer.
Use type tests sparingly
They create a shared vocabulary but do not explain collaboration – and the labels often stick longer than the insight.
9. Tips for employers and employees
For employers
- **Objective and roles before people** – that is where most of the causes lie
- **Plan the start-up clarification** – half a day saves months
- **Involve the manager** – they are part of the team
- **Team building replaces no clarification** – both have a place, but not the same one
For employees
- **Raise unclear responsibilities** – they produce friction that feels personal
- **Conflict is part of it** – avoiding it keeps a team on the surface
- **Insist on agreements** – particularly in distributed work
- **A type test is not a verdict on you** – its value is limited
10. Conclusion
Team development is frequently reduced to team building – to shared activities that improve the mood. They settle neither objectives nor responsibilities, and that is where most of the friction sits. What looks like a relationship conflict is frequently an unsettled conflict about roles.
The effective starting points are unspectacular: a shared objective everyone understands the same way, clear responsibilities, a few binding agreements, and the safety to voice objections and mistakes. That is work on the frame, not on the people – and it happens mostly in daily work, not at events. In teams distributed across countries and time zones, even less arises incidentally, so more of it has to be agreed explicitly.
One placing belongs with the widespread phase models: they are descriptions, not laws, and empirically less well founded than their currency suggests. Their use lies in making the conflict phase expected – someone who knows that friction belongs to development does not read it as failure. As a schedule they are no use.
Sources
- Fraunhofer Institute for Industrial Engineering – collaboration and team work (English pages) (opens in a new tab)
- German Association for Human Resource Management – team work (opens in a new tab)
- Federal Institute for Occupational Safety and Health – social relations at work (English pages) (opens in a new tab)
Related terms
Our promise
Software supports. People take responsibility.
Let us talk about your payroll – no strings attached, specific, and with a dedicated contact from day one.