At Red Hat, we default to open. That means sharing as much information as possible, while still protecting confidentiality and compliance regulations. Here are ways to make sure that, when communicating a change, the change will be well-received in the open organization.

Are we being transparent? To figure that out, ask yourself the following questions:

• How much information can be shared with associates at this time?

• If there’s something that can’t be shared now, be prepared to explain why as well as if and when more information will become available.

• When communicating a business change, make sure to use the Open Decision Tool. This will allow you to:

  • Solicit and incorporate feedback as well as demonstrate changes you made based on that feedback.

  • Explain the rationale for any decisions you’re communicating.

  • Provide a summary of what factors and input went into those decisions.

How are we going to solicit feedback?

• Communication at Red Hat is as much about generating a dialogue and engaging with others as it is sharing information. The Open Decision Tool covers strategies for doing this, but here are some of the ways to include feedback mechanisms in your communications:

  • Start early. The feedback process can be a back-and-forth, and that takes time. Account for that when planning around check-ins and deadlines.

  • Figure out who you’ll need feedback from. This should be a smaller group of the audience and key stakeholders. Make sure this group is diverse and a true reflection of your audience.

  • Announce how you will gather feedback and specify a deadline for feedback so you can incorporate any changes before finalizing the communication.

  • You do not have to use all the feedback you receive, but be prepared to change messaging appropriately if there are valid reasons and to explain why if there are recommendations you do not use.

  • Highlight changes made in response to feedback.

​