How to Grow Your Career as an Executive Assistant
Takeaway: An EA career can grow through deeper executive-office expertise, a lead role, or a move into broader operations. Choose the work you want, then agree on an assignment, the time to do it, and how your progress will be assessed.
You've become the person colleagues call when an executive visit changes at short notice, a sensitive meeting needs careful handling, or a plan has three gaps nobody else has spotted. You're good at the work. The next question is what you want more of.
Perhaps you'd like a more complex executive partnership. Perhaps you enjoy coaching other assistants. Or perhaps the project you ran last quarter was the part of your job you most wanted to keep doing.
Those interests point toward different next roles. Career planning becomes more useful when you can describe the work you want, rather than trying to find the single title that comes after executive assistant.
Start with the work you'd like to keep
Look back over a few recent weeks. Which responsibilities used your strongest skills? Which stretched you in a way you enjoyed? Which would you gladly do less of?
Be specific. “More strategic work” could mean preparing an executive for decisions, owning a planning process, managing a team, or analyzing a business problem. Each requires a different opportunity and some different skills.
Two broad directions can help you organize the choice.
Deepen your executive-office practice. This might mean a senior EA role, a more complex principal relationship, responsibility for an executive-office process, or leading an assistant team. It can include substantial project ownership and decision-making. Working as an EA to a CEO is one possibility, though the executive's title alone won't tell you how demanding or rewarding the position is.
Move into a broader operating remit. You might want to run a program, own a business process, manage operations, or explore chief of staff work. In that case, examine the new role's primary accountability. Which outcomes will it own? Will it have a team or budget? How much executive support will remain?
Both directions involve judgment, ownership, and results. You don't have to leave executive assistance to do meaningful work or build a successful career. And a move into operations can be a change of discipline rather than a guaranteed promotion in level or pay.
Read titles as clues
Companies use administrative assistant, EA, senior EA, lead EA, executive business partner, and chief of staff differently. A lead EA might manage people, coordinate coverage, or set standards without having direct reports. An executive business partner might do work another company calls senior EA.
Compare actual roles across four areas:
- Scope: the executives, processes, relationships, or projects covered.
- Authority: decisions the person can make and commitments they can approve.
- Resources: coverage, tools, budget, and people available to do the work.
- Terms: compensation, hours, location requirements, and development support.
A bigger title attached to the same workload and no additional authority deserves a closer look. So does a well-paid role with a less elaborate title that offers work you want. The EA salary guide explains how to compare pay sources without assuming a title guarantees a particular salary.
Try a defined assignment before committing to a path
A small, agreed assignment can tell you more than another round of browsing job descriptions. Choose something that lets you practice the work you're considering while solving a real problem.
For example, imagine the company's quarterly offsite repeatedly ends with unclear follow-up. An EA interested in deeper executive-office ownership could propose managing the full cycle: preparation deadlines, logistics, the decision record, and the handoff of actions to their owners. An EA exploring program management might propose coordinating one of the initiatives agreed at the offsite, with a sponsor, milestones, and contributors from other teams.
These are two different assignments, and neither is inherently more valuable. Both need clear ownership. The second also needs agreement from the teams whose capacity it uses.
Before you start, settle five points with your manager:
- What result are you responsible for?
- Which decisions can you make, and which need approval?
- What existing work will be reduced, reassigned, or covered?
- Who will provide feedback or help resolve obstacles?
- When will you review the assignment and discuss what comes next?
Put the agreement somewhere you can both refer to. A stretch assignment should have an end and a review, not become an indefinite second job added to your first.
Build the skill the assignment actually needs
Development is easier to use when it has an immediate application.
If you're taking on a recurring process, learn to map its steps, identify handoffs, and establish a useful measure. If you're leading a project, practice defining scope, dependencies, and the decisions needed to keep it moving. If you'll supervise others, seek support with feedback, delegation, and workload planning rather than assuming excellent individual performance will teach you management.
Business knowledge matters across these paths. Ask your executive or a knowledgeable colleague to explain the measures they use, the current priorities, and the constraints behind a decision. Read materials you're authorized to access. When something is unclear, ask about it before building a recommendation on an assumption.
Tools can help, including approved AI tools where appropriate. Learn one workflow well enough to understand its errors, review requirements, and limits. Being able to show that a process works reliably is more useful than collecting a long list of applications. Our AI and EA work guide examines that distinction.
For a possible chief of staff move, use the skills guide to compare your evidence with the work in a particular posting. A training program can fill a specific gap, but course completion doesn't establish readiness for every role with that title.
Keep evidence while the work is fresh
Record what you owned, the conditions you worked within, and what changed. Include the scale of the responsibility where it helps: the number of offices coordinated, the budget you managed, or the stakeholders involved. Use actual figures you can substantiate.
Not every useful result is a percentage. A process that now has a clear owner, a dependable coverage plan, or a decision record colleagues can find is worth describing. Explain the earlier problem and how you know the new approach helped.
Credit collaborators and distinguish your work from the team's result. Keep confidential details out of material you intend to share externally. A short private record makes the next performance conversation easier and gives you accurate material for your resume and LinkedIn profile.
Have a conversation about the next role
Bring a proposal your manager can respond to. For example:
I'd like my next role to include ownership of executive-office processes. I've enjoyed coordinating the planning cycle, and I want to develop that part of my work. Could we define an assignment for the next cycle, agree on coverage for my existing responsibilities, and review the result afterward alongside the senior EA criteria?
For a move into program management, name that direction instead. You don't need to imply a chief of staff ambition if it isn't yours.
Ask what evidence the organization would need, who makes the leveling decision, and whether an appropriate role is likely to exist. There is a difference between a skill you can develop and a position the company has budgeted to create. Learning that distinction early helps you decide whether to build internally, explore other employers, or pursue both.
Use a review date instead of a universal timeline
There's no dependable number of years that guarantees a senior title or an operations move. Scope, experience, company structure, available roles, and personal preferences all matter.
A useful plan can still be time-bound. Agree when you'll review the assignment, what you'll assess, and what decision you hope to make then. If the conversation keeps moving without clearer criteria, ask what has changed. Sustained additional responsibility should prompt a discussion about role design, capacity, and compensation, not an assumption that more unpaid work will eventually be recognized.
Frequently asked questions
Can an executive assistant become a chief of staff?
Yes. Compare the actual chief of staff remit with your experience and identify any gaps in cross-functional work, decision support, or leadership cadence. Shared skills can support the move, but the titles don't establish a universal difference in seniority. The EA-to-chief-of-staff guide covers the transition in detail.
Can I progress while staying an EA?
Yes. Growth can include deeper expertise, more complex responsibilities, a stronger partnership, team leadership, better compensation, or working conditions that suit you better. Those are worthwhile career goals without a move into another discipline.
What if my employer has no next role for me?
Ask which development opportunities it can support and whether a change in scope or compensation is possible within your current role. You can also assess external roles against the same criteria. A small organization may value your work and still have limited room to create the position you want.
Do I need a certification?
Start with the requirements of the role you're considering. A course is useful when it teaches something you need and gives you a way to practice it. Check the curriculum, cost, and employer requirements before treating a credential as the next step.
For more practical guides on executive-office and operations work, join The Brief.
