Coming soonDainvo Productivity. Soon a full email client and productivity space, written in Go to stay light and fast.See what's coming →
Dainvo

Everyday planning

How to ask for useful feedback on unfinished work

Get useful feedback before polishing a draft. Choose a question, send a small reviewable piece, agree on timing and turn the response into a next step.

Dainvo EditorialOctober 24, 20264 min read

A separate coral puzzle piece beside an unfinished teal, navy and cream jigsaw puzzle on ivory paper. Text: Ask about one part.

You've rewritten the opening six times. The slides look better. You still don't know whether the proposal answers the question your manager actually needs answered.

Another hour of polishing won't tell you what that reader thinks. A small, specific request can.

The hard part is deciding what to show and what kind of response would let you continue. "Any thoughts?" leaves that work to the person opening the file. Try giving them one decision to help you make.

Find the question you can't answer alone

Start with the uncertainty holding up the work. Perhaps you don't know whether the example makes sense to a beginner, whether a recommendation fits the budget, or whether the instructions leave out a necessary step.

Write the question before choosing the file to send. For example:

Can a new volunteer work out where to go when they arrive, using this page alone?

That question gives you a reason to share an unfinished page. You don't need the complete volunteer handbook to discover that the arrival instructions name a room nobody can find.

Developmental editor Emily Doucet discusses identifying a manuscript's audience and questions early in a February 2026 conversation with Jo VanEvery. That's advice about academic writing, but it raises a useful planning question for other work: what does this draft need to help its reader do?

If you can already answer the question by checking the brief, do that first. Save another person's attention for something their perspective can resolve.

Send a piece that can answer that question

Choose enough material for a fair response. A paragraph without context may be impossible to judge. A 40-page document may be far more than the question requires.

For the volunteer example, send the arrival page with one sentence explaining who will use it. For a budget proposal, send the recommendation and the assumptions behind its cost. For a presentation, send the two slides where the explanation becomes unclear.

Mark gaps plainly. "The figures are provisional" matters more than apologizing for the font. If the numbers are essential to the decision, verify them before asking someone to assess the recommendation.

In his October 21 account of developing a book, Tiago Forte describes using reader feedback to find confusion in draft material. His account concerns his own book and promotes it; it doesn't prove a universal productivity method. The practical opportunity here is simply to learn something from a reader while changing the work is still possible.

Ask someone who can judge this part

The most senior person available may not be the most useful reader. A new volunteer can expose confusing arrival instructions. A colleague who manages the venue can check whether those instructions are accurate. Those are different requests.

For a workplace decision, identify who can approve it. A helpful colleague's opinion doesn't authorize a budget or a change in scope. You may need both an informal reader and a formal decision later.

Keep the review within the person's role and access. Use an approved document location for confidential work. Remove unrelated client details, and check the sharing permissions before sending the link.

You also don't need to gather everyone's opinion. Start with the perspective you are missing. Add another reader when their knowledge answers a different question, rather than collecting reassurance from a larger audience.

Make the request easy to understand

Tell the person what you want reviewed, what answer would help, and when that answer would be useful. Ask whether the timing works.

Jo VanEvery's older guide to requesting comments recommends agreeing on timing and allowing colleagues to decline. The principle matters more than copying its academic timetable.

Here's an original example for the volunteer page:

Would you be willing to read this one-page arrival guide? I'm trying to find out whether someone who hasn't visited before can locate the entrance and check in. Please mark any instruction that leaves you unsure what to do. The activity descriptions are still placeholders. Would Thursday afternoon work for your comments? It's fine if you don't have room this week.

Avoid calling something a "quick look" when you haven't checked how much reading it involves. State the size and scope instead. If a conversation would be easier, offer it; don't book time without agreement. A short meeting preparation check can help you bring the question and the right version.

Plan what happens while you wait

After sending the request, record the version, the reader and the agreed response date. Keep the link beside that record so you can find the same material again.

Then choose work that won't depend on the answer. You might check the venue's opening hours while waiting for someone to test the arrival instructions. Redesigning the whole page could waste effort if the reviewer is about to suggest a different route through it.

If no response date was agreed, the request is still open. Decide when to check in rather than treating silence as acceptance. Where the deadline is fixed, raise the missing decision with the responsible person. Our guide to competing project deadlines separates your working time from time spent waiting on others.

Turn the response into a change you can check

Read the comments against your original question. "This is confusing" needs a follow-up: where did the reader lose track, and what did they expect to happen there?

For the arrival guide, a reader might mistake the delivery entrance for the public entrance. Your next task could be: "Replace the entrance photo and add the street name." Another round of general polishing would leave the actual problem unresolved.

Keep conflicting suggestions visible until you can make a decision. Two readers may have different needs. Ask which audience this version serves, or whether the instructions need a separate route for each group. You don't have to implement every preference.

Finally, check the changed passage. Can the reader now identify the entrance? If the answer is yes, finish that part and move on. If another uncertainty remains, name it before requesting another review. The next useful step should be clearer than "make this better."

More Dainvo resources for choosing the right daily planning workflow.

Esc to close