We just had a baby and everyone tells me how “lucky” I am to have such a relaxed, chill husband, but they don’t see that his relaxation is a luxury funded entirely by my hyper-vigilance.

My husband is very easy to be around.

He moves through the world at a pace that other people find appealing.

Unhurried. Unbothered.

The kind of man who can sit on the couch while the baby naps and just sit there.

Not planning. Not anticipating. Not running through the list of everything that needs to happen before she wakes up.

Just sitting.

People love this about him. His mother brags about it. My friends mention it.

“You’re so lucky,” they say. “He’s so relaxed. He’s so chill. Some men are just wrecks with a new baby.”

And I smile and say yes, I know, we’re very lucky.

What I don’t say is what I’m thinking, which is: he is relaxed because I am not.

His calm is not a character trait that exists independently of me.

It is a condition that I produce.

I am the infrastructure that his ease runs on.

He gets to be chill because I am hyper-vigilant enough for both of us.

What hyper-vigilance actually looks like

It looks like waking up thirty seconds before she cries because I’ve been monitoring her breathing sounds through the baby monitor, even in my sleep.

It looks like knowing exactly how many ounces she ate at the last feeding, what time she went down, how long she’s been asleep, whether she’s due for a growth spurt, and whether the sound she made an hour ago was gas or something worth watching.

It looks like having mentally mapped every pharmacy within ten minutes of our house that carries infant Tylenol. It looks like having the pediatrician’s after-hours line memorized. It looks like having packed the diaper bag with enough supplies for four different versions of the next six hours.

It looks like constant, low-level, never-quite-switching-off monitoring of a small person’s wellbeing, carried mostly in my head, mostly alone, mostly without anyone noticing it’s happening.

Because when it’s working—when the baby is fed and clean and sleeping safely, and the bag is packed, and the appointment is scheduled—it looks like nothing. It looks like things are just fine. It looks like everything is under control.

It doesn’t look like labor because it’s invisible. But it’s labor.

His relaxation is not an accident

My husband is not relaxed because he is a naturally calm person, though maybe he is that, too.

He is relaxed because the things that would make him anxious are being handled. The baby’s needs are being tracked…by me. The appointments are being made…by me. The supplies are being stocked…by me. The night wakings are being responded to…mostly by me.

He can sit on the couch and not worry because there is nothing in his immediate experience to worry about. Not because the worrying doesn’t need to happen—but because I’m doing it.

If I stopped, the worry would still exist. It would just be unattended. And then something would fall through the cracks, and then something would go wrong, and then he would not seem so relaxed anymore.

His calm is downstream of my vigilance. That’s not a metaphor. It’s the actual causal structure of our household.

The thing about being told you’re lucky

I understand why people say it. From the outside, a relaxed husband is better than an anxious one. Better than an absent one. Better than one who panics or checks out or makes everything harder.

All of that is true, and I know it.

But “lucky” carries an implication that his relaxation is a gift—something he’s giving me, something that exists for my benefit. And that’s where it gets complicated. Because his relaxation doesn’t reduce my load. It just makes it invisible.

A panicking husband would at least make the problem visible. You could point to it. You could say: Look, we need to redistribute this. But a relaxed husband makes everything seem fine. The calm reads as competence. The ease reads as a partnership. And meanwhile I’m running the whole operation from inside my head and nobody—including sometimes him—can see it.

The luck framing also puts me in a position where I’m supposed to be grateful for something that is, in part, my own creation. I built the infrastructure that makes him look like a good parent. I maintain it daily. And I’m lucky?

What he thinks is happening

I think he believes we’re in this together.

And we are, in the ways he can see. He changes diapers. He does bath time. He gets up when I ask him to. He’s present and engaged and genuinely loves her. None of that is nothing.

But there’s a layer underneath the visible tasks that he doesn’t see—because I handle it before it becomes visible. He doesn’t know how many things I’ve already thought through, solved, and managed by the time he walks into a room. He doesn’t know what the house would look like if I stopped running the background process.

He thinks the baseline is fine because I make the baseline fine. And because I make it look easy, he doesn’t know it’s hard.

I’ve tried to explain this, and I hear myself, and I know how it sounds. It sounds like I’m complaining about being capable. It sounds like the problem is that I’m too competent. And there’s a version of that that’s almost funny.

Except it’s not, at 4 am, when I’m the one awake again.

The performance of gratitude

This is the part that exhausts me almost as much as the vigilance itself.

I am expected to be grateful. Not just to feel it privately—to perform it. To say “I’m so lucky” when people bring up his relaxedness. To frame his baseline participation as something exceptional. To treat the fact that he is present and engaged with his own child as a gift I’ve received rather than a floor I was owed.

Every time I perform that gratitude, something in me shifts slightly.

Because gratitude is appropriate when someone gives you something extra. It’s not appropriate for someone doing the minimum. And somewhere in the gap between those two things, I’ve lost track of which one this is.

He’s a good father. He’s a good partner. He is also, structurally, the beneficiary of a system I built and maintain, and he doesn’t fully know it, and I don’t know how to tell him without it sounding like an attack on his character instead of an observation about our arrangement.

So I smile. And I say we’re lucky. And I mean some version of it.

And then I go back to running the operation that makes it true.

What I want instead of “lucky”

I don’t want him to be anxious. I’m not asking for that.

I want him to be aware. Those are different things.

Awareness would look like him understanding that the calm he moves through is not ambient—it’s manufactured, by me, continuously, without a break. It would look like him asking what he’s not seeing rather than assuming the absence of visible problems means there are no problems. It would look like him understanding that his relaxation has a cost, and the cost is being paid by someone else, and that someone deserves to be seen.

I want someone to notice what I’m carrying before I put it down.

I don’t want to stop being capable. I don’t want to manufacture chaos to make my labor visible. I just want one person—the person I’m doing all of this with—to look at me and understand what he’s looking at.

Not lucky. Tired. Working. Here.

That would be enough.