Change Management at Home

In infrastructure, nobody deploys a major platform migration on a Friday afternoon with no rollback plan. We phase it. We communicate timelines. We validate in a lower environment first, then promote to production with monitoring in place. And yet, when it comes to changes at home (new school schedules, shifting custody arrangements, introducing a new food to the dinner rotation) we often just... ship it. No phased approach. No pre-communication. No rollback.

For families operating with neurodivergence as the baseline, that approach fails almost immediately.

The Cost of Unplanned Change

Here's what I've observed in our environment: when a change lands without warning, the response isn't proportional to the change itself. It's proportional to the surprise. A minor schedule adjustment (e.g., "we're leaving ten minutes early tomorrow") can produce the same intensity of pushback as a major life transition if it arrives without lead time. The nervous system doesn't evaluate the magnitude of the change. It evaluates the gap between expectation and reality.

This maps directly to how I think about change management at work. When we migrated our monitoring platform a few years ago, the technical lift was moderate, but the people lift was enormous. Engineers had muscle memory built around the old tooling. The disruption wasn't in the new platform's complexity, it was in the delta between what they expected their workflow to look like and what it actually looked like on day one.

Phased Approaches That Work for Us

We've landed on a framework at home that borrows heavily from ITIL-style change management (though I'd never call it that out loud at the dinner table). It breaks down into three phases:

The key insight is that Phase 1 costs nothing. It's a single sentence delivered during a calm moment. But it buys enormous goodwill in Phase 3 because it removes the element of surprise. The child's nervous system has time to build a mental model of what's coming.

Rollback Plans Are Not Failure

One of the hardest mindset shifts for us was accepting that rollback isn't defeat. In infrastructure, a rollback is a sign of mature engineering practice. It means you planned for the possibility that your change wouldn't land cleanly, and you protected the system. At home, this looks like saying "we're going to try this for three days, and if it's not working, we'll adjust." That framing does two things: it reduces the perceived permanence of the change (which lowers resistance), and it gives the child agency in the evaluation process.

We've rolled back plenty of changes. Morning routine adjustments that looked great on paper but didn't account for sensory needs at 6:45 AM. Homework structures that assumed a level of executive function that wasn't available after a full school day. Each rollback taught us something, and the next iteration was better for it.

Transparency as Volatility Reduction

The pattern that keeps emerging, whether I'm managing a team of engineers or managing bedtime, is that transparency reduces volatility. When people (of any age) understand why something is changing, when it's happening, and what their role is in the transition, the emotional spikes flatten. Not to zero, but to manageable. The meltdown that would have been a P1 incident becomes a P3 that resolves with a conversation.

All of this goes to say: the frameworks exist. They're proven in environments with far more complexity than a household. The translation isn't even that difficult. The hard part is remembering to apply them when you're tired, when the morning is already sideways, when your instinct is to just push through and hope everyone adapts. They won't. Not without the phases.

What's Next

I'm working on building a lightweight "home change log" (a shared family document where upcoming changes are visible, with dates and a one-sentence explanation). It's early, and I'll share what we learn once we've run it for a few weeks. If you're managing similar dynamics at home, the question I'd leave you with is this: what's your current lead time between deciding on a change and implementing it? If the answer is "same day," that might be your root cause.