Inviting people to speak up is only the beginning. What happens after a concern is raised shows colleagues whether their contribution is taken seriously. Silence alone does not tell a manager what people think.
A familiar workplace challenge
Illustrative scenario: a maintenance team repeatedly hears “we have already discussed that” when it raises a minor process problem. At the next meeting nobody comments. The manager interprets the silence as agreement, although the issue remains unresolved.
1. Make the invitation specific and optional
Instead of asking “Any problems?”, ask which step is unclear or which assumption needs checking. Offer more than one contribution route where appropriate, such as a written note or follow-up conversation. Do not force public disclosure.
2. Clarify the concern before defending the decision
Ask what was observed, what the possible impact is and how urgent the issue may be. Acknowledge the contribution without promising an outcome you cannot deliver. Some concerns require formal or urgent reporting rather than a team discussion.
3. Show what happened next
Name the response owner and next update. Explain what can be shared and protect private information. Where no change will be made, explain the reason within your authority. A visible response helps people understand the process even when their preferred solution is not adopted.
Words to practise
“Thank you for raising that. What did you observe, and what effect is it having? I will confirm who should review it and update the team on the process. If this needs a formal reporting route, we will use that route.”
Try this at work
At the next routine meeting, invite one low-risk process concern and agree when the team will hear the response. Check whether that update actually happens.
Reflect on the outcome, turn the useful step into a repeatable routine, and share the learning with a colleague. This is the Ramology cycle of Reflect, Automate and Multiply.
Build the skill in Speak Up, Step Up
This one-day workshop uses the VOICES framework. Meeting-transcript analysis, invitation practice, issue triage and a speak-up huddle. Fictional scenarios and optional personal disclosure support participation. Feedback checks listening and follow-through.
Learning focus: Identify participation patterns without assuming motives. Demonstrate an open invitation and non-defensive response. Describe a concern using evidence, impact and urgency.
