Review included workflows, actual requests, response windows, peak periods
Review included workflows, actual requests, response windows, peak periods, exclusions, and work that needed rework. Compare evidence with the agreed scope.
Separate a scope issue from a priority issue
Separate a scope issue from a priority issue. The right change may be a clearer boundary, a different cadence, or a decision about what will wait.
Record the next scope, owner, and review date
Record the next scope, owner, and review date. A bounded rhythm protects the quality of support and makes tradeoffs visible.
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