In practice, corporate governance and compliance work often require communication across multiple departments. Where a matter involves statutory requirements, approvals, filings, timelines, or supporting information from other teams, it is often necessary to explain the background clearly so that the issue can be properly understood.
However, one practical difficulty that sometimes arises is that background explanation may be perceived differently from how it was intended.
What was meant simply as context may be read as instruction. What was intended to explain the basis of a requirement may be interpreted as telling another department how to do its work. Once that perception arises, the issue can quickly move away from the substance of the matter and become one of tone, sensitivity, or internal friction.
This is a practical issue that is often understated, but it can have real implications for how governance and compliance work is carried out within an organisation.
The intention may be explanatory, but the perception may be different
In many cross-functional matters, it is necessary to explain why something is required.
This may include setting out the background to a statutory obligation, the reason a particular timeline must be observed, the basis on which certain documents are needed, or the governance context behind a requested action. In such cases, explaining the background is often part of doing the work properly. Without context, the recipient may not understand why the requirement exists or why the matter needs attention.
However, in practice, not everyone reads such explanations in the same way.
A message that is intended to clarify the background may be received as direction. A sentence that is meant to explain the reason for a step may be taken as telling another team how to perform its own function. Once that happens, the substance of the issue may become secondary to the perceived tone of the communication.
This does not always mean that the explanation was wrong. It means that in internal corporate communication, perception can sometimes carry as much weight as intention.
The issue is not always the work itself
One of the more difficult aspects of this situation is that the underlying work may not be wrong.
The issue may not be that the person failed to discharge their responsibilities, misunderstood the requirement, or gave incorrect information. Instead, the difficulty may arise because others were unhappy with the way the matter was communicated, even where the communication was intended only to set out the relevant background.
This creates a practical tension.
Those responsible for governance, compliance, legal, or company secretarial matters often need to explain the basis of a requirement in order to move the matter forward properly. Yet doing so may occasionally be perceived as overstepping, particularly where another department is sensitive to anything that appears to comment on its role or process.
As a result, the person trying to ensure that the matter is understood correctly may find themselves criticised not for the substance of the work, but for how the explanation was received.
Why this is a broader organisational issue
At first sight, this may seem like a minor communication problem. In reality, it reflects a broader organisational issue.
In many companies, compliance and governance work depend on cooperation across functions. This means that those coordinating such matters must often explain requirements to teams that do not necessarily approach the issue from the same perspective. What may seem obvious from a governance or statutory standpoint may not appear so from an operational standpoint.
In that context, communication becomes particularly sensitive.
If the organisation is not accustomed to dealing with governance and compliance matters in a collaborative way, explanations may be misread as instruction, and context may be mistaken for interference. This can lead to avoidable friction and distract from the real issue, which is whether the matter has been understood and handled properly.
The problem is therefore not always what was said, but the organisational environment in which it was received.
Why context still matters
Although this issue is real, it does not mean that context should be omitted altogether.
In governance and compliance work, context often matters precisely because requirements do not arise in isolation. A request for information, action, or documentation is usually linked to a legal, procedural, contractual, or governance basis. If that basis is not explained, the request may be seen as arbitrary, unnecessary, or lacking foundation.
For this reason, providing background can be an important part of responsible communication.
The challenge is not whether context should be given, but how it should be framed so that it supports understanding without being perceived as directing another function’s work unnecessarily.
This is often where judgment is required.
The practical lesson: substance and tone both matter
One practical lesson from this type of experience is that in cross-functional communication, being correct on substance may not be enough.
Tone, framing, and positioning also matter.
An explanation that is factually accurate may still cause difficulty if it is expressed in a way that the recipient perceives as intrusive, prescriptive, or unnecessarily instructive. In practice, it may therefore be helpful to distinguish more clearly between:
- providing background for context;
- identifying the basis of a requirement; and
- directing another function on how to discharge its role.
Even where the intention is only to explain, the language used should make that clear.
This may mean framing the message by stating that the background is provided for context only, or clarifying that the purpose is to explain the basis of the issue rather than to direct the receiving team on how to perform its own responsibilities.
Why this matters for governance work
This issue matters because governance and compliance work often sits at the intersection of substance and communication.
The work cannot be done properly without explaining the basis of requirements. At the same time, it cannot be carried effectively across the organisation if the communication consistently creates resistance or defensiveness.
For this reason, those working in governance-related functions often need to do more than understand the rules. They also need to develop the judgment to communicate those rules in a way that preserves clarity without unnecessarily triggering internal friction.
That is not always easy, particularly where the issue itself is sensitive or where other departments are already under pressure. Nevertheless, it is part of the practical reality of the role.
A more balanced approach in practice
A more balanced approach is not to avoid context, but to communicate it with care.
Where background needs to be given, it should be expressed in a way that supports alignment rather than sounding like instruction. The purpose should remain clear: to explain why the issue matters, what requirement is engaged, and what needs to be addressed, without overstepping into another department’s operational space unless that is genuinely necessary.
At the same time, organisations should also recognise that context-setting is often part of responsible governance communication. Not every explanatory email is an attempt to instruct. In many cases, it is simply an effort to ensure that all parties understand the issue on the same basis.
A more mature organisational approach would recognise both sides of this. The sender should communicate carefully, but recipients should also distinguish between context and control.
Final thoughts
In cross-functional corporate work, the issue is not always whether the message was wrong. Sometimes the real issue is that context was mistaken for instruction.
This can be a difficult position for governance and compliance professionals, particularly where they are required to explain the basis of a matter in order to move it forward properly. What is intended as background may be perceived as direction, and the focus may then shift from the substance of the issue to the tone of the communication.
For this reason, effective governance communication requires both clarity and judgment. The substance must be right, but the framing also matters.
In practice, explaining the background to a requirement should not automatically be treated as instructing another department how to do its work. Sometimes, it is simply part of ensuring that the issue is properly understood.
Civernyx 
Leave a comment