Structured Empowerment: How CEOs Give Teams Authority Without Losing Accountability

There is an uncomfortable truth about empowerment: many leaders want teams to take ownership only when they make the decision the leader would have made. That is permission dressed up as empowerment.

As a company grows, one mistake produces a new approval, a difficult customer conversation another policy and a reporting layer appears because leaders feel less close to the work. Capable people wait, senior people review low-risk work and accountability becomes difficult to locate.

Tony Manganiello makes the point in his Inc. article that growth tests a company's decision-making model as well as its business model. Speed becomes possible when people understand the outcome, the authority attached to their role and the point at which escalation is needed.

Authority without ambiguity

I call the first discipline Authority Without Ambiguity . A person needs more than a task, title or target. They need a defined right to make decisions, with enough context to use it well.

An organisation chart tells me who reports to whom. It does not tell me whether a regional manager may recover a customer relationship, a finance lead may change a supplier or an engineering team may alter a delivery commitment.

Consider an owner-led SME in Pretoria. The operations director may own service quality but still need the founder's approval for every exception. In Sandton, a commercial leader may own a relationship without the pricing discretion to protect it. In Cape Town, a hybrid team may lose a day because nobody knows whether a shared-channel decision is authorised. In Durban, a branch manager may understand the local market yet remain unable to act.

The same issue appears in multigenerational leadership pipelines. A younger executive is told to prepare for succession, but important decisions remain reserved for the founder or family patriarch. A successor carries responsibility in name while learning dependence in practice. That is a delayed handover, not a succession plan.

The accountability boundary

The second discipline is The Accountability Boundary . This is the line between what a team can decide independently, what requires consultation and what must be escalated.

A boundary should describe more than a financial threshold. It may include customer commitments, regulatory exposure, quality, reputational risk, people decisions and effects on another team. The purpose is to make limits visible before pressure arrives.

South African businesses often carry real complexity. B-BBEE considerations, sector regulation, tax, labour requirements and procurement constraints can shape a decision. These obligations require control, but they do not automatically require every operational choice to return to the CEO.

Research by Daemen, Tsilionis and Turetken supports a balanced view. Formal controls such as standards and metrics can work alongside trust, peer coaching and mutual adjustment. Treating them as opposites is restrictive. Hybrid governance preserves autonomy while maintaining alignment.

This is the distinction between control and containment. Control protects the enterprise. Containment protects the leader from discomfort. That difference requires emotional discipline from the CEO. Emotional intelligence is a leadership discipline when a team makes a reasonable decision the CEO would not have made.

Escalation by exception

The third discipline is Escalation by Exception . Escalation should be triggered by a defined condition, not by anxiety, status or the availability of the CEO on WhatsApp.

A team should escalate when a decision crosses a legal boundary, creates material financial exposure, changes strategy, affects a critical dependency or exceeds its mandate. It should also know what does not require escalation.

Without that distinction, under-escalation lets serious issues travel too far, while over-escalation makes senior attention a bottleneck. Smite and colleagues' research makes the same point: scaled autonomy depends on coordination, communication, alignment and a few enabling constraints. If every decision is exceptional, the system has not defined the normal.

Why both extremes fail

Blanket empowerment can create local optimisation. A team may improve its own output while damaging a customer promise, regulatory obligation or another team's capacity. In diverse and hybrid organisations, the hidden traps that turn diverse teams into liabilities often begin with expectations leaders assumed were obvious.

Blanket control fails in the opposite direction. People learn to present decisions in a way that will be approved rather than in a way that serves the customer or strategy. Structured empowerment gives people room to act while making consequences, constraints and ownership visible.

Six actions to take today

1. List the decisions that are waiting. Review recent approval requests, meeting actions and messages. Identify which decisions genuinely needed your judgement and which reached you because the boundary was unclear.

2. Define winning for each team. State the outcomes that matter, acceptable trade-offs and measures of progress. A motivational slogan is not a decision system.

3. Name one decision owner. People can advise, challenge or be informed, but accountability should not be diluted across a committee. Identify who makes the final call.

4. Write the boundary. Set the authority attached to the role, including relevant financial, quality, people, customer and regulatory limits. Make clear which choices can be made without approval.

5. Specify escalation triggers. Describe the conditions requiring senior attention. Then identify decisions that should stay at team or regional level. Escalation should be an exception, not a reflex.

6. Review the system after the decision. Ask whether the outcome, information, capability or boundary was the issue. Do not turn every imperfect result into another approval. The answer may be coaching, a clearer standard or a better threshold.

These steps help leaders build multigenerational pipelines, manage hybrid teams and balance local judgement with group-wide consistency. If people fail inside a clear boundary, develop them. If they wait inside an unclear boundary, fix the system.

At The Leadership Boardroom, CEOs and founders from Pretoria, Sandton, Cape Town, Durban and the wider TLB network work through these tensions with peers who understand growth and question the comfortable answer.

If your teams ask for permission too often, structured empowerment may be the leadership work in front of you. Explore The Leadership Boardroom and consider where authority needs to move and which boundaries need to be visible.

Dennis Kriel is the founder of The Leadership Boardroom, a peer advisory community for CEOs and founders meeting in Pretoria, Sandton, Cape Town, Durban and Windhoek. A serial entrepreneur, educator and international keynote speaker, he writes on leadership, decision-making and building businesses that outlast their founders. Connect at denniskriel.com.

Sources

• Tony Manganiello, Inc., "How Fast-Growing Companies Keep Their Speed as They Scale", 16 August 2026: https://www.inc.com/tony-manganiello/how-fast-growing-companies-keep-their-speed-as-they-scale/91390310
• Daemen, Tsilionis and Turetken, *Information and Software Technology*, Volume 191, March 2026, DOI 10.1016/j.infsof.2025.107998: https://doi.org/10.1016/j.infsof.2025.107998
• Smite et al., *Journal of Systems and Software*, June 2023, DOI 10.1016/j.jss.2023.111649: https://doi.org/10.1016/j.jss.2023.111649