Executive assistant discovery call questions for leadership teams

Start with the real decision

Which questions should a leadership team answer before choosing executive assistant support? The answer should follow the leadership team's real workflows, risks, and capacity rather than a generic rule. A discovery call should diagnose the work and operating conditions, not force a premature staffing recommendation. The most useful conversation identifies where executive time is being lost, what work repeats, which commitments cannot fail, and who owns decisions. Bring a representative week rather than a wish list. The call should end with explicit assumptions and next steps: a role profile, further information needed, a proposed first scope, or a clear reason the service is not a fit. A productive provider will ask about boundaries and dependencies as readily as it asks about tasks.

Avoid the common shortcut

Do not disclose passwords, private board material, employee records, customer data, or sensitive messages during an introductory call. Use categories and redacted examples. Avoid presenting every inconvenience as urgent; the provider needs to distinguish response expectations. Be wary if the conversation jumps from a job title to a candidate or package without exploring volume, executive count, working hours, and authority. The wrong diagnosis can make a capable assistant appear ineffective because the role was never coherent.

Map the work

Ask about outcomes: which leadership commitments are late, which meetings begin unprepared, which requests interrupt focus, and what would be observably better in ninety days? Translate relief into evidence. Fewer reschedules, prepared decision meetings, current follow-up, and a clear inbox escalation path are assessable outcomes. Feeling less busy may follow, but it is too vague to design a service around.

Make ownership explicit

Ask about demand: how many calendars, inboxes, meetings, trips, reports, and active projects are involved; which work peaks monthly or quarterly; and what currently consumes the executive or chief of staff. Separate current volume from planned growth. A provider cannot estimate capacity responsibly when the request says part time but the workflow list implies daily coverage for several leaders.

Test the operating model

Ask about authority and risk: what may support schedule, draft, send, purchase, share, or change without approval; which stakeholders and topics are sensitive; and what should happen when the rule is unclear. Discuss a real tradeoff, such as a customer call colliding with an internal review. The answer reveals whether the team has delegation rules or expects the assistant to infer them.

Protect access and judgment

Ask about working rhythm: time zones, useful overlap, response windows, planning meetings, communication channels, feedback, and who resolves priority conflicts. Clarify whether after-hours contact is an emergency exception or a routine expectation. Sustainable support needs predictable review and a named client owner. Availability alone cannot compensate for missing priorities and delayed approvals.

Choose a reviewable first step

Ask about launch and continuity: which workflow should start first, what access it requires, who provisions accounts, how the provider documents work, and what happens during absence or replacement. End by restating known facts, assumptions, exclusions, and unanswered questions. The next proposal should trace back to that record so the leadership team can see why the recommended scope and model fit.

Example for a leadership team

A CEO says calendar management is the priority. Follow-up questions reveal that the calendar is not unusually full; the real problem is that meeting requests arrive through three channels, no one knows which customer meetings are protected, and pre-reads are late. The initial scope should therefore include one request channel, an access rule, a weekly priority review, and pre-read cutoffs, not merely permission to move meetings. The discovery call changes the proposed work from reactive scheduling to a bounded calendar operating system. It also makes clear that the CEO must supply priority decisions that the assistant cannot invent.

Measure whether the choice works

Judge the call by the quality of the resulting brief. It should name the business context, workflows, volume assumptions, authority, security needs, overlap, client dependencies, first-phase outcomes, and open questions. If two participants leave with different definitions of the role, schedule a short alignment step before reviewing candidates. Ten extra minutes of clarification is cheaper than onboarding against a false assumption.

Review the evidence before approval

Before approving this buying guide 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 SBA guidance on writing a business plan 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 executive support workload intake matrix and executive assistant delegation framework, 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

• executive support workload intake matrix
• executive assistant delegation framework
• get an executive support consult