Listen to Criticism Without Handing Over the Pen

When you put something you made into the world, people will have opinions about it. Some will be generous. Some will be blunt. Some will tell you exactly what they think is wrong, and some will leave you with little more than “This is terrible.”

My rule is simple: listen to all criticism, but choose whether to accept it.

That sounds straightforward, but it asks for two different skills. Listening takes humility. Deciding what to do takes judgment. If you only listen, you can end up treating every opinion as an instruction. If you only trust your own instincts, you can miss things other people are trying to show you. I want to stay open to feedback without giving away my responsibility for the work.

First, understand what they mean

It can be hard to listen when criticism stings. The first reaction might be to defend the work, explain what the critic misunderstood, or dismiss them as someone who does not get it. Sometimes the criticism really is unfair. But before deciding that, I try to understand what the person actually experienced.

If someone says a website is confusing, I can ask what they were trying to do and where they got stuck. If a reader says a story did not work for them, I can ask what felt unclear or unconvincing. A specific example is easier to evaluate than a sweeping judgment. “I couldn’t find the instructions” gives me something concrete to consider. “This whole project is pointless” is a much broader conclusion, and may not tell me what to change.

A clarifying question does not mean I agree with the criticism. It means I want to hear the real point before responding to it. Sometimes a person who sounds harsh has noticed a genuine problem. Sometimes a person who sounds confident is expressing a preference as if it were a universal rule. I need to know which kind of feedback I’m hearing.

Ask what kind of feedback it is

Criticism can be about different things. It might point to a factual mistake, a technical problem, a confusing design choice, or a gap between what I intended and what people understood. Those are often worth investigating. It might also be a matter of taste: someone does not like the style, subject, or approach. That reaction is real, but it does not automatically mean the work is failing at its purpose.

The audience matters too. If I make a board-game site mainly to create a fun experience for friends and family, their experience is especially relevant. If I build an app for my wife and me, whether it helps us matters more than whether a stranger would choose the same features. Feedback from people outside that group can still be useful. They may spot a problem or suggest an idea. I just have to weigh it against what the project is for.

Sometimes people criticize because they misunderstood the work. That could mean they were not paying attention, but it could also mean I did not make the purpose clear. A misunderstanding is not automatically the creator’s fault, and it is still useful information: I can decide whether I want to make the work easier to understand or whether the explanation is already clear enough for the people I made it for.

Check the feedback against your goals

Before changing anything, I try to ask: What am I trying to make? Who is it for? Would this change help the work do what I want it to do?

If someone says the site needs more features, but the features would make it harder for my family to use, I may choose to keep it simple. If a reader points out that a character’s decision makes no sense, I should consider whether the story supports that decision well enough. If a person who uses the app every day says a basic task takes too many steps, that is likely more important than a stranger’s suggestion for a new visual effect.

This is not a formula that makes every decision obvious. It is a way to keep the decision connected to the work rather than to the pressure of being criticized. I can ask whether the feedback is specific, whether the person has relevant experience, whether others have raised the same issue, and whether the proposed change solves the problem without creating a bigger one.

I do not need to accept a suggestion just because it came from an expert or someone I respect. Their perspective deserves consideration; I still have to decide what fits. I also do not need to reject a suggestion just because it came from someone who is not an expert. A friend or family member may notice a practical issue that a professional would overlook.

Accept, adapt, or decline

Once I have listened, there are more than two choices. I can accept the criticism and make the suggested change. I can accept the concern but solve it another way. I can decide to leave the work as it is because the criticism conflicts with the purpose or style I chose. Or I can wait and think about it before deciding.

Changing something does not mean I was foolish to make it the original way. It means I learned something after other people interacted with it. Refusing a suggestion does not mean I am arrogant or unwilling to grow. It may mean the suggestion is not right for this project. The key is being able to explain the decision to myself, even if I cannot persuade every critic.

There are cases where criticism points to harm, safety, or a real effect on other people. Then “I made it for myself” is not a reason to ignore the concern. If people are affected by the work, I have a responsibility to take that seriously. My judgment still matters, but it includes thinking about consequences and being willing to correct a mistake.

Keep your hand on the pen

Listening is part of making things well. It helps me see blind spots, understand how the work lands, and improve what I have made. But feedback is not a transfer of ownership. The person who made the work remains responsible for its choices, its goals, and its next version.

I do not want to treat every critic as an enemy, and I do not want to treat every critic as an authority. I can hear someone fully, thank them, ask questions, and take time to consider what they said. Then I can choose what to accept.

That is the balance I want: enough humility to learn, and enough confidence to remain the author. I can let criticism inform the work without letting it decide what the work is allowed to be.