From Support to Co‑Pilot: Executive–EA Partnership Guide

What makes an executive–EA partnership a true co‑pilot role?

A strong executive assistant and executive partnership works like a co‑pilot relationship: you share context, trust, and decision‑making, not just to‑do lists. When this works, executives move faster, administrative professionals spot problems early, and both can focus on the work only they can do.

That was Rob Hosking’s opening challenge in this Admin Awards Institute roundtable. As Executive Director of the Administrative and Customer Support practice at Robert Half, he sees the data: executive assistants now sit in the top 25% of in‑demand administrative roles and are recognized as strategic partners, not just schedulers. His point was blunt: your impact “doesn’t happen by accident.”

In other words, being a co‑pilot is not a personality trait. It’s a set of shared behaviors: honest communication, delegated authority, and a deep understanding of each other’s priorities and preferences. When executives delegate with real trust and assistants lead with confidence, both stop operating in crisis mode and start operating like a unit.

The roundtable panelists — pairs like Savannah McAfee and Jeffrey Smith of Omni PGA Frisco Resort & Spa, Kristin Murphy and CEO Steve Beard of Adtalem Global Education, and several university and corporate teams — didn’t talk about magic chemistry. They talked about specific moves they made together so that, over time, each side could say: this is my partner, not just my support.

How do you set expectations in the first 90 days with a new executive?

The first 90 days set your ceiling. If you start as “calendar manager,” it’s hard to later claim “strategic partner.” For administrative professionals and executive assistants, those early weeks are the best time to define the relationship as a partnership instead of a task pipeline.

Syreeta Taylor showed one concrete way to do it when she started with Dean Chris Boyer at North Carolina State University. Before he even arrived, she took a professional development course, then found a leadership‑style assessment and asked him to complete it. She discovered he was a dynamic, diplomatic leader who thrives on harmony and team cohesion — critical intel for how she should communicate and advocate.

From there, they built a 30/60/90‑day plan together. With a new college, hundreds of faculty, and more than 500 staff, they mapped who he needed to meet, what he needed to understand, and how she could chip away at that list with him. That plan wasn’t busywork; it was a shared contract about pace, priorities, and expectations.

She also paid attention to small human signals. Knowing he was people‑focused and rarely celebrated himself, she quietly gathered personal details, then organized a surprise birthday door full of cards, balloons, and cupcakes. It was a simple move that said, “This team is home, not just a workplace.” That matters when someone is new to both a city and an institution.

Savannah’s first interaction with Jeffrey Smith was just as telling: a 7:00 a.m. airport interview before the Omni resort even opened. The conversation was “very straightforward person to person” about expectations and a partnership, not errands. From day one, she knew the job was to think with him, not just follow behind him.

How does radical honesty between executives and assistants really work?

Radical honesty sounds inspiring until you’re the one who just made the mistake. The panel made it clear: honesty only builds trust when both sides treat mistakes as data, not as character flaws.

Kristin shared a stomach‑dropping example from her early days with Steve Beard. At her second board meeting, she accidentally gave confidential board‑only materials to management and an external partner. When Steve asked what happened, she initially didn’t know. Then she realized the error — and was sure she’d blown it.

At the first break, she owned it. Steve’s response was clinical, not cruel: did she understand what went wrong, and how not to repeat it? When the answer was yes, his message was simple: they still had a day and a half of board meetings; they would fix the process and move on. No public shaming. No lingering punishment. Just a clear expectation that she’d internalize the lesson, which she did.

That pattern showed up across the panel. Chief of staff Jodi Fox recalled their CEO telling her when she started, “You are going to drop balls.” For a perfectionist, that was the last thing she wanted to hear — until, inevitably, she did drop a few. Remembering that conversation let her own the misses, correct them, and keep going instead of spiraling.

Executive assistant Helin Flores put it this way: “Trust isn't built on agreement, it's built on honesty.” In past roles, her honesty had been punished, so she went quiet. With Mark Bernard, she tested the waters on day one by telling him she “couldn’t deal with all the clutter” in his office. Instead of bristling, he handed her the project. The result: a better workspace and a clear signal that her perspective was wanted, not dangerous.

When do executives know it’s time to fully trust their EA?

From the executive side, trust often starts as a decision, not a reward. Several leaders on the panel described themselves as “trust givers” — choosing to extend deep trust early, then expecting their assistants’ professionalism to prove that instinct right.

Steve talked about the difference between trusting someone to move tasks and trusting them with judgment. When he gives Kristin visibility into why decisions matter, not just what needs to get done, he’s telling her: you have the context to prioritize, to say no on my behalf, and to position me for success. That’s a very different job than shuffling meetings.

Dean Chris described a turning point with Syreeta. He came in focused on defining the college’s voice — its mission, values, and how they communicated. Over time, he noticed her emails and suggestions sounded exactly like the voice he was trying to build. That was the moment he realized she could, in his words, “speak not for me, but as me.”

LaRae Campbell sees trust not just in words, but in access. Her CEO at PG&E told her, “If it’s on my calendar, consider yourself invited.” That one sentence reshaped her role. Sitting in every leadership meeting, she wasn’t just taking notes; she was eventually sitting at the table, adding perspectives, and being read into confidential projects under NDA when other senior leaders weren’t.

For Jodi, trust looked like a two‑week vacation. Instead of pulling in another chief of staff while she traveled, she named LaRae as the single backup for the CEO. Everything ran. That decision told the entire organization who the CEO trusted to keep the engine running when both of them were out of the room.

What daily rituals and tools keep an executive–EA partnership aligned?

Behind every “we just work well together” story was an unglamorous system. The point isn’t which tools you use; it’s that your tools reflect how you actually work together.

Savannah and Jeffrey rely on a deceptively simple process Jeffrey has used for more than 30 years: the Trace file. Every important document, priority email, site‑visit alert, or seasonal task goes into a physical file organized by date and month. Each morning, Savannah lays out that day’s traces on his desk; on the first of each month, they review the monthly ones (like October budget items) together.

Anything that doesn’t matter until April gets parked in April’s folder, so it won’t be forgotten but also won’t clog today’s bandwidth. Yes, it could be done digitally, but the power is in the shared ritual: a daily and monthly rhythm where they look at the same stack of priorities at the same time.

Syreeta’s system with Chris is more digital but just as intentional. She pushed him to move from labels to multiple inboxes so his email reflected how he actually needed to work. He resisted — until the volume made it obvious that messages were getting lost. Once he saw multiple inboxes surface what needed attention first, it instantly changed how he shaped his day.

LaRae talked about a strict “no surprises” rule. She, Jodi, and their CEO share live documents where each can drop updates and notes, so if one person knows something, eventually all three do. If an organizational change is brewing, LaRae will reach out even when someone is on vacation so no one walks into a meeting cold.

And the tools aren’t just operational. Kristin and Steve have human rituals too: team dinners, birthday celebrations, and, when she was struggling mentally, Steve insisting she go home for a few days even though it wasn’t great for his calendar. Those choices send a clear message: you’re a person first, a professional second. That kind of care makes it easier to be honest when things go wrong.

FAQ: What else should administrative professionals know about partnerships?

How do I ask for more access without sounding pushy?

Tie the ask to business outcomes, not ego. LaRae didn’t demand a seat in leadership meetings to feel important; her CEO framed it as, “If it’s on my calendar, consider yourself invited,” because having her in the room made decisions and logistics smoother. You can make the same case.

What if my executive resists feedback or new systems?

Start small and specific. Syreeta didn’t overhaul Chris’s entire workflow overnight; she kept bringing back the multiple‑inbox idea as email volume grew, then implemented it once the pain was obvious. Helin started with one honest observation about clutter, turned it into a project, and earned the right to weigh in on bigger issues.

Can radical honesty backfire?

It can, especially in cultures where mistakes are punished or hierarchy is fragile. The assistants on this panel tested for safety first: sharing one vulnerable admission (Kristin’s board‑packet error), one hard truth, or one tough heads‑up — then watching how their executive responded. When honesty was met with problem‑solving instead of punishment, they leaned in.

How do I know if I’m seen as a strategic partner yet?

Look for signs of trust and voice. Are you invited into meetings where decisions are made, not just communicated? Does your executive ask for your opinion and act on it? Can you, like Syreeta and Chris, hear your shared “voice” in what you write and say on each other’s behalf? Those are the markers of a true co‑pilot role.

To dig into the full stories and hear directly from these executives and administrative professionals, watch the complete session in the Admin Awards Institute library.