How to write a business book · 5 min read
Thought-leadership frameworks — why most fail and what the good ones share
A framework is a portable mental model with a memorable name. Two markers separate the ones that get quoted from the ones that get skimmed.
The most-quoted business books all have one thing in common: one named framework the reader can sketch on a napkin. The frameworks that fail almost always fail at one of two markers — name, or originality.
Marker 1: name
A framework needs a name the reader can repeat out loud. Two or three words. Easy to pronounce. Easy to remember at the end of a long workday.
Strong names follow a pattern. They use a concrete metaphor (the “stack,” the “flywheel,” the “engine”). They number explicitly (the “three layers,” the “five forces”). They name a constraint or principle (the “minimum viable,” the “good-to-great”). They sound declarative, not academic.
Weak names are vague nouns or adjective stacks. “Strategic alignment.” “Comprehensive transformation.” “The leadership way.” These cannot survive being said in a sentence ten times in a row.
If you cannot say your framework’s name three times in a row without rewording it, the name is not done.
Marker 2: originality
The framework needs to be original to you. Not borrowed from another business book with the labels swapped. Business book readers in 2026 are sharp on derivative work; reviewers in industry communities call it out.
The honest test: would the framework still make sense if you stripped out your specific industry vocabulary? If yes, it is generic and probably borrowed. If no, if it depends on your specific operating context to make sense, the originality is real.
A second test: can you point to two specific experiences in your career where you used this framework to make a decision? If you can, the framework is real. If you cannot, it is something you read somewhere and packaged.
What good frameworks share
Beyond name and originality, the frameworks that get quoted share three traits.
Memorable in one diagram. Page-72-friendly. The reader can sketch it from memory after one read. Pyramid, matrix, flywheel, stack, sequence — pick a visual shape that fits the structure.
Actionable in 30 seconds. What does the reader do after reading? A framework that ends at “think about it” is too soft. A framework that ends at “pick which quadrant you’re in and act accordingly” lands.
Falsifiable. It can be wrong about something. Frameworks that explain every possible business outcome are not frameworks; they are vocabularies. The good ones make predictions that can be tested.
Where frameworks live in the book
Chapter 3, ideally. The first two chapters establish the problem (your story, the reader’s situation, the world that produced the problem). Chapter 3 introduces the framework as the answer. Chapters 4 through the end illustrate the components of the framework through case-study and principle.
Putting the framework in chapter 11 is a common mistake. The reader who buys the book wants the framework. Giving them the framework in chapter 3 and spending the rest of the book applying it is what works.
The component-per-chapter pattern
A four-component framework gets four chapters of application, one chapter per component. Plus opening and closing chapters. That structure gives you a 7–9 chapter book naturally, which lands at the 55–75k word count that business book readers expect.
A nine-component framework is too many components. You will lose readers by component six. Pyramid your framework to no more than four primary components, with sub-components held in reserve for the operating-detail later.
Naming workshops
A common pattern in our business-book engagements: we run a one-hour naming workshop at week 3 of the project. Ten to fifteen candidate names get generated, then voted down to the top three, then tested by saying each one in a sentence ten times. The name that survives is usually the right name.
The naming workshop is faster than agonizing alone and the cross-talk surfaces wording the author would not have reached solo.
What to do if you have many frameworks
Many of our business-book clients arrive with three to eight frameworks in their Notion doc. The work in the outline phase is to find the spine framework — the one that subsumes the others, or contains them as sub-components.
This sometimes means killing a framework the author is fond of. The math: a book with one framework outperforms a book with five reliably. The cut is the work.