Skip to content
El Observatorio

Foundations · 1 min de lectura

When There Is No Playbook: Leading Through AI-Era Hard Moments

Ben Horowitz wrote The Hard Thing About Hard Things for the moments when the management books run out — layoffs, failed bets, public humiliation, the CEO who cannot let anyone see how frightened they are. Those moments are not going away. If anything, AI-native companies will produce new versions of them faster, because the operating loop runs continuously and failure surfaces before you have time to prepare a story.

Con · estudiado y reformulado para builders AI-native“The Hard Thing About Hard Things” — Ben Horowitz

Managing Your Psychology Is Still the First Job

Horowitz's central argument is that the struggle itself is not a detour from building a great company — it is the building. Founders who treat hard moments as aberrations to be survived lose the lesson inside them. For a founder whose company is the loop — task, action, eval, human review, learning — psychological steadiness is not a soft skill. It is the condition that allows you to read what the evals are actually telling you, absorb bad signal without flinching, and update the system rather than rationalize it away.

Judgment Under Pressure Cannot Be Delegated

Agents do the first draft. The operating system runs the workflow. But when an agent misfires at scale, or a product bet collapses, or trust erodes with a key customer, the irreducible judgment call lands on a human. Horowitz was insistent that CEOs own the hard decisions personally — no laundering them through process or consensus. That same accountability structure belongs in every AI-native org: humans set the goals, define the boundaries, and own what happens when the system produces an outcome no one planned for.

Wartime Demands Clarity About What the System Is For

Horowitz distinguished peacetime leadership from wartime leadership — peacetime grows what works, wartime defends existence. AI-native founders will move between these modes faster than previous generations, because agents can execute a wrong strategy at speed. The discipline Horowitz prescribed — radical clarity about the problem, no tolerance for ambiguity in the chain of command, constant re-prioritization — translates directly into how you design goals and boundaries for autonomous workflows. Vague strategy does not become precise when you hand it to an agent; it becomes vague at scale.

Prueba el Desktop OS

Explora la escena startup de Atlanta, en vivo.

Todo lo que acabas de leer vive dentro de nuestro Desktop OS — un espacio de trabajo interactivo que se abre directamente en tu navegador. Su mesa de Atlanta mapea la escena startup de la ciudad: quién está construyendo, qué está pasando y dónde. Ábrelo y échale un vistazo.

Abre el Desktop OS →