Executive Support Operating Rhythm

How to build a repeatable operating rhythm across daily preparation, weekly review, and monthly planning. The useful version is specific enough for a second person to run and light enough to update when priorities change.

Define the outcome

Start with the outcome, not the tool. Write what should be true when the workflow is complete, who owns the result, and when the next update is due. Record the consequence of delay and the authority available to the assistant. This keeps the work tied to executive priorities rather than an unbounded list of requests.

Separate facts from interpretation. Record the source of a deadline or request, then add a recommendation only when the evidence is sufficient. A short context note makes it easier for the executive to confirm or correct an assumption without reconstructing the whole history.

Run the workflow

Use one working queue with clear states: received, preparing, waiting for decision, in progress, and closed. During the first pass, group related work and identify dependencies. During the action pass, complete items within standing authority and prepare concise options for everything else. Each option should include the tradeoff and the consequence of waiting.

Keep sensitive information in the approved workspace. Do not copy confidential message bodies into a personal tracker for convenience. Use named access, a retention rule, and a review point when the work changes hands. The Project management practice reference provides useful background for the control principle behind this workflow.

Review and improve

At the end of the agreed period, inspect carried-forward items, missed preparation, repeated questions, and work that returned because context was incomplete. Ask whether the workflow reduced executive interruption without shifting hidden work to a colleague. Keep the rule if it helped, revise it if the exception is common, and retire it if it adds ceremony without clarity.

For related operating context, compare this with the executive assistant weekly planning routine and the briefing document guide. One covers cadence while the other covers concise preparation.

A compact checklist

1. Define the outcome, owner, deadline, and authority boundary.
2. Verify the source and separate facts from recommendations.
3. Move routine work through the queue and escalate judgment calls.
4. Record the next action when work is waiting or handed off.
5. Review exceptions and update the rule at a stated cadence.

FAQ

What makes this workflow useful?

It gives the assistant a repeatable way to prepare work while showing the executive where judgment is still required. The workflow should reduce repeated clarification, not remove accountability.

How often should it be reviewed?

Review it after a meaningful role, team, tool, or priority change. Stable routines can use a monthly or quarterly review, while a new workflow benefits from a shorter initial check.

What should an assistant escalate?

Escalate matters involving legal or financial commitments, personnel decisions, safety, sensitive relationships, or authority that is not documented. Include the relevant facts and one recommended next step.