How to Design Your Intake: What Reaches You, and What Shouldn't

Intake is everything that reaches you: channels, reports, requests, escalations, standing invitations, and interruptions. Designing it means deciding, on purpose, what gets through and what does not, rather than accepting whatever accumulated.

Almost nobody has done this. It is the least examined part of executive work, and it is usually where the real constraint lives.

Why does intake get so bad?

There is a structural asymmetry underneath it, and once you see it the whole thing makes sense.

Anyone in your organization can add a channel to your intake. Only you can remove one.

A new director starts and adds you to their weekly report. A vendor relationship comes with a portal. A crisis two years ago produced a standing escalation path that nobody ever closed. Someone builds a dashboard and sets you as a recipient. Each addition was reasonable, took thirty seconds, and required approval from no one.

Removal works nothing like that. Cancelling a report means telling a person their work is not being read. Closing an escalation path means someone might feel cut off. Every subtraction costs a conversation, and the additions cost nothing at all.

So intake only ever grows. Not because anyone is careless, but because the system has hundreds of contributors and exactly one editor, and the editor is busy.

Filtering is not organizing

This is the distinction that determines whether any of this works.

Organizing means handling the same volume more efficiently. Folders, labels, rules, saved searches, inbox zero, a better task manager. The volume is unchanged. You have simply gotten faster at processing it, which means the ceiling on how much can reach you just went up.

Filtering means less arrives in the first place.

Most executives who believe they have solved their information problem have organized it. They have an elegant system for routing an unsustainable volume, and they are proud of it, and they are still the router. The measure of whether intake is designed is not how quickly you clear it. It is how much never reaches you at all.

There is a related trap worth naming: turning off notifications. That is a good idea, but it is an Attention fix, not an Intake fix. Silencing alerts changes when things interrupt you, not how many arrive. The pile is the same size when you look at it.

How do you actually design intake?

Six steps. The first one does most of the work.

1. Count your channels

Write down every distinct way a person can reach you with something that requires action. Count these separately, because they genuinely are separate:

email, each chat tool your company uses, direct messages inside project tools, text messages, phone calls, calendar invitations, ticketing or request systems, comments on shared documents, physical drop-ins, and whatever your leadership team uses that nobody else does.

Most senior leaders guess four or five. The honest count is usually nine to twelve.

The number itself is often the entire intervention. Nobody chose nine channels. Nine channels is what happens when nobody chooses.

2. Ask three questions about each one

For every channel on the list:

• What is this for, stated in one sentence?

• Who owns it other than me?

• What actually breaks if it stops existing?

The third question is the useful one. A surprising number of channels fail it completely. Nothing breaks. They persist because stopping them requires a decision and continuing them requires nothing.

3. Run the silent cancellation test on recurring reports

Recurring reports are the clearest case of intake that outlived its purpose. Someone needed a number during a specific quarter, a report was built, the need passed, and the report continued arriving forever.

The test: stop the report. Do not announce it, do not ask permission, just stop it for three weeks.

If nobody asks, you have your answer, and so does whoever was producing it. If someone does ask, you have learned it matters and you can restart it in a minute. The risk is close to zero and the information is exact.

Most executives find that roughly a third of what they receive on a schedule is unread and unmissed.

4. Consolidate rather than reorganize

The goal is fewer channels, not tidier ones. Two channels that serve the same purpose should become one, and the decision about which one survives matters far less than the fact that one of them stops.

This is unglamorous and it is where most of the durable gain is.

5. Move the filter in front of you

Here is the part that separates real intake design from productivity advice.

Filtering has to happen before you, not by you. As long as you are the one deciding what matters, you are still the router, and every item still costs you the attention required to categorize it. Sorting quickly is still sorting.

If you have a chief of staff or an executive assistant, this is the highest-value thing they can do, and it is frequently not what they are asked to do. Most assistants are given the calendar and left out of the inbox, which is backwards. The calendar is downstream.

6. Write escalation criteria

Escalation is intake too, and it is usually the least specified part.

Most teams operate with an unwritten rule that amounts to "escalate if it feels big." That produces two failures at once: things that should have reached you did not, and things that should not have did.

Write it down. Three or four lines is enough. Something reaches you if it crosses a spending threshold, affects a named customer or partner, sets a precedent, or cannot be reversed. Everything else gets decided below you and reported afterward, not before.

The specific criteria matter less than their existence. Written criteria let people self filter, which is the only version of filtering that scales.

What if nobody is available to filter for you?

Most executives will never have a chief of staff. There are a few thousand of those roles in the country and hundreds of thousands of leaders with the same problem. So the practical answer cannot depend on hiring one.

Three things work without additional headcount:

Written criteria do most of the job. Section six above is filtering that runs without a filterer. Your team can apply your rules if your rules exist. They cannot read your mind, which is what you are currently asking them to do.

Rotate a triage role among your directs. One person each week owns first pass on the shared queue. It costs each of them a small amount, it costs you nothing, and it teaches four people how you think about priority, which pays back well beyond the intake question.

Consolidate hard. Every channel you eliminate is filtering you never have to do. This is the lever available to everyone and the one most people skip because it requires conversations rather than configuration.

Why intake comes first

Intake sits upstream of everything else in how a senior leader operates. What reaches you determines what fills your calendar, which determines what decisions queue up, which determines what you can hand off.

That ordering has a practical consequence. If your intake is undesigned, downstream fixes will not hold. You can clear your calendar completely and it will refill within a month, because clearing a calendar changes your availability rather than your inflow. The same volume arrives through the same channels with the same defaults and reclaims the space.

This is why so many executives conclude that time management does not work for them. It works fine. They were fixing the wrong layer.

If you have already tried protecting your time and watched it evaporate, that experience is not evidence of weak discipline. It is fairly strong evidence that your constraint is here.

FAQ

How many communication channels should an executive have? Fewer than you currently have. There is no correct number, but nine to twelve is common and four to five is workable. The count matters less than whether anyone chose it.

Isn't some interruption necessary? Yes. The goal is not an unreachable executive, it is a deliberate one. Urgent things should reach you quickly, which is far easier when they are not competing with nine channels of routine traffic.

What if my company mandates the tools? You usually cannot reduce which tools exist, but you can reduce which ones are valid ways to reach you. "Requests come through the ticket queue, not direct messages" is a rule you can set inside almost any stack.

How long does this take? The inventory takes twenty minutes. The consolidation conversations take a few weeks, because they are conversations. The escalation criteria take an hour and produce the most durable benefit.

How do I know intake is my constraint rather than something else? The clearest signal is reversion. If you have made changes to how you work and watched them come back within a month or two, the problem is almost certainly upstream of whatever you changed.

Bob Stanke is a Chief of Staff, the role companies create when an executive's operating system has outgrown them. He writes about the operating layer of executive work: what reaches you, where your attention goes, how decisions clear, and what leaves your desk.

The Executive Operating Index scores all four components in about five minutes and tells you which one is actually binding. Take the assessment.