Creative-writing feedback is most useful when it tells you what a reader experienced, where that experience occurred, and what evidence in the draft produced it. To get useful feedback, ask targeted questions instead of only “Did you like it?” To use feedback well, separate the reader’s observation from the reader’s proposed solution, compare repeated signals, return to your story’s purpose, and make the revision yourself.
This beginner guide explains how to get feedback on creative writing, how to use critique, how to work with beta readers and peer readers, how to respond to conflicting feedback, how to give useful writing feedback, and how to revise a story without flattening your own voice. The eduKateSG fictional workshop residents Adrian, Jo, Ben, Aisha, Ryan, Mira, Clara and Ethan let us test feedback on concrete scenes rather than reduce critique to praise, correction or taste.
The core method is define the stage → choose the right reader → ask for reader experience → locate the evidence → separate observation from prescription → look for convergence and contradiction → decide against the work’s purpose → revise → reread → verify what changed. Feedback is information about how a draft reached another mind. It is not a vote that transfers authorship.
Quick Read: ask what happened to the reader
Ask: Where were you confused? What did you think Mira wanted? When did you realise the box belonged to Ben? Which line made Clara’s reply sound defensive? Did the ending feel caused by earlier choices? These questions produce usable evidence. “Was it good?” often produces politeness or broad preference.
This article owns beginner feedback and critique workflow. For self-revision, use How to Revise and Edit a First Draft. For voice preservation, use How to Develop Your Writing Voice. For craft analysis, use How to Read Like a Writer.
1. Feedback is data about reading, not a command
A reader says, “I did not realise Clara had returned the key.” That is an observation about their reading experience.
The same reader says, “Move Clara’s explanation to the first paragraph.” That is one proposed solution.
You can accept the observation and choose a different repair.
2. Feedback depends on draft stage
An early structural draft needs questions about goal, causality, character and ending. A nearly final draft can benefit from continuity, wording and proofreading notes.
Do not ask a reader to polish sentences in a scene you may delete tomorrow.
Match feedback resolution to manuscript stability.
3. Choose readers for the question
A general reader can report confusion and engagement. A genre reader may recognise conventions. A subject expert can check specialised factual material. An editor may diagnose craft at another level.
No single reader represents everyone.
Choose the source according to the uncertainty you need to reduce.
4. Ask before explaining your intention
If you tell the reader, “This is a story about responsibility and the blue box symbolises privacy,” you may contaminate the test.
First ask what they thought the story was doing.
Explain intention afterward when comparison becomes useful.
5. Protect the reader from impossible jobs
“Tell me everything wrong with this 80,000-word novel tomorrow” is not a useful request.
Define scope, deadline and the kind of response you need.
Respectful feedback begins with a workable ask.
6. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
7. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
8. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
9. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
10. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
11. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
12. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
13. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
14. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
15. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
16. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
17. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
18. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
19. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
20. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
21. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
22. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
23. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
24. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
25. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
26. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
27. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
28. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
29. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
30. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
31. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
32. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
33. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
34. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
35. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
36. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
37. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
38. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
39. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
40. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
41. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
42. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
43. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
44. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
45. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
46. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
47. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
48. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
49. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
50. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
51. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
52. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
53. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
54. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
55. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
56. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
57. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
58. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
59. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
60. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
61. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
62. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
63. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
64. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
65. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
66. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
67. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
68. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
69. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
70. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
71. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
72. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
73. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
74. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
75. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
76. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
77. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
78. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
79. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
80. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
81. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
82. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
83. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
84. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
85. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
86. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
87. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
88. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
89. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
90. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
91. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
92. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
93. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
94. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
95. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
96. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
97. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
98. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
99. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
100. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
101. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
102. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
103. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
104. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
105. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
6. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
7. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
8. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
9. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
10. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
11. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
12. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
13. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
14. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
15. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
16. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
17. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
18. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
19. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
20. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
21. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
22. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
23. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
24. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
25. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
26. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
27. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
28. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
29. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
30. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
31. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
32. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
33. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
34. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
35. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
36. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
37. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
38. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
39. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
40. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
41. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
42. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
43. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
44. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
45. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
46. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
47. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
48. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
49. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
50. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
51. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
52. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
53. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
54. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
55. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
56. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
57. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
58. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
59. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
60. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
61. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
62. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
63. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
64. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
65. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
66. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
67. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
68. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
69. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
70. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
71. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
72. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
73. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
74. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
75. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
76. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
77. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
78. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
79. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
80. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
81. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
82. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
83. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
84. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
85. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
86. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
87. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
88. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
89. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
90. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
91. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
92. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
93. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
94. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
95. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
96. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
97. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
98. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
99. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
100. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
101. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
102. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
103. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
104. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
105. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
106. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
107. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
108. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
109. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
110. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
111. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
112. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
113. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
114. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
115. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
116. Ask about confusion
Where did you stop understanding who knew what, where people were or why a choice followed?
Ask for the exact location rather than a general “confusing” label.
Then inspect viewpoint, chronology, pronouns, missing setup and information order.
Repair the cause, not merely the symptom.
117. Ask about expectation
What did you expect would happen next, and when did that expectation change?
Expectation data reveals setup, genre promise and foreshadowing.
Unexpected is not automatically bad; compare with intended effect.
Use reader prediction as evidence, not a demand for predictability.
118. Ask about character goal
What did you think the protagonist wanted in this scene?
If readers name different goals, check whether ambiguity is intentional.
A hidden goal can work; an invisible goal can make action feel random.
Return to choices and evidence.
119. Ask about stakes
What did you think could be lost, delayed, damaged or changed?
Readers need not share the character’s values, but they should understand them enough to follow decisions.
Avoid inflating stakes after feedback if specificity would solve the problem.
Small consequences can matter.
120. Ask about causality
Did the ending feel caused by earlier choices or delivered from outside?
Ask which event felt unprepared.
Then trace setup and consequence.
Do not add foreshadowing everywhere; add the missing dependency.
121. Ask about viewpoint
Whose experience did you feel closest to? Did any information seem unavailable to that viewpoint?
Readers can detect accidental mind-reading or unexplained knowledge.
A broader narrator changes the answer, so define the intended mode.
Feedback should evaluate the chosen design.
122. Ask about dialogue
Which line changed the conversation? Which line sounded unlike the speaker?
Do not ask only whether dialogue felt realistic.
Social purpose, information and voice are more diagnostic.
Read questionable exchanges aloud after receiving notes.
123. Ask about setting
Could you picture the relevant route, object and spatial relationship?
Readers do not need a complete floor plan.
Ask where orientation failed specifically.
Add the smallest anchor that repairs action.
124. Ask about pacing
Where did you want the text to move faster or stay longer?
Then ask what was happening there.
Pacing complaints can signal repetition, missing consequence or underdeveloped choice.
Do not equate fast with good.
125. Ask about ending
What changed by the end? What remained unresolved?
Compare the reader’s answer with your intended central change.
If they describe a different story, inspect setup and emphasis.
Do not explain the ending to compensate for missing textual evidence.
126. Observation versus prescription
Observation: “I expected Ben’s search to cause the ending.” Prescription: “Make Ben find the owner through a receipt.”
Keep these separate in your notes.
The observation may identify a real causal weakness while the proposed receipt is only one repair.
Authors own solutions.
127. Preference versus defect
“I prefer first person” is preference. “I could not tell whose thoughts I was reading” identifies a clarity issue.
Both are legitimate reader responses, but they carry different editorial weight.
Do not turn taste into universal law.
Define intended form before revising.
128. Single-reader signal
One reader can catch a real problem nobody else notices.
One reader can also bring an idiosyncratic preference.
Inspect textual evidence before accepting or rejecting.
Never dismiss a note solely because it is singular.
129. Repeated signal
When several independent readers stumble at the same point, investigate carefully.
Their proposed fixes may differ.
Look for the shared underlying experience.
Convergence raises diagnostic priority without dictating solution.
130. Conflicting signal
One reader wants more explanation; another wants less.
Inspect audience, passage and placement.
The problem may be timing rather than amount.
Do not average contradictory advice mechanically.
131. Expert signal
A subject expert can identify factual or procedural errors general readers miss.
Expertise in one domain does not automatically determine artistic choices in another.
Use the right authority for the right claim.
Separate factual correction from stylistic preference.
132. Genre-reader signal
Experienced genre readers may recognise conventions and promises.
They can tell you when a twist feels familiar or a setup signals another genre.
Do not assume convention must always be obeyed.
Know what expectation you are keeping or breaking.
133. Non-genre-reader signal
A fresh reader may reveal where specialist assumptions block access.
Their unfamiliarity can be useful evidence.
Do not simplify everything merely because one reader lacks genre context.
Define intended audience.
134. Emotional signal
A reader’s boredom, irritation, delight or sadness is real as experience but needs location and cause before revision.
Ask what happened immediately before the reaction.
Do not argue the feeling away.
Translate emotion into a craft question.
135. Silence as signal
If a reader comments on everything except the scene you considered central, ask what they remember from it.
Absence of comment is ambiguous.
Do not assume silence means success or failure.
Follow up with a targeted question.
136. Observation versus prescription
Observation: “I expected Ben’s search to cause the ending.” Prescription: “Make Ben find the owner through a receipt.”
Keep these separate in your notes.
The observation may identify a real causal weakness while the proposed receipt is only one repair.
Authors own solutions.
137. Preference versus defect
“I prefer first person” is preference. “I could not tell whose thoughts I was reading” identifies a clarity issue.
Both are legitimate reader responses, but they carry different editorial weight.
Do not turn taste into universal law.
Define intended form before revising.
138. Single-reader signal
One reader can catch a real problem nobody else notices.
One reader can also bring an idiosyncratic preference.
Inspect textual evidence before accepting or rejecting.
Never dismiss a note solely because it is singular.
139. Repeated signal
When several independent readers stumble at the same point, investigate carefully.
Their proposed fixes may differ.
Look for the shared underlying experience.
Convergence raises diagnostic priority without dictating solution.
140. Conflicting signal
One reader wants more explanation; another wants less.
Inspect audience, passage and placement.
The problem may be timing rather than amount.
Do not average contradictory advice mechanically.
141. Expert signal
A subject expert can identify factual or procedural errors general readers miss.
Expertise in one domain does not automatically determine artistic choices in another.
Use the right authority for the right claim.
Separate factual correction from stylistic preference.
142. Genre-reader signal
Experienced genre readers may recognise conventions and promises.
They can tell you when a twist feels familiar or a setup signals another genre.
Do not assume convention must always be obeyed.
Know what expectation you are keeping or breaking.
143. Non-genre-reader signal
A fresh reader may reveal where specialist assumptions block access.
Their unfamiliarity can be useful evidence.
Do not simplify everything merely because one reader lacks genre context.
Define intended audience.
144. Emotional signal
A reader’s boredom, irritation, delight or sadness is real as experience but needs location and cause before revision.
Ask what happened immediately before the reaction.
Do not argue the feeling away.
Translate emotion into a craft question.
145. Silence as signal
If a reader comments on everything except the scene you considered central, ask what they remember from it.
Absence of comment is ambiguous.
Do not assume silence means success or failure.
Follow up with a targeted question.
146. Observation versus prescription
Observation: “I expected Ben’s search to cause the ending.” Prescription: “Make Ben find the owner through a receipt.”
Keep these separate in your notes.
The observation may identify a real causal weakness while the proposed receipt is only one repair.
Authors own solutions.
147. Preference versus defect
“I prefer first person” is preference. “I could not tell whose thoughts I was reading” identifies a clarity issue.
Both are legitimate reader responses, but they carry different editorial weight.
Do not turn taste into universal law.
Define intended form before revising.
148. Single-reader signal
One reader can catch a real problem nobody else notices.
One reader can also bring an idiosyncratic preference.
Inspect textual evidence before accepting or rejecting.
Never dismiss a note solely because it is singular.
149. Repeated signal
When several independent readers stumble at the same point, investigate carefully.
Their proposed fixes may differ.
Look for the shared underlying experience.
Convergence raises diagnostic priority without dictating solution.
150. Conflicting signal
One reader wants more explanation; another wants less.
Inspect audience, passage and placement.
The problem may be timing rather than amount.
Do not average contradictory advice mechanically.
151. Expert signal
A subject expert can identify factual or procedural errors general readers miss.
Expertise in one domain does not automatically determine artistic choices in another.
Use the right authority for the right claim.
Separate factual correction from stylistic preference.
152. Genre-reader signal
Experienced genre readers may recognise conventions and promises.
They can tell you when a twist feels familiar or a setup signals another genre.
Do not assume convention must always be obeyed.
Know what expectation you are keeping or breaking.
153. Non-genre-reader signal
A fresh reader may reveal where specialist assumptions block access.
Their unfamiliarity can be useful evidence.
Do not simplify everything merely because one reader lacks genre context.
Define intended audience.
154. Emotional signal
A reader’s boredom, irritation, delight or sadness is real as experience but needs location and cause before revision.
Ask what happened immediately before the reaction.
Do not argue the feeling away.
Translate emotion into a craft question.
155. Silence as signal
If a reader comments on everything except the scene you considered central, ask what they remember from it.
Absence of comment is ambiguous.
Do not assume silence means success or failure.
Follow up with a targeted question.
156. Observation versus prescription
Observation: “I expected Ben’s search to cause the ending.” Prescription: “Make Ben find the owner through a receipt.”
Keep these separate in your notes.
The observation may identify a real causal weakness while the proposed receipt is only one repair.
Authors own solutions.
157. Preference versus defect
“I prefer first person” is preference. “I could not tell whose thoughts I was reading” identifies a clarity issue.
Both are legitimate reader responses, but they carry different editorial weight.
Do not turn taste into universal law.
Define intended form before revising.
158. Single-reader signal
One reader can catch a real problem nobody else notices.
One reader can also bring an idiosyncratic preference.
Inspect textual evidence before accepting or rejecting.
Never dismiss a note solely because it is singular.
159. Repeated signal
When several independent readers stumble at the same point, investigate carefully.
Their proposed fixes may differ.
Look for the shared underlying experience.
Convergence raises diagnostic priority without dictating solution.
160. Conflicting signal
One reader wants more explanation; another wants less.
Inspect audience, passage and placement.
The problem may be timing rather than amount.
Do not average contradictory advice mechanically.
161. Expert signal
A subject expert can identify factual or procedural errors general readers miss.
Expertise in one domain does not automatically determine artistic choices in another.
Use the right authority for the right claim.
Separate factual correction from stylistic preference.
162. Genre-reader signal
Experienced genre readers may recognise conventions and promises.
They can tell you when a twist feels familiar or a setup signals another genre.
Do not assume convention must always be obeyed.
Know what expectation you are keeping or breaking.
163. Non-genre-reader signal
A fresh reader may reveal where specialist assumptions block access.
Their unfamiliarity can be useful evidence.
Do not simplify everything merely because one reader lacks genre context.
Define intended audience.
164. Emotional signal
A reader’s boredom, irritation, delight or sadness is real as experience but needs location and cause before revision.
Ask what happened immediately before the reaction.
Do not argue the feeling away.
Translate emotion into a craft question.
165. Silence as signal
If a reader comments on everything except the scene you considered central, ask what they remember from it.
Absence of comment is ambiguous.
Do not assume silence means success or failure.
Follow up with a targeted question.
166. Observation versus prescription
Observation: “I expected Ben’s search to cause the ending.” Prescription: “Make Ben find the owner through a receipt.”
Keep these separate in your notes.
The observation may identify a real causal weakness while the proposed receipt is only one repair.
Authors own solutions.
167. Preference versus defect
“I prefer first person” is preference. “I could not tell whose thoughts I was reading” identifies a clarity issue.
Both are legitimate reader responses, but they carry different editorial weight.
Do not turn taste into universal law.
Define intended form before revising.
168. Single-reader signal
One reader can catch a real problem nobody else notices.
One reader can also bring an idiosyncratic preference.
Inspect textual evidence before accepting or rejecting.
Never dismiss a note solely because it is singular.
169. Repeated signal
When several independent readers stumble at the same point, investigate carefully.
Their proposed fixes may differ.
Look for the shared underlying experience.
Convergence raises diagnostic priority without dictating solution.
170. Conflicting signal
One reader wants more explanation; another wants less.
Inspect audience, passage and placement.
The problem may be timing rather than amount.
Do not average contradictory advice mechanically.
171. Expert signal
A subject expert can identify factual or procedural errors general readers miss.
Expertise in one domain does not automatically determine artistic choices in another.
Use the right authority for the right claim.
Separate factual correction from stylistic preference.
172. Genre-reader signal
Experienced genre readers may recognise conventions and promises.
They can tell you when a twist feels familiar or a setup signals another genre.
Do not assume convention must always be obeyed.
Know what expectation you are keeping or breaking.
173. Non-genre-reader signal
A fresh reader may reveal where specialist assumptions block access.
Their unfamiliarity can be useful evidence.
Do not simplify everything merely because one reader lacks genre context.
Define intended audience.
174. Emotional signal
A reader’s boredom, irritation, delight or sadness is real as experience but needs location and cause before revision.
Ask what happened immediately before the reaction.
Do not argue the feeling away.
Translate emotion into a craft question.
175. Silence as signal
If a reader comments on everything except the scene you considered central, ask what they remember from it.
Absence of comment is ambiguous.
Do not assume silence means success or failure.
Follow up with a targeted question.
176. Observation versus prescription
Observation: “I expected Ben’s search to cause the ending.” Prescription: “Make Ben find the owner through a receipt.”
Keep these separate in your notes.
The observation may identify a real causal weakness while the proposed receipt is only one repair.
Authors own solutions.
177. Preference versus defect
“I prefer first person” is preference. “I could not tell whose thoughts I was reading” identifies a clarity issue.
Both are legitimate reader responses, but they carry different editorial weight.
Do not turn taste into universal law.
Define intended form before revising.
178. Single-reader signal
One reader can catch a real problem nobody else notices.
One reader can also bring an idiosyncratic preference.
Inspect textual evidence before accepting or rejecting.
Never dismiss a note solely because it is singular.
179. Repeated signal
When several independent readers stumble at the same point, investigate carefully.
Their proposed fixes may differ.
Look for the shared underlying experience.
Convergence raises diagnostic priority without dictating solution.
180. Conflicting signal
One reader wants more explanation; another wants less.
Inspect audience, passage and placement.
The problem may be timing rather than amount.
Do not average contradictory advice mechanically.
181. Expert signal
A subject expert can identify factual or procedural errors general readers miss.
Expertise in one domain does not automatically determine artistic choices in another.
Use the right authority for the right claim.
Separate factual correction from stylistic preference.
182. Genre-reader signal
Experienced genre readers may recognise conventions and promises.
They can tell you when a twist feels familiar or a setup signals another genre.
Do not assume convention must always be obeyed.
Know what expectation you are keeping or breaking.
183. Non-genre-reader signal
A fresh reader may reveal where specialist assumptions block access.
Their unfamiliarity can be useful evidence.
Do not simplify everything merely because one reader lacks genre context.
Define intended audience.
184. Emotional signal
A reader’s boredom, irritation, delight or sadness is real as experience but needs location and cause before revision.
Ask what happened immediately before the reaction.
Do not argue the feeling away.
Translate emotion into a craft question.
185. Silence as signal
If a reader comments on everything except the scene you considered central, ask what they remember from it.
Absence of comment is ambiguous.
Do not assume silence means success or failure.
Follow up with a targeted question.
186. Observation versus prescription
Observation: “I expected Ben’s search to cause the ending.” Prescription: “Make Ben find the owner through a receipt.”
Keep these separate in your notes.
The observation may identify a real causal weakness while the proposed receipt is only one repair.
Authors own solutions.
187. Preference versus defect
“I prefer first person” is preference. “I could not tell whose thoughts I was reading” identifies a clarity issue.
Both are legitimate reader responses, but they carry different editorial weight.
Do not turn taste into universal law.
Define intended form before revising.
188. Single-reader signal
One reader can catch a real problem nobody else notices.
One reader can also bring an idiosyncratic preference.
Inspect textual evidence before accepting or rejecting.
Never dismiss a note solely because it is singular.
189. Repeated signal
When several independent readers stumble at the same point, investigate carefully.
Their proposed fixes may differ.
Look for the shared underlying experience.
Convergence raises diagnostic priority without dictating solution.
190. Conflicting signal
One reader wants more explanation; another wants less.
Inspect audience, passage and placement.
The problem may be timing rather than amount.
Do not average contradictory advice mechanically.
191. Expert signal
A subject expert can identify factual or procedural errors general readers miss.
Expertise in one domain does not automatically determine artistic choices in another.
Use the right authority for the right claim.
Separate factual correction from stylistic preference.
192. Genre-reader signal
Experienced genre readers may recognise conventions and promises.
They can tell you when a twist feels familiar or a setup signals another genre.
Do not assume convention must always be obeyed.
Know what expectation you are keeping or breaking.
193. Non-genre-reader signal
A fresh reader may reveal where specialist assumptions block access.
Their unfamiliarity can be useful evidence.
Do not simplify everything merely because one reader lacks genre context.
Define intended audience.
194. Emotional signal
A reader’s boredom, irritation, delight or sadness is real as experience but needs location and cause before revision.
Ask what happened immediately before the reaction.
Do not argue the feeling away.
Translate emotion into a craft question.
195. Silence as signal
If a reader comments on everything except the scene you considered central, ask what they remember from it.
Absence of comment is ambiguous.
Do not assume silence means success or failure.
Follow up with a targeted question.
196. Observation versus prescription
Observation: “I expected Ben’s search to cause the ending.” Prescription: “Make Ben find the owner through a receipt.”
Keep these separate in your notes.
The observation may identify a real causal weakness while the proposed receipt is only one repair.
Authors own solutions.
197. Preference versus defect
“I prefer first person” is preference. “I could not tell whose thoughts I was reading” identifies a clarity issue.
Both are legitimate reader responses, but they carry different editorial weight.
Do not turn taste into universal law.
Define intended form before revising.
198. Single-reader signal
One reader can catch a real problem nobody else notices.
One reader can also bring an idiosyncratic preference.
Inspect textual evidence before accepting or rejecting.
Never dismiss a note solely because it is singular.
199. Repeated signal
When several independent readers stumble at the same point, investigate carefully.
Their proposed fixes may differ.
Look for the shared underlying experience.
Convergence raises diagnostic priority without dictating solution.
200. Conflicting signal
One reader wants more explanation; another wants less.
Inspect audience, passage and placement.
The problem may be timing rather than amount.
Do not average contradictory advice mechanically.
201. Expert signal
A subject expert can identify factual or procedural errors general readers miss.
Expertise in one domain does not automatically determine artistic choices in another.
Use the right authority for the right claim.
Separate factual correction from stylistic preference.
202. Genre-reader signal
Experienced genre readers may recognise conventions and promises.
They can tell you when a twist feels familiar or a setup signals another genre.
Do not assume convention must always be obeyed.
Know what expectation you are keeping or breaking.
203. Non-genre-reader signal
A fresh reader may reveal where specialist assumptions block access.
Their unfamiliarity can be useful evidence.
Do not simplify everything merely because one reader lacks genre context.
Define intended audience.
204. Emotional signal
A reader’s boredom, irritation, delight or sadness is real as experience but needs location and cause before revision.
Ask what happened immediately before the reaction.
Do not argue the feeling away.
Translate emotion into a craft question.
205. Silence as signal
If a reader comments on everything except the scene you considered central, ask what they remember from it.
Absence of comment is ambiguous.
Do not assume silence means success or failure.
Follow up with a targeted question.
206. Observation versus prescription
Observation: “I expected Ben’s search to cause the ending.” Prescription: “Make Ben find the owner through a receipt.”
Keep these separate in your notes.
The observation may identify a real causal weakness while the proposed receipt is only one repair.
Authors own solutions.
207. Preference versus defect
“I prefer first person” is preference. “I could not tell whose thoughts I was reading” identifies a clarity issue.
Both are legitimate reader responses, but they carry different editorial weight.
Do not turn taste into universal law.
Define intended form before revising.
208. Single-reader signal
One reader can catch a real problem nobody else notices.
One reader can also bring an idiosyncratic preference.
Inspect textual evidence before accepting or rejecting.
Never dismiss a note solely because it is singular.
209. Repeated signal
When several independent readers stumble at the same point, investigate carefully.
Their proposed fixes may differ.
Look for the shared underlying experience.
Convergence raises diagnostic priority without dictating solution.
210. Conflicting signal
One reader wants more explanation; another wants less.
Inspect audience, passage and placement.
The problem may be timing rather than amount.
Do not average contradictory advice mechanically.
211. Expert signal
A subject expert can identify factual or procedural errors general readers miss.
Expertise in one domain does not automatically determine artistic choices in another.
Use the right authority for the right claim.
Separate factual correction from stylistic preference.
212. Genre-reader signal
Experienced genre readers may recognise conventions and promises.
They can tell you when a twist feels familiar or a setup signals another genre.
Do not assume convention must always be obeyed.
Know what expectation you are keeping or breaking.
213. Non-genre-reader signal
A fresh reader may reveal where specialist assumptions block access.
Their unfamiliarity can be useful evidence.
Do not simplify everything merely because one reader lacks genre context.
Define intended audience.
214. Emotional signal
A reader’s boredom, irritation, delight or sadness is real as experience but needs location and cause before revision.
Ask what happened immediately before the reaction.
Do not argue the feeling away.
Translate emotion into a craft question.
215. Silence as signal
If a reader comments on everything except the scene you considered central, ask what they remember from it.
Absence of comment is ambiguous.
Do not assume silence means success or failure.
Follow up with a targeted question.
216. Observation versus prescription
Observation: “I expected Ben’s search to cause the ending.” Prescription: “Make Ben find the owner through a receipt.”
Keep these separate in your notes.
The observation may identify a real causal weakness while the proposed receipt is only one repair.
Authors own solutions.
217. Preference versus defect
“I prefer first person” is preference. “I could not tell whose thoughts I was reading” identifies a clarity issue.
Both are legitimate reader responses, but they carry different editorial weight.
Do not turn taste into universal law.
Define intended form before revising.
218. Single-reader signal
One reader can catch a real problem nobody else notices.
One reader can also bring an idiosyncratic preference.
Inspect textual evidence before accepting or rejecting.
Never dismiss a note solely because it is singular.
219. Repeated signal
When several independent readers stumble at the same point, investigate carefully.
Their proposed fixes may differ.
Look for the shared underlying experience.
Convergence raises diagnostic priority without dictating solution.
220. Conflicting signal
One reader wants more explanation; another wants less.
Inspect audience, passage and placement.
The problem may be timing rather than amount.
Do not average contradictory advice mechanically.
221. Expert signal
A subject expert can identify factual or procedural errors general readers miss.
Expertise in one domain does not automatically determine artistic choices in another.
Use the right authority for the right claim.
Separate factual correction from stylistic preference.
222. Genre-reader signal
Experienced genre readers may recognise conventions and promises.
They can tell you when a twist feels familiar or a setup signals another genre.
Do not assume convention must always be obeyed.
Know what expectation you are keeping or breaking.
223. Non-genre-reader signal
A fresh reader may reveal where specialist assumptions block access.
Their unfamiliarity can be useful evidence.
Do not simplify everything merely because one reader lacks genre context.
Define intended audience.
224. Emotional signal
A reader’s boredom, irritation, delight or sadness is real as experience but needs location and cause before revision.
Ask what happened immediately before the reaction.
Do not argue the feeling away.
Translate emotion into a craft question.
225. Silence as signal
If a reader comments on everything except the scene you considered central, ask what they remember from it.
Absence of comment is ambiguous.
Do not assume silence means success or failure.
Follow up with a targeted question.
226. Observation versus prescription
Observation: “I expected Ben’s search to cause the ending.” Prescription: “Make Ben find the owner through a receipt.”
Keep these separate in your notes.
The observation may identify a real causal weakness while the proposed receipt is only one repair.
Authors own solutions.
227. Preference versus defect
“I prefer first person” is preference. “I could not tell whose thoughts I was reading” identifies a clarity issue.
Both are legitimate reader responses, but they carry different editorial weight.
Do not turn taste into universal law.
Define intended form before revising.
228. Single-reader signal
One reader can catch a real problem nobody else notices.
One reader can also bring an idiosyncratic preference.
Inspect textual evidence before accepting or rejecting.
Never dismiss a note solely because it is singular.
229. Repeated signal
When several independent readers stumble at the same point, investigate carefully.
Their proposed fixes may differ.
Look for the shared underlying experience.
Convergence raises diagnostic priority without dictating solution.
230. Conflicting signal
One reader wants more explanation; another wants less.
Inspect audience, passage and placement.
The problem may be timing rather than amount.
Do not average contradictory advice mechanically.
231. Expert signal
A subject expert can identify factual or procedural errors general readers miss.
Expertise in one domain does not automatically determine artistic choices in another.
Use the right authority for the right claim.
Separate factual correction from stylistic preference.
232. Genre-reader signal
Experienced genre readers may recognise conventions and promises.
They can tell you when a twist feels familiar or a setup signals another genre.
Do not assume convention must always be obeyed.
Know what expectation you are keeping or breaking.
233. Non-genre-reader signal
A fresh reader may reveal where specialist assumptions block access.
Their unfamiliarity can be useful evidence.
Do not simplify everything merely because one reader lacks genre context.
Define intended audience.
234. Emotional signal
A reader’s boredom, irritation, delight or sadness is real as experience but needs location and cause before revision.
Ask what happened immediately before the reaction.
Do not argue the feeling away.
Translate emotion into a craft question.
235. Silence as signal
If a reader comments on everything except the scene you considered central, ask what they remember from it.
Absence of comment is ambiguous.
Do not assume silence means success or failure.
Follow up with a targeted question.
236. Observation versus prescription
Observation: “I expected Ben’s search to cause the ending.” Prescription: “Make Ben find the owner through a receipt.”
Keep these separate in your notes.
The observation may identify a real causal weakness while the proposed receipt is only one repair.
Authors own solutions.
237. Preference versus defect
“I prefer first person” is preference. “I could not tell whose thoughts I was reading” identifies a clarity issue.
Both are legitimate reader responses, but they carry different editorial weight.
Do not turn taste into universal law.
Define intended form before revising.
238. Single-reader signal
One reader can catch a real problem nobody else notices.
One reader can also bring an idiosyncratic preference.
Inspect textual evidence before accepting or rejecting.
Never dismiss a note solely because it is singular.
239. Repeated signal
When several independent readers stumble at the same point, investigate carefully.
Their proposed fixes may differ.
Look for the shared underlying experience.
Convergence raises diagnostic priority without dictating solution.
240. Conflicting signal
One reader wants more explanation; another wants less.
Inspect audience, passage and placement.
The problem may be timing rather than amount.
Do not average contradictory advice mechanically.
241. Expert signal
A subject expert can identify factual or procedural errors general readers miss.
Expertise in one domain does not automatically determine artistic choices in another.
Use the right authority for the right claim.
Separate factual correction from stylistic preference.
242. Genre-reader signal
Experienced genre readers may recognise conventions and promises.
They can tell you when a twist feels familiar or a setup signals another genre.
Do not assume convention must always be obeyed.
Know what expectation you are keeping or breaking.
243. Non-genre-reader signal
A fresh reader may reveal where specialist assumptions block access.
Their unfamiliarity can be useful evidence.
Do not simplify everything merely because one reader lacks genre context.
Define intended audience.
244. Emotional signal
A reader’s boredom, irritation, delight or sadness is real as experience but needs location and cause before revision.
Ask what happened immediately before the reaction.
Do not argue the feeling away.
Translate emotion into a craft question.
245. Silence as signal
If a reader comments on everything except the scene you considered central, ask what they remember from it.
Absence of comment is ambiguous.
Do not assume silence means success or failure.
Follow up with a targeted question.
246. Giving feedback: begin with the reading experience
Say what you understood, expected or felt at a specific point.
“I thought the box belonged to Ryan until this line” is more useful than “confusing.”
Describe before prescribing.
The writer can then compare your model with intended effect.
247. Giving feedback: cite location
Point to scene, paragraph or moment.
Avoid dumping a global judgement without evidence.
Location makes revision efficient.
It also prevents one weak line from becoming a verdict on the whole manuscript.
248. Giving feedback: distinguish certainty
Say “I may have missed this” when appropriate.
Readers can be wrong about facts in the text.
Humility improves collaboration without weakening useful notes.
Evidence can settle the question.
249. Giving feedback: respect the chosen genre
Do not ask a quiet literary story to become a thriller simply because you prefer thrillers.
Evaluate whether the work fulfils its own promises.
Genre knowledge helps; genre policing does not.
Ask before assuming intention.
250. Giving feedback: protect authorship
Offer alternatives as options, not ownership claims.
Avoid rewriting whole passages into your voice unless the writer requested line-level examples.
A sample can illustrate a mechanism without becoming replacement text.
The author decides.
251. Giving feedback: identify strengths precisely
“Good dialogue” is pleasant but vague.
Say which exchange changed the relationship or sounded distinct.
Precise positive feedback helps writers preserve what works during revision.
Critique is not only defect detection.
252. Giving feedback: avoid personality judgement
Comment on the text, not the writer’s intelligence, maturity or worth.
“The causal link is missing” is actionable. “You are careless” is not.
Respect improves information quality.
Craft critique should remain about craft.
253. Giving feedback: separate factual correction
If a real-world claim is wrong, identify the source or basis for correction where possible.
Do not present uncertain memory as authority.
Factual accuracy and artistic preference are different note types.
Label them clearly.
254. Giving feedback: ask permission for sensitive depth
Some autobiographical or personal material may not invite speculative interpretation.
Stay with what the text presents unless the writer requests deeper discussion.
Do not diagnose authors from fiction.
Reader response can remain rigorous without invading the person.
255. Giving feedback: finish with priorities
If you have twenty notes, identify the two or three that most affect the whole work.
Structural priorities help the writer sequence revision.
Do not bury the causal break beneath comma comments.
Feedback should reduce uncertainty, not create a new pile of noise.
256. Giving feedback: begin with the reading experience
Say what you understood, expected or felt at a specific point.
“I thought the box belonged to Ryan until this line” is more useful than “confusing.”
Describe before prescribing.
The writer can then compare your model with intended effect.
257. Giving feedback: cite location
Point to scene, paragraph or moment.
Avoid dumping a global judgement without evidence.
Location makes revision efficient.
It also prevents one weak line from becoming a verdict on the whole manuscript.
258. Giving feedback: distinguish certainty
Say “I may have missed this” when appropriate.
Readers can be wrong about facts in the text.
Humility improves collaboration without weakening useful notes.
Evidence can settle the question.
259. Giving feedback: respect the chosen genre
Do not ask a quiet literary story to become a thriller simply because you prefer thrillers.
Evaluate whether the work fulfils its own promises.
Genre knowledge helps; genre policing does not.
Ask before assuming intention.
260. Giving feedback: protect authorship
Offer alternatives as options, not ownership claims.
Avoid rewriting whole passages into your voice unless the writer requested line-level examples.
A sample can illustrate a mechanism without becoming replacement text.
The author decides.
261. Giving feedback: identify strengths precisely
“Good dialogue” is pleasant but vague.
Say which exchange changed the relationship or sounded distinct.
Precise positive feedback helps writers preserve what works during revision.
Critique is not only defect detection.
262. Giving feedback: avoid personality judgement
Comment on the text, not the writer’s intelligence, maturity or worth.
“The causal link is missing” is actionable. “You are careless” is not.
Respect improves information quality.
Craft critique should remain about craft.
263. Giving feedback: separate factual correction
If a real-world claim is wrong, identify the source or basis for correction where possible.
Do not present uncertain memory as authority.
Factual accuracy and artistic preference are different note types.
Label them clearly.
264. Giving feedback: ask permission for sensitive depth
Some autobiographical or personal material may not invite speculative interpretation.
Stay with what the text presents unless the writer requests deeper discussion.
Do not diagnose authors from fiction.
Reader response can remain rigorous without invading the person.
265. Giving feedback: finish with priorities
If you have twenty notes, identify the two or three that most affect the whole work.
Structural priorities help the writer sequence revision.
Do not bury the causal break beneath comma comments.
Feedback should reduce uncertainty, not create a new pile of noise.
266. Giving feedback: begin with the reading experience
Say what you understood, expected or felt at a specific point.
“I thought the box belonged to Ryan until this line” is more useful than “confusing.”
Describe before prescribing.
The writer can then compare your model with intended effect.
267. Giving feedback: cite location
Point to scene, paragraph or moment.
Avoid dumping a global judgement without evidence.
Location makes revision efficient.
It also prevents one weak line from becoming a verdict on the whole manuscript.
268. Giving feedback: distinguish certainty
Say “I may have missed this” when appropriate.
Readers can be wrong about facts in the text.
Humility improves collaboration without weakening useful notes.
Evidence can settle the question.
269. Giving feedback: respect the chosen genre
Do not ask a quiet literary story to become a thriller simply because you prefer thrillers.
Evaluate whether the work fulfils its own promises.
Genre knowledge helps; genre policing does not.
Ask before assuming intention.
270. Giving feedback: protect authorship
Offer alternatives as options, not ownership claims.
Avoid rewriting whole passages into your voice unless the writer requested line-level examples.
A sample can illustrate a mechanism without becoming replacement text.
The author decides.
271. Giving feedback: identify strengths precisely
“Good dialogue” is pleasant but vague.
Say which exchange changed the relationship or sounded distinct.
Precise positive feedback helps writers preserve what works during revision.
Critique is not only defect detection.
272. Giving feedback: avoid personality judgement
Comment on the text, not the writer’s intelligence, maturity or worth.
“The causal link is missing” is actionable. “You are careless” is not.
Respect improves information quality.
Craft critique should remain about craft.
273. Giving feedback: separate factual correction
If a real-world claim is wrong, identify the source or basis for correction where possible.
Do not present uncertain memory as authority.
Factual accuracy and artistic preference are different note types.
Label them clearly.
274. Giving feedback: ask permission for sensitive depth
Some autobiographical or personal material may not invite speculative interpretation.
Stay with what the text presents unless the writer requests deeper discussion.
Do not diagnose authors from fiction.
Reader response can remain rigorous without invading the person.
275. Giving feedback: finish with priorities
If you have twenty notes, identify the two or three that most affect the whole work.
Structural priorities help the writer sequence revision.
Do not bury the causal break beneath comma comments.
Feedback should reduce uncertainty, not create a new pile of noise.
276. Giving feedback: begin with the reading experience
Say what you understood, expected or felt at a specific point.
“I thought the box belonged to Ryan until this line” is more useful than “confusing.”
Describe before prescribing.
The writer can then compare your model with intended effect.
277. Giving feedback: cite location
Point to scene, paragraph or moment.
Avoid dumping a global judgement without evidence.
Location makes revision efficient.
It also prevents one weak line from becoming a verdict on the whole manuscript.
278. Giving feedback: distinguish certainty
Say “I may have missed this” when appropriate.
Readers can be wrong about facts in the text.
Humility improves collaboration without weakening useful notes.
Evidence can settle the question.
279. Giving feedback: respect the chosen genre
Do not ask a quiet literary story to become a thriller simply because you prefer thrillers.
Evaluate whether the work fulfils its own promises.
Genre knowledge helps; genre policing does not.
Ask before assuming intention.
280. Giving feedback: protect authorship
Offer alternatives as options, not ownership claims.
Avoid rewriting whole passages into your voice unless the writer requested line-level examples.
A sample can illustrate a mechanism without becoming replacement text.
The author decides.
281. Giving feedback: identify strengths precisely
“Good dialogue” is pleasant but vague.
Say which exchange changed the relationship or sounded distinct.
Precise positive feedback helps writers preserve what works during revision.
Critique is not only defect detection.
282. Giving feedback: avoid personality judgement
Comment on the text, not the writer’s intelligence, maturity or worth.
“The causal link is missing” is actionable. “You are careless” is not.
Respect improves information quality.
Craft critique should remain about craft.
283. Giving feedback: separate factual correction
If a real-world claim is wrong, identify the source or basis for correction where possible.
Do not present uncertain memory as authority.
Factual accuracy and artistic preference are different note types.
Label them clearly.
284. Giving feedback: ask permission for sensitive depth
Some autobiographical or personal material may not invite speculative interpretation.
Stay with what the text presents unless the writer requests deeper discussion.
Do not diagnose authors from fiction.
Reader response can remain rigorous without invading the person.
285. Giving feedback: finish with priorities
If you have twenty notes, identify the two or three that most affect the whole work.
Structural priorities help the writer sequence revision.
Do not bury the causal break beneath comma comments.
Feedback should reduce uncertainty, not create a new pile of noise.
286. Giving feedback: begin with the reading experience
Say what you understood, expected or felt at a specific point.
“I thought the box belonged to Ryan until this line” is more useful than “confusing.”
Describe before prescribing.
The writer can then compare your model with intended effect.
287. Giving feedback: cite location
Point to scene, paragraph or moment.
Avoid dumping a global judgement without evidence.
Location makes revision efficient.
It also prevents one weak line from becoming a verdict on the whole manuscript.
288. Giving feedback: distinguish certainty
Say “I may have missed this” when appropriate.
Readers can be wrong about facts in the text.
Humility improves collaboration without weakening useful notes.
Evidence can settle the question.
289. Giving feedback: respect the chosen genre
Do not ask a quiet literary story to become a thriller simply because you prefer thrillers.
Evaluate whether the work fulfils its own promises.
Genre knowledge helps; genre policing does not.
Ask before assuming intention.
290. Giving feedback: protect authorship
Offer alternatives as options, not ownership claims.
Avoid rewriting whole passages into your voice unless the writer requested line-level examples.
A sample can illustrate a mechanism without becoming replacement text.
The author decides.
291. Giving feedback: identify strengths precisely
“Good dialogue” is pleasant but vague.
Say which exchange changed the relationship or sounded distinct.
Precise positive feedback helps writers preserve what works during revision.
Critique is not only defect detection.
292. Giving feedback: avoid personality judgement
Comment on the text, not the writer’s intelligence, maturity or worth.
“The causal link is missing” is actionable. “You are careless” is not.
Respect improves information quality.
Craft critique should remain about craft.
293. Giving feedback: separate factual correction
If a real-world claim is wrong, identify the source or basis for correction where possible.
Do not present uncertain memory as authority.
Factual accuracy and artistic preference are different note types.
Label them clearly.
294. Giving feedback: ask permission for sensitive depth
Some autobiographical or personal material may not invite speculative interpretation.
Stay with what the text presents unless the writer requests deeper discussion.
Do not diagnose authors from fiction.
Reader response can remain rigorous without invading the person.
295. Giving feedback: finish with priorities
If you have twenty notes, identify the two or three that most affect the whole work.
Structural priorities help the writer sequence revision.
Do not bury the causal break beneath comma comments.
Feedback should reduce uncertainty, not create a new pile of noise.
296. Giving feedback: begin with the reading experience
Say what you understood, expected or felt at a specific point.
“I thought the box belonged to Ryan until this line” is more useful than “confusing.”
Describe before prescribing.
The writer can then compare your model with intended effect.
297. Giving feedback: cite location
Point to scene, paragraph or moment.
Avoid dumping a global judgement without evidence.
Location makes revision efficient.
It also prevents one weak line from becoming a verdict on the whole manuscript.
298. Giving feedback: distinguish certainty
Say “I may have missed this” when appropriate.
Readers can be wrong about facts in the text.
Humility improves collaboration without weakening useful notes.
Evidence can settle the question.
299. Giving feedback: respect the chosen genre
Do not ask a quiet literary story to become a thriller simply because you prefer thrillers.
Evaluate whether the work fulfils its own promises.
Genre knowledge helps; genre policing does not.
Ask before assuming intention.
300. Giving feedback: protect authorship
Offer alternatives as options, not ownership claims.
Avoid rewriting whole passages into your voice unless the writer requested line-level examples.
A sample can illustrate a mechanism without becoming replacement text.
The author decides.
301. Giving feedback: identify strengths precisely
“Good dialogue” is pleasant but vague.
Say which exchange changed the relationship or sounded distinct.
Precise positive feedback helps writers preserve what works during revision.
Critique is not only defect detection.
302. Giving feedback: avoid personality judgement
Comment on the text, not the writer’s intelligence, maturity or worth.
“The causal link is missing” is actionable. “You are careless” is not.
Respect improves information quality.
Craft critique should remain about craft.
303. Giving feedback: separate factual correction
If a real-world claim is wrong, identify the source or basis for correction where possible.
Do not present uncertain memory as authority.
Factual accuracy and artistic preference are different note types.
Label them clearly.
304. Giving feedback: ask permission for sensitive depth
Some autobiographical or personal material may not invite speculative interpretation.
Stay with what the text presents unless the writer requests deeper discussion.
Do not diagnose authors from fiction.
Reader response can remain rigorous without invading the person.
305. Giving feedback: finish with priorities
If you have twenty notes, identify the two or three that most affect the whole work.
Structural priorities help the writer sequence revision.
Do not bury the causal break beneath comma comments.
Feedback should reduce uncertainty, not create a new pile of noise.
306. Giving feedback: begin with the reading experience
Say what you understood, expected or felt at a specific point.
“I thought the box belonged to Ryan until this line” is more useful than “confusing.”
Describe before prescribing.
The writer can then compare your model with intended effect.
307. Giving feedback: cite location
Point to scene, paragraph or moment.
Avoid dumping a global judgement without evidence.
Location makes revision efficient.
It also prevents one weak line from becoming a verdict on the whole manuscript.
308. Giving feedback: distinguish certainty
Say “I may have missed this” when appropriate.
Readers can be wrong about facts in the text.
Humility improves collaboration without weakening useful notes.
Evidence can settle the question.
309. Giving feedback: respect the chosen genre
Do not ask a quiet literary story to become a thriller simply because you prefer thrillers.
Evaluate whether the work fulfils its own promises.
Genre knowledge helps; genre policing does not.
Ask before assuming intention.
310. Giving feedback: protect authorship
Offer alternatives as options, not ownership claims.
Avoid rewriting whole passages into your voice unless the writer requested line-level examples.
A sample can illustrate a mechanism without becoming replacement text.
The author decides.
311. Giving feedback: identify strengths precisely
“Good dialogue” is pleasant but vague.
Say which exchange changed the relationship or sounded distinct.
Precise positive feedback helps writers preserve what works during revision.
Critique is not only defect detection.
312. Giving feedback: avoid personality judgement
Comment on the text, not the writer’s intelligence, maturity or worth.
“The causal link is missing” is actionable. “You are careless” is not.
Respect improves information quality.
Craft critique should remain about craft.
313. Giving feedback: separate factual correction
If a real-world claim is wrong, identify the source or basis for correction where possible.
Do not present uncertain memory as authority.
Factual accuracy and artistic preference are different note types.
Label them clearly.
314. Giving feedback: ask permission for sensitive depth
Some autobiographical or personal material may not invite speculative interpretation.
Stay with what the text presents unless the writer requests deeper discussion.
Do not diagnose authors from fiction.
Reader response can remain rigorous without invading the person.
315. Giving feedback: finish with priorities
If you have twenty notes, identify the two or three that most affect the whole work.
Structural priorities help the writer sequence revision.
Do not bury the causal break beneath comma comments.
Feedback should reduce uncertainty, not create a new pile of noise.
316. Giving feedback: begin with the reading experience
Say what you understood, expected or felt at a specific point.
“I thought the box belonged to Ryan until this line” is more useful than “confusing.”
Describe before prescribing.
The writer can then compare your model with intended effect.
317. Giving feedback: cite location
Point to scene, paragraph or moment.
Avoid dumping a global judgement without evidence.
Location makes revision efficient.
It also prevents one weak line from becoming a verdict on the whole manuscript.
318. Giving feedback: distinguish certainty
Say “I may have missed this” when appropriate.
Readers can be wrong about facts in the text.
Humility improves collaboration without weakening useful notes.
Evidence can settle the question.
319. Giving feedback: respect the chosen genre
Do not ask a quiet literary story to become a thriller simply because you prefer thrillers.
Evaluate whether the work fulfils its own promises.
Genre knowledge helps; genre policing does not.
Ask before assuming intention.
320. Giving feedback: protect authorship
Offer alternatives as options, not ownership claims.
Avoid rewriting whole passages into your voice unless the writer requested line-level examples.
A sample can illustrate a mechanism without becoming replacement text.
The author decides.
321. Giving feedback: identify strengths precisely
“Good dialogue” is pleasant but vague.
Say which exchange changed the relationship or sounded distinct.
Precise positive feedback helps writers preserve what works during revision.
Critique is not only defect detection.
322. Giving feedback: avoid personality judgement
Comment on the text, not the writer’s intelligence, maturity or worth.
“The causal link is missing” is actionable. “You are careless” is not.
Respect improves information quality.
Craft critique should remain about craft.
323. Giving feedback: separate factual correction
If a real-world claim is wrong, identify the source or basis for correction where possible.
Do not present uncertain memory as authority.
Factual accuracy and artistic preference are different note types.
Label them clearly.
324. Giving feedback: ask permission for sensitive depth
Some autobiographical or personal material may not invite speculative interpretation.
Stay with what the text presents unless the writer requests deeper discussion.
Do not diagnose authors from fiction.
Reader response can remain rigorous without invading the person.
325. Giving feedback: finish with priorities
If you have twenty notes, identify the two or three that most affect the whole work.
Structural priorities help the writer sequence revision.
Do not bury the causal break beneath comma comments.
Feedback should reduce uncertainty, not create a new pile of noise.
326. Giving feedback: begin with the reading experience
Say what you understood, expected or felt at a specific point.
“I thought the box belonged to Ryan until this line” is more useful than “confusing.”
Describe before prescribing.
The writer can then compare your model with intended effect.
327. Giving feedback: cite location
Point to scene, paragraph or moment.
Avoid dumping a global judgement without evidence.
Location makes revision efficient.
It also prevents one weak line from becoming a verdict on the whole manuscript.
328. Giving feedback: distinguish certainty
Say “I may have missed this” when appropriate.
Readers can be wrong about facts in the text.
Humility improves collaboration without weakening useful notes.
Evidence can settle the question.
329. Giving feedback: respect the chosen genre
Do not ask a quiet literary story to become a thriller simply because you prefer thrillers.
Evaluate whether the work fulfils its own promises.
Genre knowledge helps; genre policing does not.
Ask before assuming intention.
330. Giving feedback: protect authorship
Offer alternatives as options, not ownership claims.
Avoid rewriting whole passages into your voice unless the writer requested line-level examples.
A sample can illustrate a mechanism without becoming replacement text.
The author decides.
331. Giving feedback: identify strengths precisely
“Good dialogue” is pleasant but vague.
Say which exchange changed the relationship or sounded distinct.
Precise positive feedback helps writers preserve what works during revision.
Critique is not only defect detection.
332. Giving feedback: avoid personality judgement
Comment on the text, not the writer’s intelligence, maturity or worth.
“The causal link is missing” is actionable. “You are careless” is not.
Respect improves information quality.
Craft critique should remain about craft.
333. Giving feedback: separate factual correction
If a real-world claim is wrong, identify the source or basis for correction where possible.
Do not present uncertain memory as authority.
Factual accuracy and artistic preference are different note types.
Label them clearly.
334. Giving feedback: ask permission for sensitive depth
Some autobiographical or personal material may not invite speculative interpretation.
Stay with what the text presents unless the writer requests deeper discussion.
Do not diagnose authors from fiction.
Reader response can remain rigorous without invading the person.
335. Giving feedback: finish with priorities
If you have twenty notes, identify the two or three that most affect the whole work.
Structural priorities help the writer sequence revision.
Do not bury the causal break beneath comma comments.
Feedback should reduce uncertainty, not create a new pile of noise.
336. Giving feedback: begin with the reading experience
Say what you understood, expected or felt at a specific point.
“I thought the box belonged to Ryan until this line” is more useful than “confusing.”
Describe before prescribing.
The writer can then compare your model with intended effect.
337. Giving feedback: cite location
Point to scene, paragraph or moment.
Avoid dumping a global judgement without evidence.
Location makes revision efficient.
It also prevents one weak line from becoming a verdict on the whole manuscript.
338. Giving feedback: distinguish certainty
Say “I may have missed this” when appropriate.
Readers can be wrong about facts in the text.
Humility improves collaboration without weakening useful notes.
Evidence can settle the question.
339. Giving feedback: respect the chosen genre
Do not ask a quiet literary story to become a thriller simply because you prefer thrillers.
Evaluate whether the work fulfils its own promises.
Genre knowledge helps; genre policing does not.
Ask before assuming intention.
340. Giving feedback: protect authorship
Offer alternatives as options, not ownership claims.
Avoid rewriting whole passages into your voice unless the writer requested line-level examples.
A sample can illustrate a mechanism without becoming replacement text.
The author decides.
341. Giving feedback: identify strengths precisely
“Good dialogue” is pleasant but vague.
Say which exchange changed the relationship or sounded distinct.
Precise positive feedback helps writers preserve what works during revision.
Critique is not only defect detection.
342. Giving feedback: avoid personality judgement
Comment on the text, not the writer’s intelligence, maturity or worth.
“The causal link is missing” is actionable. “You are careless” is not.
Respect improves information quality.
Craft critique should remain about craft.
343. Giving feedback: separate factual correction
If a real-world claim is wrong, identify the source or basis for correction where possible.
Do not present uncertain memory as authority.
Factual accuracy and artistic preference are different note types.
Label them clearly.
344. Giving feedback: ask permission for sensitive depth
Some autobiographical or personal material may not invite speculative interpretation.
Stay with what the text presents unless the writer requests deeper discussion.
Do not diagnose authors from fiction.
Reader response can remain rigorous without invading the person.
345. Giving feedback: finish with priorities
If you have twenty notes, identify the two or three that most affect the whole work.
Structural priorities help the writer sequence revision.
Do not bury the causal break beneath comma comments.
Feedback should reduce uncertainty, not create a new pile of noise.
346. Full feedback workshop: The Blue Box
Mira’s draft ends with Ben confirming that the sealed blue box contains display clips. Reader A says to open the box earlier. Reader B values not knowing what is inside.
Reader A may be signalling uncertainty about why the box matters. Reader B values the information boundary.
The intended question is what information Mira needs to move the box responsibly. Opening it would destroy that mechanism.
A better repair may strengthen Mira’s practical goal and the partial ownership label.
347. Full feedback workshop: The Saved Seat
One reader calls Mira kind. Another says the stranger conveniently leaves exactly when Jo arrives. A third remembers the wet folder.
The kindness note identifies an effect. The convenience note targets causality. The folder note identifies a strong image.
Revision can establish that the stranger sees Jo approaching because Mira identifies her.
Keep the wet folder because it motivates the offer and preserves consequence.
348. Full feedback workshop: The Wrong Door
Some readers blame the cleaner; others blame Ryan. The writer intended neither as villain.
Inspect framing. Make legitimate trolley geometry and visitor-navigation constraints visible.
The repair is not to announce that nobody is wrong.
Feedback can reveal accidental ethical framing.
349. Full feedback workshop: The Unsent Reply
One reader wants Jo more honest; another thinks she is too blunt.
Map the exact wording each reader saw.
Changing a verdict into reading experience can solve both concerns.
Small line choices can create large social effects.
350. Full feedback workshop: The Last Label
Readers agree the two-line card works but disagree about Adrian’s response.
Clarify sequence so Adrian diagnoses the narrow template after seeing the workaround.
Preserve his design expertise and Aisha’s attribution priority.
Character fairness improves when accidental villain framing disappears.
351. A feedback decision ledger
Use columns for note, source, location, observation, proposed fix, convergence, decision, revision and result.
Useful for long manuscripts; unnecessary bureaucracy for very short work.
The purpose is traceability.
Protect private reader identities appropriately.
352. A three-pass feedback review
First read notes without editing. Then group by structural, character, viewpoint, pacing, line and factual issues. Then choose priorities.
Repeated local notes may share one structural cause.
Fix high-level causes before downstream symptoms.
Reread the manuscript afterward.
353. When to ask a beta reader
Use beta readers when the work is complete enough to experience as a whole.
A beta reader is not automatically a copyeditor, fact checker or developmental editor.
Define the role because practices vary.
Ask about reader experience at the appropriate stage.
354. When to ask a subject expert
If a story materially depends on medicine, law, science, history, language or specialised procedure, ask a knowledgeable reader to check relevant claims.
Do not ask them to certify areas outside expertise.
Separate factual verification from artistic preference.
Record corrections and sources.
355. When to stop seeking feedback
More readers do not automatically produce more certainty.
Use a stop rule when central issues have converged, major unintended confusion is repaired and remaining changes are mostly taste.
Then finish.
A manuscript eventually needs an authorial decision.
356. Feedback and voice preservation
Compare a page before and after revision. Did clarity improve while rhythm, humour and attention remain recognisably yours?
If every unusual construction disappeared, you may have over-normalised.
Restore deliberate texture where intelligible.
Feedback should help the work become more itself.
357. Feedback and AI tools
Automated systems can organise notes and compare versions but can flatten voice, invent facts or overstate certainty.
Understand terms and permissions before sharing confidential or rights-sensitive material.
Ask for diagnosis and alternatives before wholesale rewrites.
Compare substantive changes against the authoritative manuscript.
358. Feedback and school writing
Classroom feedback should map to the actual task and criteria rather than generic literary taste.
Board and school requirements vary, so use current official instructions where rules matter.
Creative ambition and assessment compliance can coexist.
One rubric is not a universal theory of fiction.
359. Feedback and publication
Editors, publications and competitions can have distinct submission and revision processes.
Follow current guidelines for the specific destination.
Keep versions and document substantive changes.
Publication feedback is both craft and process.
360. The final feedback principle
A reader owns their experience. The writer owns the revision decision.
Take confusion seriously without assuming every proposed fix is right.
Look for evidence, patterns, purpose and consequences.
Then change the manuscript and read it again as a whole.
361. Sources and further independent study
Purdue OWL’s Fiction Writing Basics and the Open University’s Start writing fiction provide independent introductory fiction guidance.
These sources do not certify this article or its original critique laboratories.
All eduKateSG residents and workshop drafts here are fictional teaching demonstrations.
Use the linked ecosystem routes above for the full internal craft sequence.
362. A final ten-question feedback card
Where were you confused? What did you think the protagonist wanted? Which moment changed your expectation? Which choice felt least prepared? Which detail stayed with you?
Where did you want more time? Where did you want less? What did you think the ending changed? What question remained? Which part would you most regret losing?
Choose questions appropriate to stage and length.
Ask for observations before prescriptions.
363. Feedback becomes craft when it changes the right layer
If readers cannot follow the ending because a causal link is missing, fix structure before commas.
If structure works but a pronoun confuses the speaker, fix the sentence. If a factual claim is wrong, correct the fact.
If one reader simply prefers another genre, preserve the intended work.
Find the layer, make the smallest sufficient repair and check downstream consequences.
364. Feedback practicum: turn ten vague notes into useful questions
“It’s boring” becomes: where did attention drop, and what was happening there? “I don’t like Mira” becomes: which action or line changed your view of her? “The ending is weak” becomes: what did you expect to cause the resolution?
“Needs description” becomes: where could you not orient physically or sensorially? “Too much description” becomes: which passage delayed a choice or repeated information?
“Dialogue is unrealistic” becomes: which line felt unlikely for this speaker to say to this listener now? “Too confusing” becomes: what did you believe at that point?
“Make it more emotional” becomes: which consequence did not register? “Needs higher stakes” becomes: what consequence was unclear? “I wanted more” becomes: more of what—context, aftermath, relationship, scene time or explanation?
Vague notes become useful when translated into observable reading questions.
365. Feedback practicum: revise one paragraph after a reader note
Draft: “Mira was worried Clara would think she was accusing her, so she tried to ask carefully about the key.” Reader note: “I still thought Mira accused Clara.”
Do not argue that the narration says she was careful. Inspect the actual line she speaks.
If Mira says, “You had the key last?” the wording can still imply possession. Revise to: “Who did you return the key to yesterday?” if Mira already knows Clara returned it.
The repair aligns spoken evidence with intended social stance.
Feedback exposes gaps between author explanation and reader experience.
366. Feedback practicum: preserve a line readers love
Three readers mention Jo’s phrase “architectural veto.” You are restructuring the scene and considering cutting it.
Ask what they value: humour, character voice, compression of the floor-track fact?
If the new scene still contains the same physical discovery, preserve or adapt the line if it remains natural.
If the floor track disappears entirely, do not keep the joke as an orphan.
Positive feedback identifies assets, not sacred relics.
367. Feedback practicum: when readers miss the theme
If readers understand the choices and consequences but name a different theme, decide whether that is a problem.
Fiction can support multiple interpretations.
If they miss a factual or causal relationship essential to the story, repair evidence.
Do not add a final moral merely to force thematic agreement.
Meaning can remain open while events stay clear.
368. Feedback practicum: when readers predict the twist
Prediction does not automatically mean failure. Ask whether the intended pleasure is surprise, suspense, inevitability or confirmation.
If surprise matters, inspect over-signalling. If suspense matters, prediction may increase tension.
Do not remove all setup to make the outcome impossible to anticipate.
A fair story often allows some readers to infer correctly.
369. Feedback practicum: when nobody predicts the twist
A completely unpredicted reveal may be delightful or arbitrary.
Ask whether readers can retrospectively identify evidence.
If not, plant fair setup or redesign the reveal.
The goal is not a required prediction rate.
The goal is a relationship between surprise and causality.
370. Feedback practicum: when one reader rewrites everything
A generous reader may return pages of replacement prose.
Thank them for the effort, then translate the rewrite into mechanisms: shorter sentences, earlier orientation, stronger verbs, different tone.
Do not adopt another person’s voice wholesale unless the collaboration explicitly calls for co-authorship or editorial rewriting under agreed terms.
Recover the problem their version tries to solve.
Then solve it in your own language.
371. Feedback practicum: when critique hurts
Do not make immediate global decisions about the manuscript while emotionally activated.
Record the note, locate the evidence and return when you can distinguish the text from the feeling of receiving criticism.
You do not need to accept disrespectful delivery to extract a useful factual point.
Nor must every painful comment contain wisdom.
Craft judgement improves when the note becomes specific enough to test.
372. Feedback practicum: when praise makes revision harder
Praise can create attachment. A reader loves a scene that duplicates another scene’s function.
Ask what quality they love—voice, image, relationship—and see whether that quality can survive elsewhere.
Do not keep structural redundancy solely because one passage is polished.
Preserve strengths while repairing architecture.
Revision can move value rather than destroy it.
373. Feedback practicum: the second-reader test
After a major repair, give only the revised passage to a fresh reader who did not see the original.
Ask the same diagnostic question.
This reduces contamination from remembered explanations.
If the new reader experiences the intended effect, the repair has stronger evidence.
Then check the whole manuscript for downstream consistency.
374. Feedback practicum: the no-explanation handoff
Send a short story without telling the reader what it is “about.”
Ask for their summary of goal, central change and ending.
Compare with your intended design.
Large differences can reveal framing or emphasis issues.
Afterward, discuss intention and decide whether difference is productive.
375. Feedback practicum: the one-question handoff
Sometimes ask only one question: “Did the ending feel caused?”
A narrow request reduces cognitive load and produces deeper response.
Use this when you already know the uncertainty.
Do not ask a reader to perform a full manuscript diagnosis every time.
Good feedback requests are scoped.
376. Feedback practicum: the keep-list handoff
Ask a trusted reader which three elements they would protect during revision.
Their answers reveal perceived strengths.
Compare across readers.
A keep list helps prevent problem-solving from flattening the manuscript.
Revision needs preservation as well as correction.
377. Feedback practicum: the factual handoff
Give a subject expert the passages containing material claims and a list of questions.
Do not require them to read unrelated chapters unless context is necessary.
Ask for sources or corrections where feasible.
Record uncertainty rather than forcing false precision.
Efficient expert review respects both accuracy and time.
378. Feedback practicum: the final proof handoff
At final stage, ask a fresh reader to look for surface errors and continuity rather than redesigning the story.
Late structural suggestions can still matter if they reveal serious defects, but every large change creates new proof risk.
Define the stage clearly.
Use version control.
Proof the actual release state.
379. Feedback practicum: close the loop
After revision, write one sentence for each major accepted note: what changed and what effect you expect.
For rejected notes, record why: genre preference, contradiction with evidence, solved elsewhere, or deliberate choice.
This prevents endless reconsideration.
It also teaches your recurring blind spots.
Feedback becomes a learning system across projects.
380. The final handoff
When the manuscript has absorbed the useful notes, stop explaining it and let it stand.
A reader should not need the workshop conversation to understand basic action, viewpoint and causality.
Not every interpretation must match yours.
The goal is a work that carries enough evidence for readers to have their own experience.
Feedback succeeds when it eventually becomes unnecessary.