Getting Feedback

There is a version of feedback that feels good and teaches you nothing: 'Wow, this is amazing!' And there is a version that feels uncomfortable and makes your project dramatically better: 'I got confused here. I expected this to happen, but that happened instead. I almost quit at this step.' Learning to ask for the second kind — and to hear it without defensiveness — is one of the most important skills a builder can develop. Your project is not your identity. Its flaws are not your flaws. They are just information.

How to Ask for Useful Feedback

Vague requests get vague responses. 'What do you think?' invites 'It looks cool!' — which tells you nothing. Specific requests get specific responses. Here are three types of targeted feedback questions that actually improve products: Confusion question: 'Was there any moment where you were not sure what to do next?' Expectation question: 'Was there anything that did not work the way you expected?' Value question: 'If you could only keep one thing in this project, what would it be?' The confusion question finds usability problems. The expectation question finds broken assumptions. The value question tells you what your core feature actually is in the user's eyes — which may surprise you.

When Priya from Lesson 1 shared her quiz app, she got three types of feedback: A classmate said the button was hard to find on a phone (signal — she moved it to the bottom of the screen). Another said the font color was hard to read on their laptop screen (signal — she increased contrast). A third said they wished it had a dark mode (noise — valid preference, but not a problem that would block most users from using the app). Priya fixed the two signal issues before her next share. She noted the dark-mode request in a 'future features' list. This is the discipline: act on what blocks users, not on every wish.

Giving Feedback Responsibly

Getting feedback only works if you are also willing to give honest feedback to others. Builders who only offer compliments are not being kind — they are wasting each other's time. Useful feedback is specific, kind, and actionable. Specific means pointing to a particular moment or element. Kind means framing it as your experience, not a judgment. Actionable means the builder can actually do something with it. Say: 'When I clicked Submit without filling in the form, nothing happened and I was not sure if it worked.' Do not say: 'Your error handling is bad.' The first tells the builder exactly what happened and where. The second is an opinion that offers no path forward.