Could You Take a Look? Giving Kind, Useful Feedback on a Coworker's First Draft
A coworker sends you a draft late in the afternoon with a short message: "Could you take a look before I send this out?" You open it and feel the familiar mix of wanting to help and not wanting to hurt. Some parts are strong. Some parts are confusing. One paragraph probably needs to go entirely. How do you say all of that in a way that makes the work better and leaves the two of you on good terms?
Giving feedback on someone else's writing is one of those everyday work skills nobody really teaches. We either soften everything until it says nothing, or we mark it up like a red-pen teacher and wonder why the next request never comes. There is a gentler middle path, and it can be learned.
Ask What Kind of Help They Want
Before you change a single word, find out what the person is actually asking for. "Take a look" can mean many things. A quick question saves both of you time and avoids the awkward moment of rewriting something they only wanted proofread.
- Is this a quick check or a deep read? Typos and tone are a different job from structure and argument.
- Who is the reader? A note for a client and a note for the team need different things.
- When do they need it back? Feedback that arrives after the deadline is not much help, however good it is.
If they are not sure, offer a default: "I'll focus on whether the main point is clear, and flag anything small along the way."
Start With What Is Working
This is not about flattery. It is about information. When you tell someone which parts are strong, you are telling them what to keep, and that is just as useful as telling them what to change. Be specific, because "looks good" gives the writer nothing to hold on to.
Compare "nice intro" with "the opening example made the problem easy to picture right away." The second one tells your coworker that concrete examples work for this reader, and they will likely use more of them. Specific praise teaches; vague praise only reassures.
Describe Your Experience, Not Their Mistakes
One small shift makes feedback easier to hear: talk about what happened to you as a reader rather than what the writer did wrong. "This section is confusing" sounds like a verdict. "I got a little lost here and had to read it twice" sounds like a report, and it is much harder to argue with.
- Point to the exact spot. A comment on the paragraph itself is clearer than a summary at the end.
- Say what you expected. "I thought this part would explain the timeline" helps them see the gap.
- Offer, don't impose. "One option might be to move this up" leaves the choice where it belongs: with the person whose name is on the work.
Try to keep the number of big comments small. Three clear suggestions are more useful than twenty scattered ones. If you notice many small things, group them: "a few sentences run long; here are two examples."
Close the Loop Kindly
When you send your notes back, add a short human line at the top. Something like, "Overall this is in good shape. The main thing I'd look at is the middle section; the rest is small stuff." That one sentence sets the tone for everything below it and keeps a long list of comments from feeling like a pile-on.
Then let it go. The draft belongs to them, and they may not take every suggestion. That is fine. Feedback is an offering, not an order. If they send the final version later, it can be nice to notice what changed: "The new opening really works." It tells them the effort was worth it, and it makes the next request feel safe.
Good feedback leaves the writer feeling more capable, not less.
When You Are the One Asking
It helps to remember how this feels from the other side. Sharing an unfinished draft takes a little courage. When you ask for feedback yourself, you can make it easier for the reader: say what kind of help you want, point to the part you are unsure about, and thank them for their time no matter what they say. Over time, a team where people trade drafts this way becomes a team where people write better, and worry less about it.
The next time a draft lands in your inbox with a hopeful "could you take a look?", try reading it as a friend would: curious, honest, and on their side. You do not need perfect words. You only need to be clear about what you noticed and kind about how you say it. The work will improve, and so, quietly, will the trust between you.