Progress Book Format
Let me start with something that took me a while to admit.
I have bought a lot of books I never finished. Not bad books. Good ones, by people who knew what they were talking about. They sit on a shelf, about a fifth read, and every time I look at them I feel a small, specific guilt.
For years I assumed that was a discipline problem. It isn't. It's a format problem, and once you see it properly you can't unsee it.
Nobody has an information problem anymore
Ten years ago, if you wanted to understand something, the hard part was finding a good explanation. That's over. You have an AI in your pocket that will explain almost anything, at any depth, in four seconds, for free.
So the scarce thing is no longer information. If anything, we have the opposite problem. There is more good material available than any of us can read in a lifetime. The bottleneck has quietly moved from finding to finishing, and from finishing to actually doing something with what we've read.
That's a different problem, and the 220-page book was not designed to solve it. A Progress Book is.

What industry trends are teaching
One. Millions of people pay money every year to not read books. Blinkist reported around 30 million users and roughly $50 million in revenue before Go1 acquired it in 2023. getAbstract has been doing this since the nineties and has over 27,000 summaries. Whole businesses exist to give you the book without the book.
Two. Short form ate everything. The average person now watches over 80 minutes of short-form video a day. Instagram Reels account for half of all time spent on Instagram. TikTok videos under 30 seconds are finished 72% of the time, and those between 30 and 60 seconds are finished 54% of the time. Length is punished almost everywhere except in publishing.
Three. Corporate training has already adapted. The microlearning platform market was around $3.1 billion in 2025 and is forecast to roughly triple by the mid-2030s. Companies with real money on the line stopped running day-long courses. They now ship small, repeated modules that fit inside a working day.
Three separate signals point the same way: readers want something complete, focused, and usable, without the padding. The rationale and the building blocks are already here.
Where most people draw the wrong conclusion
The obvious reading is "people want less, so make books shorter." I thought that too for a while. I now think it's wrong in a way that matters.
Look at what the summary industry actually proves. It doesn't prove that short books are better. It proves that a huge number of people have decided a 300-page book isn't worth 300 pages of their life, and would rather have someone else's compression of it. That says something damning about the format, not something flattering about summaries.
Summaries also have a real problem. They hand you the what and drop the why and the how. There's no space to think, and nothing asks you anything. You close the app feeling productive without having changed anything. The learning research is not kind to that model, and critics of Blinkist use the same studies I'm about to cite.
The same goes for short-form video. I'm not saying books should be more like TikTok. It won because it respects a constraint that publishing pretends doesn't exist, and that is the lesson. Copying the product is not.
So a Progress Book is not a summary, and it is not a book chopped up for the feed. Size isn't the point. A Progress Book is built around the progress the reader makes, and it is only as long as that progress needs.
Which raises a fair question: why are books so long?
Why books are that long
Mostly because of shelves. A publisher needed enough pages to justify a price and a spine you could see in a shop. That was a distribution constraint, and it has been dead for about fifteen years. Much of what sits between the good ideas in a business book is scaffolding for a business model that no longer exists.
Remove the scaffolding and you still haven't solved the real problem. A book can be short and still leave the reader exactly where they started. That is why the Progress Book Format doesn't stop at cutting length. It changes what the book is for.
What the research actually says
This is the part I care about most, because I don't want you to agree with me on vibes. Here are five things that are either well-replicated findings or clearly declared values. You can argue that I've applied them badly. You can't really argue with the findings themselves.
1. The bottleneck is working memory, not time. Cognitive load theory says learning falls apart when a single session carries more than the mind can hold. So the principle isn't "short." It's "singular": one idea, one outcome. Short is what happens as a result. That is why every Progress Book is built around a single idea.
2. Retention comes from spacing, not exposure. Cepeda and colleagues reviewed 839 assessments across 317 experiments. Material revisited across gaps beats material crammed together, and the ideal gap grows with how long you need to remember. A book read in one sitting is a good way to encode something and a poor way to keep it. You need somewhere to come back to. In the Progress Book Format, that place is the companion BookSite.
3. Being asked beats being told. This is the testing effect and the generation effect, and it's one of the most robust results in learning science. Producing an answer yourself, even a bad one, beats being handed one. The questions in a Progress Book are not decoration. They are the load-bearing part.
4. Knowledge does not become behaviour on its own. Pfeffer and Sutton called this the knowing-doing gap in 2000. It's why so much reading and training changes so little of what anyone does. The good news is that we know what helps close it. Gollwitzer and Sheeran's meta-analysis found that if-then plans ("when X happens, I will do Y") improved goal attainment with an effect size of d = 0.65, across 94 studies and more than 8,000 people. Vague intentions did far less. Specific triggers did a lot. Every Progress Book ends with one.
5. Knowledge that gets used is the knowledge worth having. This one is a value, not a finding, and I'd rather say so plainly than dress it up. There's an old prayer I keep coming back to: seek knowledge that benefits, and take refuge from knowledge that doesn't. Knowledge that sits in your head and never reaches your hands has cost you time either way.
Four things we ask a book to do
Let me be more precise about the ask. What do we actually want a book to do? I've found it comes down to four things:
See. You notice something you hadn't noticed before.
Think. You have a better model for making sense of it.
Decide. You can tell which of two options is better.
Do. You act differently.
Most books are brilliant at the first two and hand you the last two as homework. Go and figure it out yourself. Nothing in the book helps you return to it, and nothing tracks whether you did the thing. You close it seeing more clearly, and what happens next is entirely up to you: how much sticks, and whether you use any of it. The standard book fires you out of a cannon and never looks to see where you landed.

That gap is the whole reason the Progress Book Format exists.
So, what is a Progress Book?
A Progress Book is a complete book with a narrow scope, designed so that you learn it more than one way and finish it having done something.
It is complete in its own right. It's not an extract, an abridgement, or a taster for a bigger book you're meant to buy later. Nothing was cut, because nothing was padded to inflate the page count.
It is laser-focused. One idea, taught properly, beats ten ideas half-learned and half-forgotten. Think of the piccolo: a full shot of coffee, 100% of the coffee, without filling your stomach. But a Progress Book is more than a concentrated read. It's built to change what you do.
One clarification on "learning it more than one way," because this part is easy to get wrong. The research does not say to deliver the same content in two channels at once. It says the opposite. Mayer's redundancy principle found that identical information presented simultaneously in two formats can reduce learning, because working memory burns capacity reconciling them. What works is meeting the same idea again later, in a different form:
Read it.
Try it in your own situation.
Come back a fortnight later and see how someone else applied it.
These are different encounters, spread across time. That is also why collaboration belongs mostly on the application side of a Progress Book, not the knowledge side.

The manifesto
Here's what I've put together: a manifesto for the Progress Book Format, with an open invitation to the people who know this territory better than I do.
One idea, one outcome. A Progress Book teaches a single idea and aims at a single change in what the reader does.
Complete, not condensed. A Progress Book is whole at its size. If it feels like an extract, it has failed.
Asks as well as tells. The reader produces their own clarity instead of only receiving someone else's.
Includes self-assessments. Every chapter puts a question to you that you have to answer yourself.
Ends with a plan of action. You leave with one specific thing you'll do, and when.
Reconnects through a companion site. The reader returns to BookSite, a space for meeting the idea again in a different form.
Invites collaboration on action. What you did with the idea becomes part of what the next reader sees.
An honest admission, and an invitation
I don't think I have the final shape of this.
I have the observations, the research, and a format that follows from both. What I don't have is a hundred authors and a few thousand readers telling me which parts survive contact with reality. That isn't false modesty. It's just where things are.
So this manifesto is a draft, deliberately. If you write, teach, consult, or have spent years accumulating something worth passing on, I'd like your name on the next version.
Two things I'd ask of you:
Take one idea you'd normally bury inside a 200-page book and try shipping it as a Progress Book.
Tell me which of the seven points above broke when you tried.
The second is worth more to me than the first.
References
Cepeda, N. J., Pashler, H., Vul, E., Wixted, J. T., & Rohrer, D. (2006). Distributed practice in verbal recall tasks: A review and quantitative synthesis. Psychological Bulletin.
Bjork, R. A. & Bjork, E. L. Desirable difficulties: spacing, interleaving, retrieval practice, generation, varied practice.
Mayer, R. E. The redundancy principle in multimedia learning. Cambridge Handbook of Multimedia Learning.
Gollwitzer, P. M. & Sheeran, P. (2006). Implementation intentions and goal achievement: a meta-analysis of effects and processes.
Pfeffer, J. & Sutton, R. I. (2000). The Knowing-Doing Gap. Harvard Business School Press.
Sweller, J. Cognitive load theory. See also Miller's pyramid of clinical competencefor the competence sequence.
Ryle, G. (1949). Knowing how and knowing that. Stanford Encyclopedia of Philosophy.
Go1 acquires Blinkist, Sifted, 2023. Blinkist revenue and user figures via Tracxn.
Microlearning platform market size and forecast, Fortune Business Insights.
Short-form video statistics 2026, Kapwing.
Mark, G. Attention Span. Research on screen attention averaging 47 seconds.
