Hands untangling a knot of cables in dramatic light
← All writing
· 2 min read

“That’s just how it is” is not an answer.

Most broken processes survive because nobody asks why. I’d rather take the problem apart.

There’s a sentence I’ve learned to be suspicious of: “That’s just how it is.”

It usually shows up around something broken. A process with six steps that should take two. A report nobody reads but everybody produces. A form that asks for the same information three times.

“That’s just how it is” isn’t an explanation. It’s a way of ending the conversation.

My instinct goes the other way. When something is messy or stuck, I want to take it apart. How does it actually work? Why was it built like this? What would it look like if we built it today, knowing what we know now?

Most of the time there’s no villain. Things get complicated one reasonable decision at a time, and nobody ever goes back to simplify. The fix isn’t heroic. It’s someone being curious enough to look.

A few questions I keep coming back to:

  • Who is this for, and what do they actually need?
  • Which steps exist only because an earlier step exists?
  • What would we lose if we stopped doing this entirely?

To me, a problem is a puzzle worth solving. And the best part isn’t solving it. It’s when the answer makes someone’s day a little easier — and they never have to know how messy it used to be.

Comments

No comments yet. Start the conversation.

Leave a comment

Post as

Comments are read before they appear. Have an account? Sign in or create one.

Get new posts by email

Occasional field notes on RF safety and compliance.