Review at Zenpundit

Mark Safranski, who writes under the name Zenpundit, posted a review of Tempo on his site. Safranski comes from the strategic studies world - the community of thinkers who take John Boyd, Carl von Clausewitz, and Sun Tzu seriously as sources of insight about competitive dynamics. His reading of the book reflects that lens, and the lens is interesting.

What the Strategic Community Sees

The strategic studies community reads Tempo differently than the business community or the self-help community. Where a business reader looks for operational frameworks and a self-help reader looks for personal improvement techniques, the strategy reader looks for models of competitive interaction. How does tempo create advantage? How does tempo disruption create disorientation? How does the OODA loop translate from fighter-pilot dogfights to broader domains?

Safranski picked up on several threads that other reviewers had missed. He noted the connection between tempo manipulation and what Boyd called "operating inside the opponent's decision cycle." When you act faster than your opponent can process, you create a cascading series of mismatches between their orientation and the situation. They are always responding to the previous state of the world, never the current one. This is not just speed. It is the deliberate use of tempo to generate confusion.

He also noted the book's treatment of narrative as a strategic instrument. The idea that strategy is not a plan but a story - a thick narrative rich enough to guide improvisation under uncertainty - resonated with a community that has long debated the relationship between planning and adaptation.

What Surprised Me

Two things about Safranski's review surprised me.

First, he spent significant time on the concept of tempo variation rather than raw speed. Most readers, including many strategic thinkers, default to interpreting tempo as "fast is better." Safranski understood that the argument is more nuanced. Sometimes slow is the correct tempo. Sometimes the advantage comes not from being fast but from being unpredictable - from varying your tempo in ways that prevent the opponent from calibrating their response.

This is a subtlety that gets lost in popular discussions of Boyd's work. The OODA loop is not about cycling as fast as possible. It is about cycling at the right speed for the situation, and about forcing the opponent to cycle at the wrong speed. The delta matters more than the absolute rate.

Second, he engaged with the book's philosophical dimensions rather than treating it purely as a manual. Strategy books are often read instrumentally - tell me what to do. Safranski read it as an exploration of how time, narrative, and decision-making interact at a deep level. He treated the ideas as ideas, not just as tools. This is rare in any reading community, and especially rare in one oriented toward practical application.

What the Reception Reveals

How a book is received tells you as much about the audience as about the book. The strategic studies community received Tempo warmly because it spoke their language and addressed their questions. It used Boyd's vocabulary. It engaged with complexity rather than simplifying it away. It took seriously the idea that competitive dynamics are irreducibly messy and that any framework claiming to reduce them to a clean algorithm is lying.

Other communities were less certain. Business readers wanted more case studies. Self-help readers wanted more exercises. Academic readers wanted more citations. Each group wanted the book to be something slightly different from what it was, which is a common fate for books that sit at the intersection of multiple disciplines.

The gaps in reception are informative. The parts of the book that confused business readers were often the parts that delighted strategy readers, and vice versa. The concept of temporal illegibility, for instance, landed well with the strategy community - they immediately recognized it as a description of the fog of war. Business readers found it less intuitive, perhaps because the business world works hard to maintain the illusion that temporal structures are always legible if you have enough data.

Notes on the Process

Reading reviews of your own work is a strange temporal experience. You wrote the book months or years ago. The person reviewing it is encountering it now. They are responding to who you were when you wrote it, but they are responding to you as if you are still that person. There is a lag, and the lag can be disorienting.

Safranski's review made me realize that some ideas in the book had matured in my own thinking since I wrote them. His comments on tempo variation sparked new connections that did not exist when I was writing. The review was not just a report on the book. It was part of a continuing conversation, and the conversation was moving faster than the book could.

This is the limitation of writing as a medium. A book is a snapshot. It captures thinking at a moment. The thinking continues, but the book does not. Reviews, conversations, and responses keep the ideas alive by subjecting them to new contexts and new questions. Safranski's review was a good example of that process at work.

Related

• A Moment of Silence with John Boyd - Visiting the source of many of these ideas.
• An Evening of Pace, Pace, Lead with Chuck - Strategic conversation in person.
• Towards Thick Strategy Narratives - The narrative dimension of strategy.