Lowest Common Denominators: Managing 13 Engineers and 2 Kids

Both roles require the same voice: not a dictator, but a facilitator who removes blockers. The overlap is bigger than you think.

I manage a 13-person infrastructure team during the day and a household with two neurodivergent kids in the evenings and weekends. For a long time, I kept those contexts mentally separate (work brain vs. home brain, as if they drew from different skill sets entirely). It took an embarrassingly long time to realize that the core competency is identical. In both environments, my job is to identify the lowest common denominator of what people need to function well, and then build systems that deliver it consistently.

The Lowest Common Denominator Framework

When I say "lowest common denominator," I don't mean dumbing things down. I mean finding the foundational needs that, if unmet, make everything else impossible. For my team, those are clarity on priorities, protection from unnecessary interruptions, and the psychological safety to say "I'm stuck" without career consequences. For my kids, those are predictability in routine, clear expectations delivered in a processable format, and the space to recover when things get overwhelming.

The specifics differ. The structure doesn't. In both cases, my role is to figure out what's blocking forward progress and remove it before anyone has to ask.

The Facilitator Voice

Early in my management career, I defaulted to the directive voice. Here's the task, here's the deadline, here's how I'd approach it. It worked, in the sense that things got done, but it produced a team that couldn't function without me in the room. I was a single point of failure for decision-making, and that's an architecture that doesn't scale.

The shift to facilitator happened gradually. Instead of "here's what to do," it became "what's blocking you from making progress on this?" Instead of providing the answer, I started asking which options they'd considered and what data they needed to choose between them. The team got stronger. Decisions happened faster because they didn't bottleneck through me. Engineers developed judgment instead of just execution skills.

Now let's talk about how the exact same evolution happened at home. For years, the parenting voice was directive by default: "Put your shoes on. Brush your teeth. Do your homework." Functional, but brittle. It required my constant presence and produced resistance at every step because the child had no agency in the process.

The facilitator version sounds different: "What do you need to do before we leave? What's making it hard to start? Do you want to do shoes first or backpack first?" Same outcome (kid leaves the house prepared), but the path gets there through the child's own executive function rather than mine. It builds capacity instead of dependence.

Where the Metaphor Gets Concrete

Here's a table of patterns I use in both contexts, not because I'm clever about it, but because I genuinely noticed myself using the same moves:

The common thread in every row is that I'm not doing the work for them. I'm creating the conditions where they can do their own work without unnecessary friction.

The Energy Budget

One concept from my MBA pre-reading that applies to both contexts is resource allocation. Every person (engineer or child) has a finite energy budget for a given day. When I spend their energy on things that don't matter (unnecessary meetings, ambiguous instructions, unpredictable schedule changes), there's less available for the things that do matter (deep technical work, emotional regulation, learning).

My job in both roles is to be thoughtful about where I'm asking people to spend their energy. If I can absorb complexity upstream so that it arrives downstream in a simpler form, everyone performs better. This is what "removing blockers" actually means when you strip away the management jargon, I take the hit so they don't have to.

Scoping This Honestly

I want to be clear that this framework works for us, in our specific environment, with our specific team dynamics and our specific children. I'm not claiming it's universal. Some teams need more directive leadership (early-career groups, crisis situations). Some children need different approaches based on their specific neurological profiles. The principle of "find the lowest common denominator and build systems around it" is broadly applicable, but the specific implementation always requires calibration to context.

What I can say with confidence is this: if you're managing people during the day and parenting in the evenings, you're not switching between two different skill sets. You're applying the same skill set in two different environments. The sooner you stop treating them as separate, the sooner you can let the lessons from each side inform the other. The overlap is bigger than you think, and the compounding returns from recognizing it are real.