Welcome to Layered Thinking
On systems, strategy, and the invisible forces shaping product decisions.
Most product conversations start at the surface.
The UI. The flow. The feature. The metric.
But over time, I realized that the outcomes of those conversations are usually shaped somewhere else — by incentives, infrastructure, policy, integration dependencies, organizational dynamics, and risk.
Layered Thinking is where I explore those deeper forces.
I’m a product designer who has spent much of my career working in complex, constraint-heavy environments — particularly in marketplace systems where you don’t control all the variables, and certainty isn’t always available on demand. I’ve worked on checkout flows that depend on external integrations, loyalty programs shaped by third-party providers, and experiences where compliance and regulation aren’t edge cases — they’re structural realities.
In those environments, I learned something important:
You can’t design clarity into a system that doesn’t produce it.
You can’t remove friction that exists for a reason.
And you can’t make good product decisions if you’re only looking at one layer.
What interests me most isn’t the interface itself — it’s the architecture behind it.
How constraint shapes craft.
How tradeoffs compound across teams.
How trust erodes when systems overpromise.
How designers move from shipping features to owning risk.
This isn’t a blog about pixels.
It’s a space to examine the systems, strategy, and invisible forces shaping modern product work — and to think more deliberately about the layers beneath what we build.
Because great design isn’t just about what’s visible.
It’s about understanding what’s underneath.