See ‣

Ask for opinions often, even when everything is OK, to proactively collect new information for making better decisions and to explore the opportunity space which you may be blind of.

• "I'm doing this. What should I do? What would you do?"
• "I'm thinking about this idea. What would you recommend?"

In meetings and after presentations, ask for questions explicitly. Look at non-verbal queues.

Share notes before publishing.

A team leader reduces the ‣ by proactively inviting feedback.

Related:

• Be sceptical to your own opinions; Your knowledge are just guesses
• Ask for help instead of offering it
• ‣

References

‣

‣

https://www.kitchensoap.com/2012/10/25/on-being-a-senior-engineer/ Mature engineers seek out constructive criticism of their designs. Every successful engineer I’ve met, upon finishing up a design or getting ready for a project, will continually ask their peers questions along the lines of:

• “What could I be missing?”

• “How will this not work?”

• “Will you please shoot as many holes as possible into my thinking on this?”

• “Even if it’s technically sound, is it understandable enough for the rest of the organization to operate, troubleshoot, and extend it?”

  This is because they know that nothing they make will ever only be in their hands, and that good peer review is what makes better design decisions. As it’s been said elsewhere, they “beg for the bad news.”

‣ Feedback: ask for questions in meetings and after presentations. Look at non-verbal queues.

http://www.morebeyond.co.za/navigate-complexity-three-habits-of-mind/ Cultivate diverse feedback mechanisms and networks — avoid echo chambers