If every routine price exception, schedule change or customer remedy waits for the founder, the team can be busy and still unable to finish ordinary work. But vague delegation creates a different problem. People make inconsistent promises, or they escalate everything because no one knows the limits. Clear decision authority gives staff room to act while keeping important risks visible.
Decision authority is the right to make a particular choice within agreed boundaries. It does not mean one person controls every task, and it does not require a committee for each exception. The useful question is which decisions can be made close to the work, which need input, and which should still reach an owner or executive.
Why the founder approval queue grows
At an early stage, a founder may hold most decisions because the business is small and the founder knows the customers, cash position and promises already made. As teams and work grow, the same habit can turn into an approval queue. Managers remain responsible for delivery, but they cannot change a schedule, resolve a routine complaint or use a small amount of budget without waiting.
The World Bank’s SME Governance Guidebook recommends a gradual move from highly centralized decisions toward more distributed and collaborative decision-making as a business develops. It also warns that delegating too early can weaken control, while refusing to delegate can prevent the company from using its managerial and technical talent. The right pace depends on the firm’s people, risks and maturity. Read the World Bank SME Governance Guidebook.
Research on more than 1,000 CEOs and CFOs found that authority varies by decision type and that larger or more complex firms were more likely to delegate some decisions. The study is a survey of corporate financial choices, not a rule for every small company. It supports a practical point: choose limits for each kind of decision instead of applying one blanket rule. See the NBER survey on decision authority.
Map decision authority for recurring choices
Start with a short list of recurring questions from the past few weeks. Include customer remedies, discounts, shift swaps, supplier orders, hiring steps, refunds or schedule changes only where they apply to your business. Group them by the work involved. Do not start by writing a long policy for every imaginable situation.
For each group, record one accountable decision-maker, the people who must be consulted, the boundary for a routine decision, and the conditions that trigger escalation. Consultation means someone gives useful information. It does not automatically make that person an approver. One named decision-maker avoids the familiar ending where everyone is responsible and nobody decides.
Set limits people can use
Useful limits are specific enough to guide a real choice. They may depend on an approved budget, an existing customer policy, a contract the business has already accepted, a service risk or a defined level of financial exposure. Where a decision changes a legal commitment, sensitive data handling or a regulated activity, keep the required review with the people who have that authority and expertise.
Illustrative example. A service team lead may be allowed to resolve a routine complaint using an existing remedy policy. A request outside that policy goes to the operations manager. A new promise that changes the contract or creates an unbudgeted commitment goes to the executive who holds that authority. These are example boundaries, not a recommended dollar limit or legal rule.
Write the escalation trigger beside the permission. For example, escalate when the request falls outside the approved policy, creates a safety or compliance concern, changes a customer commitment, or exceeds the person’s budget. Staff should also know who can cover the decision-maker when that person is away.
Test the decision map before expanding it
Choose one recurring decision and try the new boundary for a short review period. Tell the people involved what changed, where to record the outcome, and how to raise an exception. Then check whether decisions moved faster without increasing reversals, customer complaints, rework or policy exceptions.
Track a few measures that answer the actual question: time from request to decision, the share resolved within the boundary, decisions reopened because key information was missing, and how many exceptions reached the founder. Ask the team what still feels unclear. If people do not trust the limit or lack the information to use it, widen the map only after fixing that gap.
A decision authority map should change when the work or risk changes. Review it after a new service, market, system or management role is introduced. Keep the routine choices close to the people who understand them, and keep high-impact exceptions with the people accountable for them.
Adapt the map to each market
Companies working in Georgia, the United States, Russia or several markets should not copy another country’s approval limits. Payment practices, customer expectations, contracts, employment arrangements and regulatory duties can differ. Map the applicable local requirements with qualified advisers, then make the operational limits clear to the team. This article does not give jurisdiction-specific legal advice.
Clear decision authority can help an owner see where work is waiting and whether the cause is capability, missing information, unclear limits or a process that needs redesign. DBG360 can help map those decisions, align responsibilities across people and systems, and support a practical change plan. Book a discovery call to discuss where routine decisions are getting stuck.
