I am increasingly interested in a paradox: I spend a great deal of time building more sophisticated systems while becoming more convinced that the life those systems should enable ought to feel simpler.
This is not an argument against complexity. Some of the problems worth solving are genuinely complex. Organizations coordinate thousands of decisions. Markets move. Technology changes. People bring different incentives, histories and forms of knowledge into the same room. Pretending that all of this can be reduced to a checklist usually creates a different kind of complexity later.
The question is what we do with complexity once we understand it. Do we push it outward and ask people to carry more dashboards, workflows, meetings, notifications and cognitive load? Or do we absorb more of it into the systems themselves so that people can spend more of their attention on judgment, relationships, creativity and responsibility?
Capability is not the same as progress
Artificial intelligence makes this distinction harder to ignore. We can now create, analyze, automate and coordinate at a scale that would have felt unrealistic not long ago. The natural response is to ask what else can be automated.
I think a better question is: what should greater capability make possible for the human beings inside the system?
If a company automates ten tasks but requires everyone to monitor twenty agents, review endless exceptions and live inside permanent operational anxiety, it may have increased machine productivity without improving the human system.
If technology saves labor but consumes attention, the cost has not disappeared. It has moved.
A Pura Vida stopping rule
This is where the Pura Vida philosophy has started to become more relevant to my work with technology rather than less.
One of its most useful ideas is simplicity. Not simplicity as minimalism for its own sake, but as a discipline: remove what does not make the system — or the life around it — meaningfully better.
That implies a stopping rule. More optimization is not automatically better. More automation is not automatically better. More growth is not automatically better. More intelligence is not automatically better.
The purpose of a sophisticated system should not be to make humans behave more like machines. It should give humans greater room to be human.
What I am trying to build toward
In my current work, I am experimenting with organizations in which humans set direction and increasingly capable computational systems help sense reality, organize information, coordinate work and execute within explicit boundaries.
The ambition is significant. But the success condition is not the number of agents or automations we can deploy. It is whether the organization becomes more capable per unit of human attentionwhile preserving human authority where it matters.
If the result is a founder who can think more clearly, a team that spends less time moving information between systems, a decision that arrives with better evidence, or an organization that can learn without adding another meeting, then sophistication has done useful work.
I suspect this principle extends beyond companies. We should judge much of our technology by whether it expands human agency without demanding that life reorganize itself around the machine.
High capability. Human scale.
I do not see ambition and simplicity as opposites. Nor do I think human-scale systems need to be small or technologically modest.
The interesting design problem is to build systems capable enough to deal with complexity while allowing the human experience on the other side to become clearer, calmer and more intentional.
That is a direction I want to keep exploring: sophisticated organizations, powerful technology and ambitious projects — in service of lives with enough space left in them to actually be lived.