By Nick Kim in human-centric — 23 Jan 2026

The Real Reason a Developer Missed Deadlines: Frozen Pipes

There was a week when one of our developers suddenly looked off.

Deadlines slipped.
Commits slowed down.
In meetings, he was present, but not really there.

As a founder, your mind goes straight to the usual list.

Is he blocked technically?
Is the scope unclear?
Is he disengaged?
Is this burnout?

So I did what most managers do. I scheduled a 1:1.

“Anything blocking you?”

I expected to hear about architecture. A tricky bug. A dependency.

Instead, he said:

“My water pipes froze.”

I paused.

He continued:

“I can’t shower. And even using the bathroom is a struggle. I’m barely functioning.”

That’s when it clicked.

He wasn’t stuck in the code.
He was stuck in life.

In startups, we’re trained to interpret execution issues as skill issues.

Missed deadlines? Must be productivity.
Lower output? Probably motivation.
Less communication? Maybe attitude.

But sometimes, it’s none of that.

Sometimes, it’s plumbing.

Or a sick parent.
Or a breakup.
Or financial stress people do not talk about.

We overanalyze performance when the root cause is simply human.

That conversation changed how I lead.

When someone is slipping, I do not start with:

“What’s wrong with your work?”

I start with:

“Are you okay?”

Because software runs on people.
And people run on sleep, stability, and basic living conditions.

If the water pipes break,
the sprint breaks too.