The Art of Feedback: Conversations That Improve Decisions

There is a moment familiar to many professionals. You spend days or weeks working on a solution: researching the problem, analyzing scenarios, refining details, and considering constraints. Finally, you present the result to the team and hear:

"I don't like this approach."
"I would have done it differently."
"Something feels off here."

Sometimes these comments contain an important signal. But often they leave more questions than answers. What exactly is not working? Why does it matter? What direction should be explored next?

Without this clarity, discussions quickly turn into an exchange of subjective opinions, where everyone defends their own perspective and the team loses the opportunity to improve the solution.

At the same time, high-quality feedback is one of the strongest tools for team development. It allows teams to validate decisions earlier, identify risks before implementation, and leverage the expertise of different specialists. But for feedback to be effective, it needs to be treated not as an evaluation of a person's work, but as part of the process of creating a stronger solution.

In mature teams, feedback is not a final review before launch. It is a working tool that helps analyze ideas, identify risks, and improve solutions throughout the process.

Researchers Robert Bing-You and his colleagues described this process through the metaphor of "The Feedback Tango." They showed that effective feedback requires participation from both sides: the person giving feedback and the person receiving it. Responsibility is shared between participants.

The person giving feedback is responsible for the quality of their observation: whether the comment is clear, connected to the goal, and helps move the work forward. The person receiving feedback is responsible for analyzing the information: understanding which signals are valuable, which are supported by evidence, and which are simply personal preferences.

This is what separates professional discussion from a simple exchange of opinions.

Every decision is created within a specific context. Before evaluating someone's work, it is important to understand:

• The problemWhat problem the team is trying to solve.
• The userWho the work is ultimately for.
• The goalsWhat outcomes the project is aiming to achieve.
• The constraintsWhat limitations influenced the decision.
• The stageWhat point the work is currently at.

Without this context, even well-intentioned feedback can become irrelevant.

One sign of a mature professional is understanding what type of feedback will be most valuable at a particular moment.

At early stages of work, the most valuable questions are about direction: Does this solve the actual problem? Is the logic of the scenario clear? Are there stronger alternatives?

When a solution is close to implementation, the focus shifts toward identifying specific risks: critical errors, unclear states, interaction issues, and technical constraints.

The same comment can help a team at one stage and create unnecessary confusion at another. That is why effective feedback considers not only the content of the work, but also its current state.

Teams often face a conflict between wanting to support a colleague and needing to communicate a difficult truth. Sometimes it feels easier to avoid a challenging conversation than to raise a concern. However, avoiding problems rarely helps people grow.

In Radical Candor, Kim Scott describes the concept of Ruinous Empathy — a situation where the desire to avoid discomfort results in withholding necessary honesty.

Constructive feedback should not be harsh. Its purpose is not to point out someone's failure, but to help improve the outcome.

The hardest feedback to act on is feedback that cannot be applied. Comments like "I don't like it" or "this doesn't work" do not help the author understand what needs to change or why.

Useful feedback should connect an observation with a possible improvement:

• WhatWhat specifically raises a concern.
• WhyWhy it might be a problem.
• Where nextWhat aspect of the solution should be reconsidered.

At the same time, good feedback does not always provide a ready-made answer. Sometimes the most valuable contribution is asking the right question — one that helps the team explore the problem more deeply.

High-quality feedback rarely appears in a format like "Take a look and tell me what you think." This type of request is too broad.

Before a review, it is important to define what exactly needs to be evaluated, which questions matter most, and what level of detail is needed at this stage.

For example

• Early concept"I want to understand whether the logic of the scenario aligns with the user's goal."
• Final review"I need a critical perspective: are there any obvious issues before launch?"

The clearer the request, the more useful the feedback will be.

Receiving feedback requires no less maturity than giving it. The first instinct is often to explain why a decision was made a certain way. That is natural — the author knows the full context and the effort behind the work. But sometimes a defensive reaction prevents us from hearing an important signal.

It is useful to separate two things: I created the solution, and I am not the solution. Every piece of work is a hypothesis that can be improved.

A strong professional does not try to defend every detail. They evaluate what can make the outcome stronger.

After a review, teams often receive many different opinions. They may contradict each other because every participant views the solution from their own perspective.

The goal is not to implement every suggestion. The goal is to identify recurring signals:

• RepetitionMultiple people notice the same issue.
• RelevanceThe comment is connected to a user goal.
• EvidenceThe observation is supported by data.
• ImpactThe problem affects a key scenario.

Sometimes the best outcome of a discussion is changing the solution. Sometimes it is consciously keeping it as it is, while understanding the reasoning behind that decision.

The ability to give and receive feedback does not appear automatically. Teams need to build habits:

• Discuss earlierBring solutions to the table before they are finished.
• Ask more precise questionsDefine what a review should focus on.
• Explain the reasoningMake the thinking behind comments visible.
• Treat critique as creationSee it as part of the process, not a verdict.

Strong teams are not defined by the absence of disagreement. They are defined by their ability to use different perspectives to improve the outcome.

Ultimately, good feedback is not about finding mistakes. It is a way to expand the team's collective thinking and create solutions that would not have been possible through individual work alone.

• Robert Bing-You et al. The Feedback Tango: An Integrative Review and Analysis of the Content of the Teacher–Learner Feedback Exchange, Academic Medicine.
• Kim Scott. Radical Candor: Be a Kick-Ass Boss Without Losing Your Humanity.
• Ken Blanchard. All of us are smarter than any of us.