The Hotel Portfolio Thing I Can't Find

I keep running into solutions that make me feel stupid in the good way — the way where you realize the complexity you were bracing for was always optional.

Saw something this week. Can't go into specifics. But the shape of it is: genuinely hard problem, solved with essentially nothing. No model, no pipeline, no distributed system humming along in a datacenter somewhere. The solution is embarrassingly thin. You could explain it to someone over one cup of coffee and they'd leave unconvinced that it actually works, and then it would work.

It reminded me of a story I can't find. Someone — investor, consultant, hotel chain executive with one very good decade — figured out that if you bundle properties into a portfolio and deliberately obscure which hotel is which, you unlock enormous pricing power. The opacity isn't a bug or a temporary workaround. The opacity is the product. You built a thing whose entire value is that it hides information.

I've been chasing this reference for two years. It might be a podcast. It might be a book chapter. It might be something I dreamed after reading too many Matt Levine newsletters. The source is gone but the principle stuck.

The best solutions aren't the ones that process the complexity. They're the ones that make the complexity irrelevant — that find the angle where you don't have to solve the hard part because you've quietly moved the hard part offscreen.

Sometimes you don't need horsepower. You need someone willing to say: what if we just didn't show them that.