Audit a founder's calendar for attention and energy

Founder calendar

Key takeaways

• Classify the work each meeting demands.
• Measure transitions and preparation, not attendance alone.
• Test changes against stakeholder needs.

Operating data

Playbook

A calendar can look efficient while exhausting the attention needed for leadership work. Audit two to four representative weeks and classify each commitment by purpose, decision load, preparation, emotional demand, location, and transition cost. Include work performed outside scheduled meetings so the calendar does not understate the burden.

Mark clusters that support a coherent mode of work and transitions that force the founder to switch rapidly between sales, hiring, product, people, and investor contexts. The calendar control service can turn the findings into qualification rules, protected blocks, and delegation options.

The assistant proposes patterns and gathers stakeholder constraints; the founder chooses the tradeoffs. Do not infer health conditions or label a person as productive based on presence data. If moving a recurring meeting harms an important time zone or customer relationship, include that consequence in the decision.

Compare meeting hours with preparation time, overdue decisions, reschedules, and follow-up completed after hours. Microsoft Viva Insights documentation describes ways workplace data can inform habits, subject to appropriate privacy and organizational controls.

Pilot one change, such as grouping interviews or protecting a strategy morning, then review its effect after several cycles. Preserve exceptions that produced value and reverse changes that merely shifted the burden. Founders can request a tailored support plan for an assistant-led calendar operating model.