- Joined
- Jul 11, 2012
- Messages
- 16,171
- Reaction score
- 3,734
Lots of unhelpful comments here. This is how it is:
1. Beta readers loved it, plus its sequels. Agents and publishers never read past chapter 1.
2. I wondered why, so I got tons of feedback on the first chapter, and rewrote it.
3. Repeat #1 about 100x. Not an exaggeration.
4. Repeat #2 about 150x. Not an exaggeration.
5. Everyone who read the novel expressed disbelief that I couldn't get an agent or editor to read it.
6. In recent months, I've gotten in-depth feedback on the latest version of chapter 1 from Big Five published author friends and Big Five former editors (aka industry professionals).
7. The lightbulb went on. I finally understand why 100% of industry professionals were commenting on the character's trope characteristics as a problem: It's because they expect the tropes to get played straight. They see a child genius, and expect this to be just another child-genius-saves-everyone story. It's not at all what they're expecting, but they write it off before the story takes its turn.
I'm sure some of you are thinking, "Agents are perfect gatekeepers; she's probably just an amateur writer." I've been doing this for twelve years, I have pro sales, and I don't know how you can be 100% certain that my fiction is amateur without actually having read it.
If you're making that assumption about me, it's understandable. But it's not helpful to my situation.
My beta readers include Big Five authors and slush readers for pro SFF magazines. I started out as an amateur, like anyone else, but I'm happy with my current beta reader group. They're sharp. And critical. And extremely helpful.
The comments about the trope problem in the first chapters were there all along; I just wasn't getting it as a major reason for rejection, until now. And since my beta readers offer feedback on the whole manuscript, plus sequels, I don't think they saw a solid reason for auto-rejection. They were as mystified as I was. They just kept saying, "That's weird. You still haven't gotten an agent to read it yet?"
********** If anyone else has this problem ************
It's *great* to be aware of the problem. That's step one. Now I need to try and signal the trope subversion in chapter 1, and/or in the query letter. I've gotten some excellent advice about how to go about this from other writers. Suggestions include:
- A first scene that subverts another trope, showing that this is not a typical trope story. George R.R. Martin did this in the prologue scene of "A Game of Thrones." [Spoilers] Readers expect the hapless guy to get killed by white walkers (zombies), but he makes it out alive ... only to get beheaded by the guy he reported it to. That sets up the tone of a trope-subverting story. Then readers are more willing to buy the child protagonist in chapter 1, expecting it to not turn into the typical boy-in-a-fantasy-novel-grows-into-The-Chosen-One.
- Have a character literally comment on the trope, to show that the author is aware of it. "Good thing you're not a space cadet, or people might mistake you for Ender Wiggin!"
- Embed the trope subversion in the query pitch.
I'm having trouble with these, due to reasons specific to my particular novel. But I think they're all great suggestions, and will probably work well for other writers with this problem.
I bolded that and replied, to point out that I think you're doing the same thing as with the agents. You're assuming people are thinking something, then working off and arguing with the assumption.
You're having an entire conversation/argument with people without their participation.
The assumption, however, is your own invention - not necessarily true.
You're also free to do whatever you like, but you asked for advice and got lots of it - at least some from some high-level industry professionals. If your response to all of it is just that nothing can work because it just can't because you can't do anything, well... what is it you want, exactly?
You decided on your own what the problem is, with no evidence, then decided there's no solution, despite many suggestions. Ok?