My kid brought home a 60. I felt the lecture rising and barely stopped it. Sitting with it later, the rage wasn't really about the score — it was about him not doing the thing I wanted, when I wanted. Treating him as a separate person is mostly for my own sanity, honestly.
Kid brought home a math test.
60.
"You could've tried harder, y'know?" was already halfway out of my mouth before I caught it.
Catching it doesn't make me a great parent. For about half a second before that, my head had already done the whole thing — looked at the score, judged it, panicked, started writing the lecture. Out loud or not, the inside of my head was identical.
I sat with that for a minute. What is that, exactly.
The honest answer, once I let myself say it, was kinda unflattering.
I'm mad because he's not doing what I want, when I want it.
Not waking up at 7 when I asked. Not bringing back the score I had in my head. Not finishing the homework before screen time. Not listening when I'm trying to actually say a thing.
Of course that grinds me down. Every day, a little. Some nights I'm yelling, only inside, "quit testing my patience, kid."
But — and this is the part — this isn't really his problem. It's mine. I'm walking around with a private version of "how today should go" and getting genuinely angry when the kid doesn't comply with a script he never saw.
I needed a different frame, so I borrowed one from my day job.
In tech we usually split responsibility into two buckets:
Execs mostly carry outcome. Managers carry both. The IC carries process. That's not a hard rule, but it's the rough shape.
One night, putting the kids to bed, this hit me: I think parents are mostly on the process side. And I'd been quietly behaving like I had outcome responsibility for everything my kid did.
The test score. Whether he gets into a good school. Whether he gets a good job. Whether he's happy. Whether he's healthy. Whether he marries someone kind.
Those are his outcomes.
I literally cannot do them for him. I can't take the test. I can't go to the interview. I can't be happy on his behalf.
What I can carry is process. Around here that looks like:
That's about it. "Did I do those" is on me. "How it turned out" is on him.
Same as at work, kinda — I wrote the spec, I flagged the risks, I asked for review. After that, what the user does with the product is on the user. Not me.
There's a hard ceiling on this that nobody loves to say out loud: the years I get to do this for him are basically 20, give or take.
My older kid? Maybe 14 more years if I'm lucky. My younger one, maybe 16. If I stretch and call it 25, fine. But that's the runway.
After that, his life is his. I don't get to fix it from over here. And just on the actuarial math, I'm gonna leave the room before he does. Most parents do. "I'll always be here for you" is a sweet thing to say, but, like, physically, no.
If I forget that, the bad version of this is obvious. I'm 70 and still carrying my 40-year-old's outcomes around. I've seen it in extended family. It doesn't help anybody.
"I can't parent him forever" sounds cold typed out, but what I actually mean is the warm version: I'm betting on him being able to run his own life. The things I can't do for him, I shouldn't be trying to do for him.
Okay, this is the part the parenting books bury.
You'll read "treat your child as a whole person" everywhere, framed as a thing you owe the kid. That's nice. I think it's also lowkey misleading. The way I've started to read it: you treat him as a separate person because otherwise you, the parent, will burn down.
Logically:
As long as I quietly believe he's something like an extension of me — a small unit that ought to operate the way I want — every gap between what I want and what he does is a hit. All day. Every day. "Quit testing my patience, kid" on a loop. The math doesn't work. I run out.
If I let him be a separate person, the math relaxes.
A separate person doesn't move on my schedule. Obvious, when I say it about coworkers, or my partner, or honestly myself. I don't even do what I want, half the time. So the kid not doing what I want is just... that.
"Treating him as a separate person," for me, is less a moral upgrade and more load-bearing self-defense. I need it so I don't keep getting hurt by something that was always going to happen.
Here's the annoying side effect.
If he's a separate person, then "I'm not doing my homework tonight" is his call.
And, real talk, I don't fully accept that. I can see he's going to get chewed out tomorrow. I can see the email from his teacher coming. I want to grab his shoulders and go, dude, just do it now, it's 20 minutes.
I usually do, in fact, say that.
But the logic, if I'm consistent: a separate person gets to choose to not do the thing. If a coworker decided to skip their task today, my move isn't to lose it at them — it's to make sure they know it's their call and theirs to own. Same structure.
I don't do this gracefully. I'm somewhere between "the consequences of not doing it are his to carry" in my head and "just do it, please, I'm begging you" out of my mouth. That's the gap I'm parenting in right now.
Back to the 60.
When I flinched at the number, what was actually happening was: somewhere in my chest I was holding the outcome.
If I split it cleanly:
Holding that separation, the "you could've tried harder" thing softens. Not gone. Softer. I'll absolutely flinch again at the next test. I'm not above this.
The checklist I run on myself, end of day, is process only:
Those are mine. Pass/fail on those is on me.
Grading him on test scores, college admits, future paychecks — that part isn't really my lane.
That's about where I've landed for now.
The outcomes belong to him.
I gotta keep telling myself that, honestly, or I'm not gonna make it.