| As a solo/indie dev who's currently early in building a product, I've been keeping a journal of "ideas" for content in a txt file in the codebase as I hate context switching and want to build this up before I get to it. Here's what I've done: - At the top of the file I've listed my audience, 3 personas - My content has to be useful to one of those - If I see an interesting post/take on social media I hold the link and write an idea for my own spin/take (takes 30 seconds) - log it - If I have a problem/issue that I resolve that would be useful to my audience - log it - If I have a key product/design/UX choice that took some time to think through - log it - If something takes me much longer than I thought because there's more to it (iceberge effect) - log it I've been doing this for about 6 weeks now and I've got 100 ideas for pieces of content. One of the best pieces of advice I read is that when you're solo, many times people/community rally around you. You are the product too so you have to share what you're doing, it's interesting to many, not just your customers. They care about the advice you give, the input you have, the way you build things. You are a subject matter expert in this domain, so you should structure your content with this in mind. "You escape competition through authenticity." - @naval |
Often when I return to what I write, about 60% I look back at with the novelty gone, and reassess from a more suitable eye and cross them off the list.