Skip to website

The journal · CEO behaviour and usable regional authority

Regional authority remained theoretical while every ordinary question came back to me

A routing review exposed the CEO's role in making delegation ineffective. Moving decisions required clearer authority and a change in my own behaviour, without treating the new route as proof of quality.

The route of a decision can contradict the organisation chart

We had regional leaders, reporting lines and an account of delegated responsibility. A 2025 review of 180 routine commercial decisions showed that 140 had still come to me, while forty were handled regionally. The chart described an organisation capable of local judgement. The observed route suggested a business that continued to seek the CEO's participation in ordinary matters. I needed to examine that difference without assuming it was simply a failure of confidence among colleagues.

Some people wanted reassurance before acting. Others had learned that involving me was the expected way to secure a decision, even when their formal authority appeared sufficient. My own behaviour helped create that expectation. A quick answer from the CEO can feel helpful in the moment while making the next request more likely to follow the same route. If I wanted delegation to become usable, I could not evaluate only what regional colleagues were willing to do.

The review concerned a defined group of routine commercial decisions. It did not establish that 140 decisions had been wrongly escalated under every possible circumstance, nor did it describe all decisions in the enterprise. We needed to understand the nature of the work and the reasons for the routes observed. Some matters appropriately require senior involvement. The aim was not to make the CEO disappear from the business, but to make the intended boundaries credible in practice.

We spent ₹38 lakh on training and clarification of operating authority within board-approved boundaries. That expenditure supported the work of making responsibilities understandable and usable. It was not a measured saving, and it did not transfer statutory duties. Material commitments still followed the appropriate authority. Delegation needed to connect local judgement with the enterprise's responsibilities, rather than treat the reduction of CEO involvement as an objective that could override those obligations.

The organisation chart remained useful, but it was only part of the account. Colleagues also needed to know what a boundary meant in a real decision, when escalation was appropriate and whether their judgement would be respected afterward. Those questions are not answered by assigning a title alone. A regional role becomes meaningful when the person can exercise its authority and understand the consequences, including the circumstances in which the matter belongs elsewhere.

The CEO must practise the delegation she asks others to accept

I had to consider how I responded when an ordinary question reached me. Answering it immediately might solve that individual issue while reinforcing the very dependence we were trying to change. Redirecting it without explanation could feel like withdrawal of support. The useful response needed to respect the agreed authority and help the colleague understand the route. That required a more deliberate habit from me, not merely a new instruction for everyone below the executive team.

Delegation also requires tolerance for legitimate differences in judgement. If the CEO reopens every local decision simply because she would have chosen differently, the organisation learns that nominal authority is conditional on predicting her preference. That does not mean accepting decisions outside the agreed boundaries or ignoring poor reasoning. It means distinguishing a different defensible choice from a failure that needs correction. The distinction matters if regional leaders are expected to contribute judgement rather than act as messengers.

I would want colleagues to explain their reasoning and identify uncertainty without interpreting every question as a request for permission. Discussion can strengthen a decision while leaving its ownership where it belongs. The CEO's experience should remain available, but availability need not become compulsory approval of all routine matters. The organisation has to learn that difference through repeated practice. Otherwise the formal delegation creates an appearance of distributed responsibility while the actual route remains unchanged.

Training and authority clarification were necessary because the issue did not sit entirely in my behaviour either. People need the knowledge and context to use their role responsibly. A boundary that is clear to the person who wrote it may be ambiguous to someone applying it under ordinary commercial pressure. The programme gave us a reason to examine those difficulties. The case does not claim that one expenditure removed every ambiguity or made all future decisions sound.

The board's role also remained distinct. It had approved the boundaries within which operating authority was exercised. My decision to stop becoming the route for certain routine questions did not move statutory responsibility to a regional manager. Nor did it remove the need for appropriate reporting and escalation. A credible account of delegation should preserve those responsibilities while explaining what actually changed in the operating organisation. Otherwise a management story can imply a transfer of accountability it never had authority to make.

A changed route is evidence to examine, not a complete success measure

In a later review of 180 routine commercial decisions, forty-two came to the CEO and 138 were handled regionally. Compared with the earlier equal-sized group, ninety-eight fewer decisions were routed to me. That was a clear observation about the route. It did not establish that the decisions became faster, more accurate or compliant merely because different people handled them. I wanted the improvement in usable authority examined without making the count answer questions it had not measured.

The next enquiries would need evidence about the qualities we wished to understand. Were the decisions appropriate to the authority and circumstances? Did colleagues understand when to escalate? What consequences followed? Those are different from counting who handled a matter. A leader should resist replacing one unexamined habit with one flattering metric. Moving decisions away from the CEO may be part of a healthier organisation, but the route alone cannot establish the quality of the judgement exercised there.

The cost also belongs beside the comparison. ₹38 lakh was spent on the programme; it was not an inferred saving in executive time or a quantified commercial benefit. The story does not need such a claim to be useful. It describes a management problem I helped sustain, a defined response and evidence that the routing changed. Keeping the limits visible allows the account to remain a credible basis for further review rather than a declaration that delegation is now complete.

What I would carry into another leadership setting is the willingness to examine the CEO's place in the pattern she wants to change. Colleagues may be behaving rationally in response to the habits leadership rewards. A different chart will not necessarily alter that experience. Authority becomes real through clear boundaries, capability and the behaviour of the people who could override it. The reviewed route showed progress in our case; continuing scrutiny of judgement and consequences remained part of the work.