In large energy and infrastructure projects, execution problems can begin in meetings where everything appears to have gone well.
Priorities are agreed, responsibilities assigned, and decisions recorded. Weeks later, the procurement team is working to one set of assumptions, the project team is planning around another, and the regulatory team has a different understanding of what must happen before the next milestone.
By then, each team may have acted diligently, committed resources and reported progress against what it believed had been agreed. Correcting the divergence can mean revised schedules, additional expenditure and difficult conversations with contractors, regulators and other stakeholders.
In India’s energy sector, where project delivery depends on multiple approvals, technical dependencies, and long implementation cycles, misunderstandings can travel a considerable distance before they surface. The problem begins when people leave the same meeting believing they share the same understanding.
When familiar words carry different meanings
Assumptions are essential to organisational life. They draw on experience, help people interpret incomplete information and allow work to proceed without constant clarification.
The risk arises when an assumption held by one person becomes the basis for decisions across several functions, each operating under different pressures and responsibilities.
Consider the word readiness in a project meeting. Senior management may use it to express confidence in a commissioning date, while the engineering team understands it in terms of equipment and technical preparedness. Finance may focus on expenditure approvals, while the regulatory team considers outstanding clearances. Agreement on the word establishes little about whether the conditions for proceeding are understood consistently.
As work advances, each function builds on its interpretation. Procurement commitments depend on delivery schedules, which in turn depend on approvals and equipment availability. An unexamined assumption can thus become embedded in a chain of decisions, making its original ambiguity harder to identify.
Experience can compound the problem. Senior leaders develop an intuitive understanding of priorities, constraints and acceptable risk. What seems obvious to them may be unfamiliar to those responsible for implementation.
An instruction to accelerate delivery, for instance, may be interpreted as permission to compress timelines, even when the leader intended the team to find efficiencies within existing technical and regulatory safeguards.
Hierarchy makes clarification harder. Employees may hesitate to question a direction for fear of appearing inexperienced or challenging a senior colleague’s judgement. Silence can therefore indicate agreement, uncertainty or deference, even as leaders interpret it as confirmation that their instructions have been understood.
Why accountability reviews can miss the cause
When deadlines slip or outcomes disappoint, management reviews typically examine performance, responsibilities and corrective action. These remain essential, but their effectiveness depends on identifying the actual cause of the deviation.
A project team may prioritise speed, engineering may protect equipment reliability, and the regulatory team may seek to minimise compliance exposure. Each could be acting consistently with its own understanding of organisational priorities.
A review focused exclusively on individual performance may overlook the differences in interpretation that shaped those decisions.
Tighter controls can improve reporting while encouraging defensive documentation and reluctance to exercise judgement. Leaders receive more information about deviations, but the assumptions influencing decisions remain unexamined.
A more useful review establishes how the task was understood, which constraints people considered binding, what trade-offs they believed they could make and whether competing priorities had been reconciled. This helps distinguish an execution failure from a gap in the original direction or its interpretation, allowing leaders to choose the appropriate corrective action.
Making understanding visible through strategic communication
The remedy begins when a consequential decision is communicated. Leaders need to explain the intended outcome, the reasoning behind its priority, the constraints that must be respected, and the discretion available to those responsible for delivery.
Assumptions about capacity, project readiness, acceptable risk and external dependencies deserve particular attention when they affect expenditure, schedules or regulatory obligations.
Teams also need to know when changed circumstances require an earlier decision to be reconsidered, when they can exercise judgement and when they must seek further direction.
This requires an environment in which employees can question assumptions and flag conflicting instructions without fearing that they will be judged as inexperienced or obstructive. Leaders establish that environment through their responses when someone raises an inconvenient concern or identifies a weakness in the plan.
A practical test is to ask the teams responsible for a major priority to explain, independently, what success requires, which constraints are non-negotiable and where they have discretion. Differences in their answers can reveal risks that progress reports and meeting minutes may conceal.
Leaders can then resolve conflicting interpretations, clarify decision rights and agree on how changes in circumstances should be handled before misunderstandings become costly commitments.
This is where strategic communication becomes integral to execution. It helps ensure that a decision’s intent, reasoning and boundaries remain clear as it moves through the organisation, enabling people to act consistently even when the person who issued the instruction is unavailable.
Clarity must keep pace with scale
Informal coordination can work well in small organisations, where people interact frequently and leaders remain close to daily decisions.
As organisations expand across locations, specialist functions and management layers, shared context becomes harder to maintain. External stakeholders multiply, regulatory conditions evolve, and the distance between a strategic decision and its implementation grows.
Leaders must therefore articulate what experience has taught them to take for granted, encourage teams to surface uncertainty, and resolve conflicting priorities early. Formal processes remain important, but their effectiveness depends on whether people share an understanding of the intended outcome and the boundaries within which they must operate.
For India’s energy and infrastructure businesses, this discipline becomes especially valuable during periods of transition, when new technologies, changing commercial conditions, and regulatory dependencies challenge established assumptions.
Leaders cannot eliminate uncertainty, but they can ensure that assumptions are examined and that teams understand how to act when circumstances change.
A decision’s effectiveness depends on the understanding that guides its execution.
Establishing that understanding is a leadership responsibility, beginning when the decision is communicated and continuing until the people implementing it can exercise sound judgement without direct supervision.
How do you establish that teams have understood a decision in the same way, rather than simply agreed to it?
_________________________
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: What Gets Lost Between the Ground and the Boardroom