I Stopped Calling It a Good Father and Asked What I Was Actually Modeling
# I Stopped Calling It a Good Father and Asked What I Was Actually Modeling
There’s a version of “I was there” that still teaches the wrong thing.
I wasn’t the father who missed everything. I want to be clear about that — not to defend myself, but because the post isn’t about that guy. That guy’s story is easier. More obvious. Mine was quieter and took longer to name.
I was around. I provided. The lights stayed on. I worked hard and I worked *for* them and I told myself that story so many times it stopped feeling like a story and started feeling like a fact.
The question that broke that open wasn’t “were you a good father?” It was: **what were you actually modeling, year after year, when the business needed something and the room needed something at the same time?**
That one’s different. That one has a specific answer.
—
## Always Partially Elsewhere
Here’s what the pattern actually looked like — not as a verdict, just as a description.
Physically present. Mentally still in the open tab.
Dinner at the table, brain still on the missed follow-up, the deal that was sideways, the thing I should’ve said on that call. The family learned not to ask during high-stress stretches — not because I told them not to, but because they already knew what happened when they did. That’s not a rule you make. That’s a rule that forms on its own when the pattern runs long enough.
The contractor who gets home and “just knocks out” 45 more minutes because it’ll be faster if he does it now. The agent who is technically available everywhere, which means the business can follow him into every quiet moment unless he fences it off on purpose. The solopreneur who starts the morning with actual intentions and ends up carrying the whole business into the evening through his phone.
That last one was me. More often than I’d like to say.
This isn’t a time problem. Most operators with flexible schedules still have it. The laptop closes. The business doesn’t. It lives in the nervous system — in the half-attention, the quick phone check, the subtle shift in posture when a notification comes in mid-sentence. The family doesn’t experience that as “he’s busy.” They experience it as “he’s somewhere else.”
Real estate made it worse in a specific way. The nature of the job is that you’re technically available everywhere. A showing request doesn’t care that it’s Saturday. A client texting at 9pm isn’t doing anything wrong. And if you haven’t built a wall around the quiet moments, the work fills them. Every time.
—
## The Comfortable Lie I Kept Telling
“I was building something for us.”
True statement. Clean frame. Doesn’t ask any harder questions.
I grew up knowing what it meant when the power was uncertain. That’s not something you talk yourself out of. The drive to make sure my family never felt that — never had to wonder if the heat would come on, if dinner was covered — that was real. Is real. *You can’t have freedom if you’re worried about the power getting turned off or if there’s dinner on the table. That’s gotta come first.*
I believe that. Still do.
But there’s a point where provision gets covered, and after that point, you don’t get to stop the accounting there. “I kept the lights on” is necessary. It is not sufficient. And the kids weren’t keeping score on necessity. They were watching priority.
**Kids don’t learn your priorities from what you say you value. They learn them from what you consistently choose when business and family both need you at the same time.**
Every time the business won that negotiation without a fight — without even a moment of visible conflict — that was a data point. Not for being a bad father. For what the hierarchy actually was.
I wasn’t teaching them work ethic. I was teaching them that work always comes first, that you earn your way to presence, that the people in the room are the ones who wait. I didn’t say any of that. I didn’t have to.
—
## The Structure Was the Problem, Not Just the Effort
Here’s where I want to be careful not to make this a character flaw story, because it isn’t. It’s a design story.
Self-employment promises flexibility. For parents, that flexibility almost always means family time is *negotiable*, not that presence is *protected*. There’s no manager telling you to log off. There’s no hard stop. There’s just the business, always adjacent, always accessible, always with one more thing.
Digital tools made this worse before they made it better. The phone made the business portable. It didn’t make the operator’s presence more reliable — it made the business’s access to the operator total. Always-on isn’t a work style. It’s a structural failure that looks like dedication.
I can’t blame the tools. I built the system. I chose what I let follow me into the room.
The problem was never logging more hours. It was that my nervous system never fully left work. I could close the laptop and still be somewhere else. That’s what the family actually lived with — not my absence, but my divided attention. And divided attention, run as a default long enough, teaches something. It teaches everyone in the room where they actually rank.
—
## The Week Nothing Waited for Me
There was a week — not that long ago — where I didn’t open my laptop for three days. Not as an experiment. Just how it played out.
I came back to find the pipeline had run. Leads were scored. Content had published. Nothing had waited for me.
That was operationally interesting for about ten seconds. Then it became something else.
For the first time, I had actual evidence that my presence was no longer the only thing holding the business together. Which meant, for the first time, there was a real option to be somewhere else — fully. Not “I’ll check in later” somewhere else. Actually somewhere else.
That’s not a productivity win. That’s headspace coming back. That’s the first version of structural permission I’d ever built myself to be in the room without the business being in it with me.
The AI tools and automations I’ve built aren’t interesting because they save time. They’re interesting because they create the conditions for clean attention. The pipeline runs. The content publishes. The leads get scored. So when I close the laptop, I actually close it.
What that frees me *for* — that’s the part that matters. Not fewer hours. Fewer moments of split attention. More actual presence. That’s what the whole thing was supposed to be building toward, and it took me embarrassingly long to connect those two things.
—
## What They Actually Watched
I’m not going to wrap this up clean, because it doesn’t end clean.
Alan and Kenneth are adults now. Whatever got modeled, got modeled. I can’t go back and re-run the experiment. What I can do is answer the question honestly, because the question is worth something regardless of the timing.
What did they watch?
They watched someone who cared about them and was also frequently somewhere else inside his own head. They watched work win the close calls more often than not. They watched provision get treated like presence. They watched a man who was trying — genuinely trying — in a structure that made real presence hard to choose without building it in deliberately.
I don’t think I’m unusual in that. I think it’s the default pattern for operators who came up through scarcity, who learned that the only safety was building something, who carried the anxiety of instability so long it became ambient background noise they stopped noticing.
The business was never just a business. It was proof that we weren’t going back. That feeling doesn’t clock out. It follows you to dinner and sits at the table with everyone else.
Asking what I was modeling doesn’t change the past. But it changes the question I’m living with now, which is: what do I want the next stretch to show?
Not “am I a good father?” That question is too easy to answer in your own favor.
The harder one: what are the people closest to you learning from what they watch you choose?
That one sits with you differently. It should.
—
*If you’re an operator who just recognized the pattern and you’re thinking about structure — not motivation, not discipline, actual systems that let you actually close the laptop — that’s what FlowStateOps is for. One line: [flowstateops.com](https://flowstateops.com)*