Introduction
If you work in IT, you have probably met Scrum or Agile. Even if not, the sprint rhythm is a useful frame for **when and how** to exchange feedback well.
A sprint is usually one or two weeks. The team plans documented tasks, works through them, and holds daily stand-ups: what I did, what I will do, where I am blocked.
At sprint end, many teams run a **demo** (show work) and a **retro** (reflect on process). The retro is prime time for feedback—about the work and about how people worked together.
Team building and psychological safety
A lot can happen in two weeks. In web development, time compresses; taking care of the team's mental and emotional bandwidth matters.
Constructive feedback works best in **psychological safety**—Edmondson's term for a climate where people can take interpersonal risks: share ideas, ask questions, and admit mistakes without fear of punishment or humiliation. That climate speeds knowledge exchange, especially when experience levels differ.
What people share in a retro
Typical retro prompts:
• What went well this sprint?
• What did not go well?
• What should we keep doing?
• What should we improve?
Efficient teams also name **individual contributions**: Adam solved a hard problem under pressure—that reinforces behaviour others can copy.
In a safe environment, there is also room for constructive criticism. If Anna's nitpicks slow delivery, naming that pattern—without attacking her character—can help the whole team. The receiver needs room to separate **self from behaviour**; that is a skill, not a given.
Perspective before conclusion
The hardest, highest-leverage step: switch perspective before you conclude.
Why is Anna nitpicking? Low self-esteem and competition? High quality standards? Fear of blame? Slow down, observe, and talk. We are all human, mostly trying to improve.
With that frame, feedback lands more accurately. If someone is "difficult to work with," ask the **5 W's and H** (who, what, when, where, why, how). Sometimes the reporter lacks skills to navigate the situation—not only the other person lacks cooperation.
Conclusions
Resist jumping to conclusions. You will never know every detail, but gathering perspectives beats single-story certainty.
Feedback reveals something about the **giver** too—needs, strengths, blind spots. Thoughtful feedback signals commitment to a safer team climate.
When you understand why someone acts as they do, feedback becomes a tool for trust and performance—not just correction.
Effective feedback is not only "what went well / what failed." It is building a place where people can contribute, learn, and grow—knowing we are all figuring life out as we go.
Empatalk helps teams map communication preferences before feedback becomes personal. Start at empatalk.app/survey.
Soft Skills series
Part 2 of 32. Read more on the Empatalk blog or take the Communication DNA survey at empatalk.app/survey.
Sources and further reading
• Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly. https://doi.org/10.2307/2666999
• Brown, P., & Levinson, S.C. (1987). Politeness: Some Universals in Language Usage. Cambridge University Press. https://doi.org/10.1017/CBO9780511813085