9 minutes
Inviting voices that hierarchy has taught to wait A team practice built around speaking up unprompted can quietly silence colleagues shaped by higher power-distance norms. Structured invitation fixes the practice, not the person.
What you’ll be able to do Redesign a team meeting practice so that colleagues shaped by higher power-distance norms have a structured way to contribute, without requiring them to adopt an unprompted-speaking-up style that feels culturally uncomfortable. Compare the responses to this question and explain your choice: What is the best way to address this? Document a next step for Inviting voices that hierarchy has taught to wait: In your next team meeting, build in one explicit, named turn for input from a colleague who typically waits to be asked. Structure removes the barrier hierarchy creates In cultures with higher power distance, speaking up unprompted — especially in front of authority or in a group setting — can feel presumptuous, even when the person has real expertise to offer. A meeting practice that relies on people volunteering their views unprompted will systematically favor colleagues who are comfortable with that norm, and miss colleagues who are simply waiting for an appropriate, explicit invitation to speak.
The fix is structural, not personal: build a specific turn into the meeting — round-robin, a named question, a request for written input beforehand — so that speaking is invited rather than assumed to be volunteered. This gives every colleague, regardless of their comfort with unprompted speech, a real opening to contribute.
Structured invitations that work across this difference Use a round-robin format so every person gets an explicit turn, rather than relying on volunteers.
Name the person directly with a specific question: “[Name], what's your view on the timeline?”
Offer a written or pre-meeting channel for input from colleagues who prefer to prepare before speaking in a group.
Invite explicitly, do not wait for volunteers What you can change You control whether your meeting format relies on volunteered input or builds in structured turns for everyone.
What to watch for Do not conclude that a quiet colleague has less to contribute before you have tried a structured way of inviting their input.
Your next step In your next team meeting, add one specific, named turn for input from a colleague who typically waits to be asked.
Building structured invitation Why might a capable colleague stay quiet in meetings?
Higher power-distance norms can make speaking up unprompted feel presumptuous, regardless of the quality of the colleague's ideas.
What is the structural fix?
A round-robin, a directly named question, or a pre-meeting written channel — any format that invites input explicitly rather than assuming it will be volunteered.
What should the fix never require?
That the colleague change their comfort level with speaking up unprompted in order to be heard.
Carry this forward A team norm that rewards speaking up unprompted can systematically miss the input of colleagues who were raised to wait for an explicit invitation before addressing authority.
A structured, round-robin or directly-invited turn to speak removes the barrier without asking anyone to abandon their comfort with hierarchy.
The goal is a meeting practice that surfaces every colleague's expertise, not a request that quieter colleagues perform assertiveness that does not reflect them.
A scenario decision about redesigning a team meeting to include a colleague who rarely speaks unprompted, and a knowledge check on structured invitation as the fix.
In your next team meeting, build in one explicit, named turn for input from a colleague who typically waits to be asked.
Browse and download only. Course notes are not typed or saved on this page.
Reset this lesson
Previous lesson Back to course Participation and course completion in this program do not count toward DHS-required training credits unless management, a director, or DHS leadership expressly approves an exception.
