I've been thinking about project management this week. Not in a corporate sense — Gantt charts, Jira tickets, RAG status updates. In the way a kitchen renovation actually runs. Or a school holiday schedule across three different children's commitments. Or planning your own multi-day wedding for eighty guests in the Hunter Valley over the Australia Day long weekend while managing accommodation, transport, suppliers, weather backup plans, dietary requirements, seating charts, timelines, and the very real possibility that one person will still RSVP three days before the wedding.
Someone has to hold the whole thing. Track the dependencies. Chase the tradesperson who hasn't confirmed Tuesday. Notice that the benchtop delivery conflicts with the school pickup and quietly rearrange both without it becoming a thing. Buffer for the something that will inevitably go sideways in week three, because something always goes sideways in week three.
That someone, in most households, is a woman. She does it without a title, without a team with any real accountability, and without anyone acknowledging that what she is doing is — by any professional definition — project management.
Most people still describe this work as “helping” or “being organised.”
But if you stripped the emotion out of it and dropped it into a corporate environment, everyone would immediately recognise it for what it is.
It’s project management.
Complex, multi-dependency, often emotionally charged project management delivered with no budget authority, no escalation path, and no one above you to absorb the decisions you’d rather not make alone.
And what fascinates me is that many of the women doing this work at home are also doing a version of it professionally. They run teams. Budgets. Clients. Competing priorities. Difficult stakeholders. They coordinate people across time zones all day, then come home and launch straight into a second shift of invisible operational management with none of the infrastructure that normally supports it.
No clear ownership. No agreed timelines. No definition of done. Just years of accumulated mental tabs running quietly in the background while everyone else experiences only the outcome.
It doesn't say that by midlife, some women have been running this double-shift for fifteen or twenty years. And that the cumulative cost isn't just fatigue — it's the slow erosion of being able to locate yourself in your own life, because you've been so thoroughly located in everyone else's.
And it doesn't say that when the wheels start to wobble — when the mental load tips into overwhelm and the to-do list stops feeling manageable — it is often not because these women can't cope. It's because they are running enterprise-level complexity on a notes-app-and-adrenaline system, and that system has finally hit capacity.
I know this because we put in a pool and spa back in 2019.
What started as a fairly innocent conversation about “improving the backyard” somehow evolved into a multi-month coordination exercise involving excavation schedules, fencing compliance, electrical work, landscaping, delayed deliveries, council approvals, drainage issues, weather delays, and approximately forty-seven conversations about pavers.
At one point I was tracking supplier lead times while mentally calculating whether the concrete pour would clash with school pickup and whether we could survive another week with what looked like a small construction site occupying most of the backyard.
Meanwhile my husband approached the entire project with the energy of a man fully expecting it to collapse into financial ruin, structural defects, torrential rain, or all three simultaneously. Every delay was apparently a sign the whole thing was doomed. Every unexpected cost confirmed we should probably have “just left the yard alone.”
So while I was coordinating trades, suppliers, timelines and council approvals, I was also effectively responsible for counteracting the project negativity at a spiritual level. I’m convinced at one stage I was personally yelling positive messaging into the universe just to neutralise his increasingly specific predictions about everything that could go wrong.
And of course there was a delay in week three. There is always a delay in week three. I don’t know whether this is a law of construction or simply a universal human experience, but I’ve never seen a home project escape it.
When the project was finally finished, my husband commented several times on how smoothly the whole thing had gone. Which, to be fair, it had. The trades arrived. The materials turned up. The budget broadly held. The children survived. Nobody ended up divorced over tile selections.
But smooth was not an accident.
Smooth was project management.
It was someone quietly holding the entire dependency map in their head for months while making it look effortless to everyone else involved.
This is not a complaint. It's an observation about how thoroughly invisible the skill is — even to the people standing closest to the person carrying it.
And I think we've made a category error in how we talk about this. We name it as a domestic issue, a mental load issue, a gender equity issue. All of those framings are accurate. But we've missed something by not also naming it as a skills issue — specifically, that a large number of women in midlife are sitting on significant, hard-won project management capability that has never been formally recognised, properly scaffolded, or given the tools it deserves.
That's what I've been sitting with this week.
Because if you're already doing the work — and most of you reading this are — you deserve better systems than scraps of paper, mental tabs, and hoping you'll remember everything at 2am. You should have the same infrastructure a professional project gets. A clear scope. A realistic timeline. A budget that's visible rather than approximate. Accountability that doesn't all point back at you. A way of seeing the whole thing at once instead of holding it in your head while also cooking dinner.
Better tools don't fix the underlying distribution problem. I want to say that plainly. Giving yourself a decent project framework doesn't resolve why you're the one running the project. Those are different conversations, and the structural one matters more.
But tools do something the structural conversation doesn't: they make the work visible. When a project is laid out — dependencies mapped, risks noted, decisions logged, timeline real — it is considerably harder for the people around you to experience only the outcome and miss the project entirely. The invisible becomes legible. And legible things are harder to keep taking for granted.
The question worth asking yourself is this:
What's the project you're currently running that nobody else in your household could describe in full — scope, status, what's at risk, what's next?
Not a trick question. Most of us have an immediate answer. That answer is worth paying attention to.
Start steady. Then decide.
— Gill
0 comments