How an assistant can prepare an executive weekly planning brief

Operating rhythm

Key takeaways

• Capture weekly outcomes, fixed commitments, exposed promises, blocked owners, and decision times.
• Apply this control: reconcile the brief with the live calendar, action register, owners, and source reports.
• Escalate if stated priorities exceed capacity or every item is labeled urgent.

Operating data

Playbook

A weekly planning brief reconciles ambition with actual capacity. Gather the week's intended outcomes, fixed commitments, external promises, blocked owners, and decisions that need protected time. Then inspect the live calendar rather than a copied schedule. The brief should reveal collisions and unallocated work, not simply restate every project marked important.

Divide the view into outcomes to protect, decisions due, commitments at risk, and work that can move. Asana's weekly work plan guidance offers a general planning approach; an executive brief must also show authority and consequence, because a leader's attendance or decision may be the scarce dependency rather than task effort.

Escalate when stated priorities exceed available capacity, every item is labeled urgent, or the calendar contradicts the declared order. Present a choice using hours, deadlines, and affected stakeholders: defer an outcome, delegate attendance, reduce scope, or move a fixed commitment with consent. Do not solve overload by removing preparation and recovery buffers invisibly.

At week's end, compare completed outcomes, changed priorities, displaced work, and commitments discovered too late. These findings should improve intake and forecasting, not become a performance score detached from context. Operations follow-through can maintain the source registers, and the weekly operations review provides the forum for decisions and owner updates.