Foreshadowing Isn't Too Obvious. Your Setup Scene Is Doing Nothing Else.
A beta reader hands back your manuscript and says the foreshadowing is too obvious. They saw it coming from forty pages out.
So you go back to the hint and start sanding it down. Make it glancing. Bury it in a longer paragraph. Maybe cut it to half a sentence and trust the reader to catch it.
Try that and see if it works. Usually it doesn't, and the reason has nothing to do with the sentence you've been fiddling with.
Look at the scene before you look at the hint
The standard advice on this is a calibration problem. Too obvious and you've telegraphed the ending, too buried and nobody catches it, so find the zone in between. Patricia C. Wrede's blog has the most rigorous version of that framing I've read, and the craft writing around it is mostly a set of techniques for dialling a hint down: plant it in a character habit, slip it into casual dialogue, spread your hints out so they don't cluster.
None of that is wrong. It's just answering a different question than the one your reader asked.
Before you touch the wording, ask what the SCENE is for. Not the hint. The scene. And if the honest answer is that it exists so the clue can be placed somewhere, you've found the problem, and no amount of rewording will solve it.
What an empty scene does to a hint
Think about what a reader is actually doing in a scene. They're tracking several things at once. Who wants what, what's going wrong, what this means for the thing that happened two chapters ago, whether the person talking is lying. Attention is a budget and they're spending it in a lot of directions.
Now take all of that away. One character goes somewhere, notices a thing, and the scene ends. The reader's whole attention budget has exactly one place to go.
That's when a hint stops being a detail and becomes an ANNOUNCEMENT. Not because it was written loudly. Because it was the only thing in the room.
And this is where the subtlety advice runs out of road. A less prominent hint in an otherwise empty scene is still the most prominent thing in that scene. Take it down from a shout to a murmur. Still the only sound in the room.
The camouflage trap
There's a version of the standard advice that gets close to the real answer and then goes somewhere unhelpful. It says to bury the clue among other details, or to hide it in a scene that doesn't feel important.
I'd push back on that second one specifically, because it has the diagnosis exactly backwards. A scene that doesn't feel important is a scene with no job. That's not where a hint hides. That's the condition that exposes it.
The first half, burying it among other details, is closer but it depends entirely on what those details are doing. If you've added three paragraphs of weather and a description of the kitchen so the clue has company, you haven't given the reader anything to attend to. You've given them filler, and readers skim filler. The clue is still the only load-bearing object in the scene, and now the scene is longer.
Here's the test for whether a detail is doing work: would it still belong if you deleted the hint? If the answer is no, it's camouflage, and camouflage is the thing readers see through.
What counts as a second job
A genuine narrative job is something the scene accomplishes for the story that survives the hint's removal. A short list of the ones that qualify:
Plot advancement. Something changes in the situation. A decision gets made, a door closes, somebody commits.
Character revelation. The reader learns something about who a person is, demonstrated rather than stated.
Tension or conflict. Two people want incompatible things, or one person wants something the scene won't give them.
A relationship shift. The footing between two characters is different at the end than it was at the start.
Stakes. The reader understands more precisely what it costs to fail.
What doesn't qualify: description that connects to nothing, exposition the reader didn't need yet, atmosphere for its own sake. Those are the things writers reach for when a scene feels thin, and they make the scene longer without making it busier in any way a reader can feel.
The idea that scenes should carry several functions at once is not mine and it isn't new. It's common ground across a lot of working writers and teachers, and there's a decent aggregation of craft-master positions on scene purpose if you want to see how consistently it turns up. What I haven't found anybody saying is that this is the FIRST place to look when a reader calls your foreshadowing obvious. That connection is my own, and I can't give you a citation I don't have.
The two questions
Take any scene a reader has flagged, and ask:
- What is this scene doing besides planting the hint?
- Would a reader who completely missed the hint still have a reason to read this scene, and finish it satisfied?
Answer honestly. The first question has a nasty habit of producing answers that sound like jobs but aren't ("it establishes the setting", "it shows they're worried"). Push on those. Does the setting matter later? Is the worry demonstrated through anything happening?
If question one gives you nothing, or gives you only the hint itself, the scene is single-purpose. If question two is a no, your reader was right and they were being generous about where the problem was.
The sequence matters more than either question
This is the part I'd underline if I could only keep one thing from this post.
Add the second job before you touch a word of the hint.
Not the other way round, and not both at once. If you adjust the hint and the scene at the same time, you won't know which change did the work, and you'll carry the wrong lesson into the next book. If you adjust only the hint, you're treating the symptom while the condition sits there.
So: give the scene real work. Reread it. Then ask whether the hint still reads as a hint, or whether it now reads as one detail among several things happening. Quite often it reads fine and you never touch it at all.
Where the usual advice is right
Calibration is the correct tool in one specific situation, and it's worth naming so this doesn't come across as a blanket dismissal.
If a scene already has two or three genuine jobs, the reader has plenty to track, and the hint is STILL landing like a flare, then yes, the problem is the hint. Make it glancing. Give it a surface reading that serves the moment, so a reader has an innocent explanation available and doesn't need to reach for the real one. Spread your hints further apart. All of that technique is sound and it will work, because you've already removed the structural reason it wouldn't.
The disagreement here is about order, not about whether the technique is any good.
What this looks like in practice
The shape of the fix, rather than a worked example from a book I haven't read:
A character visits a relative and notices an old rifle above the fireplace. That's the scene. The rifle matters in chapter thirty. Right now the rifle is the scene's only event, and your reader clocked it instantly.
You don't move the rifle or soften the sentence. You give the visit a reason to exist. The relative asks for something the protagonist doesn't want to give, and watching the refusal tells you who they are. Or they came to ask for money and can't make themselves say it out loud. Or it's the argument they've had four times already, except this time somebody says the unsayable part. Any of those will do, provided it connects to something the book needs.
Now the reader is tracking a request, a refusal and whatever shifted between two people. The rifle is still above the fireplace, described exactly as before, and it has stopped being the point of the scene. It's furniture in a room where something happened.
That's the whole move. The hint didn't get quieter. The scene got louder.
Where FirstReader fits
The audit above wants nothing but your draft and an honest hour, and running it by hand is how the two questions become instinct.
Where it gets tedious is finding the scenes to audit. Setup scenes are the ones most likely to be carrying this problem and they're also the easiest to forget you wrote.
FirstReader classifies every scene in a manuscript by function, and setup is one of those categories, so it can give you the list of candidates to start from. It also scores Scene Structure as one of its six craft dimensions, and narrative purpose is named inside that definition, so a scene doing very little registers in the report rather than slipping past.
What it will not do is tell you a scene is single-purpose, and it has no idea your beta reader flagged your foreshadowing. It reports what's structurally in the draft. Deciding that a given setup scene has one job and needs another is yours, and so is choosing what that job should be.
If it would help to have the candidate list rather than hunting for it, you can run a manuscript through it.
What to do next
Find the scene your reader called obvious. Don't open the paragraph with the hint in it. Answer the two questions about the scene that contains it, and write the answers down where you can see how thin they are.
If you enjoyed this, please leave a comment below to let me know. If you DIDN'T enjoy it, well, I'd like to hear from you too!
If you haven't already, please feel free to subscribe so you don't miss anything.