How to Use Feedback Without Losing Your Voice

Feedback is often a mixture of observations, preferences, constraints and suggestions. One person wants a shorter introduction, another asks for more context and a third dislikes the colour. Treating every comment as an instruction makes work incoherent; ignoring them all wastes insight.

Separate problems from proposed solutions

When someone says ‘Make the button bigger,’ ask what went wrong. Could they not find it, read its label, or activate it on a phone? The underlying observation may matter more than the suggested fix. Clarifying the problem gives you room to choose the best response.

Consider the source and purpose

Feedback from a prospective reader, editor, accessibility tester, supervisor and friend can serve different goals. Determine what expertise or experience each person brings and whose needs your work is meant to meet. Avoid using social status alone as a substitute for relevance.

Categorise responses

Choose whether to apply the change, run a reversible test, seek clarification or politely decline. Where feedback conflicts, return to the project’s stated goal. Document important decisions so future collaborators understand why a suggestion was accepted or not.

Test one improvement at a time

For a design or piece of writing, make a limited revision and ask whether the original problem is now resolved. Compare the result against clarity, correctness, safety, accessibility and the intended audience. Do not make multiple dramatic changes that prevent you from learning what helped.

How this looks in everyday life

A student receives feedback that a portfolio case study is ‘boring.’ Instead of adding dramatic claims, they ask which part was unclear. The reviewer cannot see the student’s contribution, so the revision adds a short ‘My role’ section and one permitted example. The voice remains honest and the presentation becomes stronger.

What to watch for

Some criticism is disrespectful or coercive; you do not owe everyone unlimited access to your work or attention. Safety, professional requirements and factual corrections deserve particular priority.

One useful next step

Take one recent comment and rewrite it as a question about a reader’s experience. Decide on a small test and what evidence would make it worthwhile.

A four-column feedback tracker

Observation: what did the reviewer actually experience?
Interpretation: what problem might explain that observation?
Decision: change, test, clarify or decline the suggestion?
Evidence: how will I know whether the response helped?

When two reviewers disagree

One reader says an introduction is too short; another wants it shorter. Instead of adding and removing sentences at random, identify the intended audience and the question they need answered. Test whether readers can find the main point quickly, then decide whether additional context belongs in a separate section.

Must I accept feedback from someone more senior?

Professional instructions and legitimate requirements matter, but it is still useful to clarify the underlying goal. Ask respectfully what outcome the proposed change should achieve. When a suggestion conflicts with accuracy, safety or the audience’s needs, raise the concern with evidence rather than treating every preference as equally binding.

Decision Compass can help compare competing changes against the project’s real priorities.