Where Should a Leader Spend Their Executive Function?

Leadership includes deciding which cognitive work deserves your direct attention, which can be carried elsewhere, and what you still need to understand well enough to own.

A founder can spend an entire morning thinking hard and still avoid the work that most needs their thinking.

They may review details, answer questions, remember what someone forgot, chase an update, reorganize a plan, check numbers, respond to messages and mentally keep six unfinished commitments from disappearing. By lunchtime, they have used a great deal of executive function. They may also have made almost no progress on the decision only they can make.

This is one of the more subtle problems that appears as responsibility grows. Leaders become responsible for more work, which also means more information to hold, more decisions to monitor, more people to coordinate and more loose ends with the potential to become expensive.

The amount of cognitive work surrounding leadership grows alongside the visible work.

At some point, a leader has to decide which parts of that cognitive work actually require them.

A business needs many things to be remembered, organized, sequenced, monitored and followed through. It also needs judgment, direction, interpretation, decisions and the ability to recognize what deserves attention before it becomes obvious to everyone else.

Those forms of thinking can live very close together in a working day, which makes them easy to treat as equally deserving of the leader’s attention.

They are not equally dependent on the leader.

Leadership includes allocating cognitive work according to where your own thinking creates the most value.

Leadership creates more cognitive work than any one person should carry personally

As a role expands, the leader rarely inherits only more decisions. They inherit the cognitive work wrapped around those decisions.

A hiring decision, for example, includes far more than choosing a candidate. Someone has to remember what remains unresolved, gather missing information, keep the process moving, notice approaching deadlines, compare competing considerations and make sure the right people know what happens next.

The final judgment may belong to the leader. Much of the surrounding mental work exists because the decision needs to stay organized long enough to reach that point.

The same pattern appears almost everywhere. Strategic projects generate information that needs to remain visible. Client commitments have to survive beyond the meeting in which they were made. Risks need monitoring. Decisions need follow-through. Work that crosses several people requires enough shared memory to prevent everyone from carrying a slightly different version of reality.

A leader can personally carry a surprising amount of this when the organization is small. In fact, early success may depend on it.

The founder remembers what was promised because they were in every conversation. They know which deadline is becoming dangerous because they are close to the work. They notice that a decision has stalled because most decisions still pass through them.

For a while, being the person who knows everything can look remarkably efficient.

Growth changes the economics of that approach.

The same ability to hold enormous amounts in your head can become increasingly expensive as the number of relationships, projects and decisions expands. More of your executive function becomes occupied with maintaining the work rather than shaping it.

This is where a leader can become extremely busy performing cognitive operations that the business genuinely needs while gradually losing access to the thinking the business needs specifically from them.

Your brain has become the company’s most expensive reminder system.

It may be a very good reminder system. That does not make it a sensible use of executive leadership.

Some thinking contains the leader’s unique contribution

The strongest reason for a leader to remain cognitively involved is that their judgment changes the quality of the outcome.

That may happen because they understand the wider strategy, know something about the organization that changes how a decision should be interpreted, hold authority that cannot be exercised by someone else, or have experience that allows them to see consequences others may miss.

A pricing decision for a major client might require exactly that kind of involvement. Someone else can prepare the financial history, gather the relevant contract information and organize the available options. The leader may still need to decide how much short-term revenue they are willing to trade for a longer relationship, how this agreement could affect future negotiations and whether the client is strategically valuable for reasons the numbers alone cannot show.

The surrounding information matters because it makes judgment possible.

And judgment is where the leader’s contribution becomes distinctive.

A similar thought process appears in people decisions. A leader may need to understand the performance history, hear the concerns of several people and know what options are available. Someone else can make sure that information is complete and accessible. The leader still has to decide what it means.

This matters because cognitive difficulty is not a reliable way to identify high-value thinking.

Routine work can be mentally expensive. Keeping track of twenty small commitments can require more moment-to-moment executive effort than making one important decision after the relevant information has been organized well.

A leader who allocates attention according to what feels demanding can therefore spend enormous effort in places where their personal involvement contributes very little.

The better question is not How much thinking does this require?

It is Where does my thinking change the outcome?

Accountability does not require you to perform every cognitive operation

Many leaders have a strong internal connection between responsibility and personal cognitive control.

If they are accountable for something, they want to remember it themselves. They want to know where every piece sits, review the details personally and keep the moving parts close enough that nothing surprises them.

There is logic in that instinct. Leaders are often held responsible for outcomes long after everyone has forgotten exactly how much control they had over the process. Keeping work close can feel like the safest way to remain accountable.

The problem appears when responsibility becomes confused with performing all the cognition around the responsibility.

A leader can own a decision while someone else gathers the information required for it. They can remain responsible for a deadline while a system monitors the timing. They can own the quality of an outcome while another person coordinates the sequence of work that produces it.

Accountability and cognitive ownership are different things and that changes what delegation looks like.

Delegation becomes larger than handing someone a task. It can include deciding where the thinking around the task should live.

A senior leader may still want visibility into a major project. That visibility does not require them to personally reconstruct the project’s status every time they need it. A strong system can make the important information available. A capable project lead can surface decisions that require executive judgment.

The leader stays close to the parts that deserve their attention without using their own working memory as the infrastructure holding the project together.

That is a different relationship to responsibility. It preserves ownership of the consequence while distributing the cognitive operations involved in producing the result.

The hard part is deciding what deserves to stay with you

This sounds simple until you try to apply it.

Leaders frequently carry work personally because they are good at it. They may also be faster than the person they could delegate it to, more confident in their own standard or accustomed to being the person who notices what everyone else misses.

Those reasons can remain true long after they stop being sufficient reasons to keep the work.

Consider a founder who reviews every client proposal before it goes out. Early in the business, that may have been essential. They held most of the expertise, understood the clients better than anyone else and were still establishing what good work looked like.

Several years later, the founder may still review every proposal because the practice has become part of how quality is maintained. Yet the organization now has experienced people, clear examples of strong work and established standards.

The founder’s review may add little to most proposals while requiring attention that could have gone toward the few situations where their judgment genuinely matters.

Whether the founder can continue reviewing them is not especially useful.

They probably can. Capable people can continue doing all sorts of things long after doing them personally has stopped making sense. It is one of the less convenient side effects of competence.

What matters is what the organization gives up when they do.

Deliberate attention cannot be directed toward every demand simultaneously. If a leader spends an hour reviewing work that another capable person could approve, that hour – and the attention inside it – is unavailable for something else.

The cost may appear in a strategic question that keeps being postponed, a relationship that needs attention, a risk that has not been examined carefully enough or a difficult decision that remains unresolved.

This is what makes executive-function allocation a leadership issue rather than a personal productivity issue.

The scarce element is not simply time.

It is access to the leader’s judgment where that judgment matters.

Better allocation often requires redesigning the work

Once a leader sees this problem, the natural impulse is to delegate more.

Sometimes that helps.

Sometimes the work comes straight back wearing a fake mustache.

Someone delegates responsibility for a project but remains the only person who knows the history behind it. Every question still requires them. Someone else takes over scheduling, yet the leader keeps all the relevant priorities in their head, so the scheduler has to ask constantly what should move. A team is expected to make decisions independently while important information remains concentrated with the person who wants fewer interruptions.

In each case, the visible task moved.

The cognitive dependence stayed in place.

This is why better allocation often requires redesigning how information, decisions and responsibility move through the work.

If someone else is going to monitor a project, they need access to the information that makes monitoring possible. If a team is expected to make routine decisions, the boundaries of those decisions need to be clear enough that they do not have to seek permission every time. If a leader wants to stop remembering dozens of commitments personally, those commitments need a trustworthy place to live.

External systems matter because they can carry forms of cognition that organizations otherwise leave inside individual people. A shared record can carry memory across a team. A clear process can carry sequence. A visible dashboard can carry monitoring. A decision rule can reduce the amount of repeated judgment required for situations the organization already understands.

None of these removes thinking from the organization.

They place the thinking somewhere that does not require one person’s executive functions to recreate it every time.

That creates an important shift for leaders. Their job becomes partly architectural. They decide which information needs to remain visible, which decisions require their involvement, where responsibility should sit and how the organization will carry the cognitive work that continues after they leave a meeting.

The work that most needs you may be easier to neglect

There is a final complication.

The forms of thinking that most need senior leaders often produce the least immediate pressure.

A strategic decision can wait another day. A question about the future of the business can wait another week. Developing a talented person can be postponed because nobody’s computer will start flashing red if the conversation does not happen by 4:00.

Operational cognitive work behaves differently. It arrives already attached to deadlines, questions, requests and notifications. It tells you exactly what needs attention and often rewards you with the satisfying experience of completion.

There is always another small problem willing to save you from the terrible ambiguity of thinking about a large one.

That makes allocation harder than simply identifying which work has the greatest value. The leader also has to protect access to that work from the demands that are easiest to respond to.

For some leaders, this means noticing how much of their day is spent keeping information alive. For others, the issue is monitoring work that could be visible through better systems, remaining involved in decisions that have long since become routine, or personally organizing tasks that no longer require their expertise.

The question becomes:

Which cognitive work genuinely needs me?

That is narrower than “What should I delegate?” The focus is where your understanding, judgment, authority or experience changes what happens.

From there, you can consider what should happen to everything surrounding that work: the remembering, tracking, organizing, retrieving and monitoring that the organization still needs but does not necessarily need from you.

Your organization may need thousands of cognitive operations to function well.

It does not need all of them to happen inside you.

Leadership includes deciding where the thinking lives – and protecting your own thinking for the places where it changes what happens.