Showing Someone Your Story

Hand someone a piece you've written and ask "what did you think?" and you'll usually get one of two answers: polite vagueness ("I liked it!") or a list of typos, because that's the easiest, safest thing for another person to point out. Neither one actually tells you what you need to know, and that's not because your reader wasn't paying attention — it's because the question you asked was too broad to answer well.

Asking a question that can actually be answered

A more useful question points at something specific: "Where did you start skimming?" "Did you see the ending coming, and if so, how early?" "Which character felt most real to you, and which one felt flattest?" These questions work because they don't ask a reader to evaluate your writing in general — they ask for a report on their own experience reading it, which is something anyone can actually give you, whether or not they think of themselves as a good critic.

It also helps to tell a reader what you were trying to do before they read it, not so they'll be kind about it, but so they know what to actually watch for. "I was trying to make you unsure whether to trust this character" turns a vague reading experience into a specific thing they can report back on: did it work, and at what point, if any, did they stop being unsure?

Sharing work well isn't about building up the courage to hand it over. It's about deciding, ahead of time, exactly what you want to learn from the person reading it.