I Built a Model of Something That Didn’t Make Sense

I’ve always noticed how people often take something complex and turn it into a clean, confident statement.

Life doesn’t really work like that. Systems don’t work like that. Most things are messier than they look, shaped by multiple variables, small dependencies, and a lot of hidden structure.

We compress all of that into something simple—and then we act certain about it.

That always felt off to me. So it’s ironic that I built a model.

Because models are supposed to simplify. They’re supposed to reduce complexity into something you can point to and say, “this is what’s happening.”

But that’s not what this one is doing.

It’s not trying to explain everything or give the right answer. It’s trying to show what happens when we take a complex process and compress it into something that looks finished.

Most of the time, we don’t see the process. We see the output—the number, the interpretation, the final result. And it looks precise. It looks stable. It looks certain.

But that certainty doesn’t always come from the underlying reality.

It often comes from how the system is structured: how the data is generated, how it’s interpreted, how it’s reduced into a final form. Each step compresses a little more of the original complexity, until the result carries more confidence than the process behind it really supports.

That’s what the model is meant to surface.

Not what’s right or wrong, but where confidence and complexity start to drift apart.

I started thinking about this in pulmonary function testing, but the same pattern shows up in other systems with clean, final outputs.

I didn’t build a model to simplify reality.

I built a model to show how simplification can create the illusion of certainty.