Coaching practices for Colleague Secretly Excluded From Meeting
Describe almost anything you are working through and IX Coach finds the practices whose real-world fit is closest. For Colleague Secretly Excluded From Meeting, these are the strongest matches in the current practice library.
Does this sound like the set of challenges you might be facing?
- I keep quietly blocking off my focus time and saying nothing, and then seething every time a colleague books right over it
- When I quietly decline meetings to protect my focus time it comes across as me being unavailable or standoffish, and I keep having to re-negotiate it one request at a time
- A single meeting scattered through an otherwise open day ruins the whole thing
- Our brainstorms always get hijacked by the same two loud, senior voices while the quieter people
- Someone senior just found out about a change after the fact and was hurt they were the last to know
Practices that may help
- Communicate your theme-day structure to collaborators
Let colleagues know which days are off-limits for meetings so the structure is sustainable, not secret.
Theme Days, Made Practical - Communicate your schedule mode to collaborators
Tell your team when you are in maker mode and what that means for response times.
Maker vs Manager Schedule - Batch meetings into one or two days per week
Cluster all coordination into designated meeting days so the remaining days stay structurally intact.
Maker vs Manager Schedule - Use round-robin turns to equalize contribution
Give everyone a timed, equal turn — it prevents a few voices from dominating and pulls quieter members into the space.
Osborn’s Brainstorming Rules, Made Practical - Inform stakeholders before they ask, not after they complain
I’s are one-way — they receive information; the cost of surprising them is always higher than the cost of telling them.
The RACI Matrix, Made Practical - Get genuine commitment, not false consensus
Teams that avoid conflict often confuse silence for agreement — false consensus is catastrophic for execution.
The Five Dysfunctions of a Team, Made Practical - Appoint an explicit devil’s advocate role
Give one person the formal job of arguing against the plan — making dissent structural, not personal.
Red Teaming: Stress-Testing Plans Before They Fail - Use the talking piece to enforce equal voice
Only the person holding the talking piece speaks — everyone else listens.
The Circle Process (Kay Pranis) - Let the report own the agenda
It’s their meeting — they bring what matters to them, and you adapt to it.
Effective One-on-Ones, Made Practical - Batch all meetings onto meeting days
Route all collaboration, calls, and meetings into dedicated days so they don’t fragment the rest.
Theme Days, Made Practical
Related concerns
- How To Structure A Productive Meeting
Judge a meeting’s productivity by the ratio of Action Steps it generates, not by how engaged or interesting it felt.
Maximize the Action Step ratio in meetings
- How To Support A Colleague Who Finds Meetings Extremely Tiring
Route all collaboration, calls, and meetings into dedicated days so they don’t fragment the rest.
Batch all meetings onto meeting days
- My Boss Wants Me To Attend A Meeting Every Day Before Work Hours
Route all collaboration, calls, and meetings into dedicated days so they don’t fragment the rest.
- My Product Manager Traveling To My City Should I Meet Her In Person
Tell your team when you are in maker mode and what that means for response times.
Communicate your schedule mode to collaborators
- No Meeting Day Policy
Cluster all coordination into designated meeting days so the remaining days stay structurally intact.
Batch meetings into one or two days per week
- Reduce Meetings At Work
Route all collaboration, calls, and meetings into dedicated days so they don’t fragment the rest.
Describe your situation in your own words to search the complete practice library.