How I Think About Systems

I don’t start with trends, technologies, or narratives.

I start with constraints.

Most systems—whether financial, technical, or organizational—only make sense when viewed through the limitations they operate under. Remove those constraints, and you’re no longer describing reality, only a simplified model of it.

My approach is based on a few principles.

1. Constraints define the system

Instead of asking what is possible, I start by asking what is unavoidable.

Physical limits (latency, energy, space)
Operational limits (coordination, reliability)
Structural limits (authority, incentives)

These constraints shape what can actually work.

2. Order matters

Not everything can be built at once.

Some layers must exist before others:

Coordination before scale
Payments before markets
Settlement before finance

Understanding what comes first is often more important than understanding what comes later.

3. Systems are layered

I try to separate systems into distinct layers:

Physical layer (resources, infrastructure)
Operational layer (processes, interactions)
Financial layer (pricing, settlement, incentives)

Confusion often comes from mixing these layers together.

4. Look for where existing models break

Most ideas fail not because they are wrong, but because they are applied in environments where their assumptions no longer hold.

I look for:

where latency breaks coordination
where authority becomes unclear
where synchronization is no longer guaranteed

These are the points where new systems need to emerge.

5. Design from first principles

Instead of extending existing models, I try to rebuild systems from the ground up based on the environment they operate in.