I definitely lean toward sharing finished stories. For me, the act of putting a piece out into the world feels like presenting a complete gift, not just the raw ingredients. When a story is truly finished meaning it’s been through multiple drafts, self-edited, and ideally, had a final polish it represents the absolute best version of my vision for that work.
Sharing a completed manuscript allows me to receive feedback on the overall impact and effectiveness of the storytelling, rather than just nit-picky details. I want to know if the ending landed, if the themes resonated, and if the character arc felt earned. Feedback on a work-in-progress often feels like "development notes," which can be helpful, but also overwhelming. By contrast, feedback on a finished story is about connection and interpretation, which is what I crave as a writer. It’s about celebrating the journey's end, not detailing the map.
Talha Bin Tayyab
Personally, I find sharing works in progress (WIPs) much more valuable, especially in a supportive forum setting. Writing can be such a solitary activity, and WIP critiques are like having a co-pilot during the most challenging part of the flight. When I’m stuck on a tricky plot point, or I realize my character's motivation is fuzzy, getting early, targeted feedback can save me weeks or even months of wasted effort going down the wrong path.
The key benefit here is efficiency and course correction. If I spend six months writing a whole novel and then find out my protagonist is unlikeable or the world-building is confusing, I face a massive, demoralizing overhaul. If I share the first three chapters, I get that crucial information immediately and can adjust my trajectory while the story is still flexible. It’s a vulnerable approach, but the potential for growth and a stronger final product makes it worthwhile.
I think the best answer lies in a strategic mix of both, depending on the stage of the project and the type of feedback I need. For example, I will always share Works in Progress when I am trying to solve a specific, high-stakes problem like troubleshooting a scene that feels flat, or testing the voice of a new character. I’ll share a very small, targeted excerpt just for that purpose, treating it like a diagnostic test.
However, I will only share finished stories with a wider audience or for publication consideration. I want the general reader's first experience with my world to be the cleanest, most polished one. It boils down to respecting the reader's time and my own process. WIP feedback is for the workshop and the editor; finished work sharing is for the reader and the market. Both are necessary steps, but they require different audiences and environments.
Honestly, I strongly prefer only sharing finished stories. My main reason is one of personal psychology: I need the space and clarity to complete my own vision without external noise clouding my judgment. When I’m drafting, the story is incredibly fragile. If I share a WIP and someone immediately points out a flaw or suggests a major change, it can derail my confidence and confuse my internal compass for the rest of the draft.
I need the work to be whole and sound before I open it up to critique. Once the story is fully formed the beginning, middle, and end are fixed I can receive feedback much more objectively. At that point, the notes are about refinement, not fundamental change. Sharing a WIP feels like asking people to paint on my canvas before I've even sketched the outlines, and for me, protecting that initial, private creative spark is essential to actually finishing the work.
