Coaching & Workshops
When people do not raise problems early you find out about them late and expensively. This session works on why your team stays quiet and what a manager has to do differently, which is usually more than they expect.
Why it matters
People are quiet because at some point speaking up cost someone something. Maybe an idea got dismissed, maybe a problem got treated as a complaint, maybe someone was visibly punished for being right at the wrong moment. The team learned, and the learning outlasts whoever taught it.
The cost is that you get the news late. Quality problems, slipping schedules, a customer about to leave, and a resignation you did not see coming all arrive as surprises in teams where raising things early is not safe.
What the session covers
In the room
What happened here before. Teams are quiet for specific, local reasons, and generic training does not touch them.
Interrupting, solving too fast, or reacting badly under pressure. Small habits with large effects.
Ways of running a meeting that make it easier to raise a problem than to sit on it.
Signs you need this
The clearest signal is a gap between what people say in a meeting and what they say in the corridor. Everyone notices it and it is rarely named.
If two or three of these are true you are past the point where it resolves on its own. None of them are unusual, and all of them are cheaper to fix than to wait out.
Sound familiar
Afterward
Which is the entire commercial argument. Late information is what makes small problems expensive.
Specific structural adjustments that make raising something the path of least resistance.
Usually the single biggest variable, and usually invisible to them until someone says it out loud.
How it runs
An intact team with its manager. We do preparatory work with the manager first, because they are frequently part of the cause and need to hear that privately.
Sessions run on site or virtually, and they are built around situations attendees bring rather than case studies from a textbook. You get a fixed fee before we start, and the person who scopes it is the person who delivers it.
Practicalities
Questions
That is the underlying idea, but we avoid running it as a concept session. It works when it is about this team and what actually happened here.
Yes, and that is often the delicate part. We usually do preparatory work with the manager first, because they are frequently a cause without knowing it.
Then the session has told you something important. We often pair it with an anonymous pulse survey beforehand so there is data in the room.
Half a day with the team, plus a preparatory session with the manager.
Not on its own. If there is genuine misconduct this is the wrong instrument and we will tell you.
Then we would not run the team session yet. A session where the manager reacts badly to the first honest thing said sets the team back a year.
A pulse survey gives you the data anonymously and is a good precursor. But data does not change a team's behavior on its own. The conversation does.
Yes, though we would want to understand the context first, and there are topics that belong in a different forum.
Related
Get the data before the session so the room has something to react to.
Engagement Surveys →Sometimes the silence is about two specific people.
When Two People Will Not Work Together →Senior-led, delivered by the person you meet
Tell us what is happening and we will scope the right approach. No obligation, and we will say if one of the others fits better.
Tell us what is going on