My husband and I both work full-time job
Question
My husband and I both work full-time jobs, and we have a 3-year-old and an 11-month-old.
The physical chores are somewhat shared if I ask (he washes dishes if asked, takes out trash), but the "invisible mental load" falls 100% on me: tracking pediatrician checkups, monitoring diaper/formula inventory, scheduling daycare seasonal camps, noticing when shoes no longer fit, planning dinner meals.
When I brought it up last night, I snapped and said: "I have to project-manage our entire family while you just wait for instructions!"
He got defensive and replied: "I work hard too, and I do whatever you tell me to do, so stop treating me like an employee!"
Now we are in cold silence.
Could you provide guidance on:
- An opening script speakable out loud to reset the conversation and repair the rupture without defensiveness or guilt-tripping.
- Shifting from "task execution upon instruction" to "full domain ownership" (e.g. Conception, Planning, Execution of an entire domain like dinner or daycare prep).
- A concrete, specific request for this Sunday's 20-minute check-in.
- If he responds defensively, provide exact speakable lines to de-escalate.
Answer
I'll read the relevant reference cards for this situation.
The cold silence is the time to break, not the time to wait. You're not at 7/10 heat, but the longer it sits, the longer each of you builds your case in private. Here's a script you can use first — the repair line — then the reframe, the Sunday ask, and the de-escalation lines.
Opening line — say this first
I owe you an apology for what I said last night — calling you someone who just waits for instructions like an employee. That was unkind, and I'm sorry. I don't want to keep a scoreboard. Can we sit Sunday at 10 for twenty minutes and redesign how we own the unseen work? I'd bring three domains I'd take fully. I want to hear three you'd take fully. Then we pick.
Why this opener works
- It owns your snap first ("I owe you an apology"). It does not start with what he did wrong — that is guilt-tripping and invites his counter-defence.
- It has one concrete request with a named time and length (Sunday 10, twenty minutes). No "we should talk sometime."
- The framing is "redesign," not "complaint." That lowers his threat response.
---
1. The reframe: task execution → full domain ownership
The shift is from "I list, you do" to "you carry the whole thing, end to end." It has three layers.
| Layer | What it looks like | Example: dinner |
|---|---|---|
| Conception | Noticing the need exists | Fridge is empty tonight |
| Planning | Deciding what to do | Pasta, salad, fruit |
| Execution | Doing it | Shop, cook, clean up |
Today, you carry all three layers for almost everything. He carries Execution only — and only when you prompt it. That is why it feels like project management: you are the PM.
The rule of a domain: the owner carries all three layers and does not check in at each step. They surface only the outcome, or only when blocked.
Domains to put on the table (pick three each):
- Dinner (Mon–Fri): menu, shopping, cooking, kitchen cleanup
- Kids' medical: well-child visits, vaccine schedule, pharmacy runs
- Daycare / camps: registration windows, seasonal signups, teacher emails
- Wardrobe: shoes, clothes, seasonal swaps, outgrown bin
- Stock: diapers, formula, toiletries — what to buy, when to reorder
---
2. The Sunday 20-minute check-in — what to say and how to run it
Speakable request (use this exact line when you sit down):
Sunday at 10, twenty minutes, one topic: who owns what. No list of past failures. You pick three. I pick three. We choose. The choosing is the answer.
Shape of the twenty minutes (in order):
- Appreciation — one thing he actually does that you value. Not performed. eal. (This sets the tone. Two minutes.)
- eframe in plain words — "I want to stop being the project manager. I want us each to own full domains end to end."
- Domains on the table — each writes three. Compare. Pick together. No debate about who should pick which — just fit the math.
- The handoff rule — "If it's yours, you don't ask me at each step. Tell me the outcome. Ask me only if you're stuck."
- eview date — revisit in two weeks, ten minutes. Just: what's working, what to adjust.
End on time. Stop at twenty minutes whether you've finished or not. Finishing is not the point. A short, repeatable Sunday is.
---
3. If he gets defensive — speakable lines
You said exactly this last night, so his defence was predictable. Here are the lines for what he might throw back.
If: *"I do everything you ask!"*
→ "That's exactly what I'm trying to change. I want you to own a domain so I stop asking."
If: *"So I'm supposed to read your mind?"*
→ "No. I want to stop being the one who lists. You pick the domain. You decide inside it. You only come to me if you're blocked."
If: *"You'll just blame me when I get it wrong."*
→ "If it's yours, I won't audit it. I'll say it once if I see a real problem. Otherwise it's yours."
If: *"I work all day too."*
→ "I know. This isn't about hours. It's about the thinking, not the doing."
If: *"Why does this have to be me?"*
→ "You don't take all of it. You pick three. I pick three. We split."
If he goes quiet or walks out:
→ "I'll be in the kitchen at 10 on Sunday. Twenty minutes. I'd like you there. If not this Sunday, name the next one."
If he says yes but does nothing for two weeks:
→ That is data, not a fight. Bring it back at the two-week review, not before.
---
Honest limits. I can give you the shape of the conversation, not the man. If the cold silence doesn't break with this opener, the underlying issue may be bigger than workload distribution — it may be that he hears any request as a performance review. If after two or three of these check-ins nothing shifts, the next move is a couples counsellor, not a better script. That's not a failure on your part; it's the right next step when the same loop returns and one person keeps doing the redesign alone.