Launching my first published product at 60 was exciting, but it was also a much bigger learning experience than I expected.
The project was Watchmen on the Wall: 30-Day Guided Prayer & Intercession Journal. The journal grew out of something deeply personal to me—prayer, intercession, Scripture, and learning to spend time in the presence of God—but publishing it required me to learn an entirely different set of skills.
I had to take something that existed as teaching, notes, prayers, Scriptures, and ideas and turn it into an actual book that another person could order and hold in their hands.
That meant learning formatting, page sizing, cover requirements, Amazon KDP, proofing, corrections, and the sometimes frustrating process of discovering that what looks right on my computer doesn't necessarily meet a publishing platform's technical requirements.
This was my first real lesson in what I now call digital carpentry: you build, inspect, correct, and keep building until the thing is finished.
From Blank Screen to Published Work
Creating a 30-day guided prayer journal involved much more than putting words on pages.
Each day needed Scripture, teaching, reflection questions, prayer, a declaration, and writing space. I also wanted dedicated “My Parchments” pages where readers could record Scripture, prayer, what they heard, and what they were learning.
Then came the physical layout.
Margins mattered. Font sizes mattered. Page count mattered. The dimensions of the interior affected the cover. Even something as simple as adding or removing pages could affect what was required for the finished book.
My final journal became an 86-page, 7 × 10-inch paperback with a standard-color interior on white paper and a matte cover.
That experience taught me something I think new self-publishers need to hear: writing the book and producing the book are two different jobs.
Finishing your manuscript is a major accomplishment, but there is still a production process between that manuscript and the book someone receives from Amazon.
Lessons Learned During Self-Publishing
Amazon KDP was where some of my biggest lessons happened.
One issue involved the cover and spine. The lettering on the spine was too close to KDP's allowable boundaries, so the cover had to be corrected and uploaded again.
I also encountered a brand-associated-content warning during the publishing process. When you're new to KDP, messages like that can make you wonder whether you've done something terribly wrong. I had to work through the issue instead of assuming the entire project had failed.
Eventually, the corrected files were accepted and the paperback was published.
That changed the way I look at publishing problems.
A rejection or warning does not necessarily mean your book is a failure. Sometimes it simply means there is a technical problem that has to be identified and corrected.
I also learned not to make random changes just because I'm nervous about an automated message. I want to understand what the actual problem is, correct that problem, and preserve the parts that are already working.
That's a lesson I'm carrying into every digital product I build.
The Part Nobody Sees in the Finished Product
When someone sees a finished journal on Amazon, they see the cover, description, price, and preview.
They don't see all the little decisions behind it.
They don't see the formatting changes, rejected versions, corrected uploads, rereading pages, checking margins, worrying about whether something is positioned correctly, or wondering whether the platform is going to approve the latest version.
And they definitely don't see the learning curve of doing all of this when technology isn't your professional background.
That's one reason I'm documenting this journey.
I don't want The Digital Carpenter to show only polished finished products. I want to preserve the process—the mistakes as well as the wins—because that's the information I would have wanted when I started.
Serving Others Through Something I Actually Finished
Watchmen on the Wall means more to me than simply proving I could publish a book.
I created it to help believers develop a more intentional life of prayer and intercession. Seeing it become a real paperback meant that something that had lived in my heart, my notes, and my computer could now become something another person could actually use.
But it also gave me something important for this new business journey:
A receipt.
Not just a financial receipt—a result.
I can say that I wanted to learn self-publishing, and now I have actually taken a book through the process. I encountered problems. I corrected them. I learned from them. And I finished.
That experience is now something I can build on rather than something I'm merely planning to do someday.
What I Would Tell Someone Publishing Their First Book
Don't wait until you understand every part of KDP before you begin.
Learn enough to take the next step, but expect to make corrections.
Read the messages Amazon sends you carefully. Order a proof or author copy when appropriate. Look at the physical product rather than relying entirely on what you see on a computer screen. And keep your final files organized so you know which version is actually the approved version.
Most importantly, don't confuse a technical correction with failure.
My first publishing experience wasn't perfectly smooth. It was real.
And that's exactly what I'm documenting as I build an online business at 60—not a story where everything works the first time, but what actually happens when I try it.
One board. One nail. One mistake. One lesson at a time.