In an energy business, a decision rarely stays within the room where it is made.
A regulatory development may change a project assumption. A connectivity issue may affect a timeline. A commercial decision may alter a PPA, financing model or procurement plan. The implications then move across legal, regulatory, finance, commercial, engineering and operations.
Then comes the email. A few paragraphs explain what has been decided and what needs to happen next. The leadership team considers the matter communicated. Instead, the questions begin.
What exactly has changed? Does this apply to our project? Is this final, or are views still being sought? Does it affect what we had already agreed?
A manager starts explaining the email. Another clarification follows. A meeting is called. The sender wonders why a message that seemed straightforward has created so much uncertainty.
It is tempting to blame poor writing or inattentive reading. But many such emails are grammatically clear and factually accurate. The difficulty lies in the distance between what the sender knows and what the recipient has been given to understand.
The sender has the context, but the recipient only has the message.
The context stays with the decision-makers
A consequential decision carries more than its final wording. It has a reason, a history, a sense of timing and a set of assumptions around it. It also contains distinctions that may be obvious to those involved: what has been decided, what remains open, what is changing and what is staying the same.
An email can convey the conclusion without conveying all of those distinctions.
The sender may regard the surrounding context as self-evident because it has been part of the discussion for weeks. The recipient may encounter the issue for the first time through a few paragraphs on a screen.
Hierarchy, timing, and organisational mood can further shape how the message is read. Two people can therefore read the same email and reach different conclusions without either misunderstanding the words. They may simply be supplying different context.
The email has a long way to travel
This is critical when a decision has to move across functions before it becomes action.
Consider a project decision arising from a regulatory development. The leadership team may understand the full reasoning behind it. The email reaches the project team, finance, commercial, legal and regulatory functions, each looking for a different implication.
Does the project milestone change? Does the financial model need to be revisited? Are contractual positions affected? Is any regulatory response required?
The same pattern appears when a project is delayed, a financing decision changes, a commercial position shifts or the business changes its approach to a project.
The decision may be clear at the top, but as it travels, its meaning can become less clear. This is where an internal communication problem starts becoming an execution problem.
More words rarely solve the problem
When an email generates questions, the instinct is often to add more information.
A second email follows with further explanation, qualifications and caveats. But more information can make the message harder to use. Readers skim. Functions focus on what matters to them. A qualification intended to narrow the decision gets missed while an incidental phrase acquires significance.
The issue is less about how much information is provided than whether the right information has been anchored. Three questions are particularly useful:
Why is this happening now?
What changes for me?
What stays the same?
The answers may be obvious to those who made the decision. But they are often much less obvious to those receiving it.
Make intent and boundaries explicit
Before sending a consequential email, establish what kind of message it is. Is it informational, directional, or exploratory?
That distinction becomes important when responding to regulatory developments, project changes, or commercial decisions. A request for views can be mistaken for an instruction. A proposal can start being treated as a decision. A limited project change can be understood as a wider strategic shift.
The boundaries need equal clarity.
What has been decided? What remains flexible? What is still under discussion? What remains unchanged?
When these are left unstated, the organisation fills the gaps itself.
Design the communication before drafting it
For a material internal message, five things should be clear before the first sentence is written:
Decision: What exactly has been decided?
Reason: Why is it being communicated now?
Impact: What changes for the relevant people, projects or functions?
Boundary: What remains outside the decision?
Action: What is expected, from whom, and by when?
There is also a simple test for important communications: give the draft to someone who was not in the decision-making room and ask them what they think it means.
Would they identify the same decision? Understand why it is happening now? Know what changes for their function? Distinguish what is settled from what remains open?
If their answers differ from the sender’s intention, the ambiguity has been found early.
For decisions with several downstream implications, managers cascading the message should have the same core context, boundaries and expected actions. That reduces the need for each layer of the organisation to reinterpret the decision independently.
The question before pressing send
Leaders often assess an email from the sender’s perspective: Is it accurate? Is it clear? Does it contain enough information?
The recipient is working out something else: What is happening? Why does it matter? What does it mean for my role? What do I do next?
A better question before sending a consequential message is:
What conclusions might a reasonable reader draw from this email?
That question shifts the focus from expressing a decision to designing how it will be understood.
In an energy business, an email may take minutes to write while the decision it carries takes months to reach execution, moving through regulatory, commercial, financial, project and operational layers along the way.
The best internal emails carry enough context, intent and boundaries for people to act on the decision itself, rather than on the version the organisation has reconstructed.
How do you ensure that a consequential internal email carries enough context for teams to act without having to reconstruct the decision themselves?
_________________________
Want more insights like this?
Click here to join our WhatsApp Channel for strategic communications insights, leadership perspectives, industry observations, in-depth analysis, and practical communications tips.
_________________________
Also read: When Delegation Fails, Look at What the Team Was Asked to Interpret
Does Flexible Operation Damage Thermal Plants?
When Does a Stakeholder Argument Influence Regulation?
What If Professional Visibility Has Less to Do With Being Seen?