Contents
To ask for useful feedback on a creation, explain what you’re sharing, what stage the work is at, and what question you’d like an opinion on. Choose someone able to consider that point, then give them the chance to decline or take some time. You’ll have a more focused exchange than with a general request for approval. After asking for feedback, the next step is to sort through criticism you received. Sharing and asking for a critique are two separate choices: you can also choose an initial audience for an imperfect creation. Focused feedback becomes more useful when you know what qualitative progress you’d like to see. For a piece of writing, a focused request might be to identify points of hesitation during a read-aloud. If your experiment is based on an existing work, you can ask for feedback on how much it depends on the reference and which choices are your own.
Feedback can be about a text, an image, an object, or a presentation. It doesn’t automatically tell you which direction to take. Your role is still to understand the observation, compare it with your intention, and decide what you want to test. Not every preference someone expresses becomes a required correction.
Choosing the right time to share
A very open-ended draft and a nearly finished version call for different questions. At the beginning, you might ask whether the main idea is clear. Later, you might check readability, usability, or a finishing detail. Explain what’s still provisional so the conversation doesn’t focus on a part you already know is unfinished.
You don’t necessarily have to share your work as soon as you feel uncertain. Sometimes a small experiment on your own can answer the question. On the other hand, waiting until the very last minute makes changes harder. Choose a time when you can still use the feedback without having to redo a disproportionate amount of work.
The creative project journal can keep a list of open questions. Choose the one that would genuinely benefit from an outside perspective. That way, you won’t ask the other person to resolve every uncertainty that has built up while you’ve been creating.
Finding the right person for the question
To check how an object is used, someone close to its future user may be a good choice. For a technical question, look for someone familiar with the practice. To find out what a reader understands on a first read, someone new to the subject may offer a different perspective from a specialist.
Explain the size of the request. Reading two pages, testing an object for ten minutes, and reviewing an entire dossier aren’t the same commitment. Give a deadline only if it’s necessary and reasonable. Don’t assume that friendship or being close means someone is automatically available.
You can also specify the format that would help you: a few written observations, a short discussion, or an annotated draft. If the document contains private information or concerns other people, remove anything unnecessary before sharing it and choose an appropriate recipient.

Asking a question that invites an observation
“Do you like it?” can be a genuine question, but it mostly tells you someone’s preference. To improve a version, ask instead what the person understands, notices, or is able to do. “At what point did you understand the subject?” or “What information do you look for first?” will give you more specific feedback.
Avoid questions that already contain the answer you expect. “You think this page is clearer, right?” makes it harder to disagree. Ask the question simply and let the person describe their experience in their own words.
You can show two versions, but explain how they differ without saying right away which one you prefer. Ask what effect each version has and in what context it might seem more suitable. The comparison becomes more useful than a standalone vote between two options.
Flip cards
Turning a vague request into a specific one
“Is it good?”Flip
Which part is easy for you to understand, and where do you have to reread or ask for clarification?
“Which one do you prefer?”Flip
How does each version change the way you view or use the object?
“What’s wrong?”Flip
Which point seems least clear to you in relation to the stated use?
“How would you do it?”Flip
What observation leads you to suggest this change?
Read alsoLimiting beliefs: how to recognize and move beyond them, one step at a timeListening before defending every choice
Let the person finish sharing their observation. Note the important words and ask for an example if you don’t understand. You can explain your intention afterward, but an immediate explanation can hide the information you’re looking for: what the creation communicates without your commentary.
Distinguish three levels of feedback: observation, interpretation, and suggestion. “I couldn’t find the button” describes an experience. “It seems secondary” offers an interpretation. “Make it red” is one possible solution. You can take the observation into account without adopting that exact solution.
If the feedback is still general, ask about a specific passage or moment. “The text is long” can mean several things: repetition, difficulty finding the main idea, or an unfamiliar subject. A clarifying question helps you understand the problem before deleting a section at random.
Sorting feedback in your journal
After the conversation, sort the points into three groups: to fix, to test, and to set aside. A factual error or missing information may need correction. A color preference may be worth testing, or it may not fit your intention. Briefly note the reason for your choice.
Return to the success criteria for the version. Feedback can be valid while relating to a different use than the one you have in mind. In that case, you can clarify the scope instead of changing the whole project. Conversely, several consistent observations about a central point deserve special attention. As delivery approaches, sort through the final details to finish a defined version.
Avoid counting reviews as if they were an objective measure of quality. People don’t all have the same context, expectations, or experience with the object. Keep track of where the feedback came from and the circumstances around it to understand what it can teach you.
Testing a limited change
Choose one change at a time when you want to observe its effect. If you change the structure, color, and text all at once, you won’t know what made the version clearer. Keep a copy of the original to compare, especially if the change is difficult to undo.
Define the question for the next review. “Does the caption now make the photograph understandable without an explanation?” gives you something concrete to check. You can ask someone else to explore the version if the first person already knows too much about the project, as long as sharing it is appropriate.
Note the outcome and the decision. A suggested change may not solve the problem or may create another one. That’s no reason to ignore the initial feedback; you can look for another solution to the observation that still holds true.
Keeping your creation separate from judgments about you
Feedback is about one version, in one situation. It doesn’t sum up your talent, your commitment, or your future in the activity. You can feel disappointed or upset and still choose to reread the observations later. You don’t have to decide on all the changes right away.
The guide to comparing yourself without putting yourself down can help when feedback triggers a broad comparison with other creators. Return to the work you shared, the circumstances, and the question you asked. A version can evolve without you having to defend your whole identity.
Finally, thank the person for the time they spent, without promising to apply every suggestion. You can tell them what the exchange helped you clarify. This closing acknowledges their help while leaving you responsible for your choices and free to create.
Frequently asked questions
Should I ask several people?
Not always. One well-chosen person may be able to answer a specific question helpfully. Asking for too many opinions too soon can make your choices more confusing.
What should I do with conflicting feedback?
Compare people’s uses and expectations. Both observations may be consistent in different contexts. Then return to your intention and test the most relevant solution.
Can I turn down a suggestion?
Yes. First, try to understand the observation behind it, then decide. You can thank someone for their perspective without adopting their exact proposal.



