Classify messages by the relationship, requested outcome, consequence, sensitivity
Classify messages by the relationship, requested outcome, consequence, sensitivity, and response authority involved. Sender identity can supply context, but it should not decide the action by itself.
Give each class a support action
Give each class a support action: file, acknowledge, draft, route, protect time, or escalate. State the evidence that moves a message between classes so the rule remains usable during pressure.
Sample the taxonomy during a weekly inbox review
Sample the taxonomy during a weekly inbox review. Repeated misroutes may mean the relationship map is stale, the request channel is wrong, or a decision boundary needs a concrete example.
Related resources
Frequently asked questions
Should one assistant support the whole executive team?
Sometimes. It works when priorities are clear and executives share one operating rhythm.
What should happen before a consult?
List the meetings, inbox rules, recurring reports, and decisions that need support.
Ready to define the role?
Use a recent leadership week to scope the support that would make the biggest difference. The consultation is a working conversation, not a generic pitch.
Book a consultation