Turn feedback into one change

At 9:15, a message lands beside your draft: "This section is hard to follow."

You read the sentence twice. The comment describes a page. Your mind turns it into a judgment about the whole piece, your ability, and the hours you have already spent. The next temptation is to change everything at once.

Take the comment as a request for one adjustment you can see and test.

"Hard to follow" might become: put the main point in the first paragraph. "Too slow" might become: remove the opening example and begin with the decision. "I am missing the point" might become: add one sentence that says what the reader should understand by the end.

The original comment can stay broad. Your response needs a smaller edge. Choose one change that could make the problem better, then look at the result.

A reviewer may have noticed a real problem without naming its exact cause. You can learn more by testing one plausible cause than by making ten unrelated edits. The test also keeps the comment in its proper place: feedback describes the work in front of you; it leaves your identity out of the sentence.

Broad feedback creates a large, shapeless job. You can spend an hour moving sentences, changing headings, and polishing words while the original problem remains hard to name.

One change gives the work a visible question: does the reader find the main point faster after the opening moves? Does the shorter introduction make the section easier to enter? Does the added sentence answer the question that caused the confusion?

Begin with a reasonable adjustment and a way to inspect what changed. A small test turns embarrassment into information you can use for the next pass.

Choose one piece of work that received a vague comment, or one piece that you have been avoiding because you already expect criticism. Set a timer for 15 minutes and write three lines:

Make only that change during the timed block. Read the affected section once from the beginning. Ask what a reader can understand sooner, where the reader still has to guess, and whether the revision gives you a clearer next move.

If the change helps, keep it and choose the next small adjustment later. A missed test still tells you which explanation deserves less attention. Write one sentence about the result before you close the file.

Feedback becomes easier to carry when it becomes specific work. Take one comment, make one change, and let the next read tell you where to go.