Chris Fenning shows how to structure a risk in an email using a Goal-Problem-Solution format. State the likelihood and impact: X chance leads to Y result. End with a clear call to action or solution.
So let's say I'm an architect. I see some risks coming along. I know this will impact the project, but I don't know how to articulate that in an email. So what would be your solution to articulate risks in a project in an email?
If I was sending it in an email, again, I'd fall back on goal, problem, solution. And if your organization has a risk format, use that format, but slot it into GPS. Our goal is to do this. The problem is, and then describe the risk using whatever risk structure happens to be there. There is X chance that this may happen resulting in Y. That's one of the formulas. And then go to the solution and say, what are we gonna do about it?
So, the call to action is the key.
Yes. I think this thing is going to happen. I think it's quite likely. Here is the impact. Here's what I'd like to do about it.
How to write a Work email subject line #communicationtips #tips #email #subjectlines
