The Skills Are Agnostic: What a Project Manager, a Virtual Assistant, and a Mom Have in Common

Here is a day in my life.

A stakeholder and I are mid-conversation. They're engaged, locked in, until something redirects them. A new priority has materialized. They expect me to absorb it, adjust, and keep moving without missing a beat. Their attention window closes. The new direction is set. They're already gone, leaving me holding the original goal, the new one, and the gap between them.

Is this a founder who barges into the project mid-sprint with a feature request he'll have forgotten by Friday?

Or is this one of my toddlers during breakfast?

Both. And the skill required to navigate them is exactly the same.

The contexts are different. The skill set is not. That's the argument I want to make, carefully, because it's easy to get wrong in ways that matter.

Managing a Household Is Project Management. I Mean That Literally.

There are stakeholders with competing priorities. There are dependencies, the dog can't be fed before the kids are up, or else the chaos compounds. (And I'll note: the dog is often the most overlooked member of the household and also the most reliable. Has your dog ever not been happy to see you fulfilling their role as emotional support?) There are recurring deliverables: school drop-offs, chicken chores, dinner, the schedule that lives entirely in your head because nobody else is tracking it.

There is risk management; the sick day that collapses three other plans, the appointment that runs long and takes the afternoon with it. There is scope creep, the quick errand that somehow unearths a backlog of other dependencies, the small house project that somehow becomes three. And it’s just a typical Monday.

And there is the thing that makes it hardest of all: none of it gets named. There's no project plan. No status update. No stakeholder who says, I see how much you're holding. The work is invisible until it breaks down, and when it breaks down, somehow that gets noticed immediately.

A parent managing a household is running a continuous, multi-stakeholder, zero-downtime operation with no documentation, no budget, and no title. That is not a soft comparison. That is a description of genuinely difficult operational work, the kind organizations pay consultants significant money to design, and pay moms nothing to execute.

The Title Was Missing. The Skill Wasn't.

When I was given the opportunity to lead and coach Virtual Assistants and Executive Assistants, I kept seeing the same pattern. These were people who had spent years, sometimes decades, managing calendars, communications, logistics, and the priorities of founders and executives who changed direction constantly and expected seamless execution anyway.

They were doing stakeholder management. They were doing real-time risk mitigation. They were triaging competing priorities on the fly, protecting their executive's focus the way a PM protects a team's capacity. They were translating vague, half-formed asks into clear, executable tasks. They were holding institutional knowledge that would have taken a new hire six months to acquire, and doing it without any of the formal structures that make that knowledge visible or transferable.

What most of them didn't have was the language to name it.

They didn't see themselves as project managers because nobody had told them that the work they were already doing had a framework, a methodology, a professional identity with real market value attached to it. They had spent years developing sophisticated operational intelligence in a context that doesn't come with a title, and so they undersold themselves constantly, to employers, to clients, and to themselves.

That's not a gap in their skills. That's a gap in how we talk about those skills. And that gap is expensive, for them and for the organizations that can't see what's standing right in front of them.

Scale Is Not the Same Thing as Skill

Here's where I need to be precise, because this is where the argument gets complicated.

A PM managing a $50 million international implementation: cross-functional teams, enterprise stakeholders, regulatory compliance, multiple time zones, is not doing the same job as a stay-at-home mom managing two kids and a household. I'm not arguing otherwise. The contexts are not equivalent. The scope is different. The stakes are different. The documentation, the governance, the professional accountability structures, all different, and those differences matter.

What I am arguing is this: scale is not the same thing as skill.

The ability to read a room. To triage competing priorities under pressure. To manage a stakeholder who keeps changing the ask without losing the thread of the original goal. To protect a team's capacity from unnecessary interruption. To build a system that keeps running even when you're not standing over it, these abilities don't appear fully formed the first time someone opens a project management tool. They develop through practice. Through repetition under pressure. Through every context where someone is responsible for holding complexity together on behalf of other people.

A mom who has spent five or more years managing a household has been practicing those skills, without the feedback loops or formal frameworks that would make the practice visible. A VA who has spent a decade anticipating an executive's needs before he knows he has them has been practicing those skills, without the title or the salary that would signal their value to the outside world.

They didn't earn a PMP. But they earned the capability. And those are not the same thing.

The Load-Bearing Wall Has No Title

Organizations pay for the PM title. They underpay for the EA title. They don't compensate the mom at all. But the cognitive load is comparable. The stakeholder complexity is comparable. The consequence of getting it wrong is comparable.

What differs is visibility.

The PM has a methodology with a name and a credential to signal it. The EA has a job description that systematically undersells what she's actually doing. The mom has a to-do list that never ends and no performance review, and in most conversations about workforce value, no seat at the table.

This matters beyond fairness, though fairness is reason enough. It matters because when we don't name a skill, we don't develop it intentionally. We don't build systems around it. We don't protect the person doing it from burnout. We just expect it to keep running, quietly and invisibly, until it doesn't.

The invisible operator is the load-bearing wall of every organization and every household. Remove her and everything downstream wobbles. But because the work is invisible, the wobble is the first moment anyone looks up and wonders what happened.

What I've learned across sixteen years of PM work, household management, and coaching VAs and EAs is this: the skills are agnostic. They don't care what context they live in.

Reading a room. Translating a vague ask into a clear next action. Knowing which fire to put out first and which one to let burn a little longer. Protecting someone's time and energy so they can do the work only they can do. Building the system that keeps running when you're not watching. These show up in a sprint planning meeting and in a school morning that has to go smoothly or the whole day breaks. They show up in an executive's inbox and in a household budget that has to stretch.

The org chart didn't invent them. The title doesn't grant them. They belong to the person who developed them, wherever she developed them.

What Gets Named Gets Built.

The credential matters. I want to be clear about that. The PMP signals a baseline of structured knowledge and professional commitment that has real value, and I earned mine for exactly that reason. But when organizations conflate credential with capability, they miss people who have spent years developing genuine operational intelligence in contexts that don't come with titles. That's not a soft skills argument. That's a talent strategy failure.

The first step toward closing that gap is naming the work.

Not as a performance for someone else, as a way of seeing it clearly yourself. Once you can name what you're doing, you can build systems around it, document it, teach it, protect it, and articulate its value in rooms where decisions get made.

If you're a VA or EA reading this and something here feels familiar, that recognition is data. The work you're doing has a framework. It has value. And you deserve to be able to name that value clearly, to a current employer, a future client, or yourself.

If you're a mom reading this and you just recognized your morning routine in a project risk register, same. The skills you built managing a household, competing schedules, and a rotating cast of small, unreasonable stakeholders are real and transferable. They didn't disappear while you were home. If anything, they got sharper.

This week: pick one recurring process in your work or your life that lives entirely in your head. Write it down. Give it a name. Make the invisible visible.

That's where it starts.