I work as a technology leader, but I write to understand why things happen.

Most writing about software focuses on practices, tools, or frameworks. Some of it is useful. Much of it misses the deeper question: why well-intended efforts, led by capable people, so often produce systems that disappoint.

This site exists to explore that gap.

Over the years, I’ve worked with organizations of different sizes and levels of complexity, helping them build software systems and the teams behind them. I’ve held senior leadership roles and seen firsthand how decisions made with clarity at the top slowly distort as they move through people, incentives, and structure.

What interests me is not failure in the abstract, but mechanism. How intent degrades into process. How structure reshapes behavior. How systems quietly override what individuals believe they are doing.

The essays here are not tutorials and not prescriptions. They are attempts to name patterns that tend to repeat across organizations, regardless of tooling, methodology, or maturity. Many of them start from situations that felt confusing or contradictory at the time, and are written only after those situations became legible.

I write primarily for people who carry responsibility: CTOs, senior leaders, investors, and operators who sense that something is off, even when metrics look fine and plans appear sound. If you’ve ever wondered why a change felt reasonable yet failed to land, or why an organization keeps producing the same outcomes despite sincere effort, these essays are for you.

This is not a consulting site, a résumé, or a collection of hot takes. I’m not interested in performance or persuasion. I write to clarify my own thinking, and to offer language that others may find useful when reasoning about their own systems.

I occasionally advise investors and organizations on technology, software strategy, and organizational risk.

If something here resonates, you’re welcome to reach out. I read every message, even if I can’t always reply.

– Esteban