What interests me in J. Christopher Herold's The Mind of Napoleon is the relationship between thinking and doing.
Herold edited and translated a selection of Napoleon's written and spoken words. The range goes beyond war into government, human behavior, education, and other subjects. In the introduction, Herold presents thought as something Napoleon repeatedly directed toward action.
That is the part I want to bring into the modern world.
An ambitious idea has to pass through a chain of decisions before it becomes anything. Someone has to understand the situation, decide what matters, learn what is missing, organize the work, and keep correcting it.
I am interested in the mind capable of doing that.
Let thinking produce a decision
You can think about a problem for a long time without making it clearer.
The conversation gets broader. More possibilities appear. Every answer creates another question. Eventually the discussion begins to feel productive because it contains so much thought.
I want to know what the thought allows us to do next.
For a business, that could be deciding which process to change first. For a product, it could be identifying the user whose problem we are going to solve. For yourself, it could be choosing the capability you need to develop instead of imagining a future version of your life.
A useful idea should eventually change a decision or an action. That is the standard I want to apply to my own thinking.
Give the details the attention they deserve
One observation in Herold's introduction that stands out is Napoleon's willingness to engage with practical details alongside large questions.
I connect that to a problem I see in how people talk about building.
The vision sounds large. The actual work sounds small: define a status, correct a field, decide who receives a notification, understand why a customer gets stuck, or check what happens when the same event arrives twice.
Those details are where the intended result either becomes possible or falls apart.
If a detail affects the outcome, I want to understand it. Calling it beneath the vision does not remove its effect on the vision.
This is part of what attracts me to software and operating systems. You can move between the overall goal and the exact mechanism that supports it. Both levels matter.
Read the contradictions too
Herold's selection preserves a fragmented and sometimes contradictory mind. That makes it more interesting to me than a tidy set of leadership maxims.
I can admire the force of a person's thinking and still examine where it becomes self-serving. A line that sounds impressive in isolation can look different beside another line, or beside what the speaker actually did.
I want to read that way. Take an idea seriously, ask what makes it useful, and keep enough independence to decide where it stops being useful. That is a better intellectual habit than collecting quotations that confirm the identity you already want.
Learn what the task requires
An ambitious goal will usually require knowledge you do not currently have.
That can become a reason to retreat, or it can become a description of the next work.
If the project requires understanding an industry, learn the operation. If it requires making a technical decision, learn enough to evaluate the alternatives. If it requires leading other people, develop the ability to communicate the direction and listen when the plan meets reality.
This is the idea of deliberately becoming more capable that I keep returning to.
The person capable of handling a larger goal is built through the demands of the work. You do not have to feel finished before starting to develop the missing ability.
AI makes direction more valuable
The modern version of this problem has an unusual feature: it is becoming much easier to produce.
You can generate a proposal, a design, code, or a large set of alternatives quickly. That gives a capable person more reach.
It also makes it possible to advance an unclear idea much further before you recognize the confusion.
I use AI extensively, so I want to be precise about the responsibility that remains with me. What should exist? What should happen? Which answer is useful? What evidence would show that the work succeeded?
The tool can accelerate the work. I still need to direct it and judge the result.
If the cost of producing an answer falls, the value of choosing the right question becomes easier to see.
Keep confidence connected to information
There is a temptation in reading an extraordinary historical figure to make confidence the entire lesson.
My own conclusion is more demanding.
Have enough confidence to act, then create ways to learn whether the action is working. Make it possible for someone to point out a problem. Look at the behavior of the customer, the operation, and the product.
The founder who needs every decision to prove their brilliance makes the business harder to improve. I would rather become better through a correction than defend an answer because I was the one who gave it.
That takes a different kind of confidence: confidence that you can keep developing.
Ambition should leave something useful behind
What I take from this book is a question I want to keep asking myself: what does this amount of thinking make possible?
An idea can become a product. A product can become a business. A business needs systems capable of carrying the work after the initial energy has passed.
That progression interests me much more than the appearance of being ambitious.
I want to learn, decide, build, and become more capable through the process. The result should make the ambition visible in something other people can actually use.
Source: J. Christopher Herold, editor and translator, The Mind of Napoleon: A Selection from His Written and Spoken Words, Columbia University Press, 1955; especially the introduction. Edition information. The modern applications above are my interpretation.