Executive assistant first 90 days: a success plan for leaders

Start with the real decision

What should an executive and assistant accomplish in the first thirty, sixty, and ninety days? The answer should follow the leadership team's real workflows, risks, and capacity rather than a generic rule. The first ninety days should expand ownership based on demonstrated readiness, not a calendar alone. Begin with context and narrow access, move into supervised execution, and then stabilize a defined portfolio of workflows. The executive and assistant share responsibility: the assistant learns and documents the system; the executive supplies priorities, decision rights, feedback, and timely approvals. Use a written success plan with outcomes and review points. A new hire cannot infer years of relationship history from a job description, and withholding context is not a meaningful test of initiative.

Avoid the common shortcut

Avoid granting every permission on day one or delaying all access until trust feels complete. Both extremes prevent useful evidence. Do not judge success by how full the assistant's task list becomes. Early volume can hide rework, unclear authority, and dependence on constant executive rescue. Avoid changing communication preferences without updating the written rule. Onboarding fails when the assistant receives contradictory instructions from several leaders and no one is accountable for resolving the conflict.

Map the work

Before day one, name the onboarding owner, supported leaders, first workflows, systems, required training, and review schedule. Prepare a relationship map, recurring meeting calendar, current priorities, vocabulary, and examples of good outputs. Provision only the access needed for observation and the first tasks. Tell relevant colleagues what the assistant owns now and what will transfer later.

Make ownership explicit

Days one through thirty focus on context and safe practice. The assistant observes key rhythms, learns where authoritative information lives, performs low-risk tasks, and records questions. The executive explains preferences as reasons and boundaries, not isolated likes. Review calendar choices, draft communication, confidentiality scenarios, and escalation examples. By day thirty, both parties should agree on the current workflow map and the next ownership step.

Test the operating model

Days thirty-one through sixty add supervised ownership. The assistant runs selected recurring workflows, prepares recommendations, and escalates defined exceptions. Hold a short weekly operating review using real cases: what arrived, what was decided, what waited, what required rework, and which rule was missing. Add access only when a workflow requires it and remove temporary permissions that no longer have a purpose.

Protect access and judgment

Days sixty-one through ninety stabilize the role. The assistant should own an agreed portfolio with visible service levels, maintain current handoff notes, and identify one or two system improvements supported by evidence. The executive should spend less time supplying repeated context, but remain available for consequential decisions. Review capacity before adding attractive new work; successful onboarding often generates demand faster than it creates safe capacity.

Choose a reviewable first step

At day ninety, compare outcomes with the starting brief. Review prepared meetings, follow-up completion, response windows, calendar changes, corrections, stakeholder feedback, access, and executive coordination time. Decide what to continue, change, add, or stop. Document the new baseline and development priorities. The review should not manufacture certainty about a long-term relationship, but it should show whether trust is becoming operational through reliable work and clear boundaries.

Example for a leadership team

A founder hires an assistant to manage calendar, inbox triage, and weekly leadership follow-up. In month one, the assistant observes the inbox, schedules internal meetings, and drafts the follow-up list. In month two, the assistant applies an approved inbox taxonomy and proposes external meeting moves, while the founder approves sensitive replies. In month three, the assistant owns the Monday planning packet and calendar review. The team postpones travel ownership because the volume data shows that inbox work is heavier than expected. That is a successful adjustment, not an onboarding failure, because the scope follows evidence.

Measure whether the choice works

Use a small onboarding scorecard: access completed and reviewed, workflows observed, workflows accepted for independent ownership, response windows met, corrections, repeated questions converted into rules, and executive time spent clarifying. Pair the numbers with examples. A declining question count is useful only if the assistant is acting from real authority rather than guessing silently.

Review the evidence before approval

Before approving this onboarding decision, hold a short evidence review with the executive, the person who will manage the work, and any owner responsible for security, people, tax, legal, or specialist questions raised by the scope. Read the actual proposal, agreement, workflow, or candidate evidence rather than relying on a sales summary. Write what is confirmed, what remains an assumption, which conditions must be satisfied before access begins, and who can accept each condition. Use CISA cybersecurity resources for small and midsize businesses as a primary reference for the relevant external principle, then ask a qualified owner to interpret requirements that depend on your location or facts. The review should produce a go, revise, or stop decision with reasons.

Write the launch brief

Turn the decision into a one-page launch brief. Include the supported leaders, first workflow, intended outcome, input owner, service window, access needed, authority boundary, escalation contact, success evidence, and review date. Link the operating references, including founder executive assistant first 90 days and executive support onboarding checklist, so the person doing the work can find the surrounding rules. Walk through one normal case, one ambiguous case, and one failure case before expanding the scope. If the team cannot agree on the safe action in those examples, the design is not ready for a new assistant or provider to interpret under pressure.

Turn the guide into an action

Use this guide as a working decision record. Write the assumptions, owner, evidence, next review date, and safe response when an answer is missing. Keep executive judgment with the accountable leader and specialist decisions with qualified owners. HireExecutiveTeam helps leadership teams define and staff practical executive support; a useful next step is to compare the framework here with your current calendar, inbox, meeting, board, travel, and follow-through workload before discussing a role or service.

Related resources

• founder executive assistant first 90 days
• executive support onboarding checklist
• founder operations support