Why some EAs start moving ahead


Hi Reader,

In the last few emails, I’ve talked about invisible work.
How it shapes careers.
And how many people learn, over time, to shrink their language around what they do.

Today I want to talk about the other side of that.

What actually changes when someone stops doing it.

The first shift is internal.

People stop thinking of themselves as “just support” or “a safe pair of hands”.

They start seeing themselves as someone who:

Keeps things moving.
Creates clarity.
Protects focus.
Influences outcomes.

That might sound subtle, but it isn’t.

Because how you see your role shapes what you reach for.

When you see yourself as operational, you aim for operational opportunities.

When you see yourself as someone who influences outcomes, you start expecting different conversations.

The second shift is external.

When people begin speaking about their work more clearly, others start responding differently.

With better questions.
More trust.
More invitations into discussions they were previously adjacent to.

This matters even more in the context we’re in now.

We’re already seeing more organisations treat “admin” as something that can be automated or outsourced.

Which is exactly why the EA role is quietly splitting into two paths.

Task-based support.

And strategic support.

The work that makes EAs future-proof has never been about tasks.

It’s judgement.
Context.
Relationship intelligence.
Knowing what matters, to who, and when.
Reading a situation before it becomes a problem.

The EAs who succeed long-term are not the ones who just execute tasks well.

They’re the ones who:

Understand the business.
Anticipate impact.
Create leverage for their executives.
Operate with commercial and organisational awareness.

Those things are hard to quantify.

They don’t fit neatly into a job description.

And they’re exactly the things that can’t be replicated by AI or offshore task lists.

This is usually where momentum starts, because this is where people become clearer.

Clear about what they bring.
Clear about where they add value.
Clear about the level they’re operating at.

I’ve watched it happen, again and again.

Next time, I’ll share more about what naming your work actually looks like in practice, and why it’s simpler than most people expect.

For now, sit with this: Minimising your language about your work isn’t lack of confidence or a personality flaw.

It’s a pattern.

And patterns can be changed.

See you soon,
Trinity

Trinity James

Career Coach

Views Professional Development

www.viewspd.com.au

Thank you for being here Reader I appreciate you!

Trinity James

You're doing work that's holding entire organisations together. Your resume probably doesn't show that yet. Neither does your LinkedIn. Neither do your interview answers. That's exactly what I help EAs fix. Subscribe for a weekly email written specifically for you.

Read more from Trinity James

Hi Reader, I’ve been thinking about something a client said during interview prep last week: “My confidence comes from competence.” I loved that because it felt like the opposite of “fake it till you make it.” A lot of the people I work with do not need to fake confidence. They need help seeing the evidence they already have, then practising how to speak about it clearly. That is often the real work of interview prep. Learning how to explain what you have actually done, with evidence that...

Hi Reader, I had a task sitting on my list for two weeks. I knew exactly what it was. I knew it probably wouldn’t even take that long. And yet every time I opened the document, I stared at it for about ninety seconds, felt my whole body say “absolutely not, thank you,” and decided my desk urgently needed dusting. Not my proudest moment, I'll admit. It got me thinking about procrastination, and all the advice we get bombarded with on this topic. I don't think we need another app to solve this...

Hi Reader, I've been running a lot of live sessions lately and last week one moment stood out. We were looking at a job ad together (Ralph Lauren, senior EA role) and someone flagged a single line in the requirements. The chat went off. Instantly. Strong opinions, both directions. It made me realise that the instinct these EAs had in that moment, that gut read of what a role is really asking for, is exactly what most resumes are missing. And it's costing them interviews. So I wrote about it:...