Module 12
Feedback
How Do You Learn from Results and Others?
Book section: Feedback — How do you learn from results and others?
Core lesson: Creative work needs contact with reality. Share it appropriately, seek useful responses, and retain responsibility for your decisions.
Learning outcomes
- Build a feedback loop for a real creative piece.
- Distinguish relevant criticism from approval, silence, and personal taste.
- Share work without depending on friends or family to become its audience.
Lesson
1. Work hidden forever cannot teach you everything
Private practice is important, but some problems appear only when another person uses, reads, watches, or encounters your work. The book repeatedly encourages putting work into the world, accepting rejection, and making small public attempts. Sharing can be uncomfortable precisely because it reveals the distance between intention and reception. That distance is useful information.
2. Choose the right people to ask
The book warns against pressuring friends and family to consume every project. Their affection does not make them the target audience, nor does a polite compliment tell you what needs improving. Find people with a reason to care about the kind of work you are making. Ask small, specific questions. Instead of “Is it good?” try “Where did your attention drop?” or “Could you complete the central task without my explanation?”
3. Judge feedback on merit
Feedback is not an order. A response may identify a real problem while offering an unsuitable solution. Several people saying an instruction is confusing is important. One person preferring a different style may simply have a different taste. Look for patterns, concrete observations, and relevance to your goal. The author advocates listening and remaining the person who steers the ship.
4. Silence is ambiguous
A work that receives little attention might be weak, poorly distributed, narrowly relevant, or simply unnoticed. The book cautions against expecting immediate validation. Avoid inventing a flattering explanation, but also avoid treating one quiet launch as a final verdict. Continue to make, improve, and find more relevant opportunities to test.
5. Make feedback a cycle
A practical loop is make → show → observe → decide → revise → show again. Use your own tools or work as an ordinary user would. Read your writing aloud. Explain a concept out loud to find gaps in your understanding. Approach a relevant publication or community rather than waiting for attention to arrive. The next experiment should answer a question revealed by the previous one.
Practical exercise — Prepare a useful feedback request (20 minutes)
Choose one piece that is ready enough to show. Define its intended audience and one aspect you need to learn about. Write three precise questions, such as What did you think this was for? Where did you get stuck? What felt most useful? Avoid asking someone to evaluate your talent or personal worth.
Example: An app maker asks three people to complete one task, watches where they hesitate, and records each problem before defending the design.
Assignment — Close the feedback loop
Share one real piece with at least one relevant reader, viewer, tester, or mentor. Record exactly what they said or did. Identify one change you will make and one suggestion you will not follow, with reasons. If no response arrives, record what you can and plan a more relevant second attempt rather than fabricating a conclusion.
Reflection
1. Am I looking for information that improves the work, or reassurance about myself?
2. Who is genuinely qualified to respond to the question I am asking?
3. How can I make my next attempt easier to evaluate?
Module takeaway: Show the work, listen without surrendering judgement, and let evidence improve the next version.