The Handbook That Never Shipped
Perfectionism in course production is a sequencing problem, not a quality one. The genuinely hard part of this business starts after you ship.
Justin Allan, NP4 min read

You are not making it better. You are making it later. Those have felt like the same activity for about six weeks now.
I want to tell you about a business I consulted with, because I have watched this happen from the outside and the shape of it is very clear from there.
The story
They were building an exam prep book for a certification in their field. Two partners, a lot of work already done, genuinely knowledgeable people.
I read it, and my honest reaction was that exam prep in their space was crowded — a lot of established products, a lot of competition on price. But the thing they had built was better than an exam prep book. Read a different way it was a superb handbook for someone to keep with them during clinical rotations, which is a narrower audience with almost nobody serving it and far more willingness to pay.
They agreed immediately. It was one of those conversations where the idea visibly improved in the room, and I came away thinking they had something.
I spoke to them again about a month later and asked where they had got to. His partner answered. He was still working on it.
It had been more or less ready when we first spoke. In the month since, it had not been repositioned, or launched, or put in front of a single potential buyer. It had been improved — and he was still improving it, and the partner's tone made it clear this was not the first month that had gone this way.
That is the whole story. There is no second act, which is rather the point.
What the month actually cost
Here is the part I want you to sit with, because it is not the obvious lesson.
The obvious lesson is "done is better than perfect," and everybody has already heard it and it changes nobody's behaviour, because in the moment the work genuinely is getting better. He was not procrastinating. He was doing real editing that produced real improvements.
The problem is what he was not doing.
Building the product is the easy half of this business. It takes time and it is work, but it is work you can do alone at a desk, on your own schedule, entirely under your control, with no possibility of public failure. The hard half is everything after: getting anyone to know it exists, finding out whether the people you built it for actually want it, discovering that the thing they will pay for is slightly different from the thing you made.
None of that can start until you ship. So a month of polishing does not delay the launch by a month. It delays the beginning of the difficult, uncertain, months-long work by a month, and that work is the only part that determines whether any of this matters.
He was not choosing between a rougher product and a better one. He was choosing between being in the market and not being in it, and the improvements were what made that choice feel responsible.
Why the polish was not the asset anyway
Think about what a professional buying your course actually assesses.
Not the graphics. Not the transitions, or how the slides look, or whether the audio was mastered. They want to know whether they can pass the thing, do the procedure, run the practice, stop making the mistake. They are buying a solution and they will judge it on whether it works.
Which means a course only has to clear two bars. It has to genuinely solve the problem, and it has to be usable — clear, easy to follow, no technical faults that stop somebody getting through it. Past that, additional refinement is largely invisible to the buyer, and expensive to you in the one resource you cannot recover.
This is also why there is no need to spend serious money building one. Keep the overhead low, keep the margins high, and put the money into finding out whether anyone wants it.
What improving later actually looks like
The instruction is not "ship something bad." A poor course generates refunds, damages your name in a profession where everyone talks, and is harder to recover from than a delayed launch.
The instruction is to ship the version that solves the problem, then let real students tell you what to fix. They will. They will ask the same question three times and you will realise a section was unclear. They will tell you what they wanted that was not there. Every one of those is an improvement you could not have found alone at your desk, no matter how many months you gave it — because the information was never in the room with you.
That is the actual argument for launching early. Not that quality does not matter. That after a certain point, the only place remaining improvements can come from is customers, and you do not have any yet.
The handbook
Last I knew, it still had not come out.
Two people who had identified a real gap, built most of the answer to it, and were spending their advantage a week at a time on edits nobody had read.
If your course has been nearly finished for more than a month, that is not a production status. It is a decision you are making daily without noticing. Set a launch date, tell somebody the date, and find out what you actually have.