Good meetings do not depend on the fastest or most confident speakers volunteering every useful idea. When status, hierarchy, personality, language or group dynamics make speaking up costly, relevant information can remain invisible even when everyone in the room technically had an opportunity to contribute.<\/p>\n
The goal is not to force quieter people to speak more. It is to design the meeting so that useful information can surface through more than one route and so that disagreement does not require unusual confidence.<\/p>\n
Speaking up is not simply a personality choice. Research on psychological safety and employee voice shows that hierarchy, interpersonal risk and expectations about how leaders will respond can affect whether people raise concerns or alternative views.<\/p>\n
A systematic review of interventions targeting psychological safety, speaking up and voice found mixed results across 14 interventions. Educational activities alone did not consistently change deeply rooted speaking-up behaviour, which is a useful warning against treating one facilitation technique as a universal fix.<\/p>\n
Source: O’Donovan & McAuliffe, systematic review of psychological safety, speaking up and voice interventions<\/a><\/p>\n Amy Edmondson’s work on psychological safety similarly emphasises the role of leader behaviour: asking genuine questions, signalling that other people’s information is needed and responding constructively when someone brings bad news or disagreement.<\/p>\n Source: Harvard Business School Working Knowledge, psychological safety and inviting voice<\/a><\/p>\n \u201cSupplier update\u201d tells participants the topic. \u201cWhat has changed in supplier performance since last week, and what risk needs a decision today?\u201d tells them what information the meeting needs.<\/p>\n Specific questions let people prepare before the social pressure of the meeting begins. They are particularly useful when participants need time to check data, translate technical information into plain language, or formulate a view in a second language.<\/p>\n If the chair announces a preferred answer first and then asks \u201cany objections?\u201d, disagreement can carry unnecessary interpersonal cost.<\/p>\n For decisions where independent information matters, collect views before the senior person’s position becomes the obvious reference point. Options include:<\/p>\n This is not about pretending every view has equal expertise. It is about hearing relevant information before authority shapes what feels safe to say.<\/p>\n \u201cSara, what are you seeing from the warehouse side?\u201d can make contribution easier. \u201cSara, you haven’t said anything, what do you think?\u201d can feel like public evaluation.<\/p>\n A useful invitation explains why the person’s perspective matters. Ask for information they are positioned to know, and give people a way to say they need to check before answering.<\/p>\n When every tentative idea is immediately challenged, participants learn that only polished ideas are worth voicing. For exploratory decisions, create a short generation phase before debate.<\/p>\n That might be two minutes of individual note-taking, a shared document or a round in which people name risks without solving them yet. Evaluation comes afterward.<\/p>\n A structured round is slower than free conversation, but speed is not always the objective. For safety, operational risk, major changes or decisions that affect several functions, asking each relevant role for a view can expose information that would otherwise remain outside the dominant conversation.<\/p>\n The chair should still distinguish expertise from preference. A structured round guarantees an opportunity to contribute, not automatic agreement with every contribution.<\/p>\n Consider a hypothetical ten-person operations review where the manager and two senior staff dominate discussion while warehouse employees rarely volunteer observations.<\/p>\n The manager redesigns the meeting:<\/p>\n The purpose of this scenario is not to claim a measured percentage improvement. It shows how meeting design can reduce dependence on spontaneous speaking confidence.<\/p>\n Hierarchy can make disagreement harder in many organisations, but it should not be reduced to a stereotype about a country or generation.<\/p>\n If junior staff rarely challenge senior people, redesign the process instead of telling them to \u201cbe more confident.\u201d Ask the most senior person to speak later, collect independent views first, invite written concerns and visibly reward useful dissent when it appears.<\/p>\n Research on speaking-up interventions repeatedly points to hierarchy and psychological safety as system-level factors, not merely individual communication skills.<\/p>\n Language, cultural norms and previous workplace experience can influence how comfortable someone feels interrupting, disagreeing or speaking without preparation. But nationality does not reliably predict an individual’s behaviour.<\/p>\n Use structure that works across different preferences:<\/p>\n For the broader communication context, see our guide to cross-cultural communication skills for international teams<\/a>.<\/p>\n Do not measure success by how many people spoke. Watch whether the quality and range of information improves.<\/p>\n Useful questions include:<\/p>\n Psychological safety is damaged quickly when leaders ask for candour and then punish the messenger.<\/p>\n Inclusive participation is easier when the meeting structure reduces the cost of speaking. Leaders often try to solve silence in the room by asking, \u201cDoes anyone have anything to add?\u201d That question comes too late. By then the agenda, hierarchy and early speakers may already have defined what feels safe or useful to say.<\/p>\n Start by sending the actual questions the meeting needs to answer. People who prefer to process information before speaking can arrive with a view rather than constructing one while more vocal colleagues are already debating. Where the issue is complex, a short pre-read can be more inclusive than a dense presentation delivered live.<\/p>\n Inside the meeting, give participants a brief period to think or write before discussion begins. This is especially useful for risk reviews, lessons learned and problem-solving meetings because it reduces the tendency for the first plausible answer to dominate.<\/p>\n When hierarchy is strong, consider asking the most senior person to speak later. Their view still matters, but delaying it can prevent other participants from simply aligning with an early executive opinion. Facilitators can also invite functions in a purposeful order, for example operations before finance, or local teams before headquarters, where those perspectives are easily overshadowed.<\/p>\n Direct invitations should be specific and optional rather than performative. \u201cMaya, you work closest to the hand-off. What are we missing operationally?\u201d is more useful than abruptly asking a quiet person to \u201csay something.\u201d The invitation gives a reason why their perspective matters.<\/p>\n Finally, track whether the meeting actually changed. Useful signs include fewer repeated issues, clearer owners, more dissent raised before decisions, a wider distribution of contributions and fewer decisions reopened because an important perspective was absent. The goal is not equal airtime. It is better information and better decisions.<\/p>\n The previous version used an unsupported 27% versus 9% alignment statistic and presented a fictional operational scenario as though it were a real regional retail-company case. Those claims have been removed. The revised example is explicitly illustrative, and the recommendations are grounded in research on psychological safety and employee voice.<\/p>\n Evidence-informed meeting practices that make useful input easier to surface through preparation, structured participation, psychological safety and multiple ways to speak up.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","footnotes":""},"categories":[404],"tags":[],"class_list":["post-9475","post","type-post","status-publish","format-standard","hentry","category-professional-development"],"_links":{"self":[{"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/posts\/9475","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/comments?post=9475"}],"version-history":[{"count":5,"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/posts\/9475\/revisions"}],"predecessor-version":[{"id":10763,"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/posts\/9475\/revisions\/10763"}],"wp:attachment":[{"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/media?parent=9475"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/categories?post=9475"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/tags?post=9475"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}1. Send questions, not only agenda headings<\/h2>\n
2. Ask for input before the most senior view sets the frame<\/h2>\n
\n
3. Use direct invitations without turning them into tests<\/h2>\n
4. Separate idea generation from evaluation<\/h2>\n
5. Use structured rounds when missing a perspective would be costly<\/h2>\n
An illustrative meeting redesign<\/h2>\n
\n
What to do when hierarchy affects voice<\/h2>\n
Multicultural teams: avoid turning culture into a diagnosis<\/h2>\n
\n
What leaders should watch after changing the meeting<\/h2>\n
\n
Design participation into the meeting before it begins<\/h2>\n
Questions in advance<\/span><\/div>\n
Silent reflection<\/span><\/div>\n
Structured input<\/span><\/div>\n
Test the dominant view<\/span><\/div>\n
Owner and next step<\/span><\/div>\n<\/div>\n<\/figure>\nA practical checklist<\/h2>\n
\n
What this article no longer claims<\/h2>\n
Sources<\/h2>\n
\n