Before you coach a new team, build trust.
You may see improvement opportunities very quickly as a new Scrum Master.
That does not mean the team is ready to hear them.
Good coaching depends on trust.
And trust takes a little time.
Coaching without trust feels like interference
You might have useful ideas.
You may even be right.
But if people do not know you yet, early advice can land badly.
It can feel like:
- judgement
- process policing
- someone telling them how to work before earning the right
That is why listening comes first.
Start with people, not process
Before you try to coach the team, get to know the people in it.
Make time for short one-to-one conversations.
Ask things like:
- What is it like to work in this team just now?
- What helps you do your best work?
- What has been frustrating recently?
- What do you wish changed?
- What is already working well?
The goal is not to fix things in the conversation.
The goal is to help people feel heard.
Feeling heard changes the relationship
When people feel listened to, they relax.
They become more open.
They speak more honestly.
They are more willing to reflect.
That is the ground coaching needs.
Not authority.
Not a framework.
Not a clever retrospective format.
Trust first.
Coach later, with the team
Once trust begins to grow, coaching becomes easier.
Now you can help the team:
- reflect honestly
- name problems openly
- explore better ways of working together
That is very different from arriving with answers.
A simple rule
Do not rush to be the expert.
First become someone the team can trust.
That is often the real start of effective Scrum Mastery.
Reflection
This week, in one conversation with a team member, try to do less advising and more listening.
Leave a little more space.
Ask one follow-up question.
Notice what changes.
