Decision overload is not a stamina problem

In Aman Merchant's work with founders and CEOs, decision overload rarely starts as a personal productivity problem. It begins when an organisation treats the leader's attention as an open channel.

The symptoms are familiar. A calendar fills with short approvals. Team members bring exceptions rather than recommendations. Strategic questions arrive beside routine choices, each carrying the same visual weight and emotional urgency. By the end of the day, the leader has been busy without being properly available for the few decisions only they could make.

The usual response is personal: work faster, delegate harder, create a better morning routine. Those moves can help. They rarely hold when the organisation continues to route uncertainty upward.

This is attention architecture: the deliberate design of what reaches the CEO's judgment, what routes to another owner, what a standing rule governs and what no longer deserves a decision at all.

Decision load is created before the decision reaches you

A CEO experiences overload at the end of a chain. Earlier in that chain, somebody was unsure who owned the choice, what risk they could accept, which evidence mattered or whether they would be supported if the result was imperfect. Escalation felt safer than judgment.

This is why delegation can disappoint. A task moves to a capable leader, but every meaningful trade-off still returns to the founder. Activity is distributed while authority remains concentrated. The CEO gains more people and more incoming decisions at the same time.

Aman Merchant's working thesis is that sustainable clarity begins by redesigning exposure, not by increasing processing speed. The first leadership question is not, "How can I decide all of this better?" It is, "Why did this decision reach me at all?"

Build an attention filter before another productivity system

A useful filter gives incoming choices four possible routes. Some are genuinely CEO-only because they alter strategy, capital, leadership composition or material reputation. Some belong to another named owner. Some should be governed by a standing rule. Some should be eliminated because the cost of deciding exceeds the value of the choice.

The filter is not an inbox trick. It is an organisational agreement. A decision that belongs elsewhere needs an owner with real permission. A decision governed by a rule needs a clear threshold. A CEO-only choice needs protected time and the right evidence, not a hurried slot between operating updates.

When these categories remain implicit, urgency wins. The loudest customer, newest message or most anxious colleague gains access to the leader's judgment. Over time, attention becomes an accidental strategy because whatever reaches the CEO repeatedly receives organisational energy.

Protect judgment through classification and rhythm

Good decision architecture separates choices by reversibility, materiality and time horizon. A reversible operating test should not receive the same ceremony as a senior hire or a capital commitment. A strategic question should not be forced through the same forum used to clear weekly exceptions.

Rhythm matters because constant availability makes every moment a decision moment. A weekly decision docket can collect non-urgent cross-functional choices. A defined escalation channel can reserve interruption for conditions that cross a real boundary. A monthly review can ask which decisions returned and what the recurrence reveals about the system.

Recovery belongs in this design too. It is difficult to exercise judgment when reflection is treated as spare time that will appear after the work is done. Leaders need a protected calendar block in which no new decisions are introduced or resolved, not as a wellness break but as operating space to assess the few choices that merit their judgment. That is not retreat from responsibility. It is maintenance of the capacity on which high-consequence work depends.

Use returning decisions as diagnostic evidence

For two weeks, capture every decision that reaches the CEO. Do not begin by judging the person who escalated it. Record the category, intended owner, missing information, perceived risk and reason it moved upward.

Then look for repetition. If pricing exceptions keep returning, the commercial boundary may be unclear. If senior hiring repeatedly stalls, the role outcome or final decision right may be ambiguous. If meetings produce discussion but no commitments, the forum may lack a decision purpose.

Choose one recurring family and write a small decision contract: owner, required inputs, boundary, escalation condition and review point. Let the next case run through that route. If it returns, treat the return as evidence about the design before reclaiming the choice.

The aim is not to remove the CEO from consequential decisions. It is to preserve the CEO for them. A leader should remain central to direction without becoming the default processor for every uncertainty the organisation produces.