All of the above!
I literally have a post that is sitting unpublished for every one of those reasons. I think most of my posts though, sit because I write them in chunks over time. I throw content on the page, then a day or two later come back and refine it and repeat that cycle a few times until the post is ready. I only have 30 min to an hour to write most of the time so that process works for me.
I work on posts in a similar way and I found this way to be even better than writing all at once because I get a fresh view each time.
My problem is my chunks of time are often too far away from each other :D
I only start a draft the week I plan to release it, after I chose that week's topic, so I don't have any unpublished posts. But I do have a list of maybe 10 post ideas/skeletons that I will eventually work my way through - maybe in the next 10 weeks ;)
Many of the points fit. Sometimes I create a draft with just the topic, add content over time and then see someone posted a similar topic and (in my opinion) much better explained.
So I throw the draft away or let it sit there.
I have a lot of drafts and notes for possible posts. Most of them are far from being complete. Maybe I'll return to them, maybe not.
The reasons are typically both lack of enthusiasm and being busy. If I finish a post, no matter if I'm afraid or not, I'll publish it. The hard part is working on the post and editing it.
I have at the moment 12 drafts in my wordpress post archive, some with rough ideas, some with parts I removed from other posts, one or two are maybe 20% done.
For I'm a bit perfectionist when it comes to storytelling, publishing a half done post is not an option, though I learned to get shorter with my #100CodeExamples challenge.
I guess I will revisit most drafts someday...
Nope. Maybe... No. Yes... Mmm..noyes.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.