Thinking space
A team starts afresh. What do we take with us from the past?
The first meeting in the new line-up. Some are new, others have been there for years, a few familiar faces are missing. Someone says: "We're looking ahead now." Everyone nods, and it sounds right.
Two weeks later, a passing remark: "But we've tried that before." The new people don't know what is meant. The others know exactly. Nobody explains it.
Whether in a company after a reorganisation, in an association after the board election, in a school team or in a non-profit organisation: a new organisational chart applies from day one. People's experiences do not start afresh.
What comes along, whether we want it or not
Those who stay bring knowledge with them: what has worked, which ideas have already failed and why. Added to this are memories of promises that were not kept, of decisions that were experienced as unfair, of questions that were never resolved, only postponed. And sometimes a bond with people who have left.
Those who are new bring their own experiences from other teams. Perhaps he or she senses that certain topics are sensitive without knowing why.
None of this is a problem from the outset. Much of it is valuable. It only becomes difficult when the past has an invisible say in decisions: when a proposal is rejected because it is reminiscent of earlier times, or when someone stays silent because the answer already seems known.
Not working through everything, but knowing what still has an effect
A new start does not require renegotiating every past dispute. That would tie a team to the past rather than free it from it. It does, however, require clarity about what still has an impact today.
A simple distinction helps here. Some things are closed and may rest. Some things are memory and deserve respect above all. And some things are still open: an unclear responsibility, a decision never taken, a disappointment that still determines how much trust someone gives. Only this last part needs clarifying.
Those who make this distinction can do justice to the past without clinging to it. Sometimes one honest sentence is enough: "A number of things were difficult here in the past. We won't pretend that never happened."
Taking care with those who are no longer here
Particular restraint is needed towards people who have left. They can no longer contribute their view. A judgement about people who are absent is quickly made and hardly possible to correct. Anyone who speaks disparagingly about them also hurts those who were close to them.
For managers, this means first of all: say what is changing and what remains, because people fill gaps with assumptions. The reasons for a departure may be confidential. That can be said openly without seeming secretive. And do not devalue what came before with the word "restart". Anyone who has built something up over years can easily hear in it that it counted for nothing.
New people need context, not stories about individuals. Explaining why something is the way it is helps. Sorting people into camps before the first conversation does harm.
Trust does not grow at the team event
After a change, it is tempting to introduce new rules, processes and meeting formats quickly. Sometimes that is right. But if what is open remains unresolved, new rules can easily replace a conversation that nobody wants to have. The article on control and trust pursues a related thought.
Trust tends to grow in small things: when agreements are kept, when disagreement is not punished, when a mistake can be discussed without anyone being exposed. Harmony that only holds as long as nobody raises anything sensitive does not carry far. A team can disagree and still share responsibility, if everyone knows what they stand for together.
Perhaps that is the real question before any new structure: What from the time before still has an effect on us today, even if nobody talks about it? And straight after that: Which of it do we want to take with us deliberately?
Thinking further: How trust, disagreement and responsibility become effective in everyday work is described on the page Collaboration and leadership.
Context: The example is fictitious and does not describe any specific organisation. The article is a reflection, not a method with proven effect, and does not deal with employment law questions.