Executive Support Role Scope Diagnostic

Start with the decision: work diagnosis

For role selection, work diagnosis matters because founders choose the role design that matches the work rather than a fashionable title. 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: decision scope

For role selection, decision scope matters because founders choose the role design that matches the work rather than a fashionable title. 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: planning horizon

For role selection, planning horizon matters because founders choose the role design that matches the work rather than a fashionable title. 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: stakeholder reach

For role selection, stakeholder reach matters because founders choose the role design that matches the work rather than a fashionable title. 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: operating cadence

For role selection, operating cadence matters because founders choose the role design that matches the work rather than a fashionable title. 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: administrative depth

For role selection, administrative depth matters because founders choose the role design that matches the work rather than a fashionable title. 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: hybrid-role risks

For role selection, hybrid-role risks matters because founders choose the role design that matches the work rather than a fashionable title. 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: candidate evidence

For role selection, candidate evidence matters because founders choose the role design that matches the work rather than a fashionable title. 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: first-quarter outcomes

For role selection, first-quarter outcomes matters because founders choose the role design that matches the work rather than a fashionable title. 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: redesign triggers

For role selection, redesign triggers matters because founders choose the role design that matches the work rather than a fashionable title. 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 role selection

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 work diagnosis with decision scope during role selection. If stakeholder reach changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare decision scope with planning horizon during role selection. If operating cadence changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare planning horizon with stakeholder reach during role selection. If administrative depth changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare stakeholder reach with operating cadence during role selection. If hybrid-role risks changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare operating cadence with administrative depth during role selection. If candidate evidence changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare administrative depth with hybrid-role risks during role selection. If first-quarter outcomes changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare hybrid-role risks with candidate evidence during role selection. If redesign triggers changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare candidate evidence with first-quarter outcomes during role selection. If work diagnosis changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare first-quarter outcomes with redesign triggers during role selection. If decision scope changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare redesign triggers with work diagnosis during role selection. If planning horizon 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