Coaching practices for Team Communication Norms
Describe almost anything you are working through and IX Coach finds the practices whose real-world fit is closest. For Team Communication Norms, these are the strongest matches in the current practice library.
Does this sound like the set of challenges you might be facing?
- My team has finally figured out how to work together, but it all lives in everyone’s heads
- When someone on my team drops the ball, everyone just waits for me to be the one to say something
- Everyone on my team is quietly playing for their own scoreboard
- I’ve told my people a hundred times they can disagree with me, but they still don’t
- On my team nobody will admit they’re stuck or wrong or don’t know something
Practices that may help
- Norming: codify agreements in writing
What the team has figured out informally needs to become explicit so it survives personnel changes.
Tuckman’s Stages of Team Development - Create a culture of peer-to-peer accountability
Teams that only hold each other accountable through the manager haven’t built real accountability at all.
The Five Dysfunctions of a Team, Made Practical - Align around collective results, not individual status
Teams fail when members prioritize their own visibility or department’s success over the shared goal.
The Five Dysfunctions of a Team, Made Practical - Teach speak-up skills, not just encourage speaking up
Give team members specific language for raising concerns, not just permission to raise them.
Psychological Safety in Teams - Build vulnerability-based trust
Teams that can’t admit weakness, mistakes, or ignorance to each other cannot genuinely collaborate.
The Five Dysfunctions of a Team, Made Practical - Create a communication batch protocol for your team
Agree with collaborators on expected response windows so batching doesn’t create perceived unavailability.
Task Batching: Grouping Similar Work to Cut Switching Costs - Default to asynchronous communication
Treat real-time communication as the exception, not the default — most things do not require an immediate response.
Designing a Calm Company (Fried & Hansson) - Create safety for experimentation and honest challenge
Make it safe to raise problems, test new ideas, and disagree — before expecting the team to transform.
Transformational Leadership, Made Practical - Set clear, single-point accountability
One named owner, an agreed standard, and a check-in cadence set up front — not nagging.
Effective Delegation, Made Practical - Invite input explicitly and specifically
Ask for candid input on a specific topic — not "any thoughts?" but "where do you see this plan failing?"
Psychological Safety in Teams
Related concerns
- How To Sustain Team Norms
What the team has figured out informally needs to become explicit so it survives personnel changes.
Norming: codify agreements in writing
- Team Norms Document
What the team has figured out informally needs to become explicit so it survives personnel changes.
- Belonging In Team
Make every team member feel valued and accepted as a human being before expecting performance.
Establish inclusion safety — belonging without conditions
- How To Get Team To Speak Up
Give team members specific language for raising concerns, not just permission to raise them.
Teach speak-up skills, not just encourage speaking up
- How To Rebuild Team Cohesion
Teams fail when members prioritize their own visibility or department’s success over the shared goal.
Align around collective results, not individual status
- Structured Communication Team
Treat real-time communication as the exception, not the default — most things do not require an immediate response.
Default to asynchronous communication
Describe your situation in your own words to search the complete practice library.