logo.png

Publishing the Adventure Series VII - Why Your First Book Doesn't Need to Be Perfect, It Needs to Be Finished

Wednesday, November 18, 2026

Primary Blog/Blogpost/Publishing the Adventure Series VII - Why Your First Book Doesn't Need to Be Perfect, It Needs to Be Finished

Author:

Mike Taylor

Publishing the Adventure Series
ARTICLE 7

Why Your First Book Doesn't Need to Be Perfect, It Needs to Be Finished

By: Mike "TaylorLyfe" Taylor

There is a draft of your first book that will never exist. It's the perfect version, every encounter balanced exactly right, every piece of prose polished to its absolute best, every illustration exactly matching the vision in your head, released on a timeline that gave everyone involved all the time they could have wanted.

That book doesn't exist because perfect doesn't ship. At some point, every creative project has to cross the line from "being worked on" to "done," and that line is drawn by a decision, not by reaching some objective state of completion. Nothing is ever objectively complete. It's complete when you decide it's complete.

The fear of shipping something imperfect is one of the most common reasons promising projects never become real things. Here's why finished beats perfect, every time.​

Perfect Is a Moving Target

The longer you work on something, the more you see in it. Early drafts have obvious problems that are easy to fix. Later drafts have subtler problems, problems you can only see because you've gotten better at seeing problems, which happened because you kept working on this project.

This creates a trap: the more time you spend trying to perfect something, the more imperfections become visible to you, which creates the feeling that more time is needed, which in turn reveals more imperfections. The goalpost moves with your skill level. You can chase it forever.

Finished work breaks this cycle. A finished book has flaws. Every book ever published has flaws, typos that slipped through, an encounter that doesn't quite land, a piece of art that's good but not the artist's best work. The flaws don't disqualify the book from existing. They're just part of what it is.​

Real Feedback Only Happens After Release

Here's something that doesn't become obvious until you've shipped something: the feedback you get from actual readers and players, after release, is qualitatively different from anything you can get before release.

Beta readers, playtesters, your own assessment, all of this is useful, but it's feedback from people who know it's not finished, who are evaluating it as a work in progress. The feedback that comes after something is real, when people are actually playing your adventure at their tables, when they're posting about it, when they're telling you what worked and what they changed, that feedback is the most valuable information you'll ever get about your own work. You can only get it by releasing.

Your second book will be better than your first, not primarily because you got better at writing in the abstract, but because your first book taught you things about your own work that no amount of pre-release polish could have taught you.

"Finished" Includes a Plan for What's Next

Part of what makes "finished" feel achievable rather than terrifying is understanding that finishing this thing doesn't mean you're done with the ideas in it. If there's a creature you didn't get to develop fully, it can be in the next thing. If there's a piece of lore you wish had more room, there's more room in future books. If the map for this dungeon isn't quite what you envisioned, the next map can be better because you'll have learned things from this one.

Finished doesn't mean "this is the only chance these ideas get." It means "this version of these ideas, at this point in their development, is going out into the world now, and other versions can exist later."

This reframing takes enormous pressure off. You're not trying to capture everything perfectly in this one document forever. You're putting a snapshot of where things are right now into the world, and the world, and your own continued work, will carry things forward from there.​

The Team Around You Is Waiting for "Finished," Not "Perfect"

If you're working with a team, editors, artists, playtesters, other writers, every one of them is, at some point, waiting for your decision that something is done so they can do their part. The editor can't finalize edits on a manuscript that keeps changing. The layout person can't build pages around text that's still being revised. The artist working on a cover needs a final title and tone, not a moving target.

Holding onto "not quite perfect yet" doesn't just affect your own timeline; it affects others' timelines, too. It holds up everyone whose work depends on yours being settled. Sometimes the most generous thing you can do for your team is decide something is done, even if you'd still change things given infinite time.

Scum Among Us is not a perfect book. No book is. It's a finished one, written, edited, illustrated, played, and out in the world, where it's doing the thing books do: being read, played, and enjoyed by people who weren't part of making it. That's what finished gets you that perfect never will.

Explore it at chaoticchronicles.com.

Don't Forget to Check out our stuff!

customer1 png

Mike "TaylorLyfe" Taylor

CEO Of Chaotic Chronicles

Mike "TaylorLyfe" Taylor

Greetings, I'm Mike "TaylorLyfe" Taylor, the friendly face behind the scenes. It brings me immense joy to welcome you to our world of endless possibilities and captivating stories. Engage with our diverse range of content and look forward to regular visits filled with inspiration and excitement!