Measurement
Key takeaways
- Measure outcomes and exceptions rather than task volume.
- Pair each metric with a definition and decision it informs.
- Use samples to detect hidden rework and unsafe speed.
Operating data
Playbook
Executive assistant metrics should reveal whether an operating system is becoming more reliable. Counts of emails touched or meetings booked reward volume without showing judgment. Start with the failure or decision the metric should expose, then define the event, source, owner, and review cadence.
Useful measures vary by lane: unprepared meetings, avoidable reschedules, commitments closed with evidence, messages missing their response standard, reopened tasks, or trips with unresolved handoff items. Keep denominators visible so a count is not mistaken for a rate or trend.
Asana's overview of project reporting discusses status, progress, and reporting context. Executive support can borrow that discipline while avoiding false precision: explain collection gaps and do not combine unlike workflows into a single performance score.
Balance speed with quality. A falling response time is harmful if drafts require correction or sensitive messages are misrouted. Sample completed work for accuracy, authority compliance, and rework, then discuss the examples alongside the trend rather than treating the dashboard as self-explanatory.
The services overview helps map measures to inbox, calendar, travel, and follow-through outcomes. Metrics should improve the workflow, not surveil every minute. Do not infer assistant effort or intent from a tool timestamp that was designed for another purpose.
At review, choose an intervention and a recheck date: clarify a rule, remove an intake path, rebalance ownership, or improve a brief. The weekly operations review can host that decision. Retire measures that no longer change behavior or expose risk.
FAQ
When should a leader delegate this workflow?
Delegate it when repeated coordination, routing, or follow-up is taking time away from decisions that only the leader can make.
What should the assistant own first?
Start with intake rules, status visibility, and escalation timing so the assistant can act consistently before the workflow expands.
