A team can follow every instruction and still make the wrong decision.
Tasks are completed, deadlines are met and reports are submitted, still decisions slow down when circumstances change. Routine matters move upwards for approval, while capable people hesitate to act. Senior leaders become the point through which too many decisions pass.
The problem usually lies in what people understand about the decision they are executing.
In energy and infrastructure businesses, decisions move through regulatory, engineering, procurement, finance and execution teams, over several months or years. By the time an instruction reaches the person acting on it, the assumptions behind the original decision may have changed.
The instruction remains clear, but the situation has changed. Execution then depends on whether people understand the intent behind the instruction well enough to exercise judgment.
Where intent gets lost
Consider a project where the leadership direction is to protect commercial viability within the regulatory framework.
As the decision moves through the organisation, it can become a series of operational instructions: obtain an approval, follow a process, use an established contractual approach, escalate specified issues.
These instructions may all be reasonable, but the problem appears when an issue falls outside them.
A regulatory interpretation changes. A supplier misses a milestone. A stakeholder introduces a new constraint. A commercial assumption no longer holds. A technical problem emerges that was not anticipated when the decision was made.
The team now has to decide. Someone who understands the intended outcome has a basis for making that decision. Someone who has received only the instruction is more likely to seek further direction.
With the passage of time, people become good at following the letter of an instruction while losing sight of the outcome it was meant to achieve. Work remains accurate. Judgment becomes cautious.
That creates dependency. Matters that should be resolved at the working level move upwards. Senior leaders spend time on decisions requiring context rather than authority. Teams hesitate to act outside explicit instructions.
An escalation problem may have started as a communication problem.
Compliance does not establish alignment
Power and infrastructure organisations need controls. Safety procedures, statutory requirements, technical standards, contractual obligations, and regulatory processes often require disciplined adherence. In some situations, strict instruction-following is precisely the right behaviour.
The problem comes when compliance becomes the main evidence that communication has worked. A completed checklist confirms that a process was followed. It does not establish whether the team understands what the process is designed to protect.
That distinction is important when circumstances move beyond those anticipated by the instruction.
A team that understands the underlying intent can assess the change and act within its authority. A team trained primarily to follow instructions is more likely to escalate an unfamiliar situation.
With time, decision-making shifts upwards. Senior leaders become bottlenecks, while people closer to the issue become cautious about exercising judgment.
How instruction-heavy cultures develop
Instruction-heavy cultures usually grow through attempts to control risk. A leader sees a mistake and introduces a control. A template follows. An approval is added. A previous incident becomes a standing instruction.
Each measure may address a genuine risk. People then learn which behaviours feel safe. If exercising discretion attracts more scrutiny than following an instruction, escalation becomes the rational choice.
The organisation sees more escalations and adds more controls. Senior leaders end up carrying decisions that should sit lower in the organisation.
The exposure is greater in infrastructure businesses because decisions rarely involve a single variable. Schedule, cost, safety, regulation, technical feasibility, contractual commitments, stakeholder expectations and long-term asset performance can all shape the same decision.
No instruction manual can anticipate every combination. The reasoning behind the instruction has to travel with it.
Intent needs to be explicit
Intent is more than explaining why a decision was taken.
For a consequential decision, people need to know four things:
- The outcome to protect,
- The boundaries that cannot be crossed,
- The discretion available to them, and
- The circumstances that require escalation.
That is the decision logic around an instruction.
Senior leaders often hold this logic implicitly. Experience tells them which risks are acceptable, which commitments are critical, where regulatory boundaries are firm and which compromises are possible.
Teams do not automatically have that context. If they receive only the conclusion, they are being asked to execute a decision without the reasoning behind it.
This becomes important in long-cycle projects. Assumptions made during planning may change during procurement or construction. Regulatory positions may evolve. Project teams may change. Commercial constraints may emerge.
The original decision-maker cannot resolve every subsequent exception. The reasoning needs to become part of organisational memory.
A concise decision log can record the intended outcome, material constraints, significant trade-offs, decision ownership and escalation triggers. Its value is preserving context when decisions cross functions or teams.
Communication can build judgment
Strategic communication has a role beyond announcing decisions.
When communicating a consequential decision, leaders can explain the reasoning, clarify boundaries, identify acceptable trade-offs, state where flexibility exists, and specify when the decision should be revisited.
Mistakes and near-misses can show teams how the organisation expects judgment to work under pressure.
Project and leadership reviews can reinforce the discipline. Instead of asking only whether an instruction was followed, leaders can examine what decision was made, which assumptions informed it, what changed and whether escalation was necessary.
This builds decision confidence and reduces dependence on permission.
The test comes when circumstances change
Communication reveals its value when the plan stops working as expected.
A project is delayed. A supplier fails to deliver. A regulator takes a different view. A stakeholder challenges an established approach. A commercial assumption changes.
→ Can the team identify what the organisation is trying to protect?
→ Can it distinguish a non-negotiable requirement from an area where adjustment is possible?
→ Can it recognise what falls within its authority and what requires escalation?
These questions matter at functional boundaries.
Regulatory teams protect compliance. Procurement protects contractual position. Finance protects cost discipline. Engineering protects technical integrity. Project teams protect schedule and delivery.
Each function can perform its role correctly while the larger objective becomes fragmented. Shared intent gives those functions a common reference point.
The leadership discipline
The answer is not to remove instructions or push every decision downward. Leaders still need clear controls and accountability. They also need to communicate the logic that allows people to use those controls when circumstances change.
When delegating an important decision, four elements should be clear:
→ what outcome matters,
→ what must remain protected,
→ where the team can exercise judgment, and
→ when the matter comes back to leadership.
That logic should appear consistently in decision notes, meetings, reviews, and performance conversations.
With time, teams become better at recognising patterns, assessing trade-offs and distinguishing genuine exceptions from routine issues. Escalations become more relevant. Senior leaders recover time for decisions that genuinely require their involvement. Decision-making becomes less dependent on a handful of individuals.
The question for a leader therefore extends beyond whether people did what was asked. It is whether they understood what the decision was trying to achieve well enough to make a sound call when circumstances changed.
In a sector shaped by regulation, large capital commitments, long project cycles, and changing stakeholder expectations, circumstances will inevitably move beyond the assumptions behind an instruction.
The organisation’s resilience depends on what people know beyond the instruction itself.
Communication has succeeded when people can make a sound decision without waiting for another instruction.
That is when intent becomes organisational capability.
What tells you that your teams understand the intent behind a decision rather than simply following the instruction?
_________________________
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: How BRICS Is Reframing the Global Energy Conversation
When Incentives Speak Louder Than Leadership