A junior technician sees something, has a question, or disagrees with the approach but stays quiet around senior employees or supervisors.
Silence is not proof of agreement
Junior employees often calculate the social risk of speaking before they calculate the technical value of the observation. If previous questions were mocked or dismissed, silence can become rational.
A leader should notice who is never speaking, not only who speaks most.
Ask for the observation before the conclusion
Instead of putting the junior technician on the spot with "What do you think is wrong?", ask what they noticed, what changed, or what measurement concerns them.
That makes it easier to contribute evidence without pretending to have senior-level certainty.
Protect questions without rewarding guessing
Psychological safety should not mean every idea is treated as equally correct. Teach junior people to bring observations, logic, and evidence.
They should learn that being wrong after thoughtful reasoning is acceptable. Careless guessing is different.
Use senior technicians deliberately
Strong senior people can either amplify learning or shut it down. Set expectations that questions from developing technicians are part of building the team.
Do not pair a junior employee with a senior person who routinely humiliates learners and then blame the junior person for failing to develop.
Useful language
What good looks like
Junior technicians learn to contribute observations and reasoning earlier, senior people help build capability, and the team gets more information before decisions become failures.