Executive Assistant Performance Review: Evidence and Questions

Start with the decision: role outcomes

For performance review, role outcomes matters because managers assess outcomes, judgment, reliability, and growth fairly. The first design choice is to define the decision this element supports. Collecting information without a decision target creates busywork and invites inconsistent interpretation. Write down the current state, the desired state, and the person who can approve a change. Then use one recent, non-sensitive example to see whether the rule is understandable in practice.

Establish a baseline: service evidence

For performance review, service evidence matters because managers assess outcomes, judgment, reliability, and growth fairly. Observe the current process for a representative period before promising an improvement. Note normal demand, exceptions, dependencies, and where executive attention is actually required. Write down the current state, the desired state, and the person who can approve a change. Then use one recent, non-sensitive example to see whether the rule is understandable in practice.

Define ownership: stakeholder input

For performance review, stakeholder input matters because managers assess outcomes, judgment, reliability, and growth fairly. Name the operator, accountable decision maker, and escalation owner separately. This prevents administrative execution from being mistaken for authority to make the underlying business decision. Write down the current state, the desired state, and the person who can approve a change. Then use one recent, non-sensitive example to see whether the rule is understandable in practice.

Set an observable standard: judgment examples

For performance review, judgment examples matters because managers assess outcomes, judgment, reliability, and growth fairly. Translate expectations into evidence a reviewer can inspect. A status label alone is weak; a source, timestamp, next action, and acceptance condition make the work reviewable. Write down the current state, the desired state, and the person who can approve a change. Then use one recent, non-sensitive example to see whether the rule is understandable in practice.

Test the exception path: error recovery

For performance review, error recovery matters because managers assess outcomes, judgment, reliability, and growth fairly. Walk through a realistic missing-input or urgent-change scenario. The normal path rarely exposes unclear permissions, weak handoffs, or hidden reliance on personal memory. Write down the current state, the desired state, and the person who can approve a change. Then use one recent, non-sensitive example to see whether the rule is understandable in practice.

Protect sensitive context: capacity context

For performance review, capacity context matters because managers assess outcomes, judgment, reliability, and growth fairly. Apply least privilege and keep confidential material in its approved system. Coordination records should point to controlled sources rather than duplicate sensitive details. Write down the current state, the desired state, and the person who can approve a change. Then use one recent, non-sensitive example to see whether the rule is understandable in practice.

Pilot before scaling: development goals

For performance review, development goals matters because managers assess outcomes, judgment, reliability, and growth fairly. Use one bounded workflow and a short review window. A pilot should reveal unclear fields, unrealistic response expectations, and decisions that still lack an owner. Write down the current state, the desired state, and the person who can approve a change. Then use one recent, non-sensitive example to see whether the rule is understandable in practice.

Review quality fairly: calibration

For performance review, calibration matters because managers assess outcomes, judgment, reliability, and growth fairly. Sample both routine items and exceptions. Separate operator error from unclear instructions, unavailable access, late upstream input, and changing executive priorities. Write down the current state, the desired state, and the person who can approve a change. Then use one recent, non-sensitive example to see whether the rule is understandable in practice.

Measure the useful outcome: review conversation

For performance review, review conversation matters because managers assess outcomes, judgment, reliability, and growth fairly. Choose measures that reveal reliability or decision speed, not raw activity. Volume can rise while value falls if rework and unresolved exceptions are hidden. Write down the current state, the desired state, and the person who can approve a change. Then use one recent, non-sensitive example to see whether the rule is understandable in practice.

Recalibrate deliberately: follow-through

For performance review, follow-through matters because managers assess outcomes, judgment, reliability, and growth fairly. Schedule a review after the operating context changes. New leaders, systems, travel patterns, or business priorities can invalidate a previously sensible design. Write down the current state, the desired state, and the person who can approve a change. Then use one recent, non-sensitive example to see whether the rule is understandable in practice.

Scenario prompts for performance review

Use these prompts in a working session. They connect operating details so the team can find dependencies that a single checklist field may miss. Compare role outcomes with service evidence during performance review. If judgment examples changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare service evidence with stakeholder input during performance review. If error recovery changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare stakeholder input with judgment examples during performance review. If capacity context changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare judgment examples with error recovery during performance review. If development goals changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare error recovery with capacity context during performance review. If calibration changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare capacity context with development goals during performance review. If review conversation changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare development goals with calibration during performance review. If follow-through changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare calibration with review conversation during performance review. If role outcomes changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare review conversation with follow-through during performance review. If service evidence changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare follow-through with role outcomes during performance review. If stakeholder input changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow.

A simple implementation sequence

Choose one representative workflow, name the accountable manager, and document the current path before changing it. Agree on a small field set and two or three acceptance tests. Run the design for a limited period, including at least one exception, then review the evidence with the people who perform and receive the work. Correct unclear permissions first, simplify fields that do not inform a decision, and publish the approved version where the team already works.

Questions to take into a provider or candidate conversation

Ask for a job-relevant example of how the person would clarify scope, protect sensitive information, surface a conflict, and document completion. Ask who reviews quality, how continuity works, and what happens when the request exceeds the agreed authority. Strong answers distinguish facts from decisions and describe escalation without claiming that every situation can be scripted.

Related resources

• Executive support services
• Executive support research
• Contact HireExecutiveTeam