Most principals who feel overloaded with administrative tasks, start with the calendar to fix it.

It makes sense. Make a list of what you do regularly and decide what are the things only you can do. Then remove the rest. That works, but it only addresses the half of the load you can see coming.

The other half never appears on any list, because you cannot write down in advance the questions people are going to ask you.

Attention is an operating resource

Your attention capacity is fixed. It runs down through the day, and interruptions make it harder to recover.

So look at what consumes your attention. It tells you more about how your wealth operates than any org chart does. The usual diagnosis is volume. Too much coming in and there is not enough hours in a day.

So the usual answer is to add more capacity, hire someone, get a better assistant, outsource more.

But adding capable people to a poorly structured system doesn't stop the interruptions. Someone else intercepts them, holds them, batches them, then brings them back to you later.

The questions haven't gone away. They've changed route. Six months later, the same questions still reach you, and now you're paying someone salary along the way.

Interruptions aren't a volume problem. They're a signal.

Every question that keeps coming back points to something missing in the operating system.

Once you see interruptions that way, they stop being an irritation and become a map. The question itself tells you what needs fixing.

Four types, four different gaps

→ Routing. "Who should look at this?"

Someone can handle the work, but nobody clearly owns it.

What's missing: a named owner.

→ Recall. "What did we decide about this?" "Which entity holds it?" "What did we agree with the bank?"

The answer exists, but it's in your head.

What's missing: a record someone else can read.

→ Permission. "Are you happy for us to proceed?"

Nobody doubts what should happen. They doubt whether they have the authority to do it.

What's missing: a written threshold and delegation of authority.

→ Reconstruction. The decision really does belong to you, but it arrives across five emails and a phone call. You spend more time rebuilding the context than making the decision.

What's missing: someone responsible for preparing the decision before it reaches you.

These distinctions matter because the fixes are different.

Clearer thresholds won't solve a recall problem. Better reporting won't solve a routing problem. A fancy software or AI won't fix all four.

Treating them as one problem is how families spend money without reducing the load.

Why the problem grows

Complexity doesn't grow in the way people expect.

Add an entity and you haven't added one more thing to manage. You've added more connections: to tax, liquidity, reporting, estate planning and each advisor's role.

On top of that, each specialist may own their area well. The problem always sits in the gap between those domains. That's where most questions come from. And that's why they reach the principal.

Not because anyone decided they should, but because the principal is often the only person who sits across all of them. You end up owning the gaps by default. You're the invisible family office.

As the number of advisors and entities grows, those gaps multiply much faster than the headcount does.

Why it persists

So, why this problem stays for as long it does, especially when the people involved in supporting the principal are all good at solving problems.

The answer is very simple: answering is faster than fixing.

A question takes ninety seconds to answer. The rule that would stop it coming back may take an hour to define, agree and write down.

So answering is the sensible and default choice today, and tomorrow, and the next time.

No single interruption feels expensive enough to justify fixing the system behind it. The cost only becomes clear when you add them together.

There's a second reason: being asked can feel like respect. Being responsive can feel like good leadership.

Both can be true in a business as well. In operating your own wealth, the same habits can leave you with a system that can't run for a month without you. Whether you are on holiday, taking time off or simply unreachable.

Running the audit

For thirty days, log every interruption that reaches you because of the family's wealth.

Use five columns:

→ What was asked. One line.

→ Domain. Investments, capital calls and liquidity, property, entities and tax, household, banking.

→ Type. Routing, recall, permission or reconstruction.

→ What was missing. The owner, record, rule or preparation that would have kept it away from you.

→ Energy. Great, neutral or draining.

The last column may look softer than the others but trust me it isn't. Two interruptions can look identical on paper and cost you very different amounts depending on when they arrive and what they interrupt.

Pay attention to the draining ones. That's where the system is taking the biggest toll, even if those interruptions aren't the most frequent.

Run the audit for thirty days, not seven. Because a week time catches noise and it misses the cycle.

Much of what takes a principal's attention runs monthly or quarterly: reporting, distributions, renewals, filings and capital calls.

If you track only a week, the work can look random. Track a month and you'll often find that much of it follows a schedule. Scheduled work can move into a regular cadence.

Reading the result

Don't read the output as a list. Turn it into a grid.

Put domains down one side and the four interruption types across the top. A shape will start to appear.

One domain may generate most of the recall questions. One advisor relationship may produce most of the routing. You may find a cluster of permission questions just below a threshold nobody has written down. Entities and tax may fill one column while property stays empty.

That shape tells you what to build first and where.

It gives you an answer for this family, rather than the generic answer of "better governance," which doesn't tell anyone what to do on Tuesday morning.

The grid also tells you what should keep reaching you.

Some interruptions belong with the principal because they require your judgement, your authority or your relationship.

If someone calls because the relationship itself requires a conversation with you, that's not inefficiency. Routing the call away just to make the system look cleaner can cost more than it saves.

I've been testing this framework with a small number of families. I don't see it as a finished framework yet. I call it the Principal Attention Audit.

If you run the audit, I would love to hear back from you. Reply and tell me what the grid showed you. More importantly, tell me what it missed.