Jobs vs. Machiavelli: Should Founders Build Loyalty Through Love or Through Fear?

Steve Jobs first

Jobs perceives technological possibilities as paradigm-shifting moments that require revolutionary market creation, not as incremental improvements within existing competitive frameworks.

Niccolò Machiavelli first

Machiavelli perceives all situations as strategic laboratories where power dynamics can be empirically analyzed to extract transferable principles, not as moral scenarios requiring ethical judgment or personal positioning.

Collision highlight

One side treats the problem as a governance decision; the other treats it as an evidence problem. That split is the article's core signal.

Steve Jobs

I never tried to make people fear me. What I tried to do was make them believe — genuinely believe — that the work we were doing mattered enough to demand the best they had. When I told a team that a product they had built was shit, I was not trying to generate fear of consequences. I was trying to break the frame in which 'good enough' was an acceptable answer. The fear that some people describe feeling around me was the fear of not living up to what the work required — and that is not a management instrument. It is the natural response to being in the presence of work that has a standard. If the work doesn't have a standard that creates some fear of failure, the work doesn't matter enough.

Niccolò Machiavelli

Jobs is describing what I would call the ideal case of love-based loyalty — where the devotion attaches to the mission rather than the person, and the standard is enforced by belief rather than consequences. I do not dispute that this ideal exists or that it produces exceptional results when it is achieved. My concern is with the failure mode of the ideal. Jobs is also describing the mechanism of fear without acknowledging it as such: the fear of not living up to the work is still fear. The 'reality distortion field' that Jobs's colleagues described — the experience of being convinced that the impossible was achievable, and feeling the consequences of not achieving it — is not a description of love. It is a description of a particularly sophisticated form of accountability enforcement, where the standard is so high and the leader's belief in it so absolute that failure to meet it feels like a personal betrayal of something sacred.

Steve Jobs

The test of love versus fear as a leadership instrument is what happens after the leader leaves. An organization built on fear — on compliance with consequences enforced by a specific person — loses its coherence the moment the feared figure is gone. The enforcement mechanism disappears with the enforcer. An organization built on genuine belief in the mission can sustain that belief after the leader departs because the mission predates and outlasts any individual. When I was pushed out of Apple in 1985, the company did not hold. Not because the people stopped caring, but because the vision had not been distributed deeply enough into the organization to operate without me as its interpreter. That was my failure — not the approach, but the execution. The approach is still correct: if you build loyalty through mission, the mission can survive you. If you build loyalty through fear of you, nothing survives you.

Niccolò Machiavelli

The 1985 example is instructive, but Jobs draws the wrong lesson from it. The problem at Apple in 1985 was not insufficient love of the mission. The problem was insufficient structure — the accountability mechanisms that Jobs had built were too personal, too dependent on his presence, too idiosyncratic to be reproduced by Sculley. This is a structural failure, not a failure of the love-versus-fear model. My recommendation for a prince who must be absent from his territories is precisely this: build institutions, not dependencies. The enforcement structure should operate regardless of whether the feared figure is present. A founder who builds that structure correctly — clear standards, clear consequences, clear processes for applying them — can be absent, depart, or be succeeded without the structure collapsing. Jobs failed to do this. He is correct that love of mission is more durable than fear of a person. But his model conflates love of mission with love of Jobs, and then uses the failure of the latter to argue against the reliability of Machiavellian structure.

Steve Jobs

The structural argument is correct, and I accept it as a convergence point. The question is not whether you want people to be devoted or disciplined — you want both. The question is the sequence and the priority. Fear-first leadership establishes compliance before it establishes vision. Vision-first leadership establishes mission before it establishes accountability. The failure mode of fear-first is that the compliance is real but the belief never arrives — you get an organization of people who follow the rules and have no idea why the rules matter. The failure mode of vision-first is that the belief is real but the accountability is inconsistent, because holding people to a standard feels like betraying the relationship. The resolution is that accountability is not in tension with mission — it is an expression of it. When I rejected work that didn't meet the standard, I was not punishing people. I was refusing to let the mission be betrayed by work that was below it.

Niccolò Machiavelli

Then we are closer than the framing of the question suggests. The practical recommendation I would offer a founder is this: establish the performance standard before you establish the personal relationship. The standard gives the relationship its content — devotion to what? loyalty to what purpose? — and makes the accountability structure legible as mission-defense rather than arbitrary authority. A founder who establishes the relationship first and the standard second will always find it harder to enforce the standard, because enforcement feels like a change in the relationship rather than a feature of it. Jobs's model works when the mission is clear enough that the standard is self-evident, and when the leader is present enough to interpret the standard continuously. Machiavelli's model works when the standard must operate in the leader's absence, or when the mission cannot yet be articulated clearly enough to carry the enforcement weight. Most organizations need both: Jobs's mission clarity to give the standard meaning, and Machiavelli's structural discipline to make the standard survive.