A 90-Day Plan for a New Executive Assistant

Start with the decision: pre-start setup

For 90-day onboarding, pre-start setup matters because a new executive assistant earns context and responsibility without premature access. 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: first-week observation

For 90-day onboarding, first-week observation matters because a new executive assistant earns context and responsibility without premature access. 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: relationship map

For 90-day onboarding, relationship map matters because a new executive assistant earns context and responsibility without premature access. 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: access sequencing

For 90-day onboarding, access sequencing matters because a new executive assistant earns context and responsibility without premature access. 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: calendar baseline

For 90-day onboarding, calendar baseline matters because a new executive assistant earns context and responsibility without premature access. 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: communication norms

For 90-day onboarding, communication norms matters because a new executive assistant earns context and responsibility without premature access. 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: first ownership

For 90-day onboarding, first ownership matters because a new executive assistant earns context and responsibility without premature access. 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: 30-day review

For 90-day onboarding, 30-day review matters because a new executive assistant earns context and responsibility without premature access. 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: 60-day expansion

For 90-day onboarding, 60-day expansion matters because a new executive assistant earns context and responsibility without premature access. 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: 90-day outcomes

For 90-day onboarding, 90-day outcomes matters because a new executive assistant earns context and responsibility without premature access. 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 90-day onboarding

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 pre-start setup with first-week observation during 90-day onboarding. If access sequencing changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare first-week observation with relationship map during 90-day onboarding. If calendar baseline changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare relationship map with access sequencing during 90-day onboarding. If communication norms changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare access sequencing with calendar baseline during 90-day onboarding. If first ownership changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare calendar baseline with communication norms during 90-day onboarding. If 30-day review changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare communication norms with first ownership during 90-day onboarding. If 60-day expansion changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare first ownership with 30-day review during 90-day onboarding. If 90-day outcomes changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare 30-day review with 60-day expansion during 90-day onboarding. If pre-start setup changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare 60-day expansion with 90-day outcomes during 90-day onboarding. If first-week observation changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare 90-day outcomes with pre-start setup during 90-day onboarding. If relationship map 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