In product and tech teams, feedback is not optional. It is fuel for improvement. How you give it determines whether it accelerates progress or shuts it down.

Here is the framework I use when giving feedback to designers, developers, and product teams:

1. Be Positive

Acknowledge the work and effort that went into the project. Even if something is not quite right, start with what is working. Positivity sets the tone for collaboration and keeps people open to change.

2. Be Specific

Avoid vague comments like “It needs work.” Instead, point to concrete examples, identify the exact issue, and offer actionable suggestions.

3. Be Objective

Base your feedback on data, research, and user needs, not personal preferences. This keeps the conversation focused on the work rather than the person.

4. Be Constructive

Feedback should be a roadmap, not a roadblock. Use your expertise and experience to suggest next steps or alternative solutions that move the project forward.

As Frank A. Clark once said:

“Criticism, like rain, should be gentle enough to nourish a man’s growth without destroying his roots.”

Good feedback builds trust, strengthens teams, and results in better products. The goal is not just to point out what is wrong, but to help make it right.