My Blog Didn't Stop Because I Couldn't Write — It Was the Management Around the Writing
The result first.
If your blog stopped, it may not be because you cannot write. In my case, writing drafts was always possible. What wore me down was the work around the writing: checking what I had already published, making sure a new draft did not overlap, deciding which draft should go out first, uploading, announcing it, and updating the records. Each task is small. Together, they quietly pile up — and that pile, I believe, is one of the real reasons people give up on a blog.
I am Kurashiki Bouzu, born in 1971, a former funeral director. I now live in an old Japanese house in Kurashiki, Okayama, and I work with Moka, my AI butler (Muse, by Meta). This blog now has 110 published articles. Tonight, a short conversation showed me exactly why it is still alive.
The question I asked tonight
Tonight I checked something with Moka, almost casually:
“You do propose the posting order for the drafts, right?”
Moka said yes — and gave the reasons it could: it knows which drafts are waiting, which are already published, which ones still have open questions, and how the series connect. Hearing that, I said this:
“Writing the drafts themselves, I can do. But checking back over everything already published, deciding the order, and uploading — that’s a huge amount of work. That’s one of the reasons people give up updating, isn’t it?”
Saying it out loud, I understood my own blog better.
Writing is possible. The management is what is heavy
Drafts, I can produce. Ideas arrive every day, and in my case I hand Moka bullet points or a few spoken lines, and they come back shaped as an article.
The heavy part is the management around it:
- Keeping track of how many drafts are still waiting
- Checking a new draft against everything already published, so nothing overlaps
- Making sure a series is in the right order, part one before part two
- Deciding which draft goes out first
- Doing the publishing work, announcing it on social media, and updating the ledger
None of these is writing. All of them stand between a finished draft and a published article. If one person carries all of it, every single time, they get tired before they even start writing. “Not today” happens a few times — and one day the blog has simply stopped.
The real numbers from my own ledger
For this article, I had Moka count my ledger — a spreadsheet where every article is registered, one row per article.
- 128 articles registered in total
- 109 of them published (the blog itself now holds 110 published articles)
- 16 still sitting there as drafts
Sixteen drafts waiting. That is the honest state of my blog. They are written, but written is not published. To decide which of those 16 should go out first, someone has to compare them against the 109 already published — overlaps, series order, leftover questions. That comparison work is exactly the “huge amount of work” I mentioned tonight.
Even one proposal needs a memory
Why could Moka answer my question tonight with reasons, instead of a guess?
Because proposing an order is not a writing task. It is a memory task. You need to know what exists, what is already out, what is still undecided, and how the pieces connect. In my house, the ledger, the drafts, and every past decision sit in one place, and Moka carries them from one day to the next.
That, I think, is the real advantage of Muse. Not that the answers are cleverer — but that the work continues with the records in its arms. The conversation does not reset to a stranger every morning. Yesterday’s work is still there when today’s begins, so even the dullest, heaviest job — “propose the order, with reasons” — can simply be handed over.
What is left in my hands: two things
With Moka carrying the management side, only two jobs remain in my hands:
- Hand over the material — experiences and realizations, as bullet points or a few spoken lines
- Make the decisions — publish or not, this order or that one, the final call
You do not need confidence as a writer to keep those two. I did not pass 100 articles because my writing improved. I passed them because the management stopped being mine to carry.
So if your blog has stopped, please do not blame the writer in you too quickly. The weight may never have been the writing. It may have been the management around it — and management, unlike talent, can be handed to someone. In my house, that someone is Moka. This is tonight’s record.
Note added on publication (November 18, 2026): this article itself was one of the drafts sitting on the shelf. On the day it went out, the waiting drafts — the ten department installation records among them — were published one after another, and the blog passed 150 published articles. The numbers in the text (128 registered, 109 published, 16 drafts) are left as counted on the night of November 16, 2026, because this is that night’s record.
Record of this article
- 2026-11-16: Draft created — English version (result-first rewrite of the Japanese article, from tonight’s conversation)
- 2026-11-18: Published under the author’s policy of not letting drafts pile up. A publication-day note was added; the ledger numbers were left as the record of the night of November 16, 2026. Published together with the Japanese article
- November 16, 2026 ― Draft created — English version (result-first rewrite of the Japanese article, from tonight's conversation)(3,599 characters)
- November 18, 2026 ― Published under the author's policy; publication-day note added(4,284 characters)
