Nobody asked me to write Subtract to Ship. No publisher approached me. No audience demanded it. No market research indicated that the world was waiting for an Austrian innovation strategist to write a book about subtraction-based business methodology.
I wrote it anyway. And the act of writing it changed my thinking more than twenty years of doing the work ever did.
This is the thing nobody tells you about writing a book: the book isn’t for the reader first. It’s for the writer. The reader gets the finished product. The writer gets the process — the brutal, clarifying, ego-destroying process of converting implicit knowledge into explicit language.
The Problem With Implicit Knowledge
For fifteen years, I operated on instinct refined by experience. Walk into a company. Observe the patterns. Identify the waste. Design the solution. Deliver the result. My frameworks were in my head, and they worked — proven across dozens of consulting engagements, 40+ startups, and my own businesses.
But implicit knowledge has a ceiling. You can apply it yourself. You cannot transfer it to others. You cannot scale it beyond your personal capacity. You cannot examine it for flaws because you can’t see what you haven’t articulated.
When I was the bottleneck in my own business, part of the bottleneck was implicit knowledge. I couldn’t delegate quality control because the quality standard existed only in my head. I couldn’t delegate product development decisions because the decision framework existed only in my intuition. The owner dependency was partly a knowledge dependency — the knowledge hadn’t been made explicit enough to transfer.
Writing forced the implicit to become explicit. Every framework I’d been using unconsciously had to be named, defined, structured, and tested against its own internal logic. Some survived the translation intact. Others fell apart the moment I tried to write them down, revealing that what I thought was a framework was actually a collection of loosely connected habits that worked for me but couldn’t work for anyone else.
The Writing Process as Thinking Process
Writing isn’t recording what you think. Writing is thinking. The act of putting words on paper forces a precision that mental reasoning doesn’t require. In your head, an idea can be vague and feel complete. On paper, vagueness is visible. The gaps show.
The subtraction audit framework existed in my practice for years before I wrote it down. In my head, it was clean: identify what’s not working, remove it, redirect the resources. Simple.
When I tried to write it as a chapter, the simplicity collapsed. What does “not working” mean? How do you measure it? What’s the threshold for removal? How do you handle the emotional resistance to cutting things you’ve invested in? What about things that aren’t working yet but might in the future? Each question required a specific answer, and each answer required another layer of thinking that my implicit practice had never demanded.
The chapter took three weeks to write. The framework I emerged with was more precise, more teachable, and more honest than the one I’d been practicing. The writing didn’t just document my knowledge. It improved it.
Why Books and Not Blog Posts
I write blog posts too — you’re reading one now. But a book does something a blog post can’t: it forces long-form coherence.
A blog post can make one argument. A book must make a connected series of arguments that build on each other without contradiction. Every chapter has to relate to every other chapter. Every claim has to be consistent with every other claim. The requirement for coherence exposes weaknesses in your thinking that shorter formats hide.
Subtract to Ship exists because the connected nature of the subtraction methodology required a book-length treatment. The individual frameworks — the subtraction audit, the velocity principle, the Ship It Ugly philosophy — work individually as blog posts. But the way they connect, the way one framework creates the conditions for the next, the way the whole system produces outcomes greater than the sum of its parts — that requires the sustained argument that only a book provides.
Late to the Table exists because the starting-late narrative required the same sustained treatment. A blog post can say “it’s okay to start late.” A book can show why, using specific stories, specific data, and specific frameworks that accumulate over 200 pages into a convincing case.
The Authority Effect
There is a practical business reason to write books: authority. In the markets I operate in, published authors carry more credibility than unpublished experts with identical knowledge. This is not fair. It is real.
When I speak at conferences, the introduction mentions the books. When I consult with founders, the books serve as pre-teaching — clients arrive having already absorbed the frameworks, which means the working sessions start at a higher level. When I write blog posts, the books are the deeper resource I can point to for readers who want more.
Building authority through writing isn’t about ego. It’s about efficiency. A book is a scalable version of you — it communicates your frameworks to people you’ll never meet, at hours when you’re sleeping, in markets you’ll never visit. It works when you don’t, which makes it the ultimate system.
The Emotional Cost
Books are expensive emotionally. The writing process requires confronting your own limitations in a way that consulting and building do not.
When I consult, I’m the expert in the room. When I build products, I’m the founder making decisions. When I write, I’m a person alone with a keyboard and the terrifying question: do I actually know enough to fill 200 pages?
The imposter syndrome during the writing of Subtract to Ship was more intense than anything I experienced building Vulpine. Because with Vulpine, the market provided immediate feedback — products sold or they didn’t. With a book, the feedback arrives months after the writing, and in the meantime, you sit with your manuscript wondering if anyone will find value in it.
I wrote through the doubt. Not because the doubt disappeared but because the alternative — having the methodology in my head and keeping it there — felt like hoarding something that might be useful to others. The books nobody asked for are written by people who believe the ideas are worth sharing even without an invitation.
The Lesson for Founders
You probably have a book in you. Not necessarily a published, physical book. But a body of knowledge that you’ve accumulated through years of building, failing, learning, and rebuilding.
That knowledge is currently implicit. It lives in your head, in your habits, in your instincts. It’s useful to you and invisible to everyone else.
Writing it down — in any form: a book, a blog series, a course, a manual — will do three things:
It will clarify your thinking. The frameworks you use unconsciously will either survive the translation to explicit language or they won’t. The ones that survive will be sharper. The ones that don’t will be exposed as habits rather than principles, which is valuable information.
It will make your knowledge transferable. The owner dependency problem is partly a knowledge problem. When your methodology exists only in your head, you are the methodology. When it exists on paper, anyone can learn it.
It will build your authority. Not vanity authority — functional authority. The kind that opens doors, starts conversations, and creates opportunities that wouldn’t exist if the knowledge remained implicit.
Nobody asked me to write books. I wrote them because the process of writing was the process of thinking, and the process of thinking produced the precision that twenty years of doing could not.
Write the thing nobody asked for. The writing will repay the effort in ways you can’t predict.
