I got this advice from a product manager I worked with: Lead with the bottom line.
When you want to deliver a message, mention **What is the impact of what I'm about to tell you** before you give context.
Without that crucial piece of information, the person receiving the information will have a harder time knowing which details to focus on about your message.
# Example of not doing this.
> We discovered that there was a bug in one of our workers, and the changes we're doing to calculate recommendations exposed it. This means that the service that checked when all recommendations are finished only worked when they appeared in a certain order, but the new recommendations changed the timing.
> Because of this, we won't be able to deliver the personalization view by this week.
Giving context is helpful, but the order in which these pieces of information are presented doesn't tell me how to process it.
Has there been data loss? Is the service down? Do we need all hands on deck?
# Example of doing this
> We won't be able to deliver the personalization view by this week.
> The reason for this is that we discovered that there was a bug in one of our workers, and the changes we're doing to calculate recommendations exposed it. This means that the service that checked when all recommendations are finished only worked when they appeared in a certain order, but the new recommendations changed the timing.
The change is very small, but already the message is different. Because you start with the "effect", I can properly contextualize the information provided afterwards.