LEARN. PRACTICE. GROW.Concept and mechanism
Useful feedback describes a situation, observable behavior, and its effect while allowing the other person to explain context. Avoid turning one event into a claim about personality or intent. An individual conversation should cover difficulties, development, and support as well as task status. Agree an agenda and record relevant actions with appropriate access; personal performance information should not be published on a general board. Frequency and format depend on role and needs. If the Team Lead lacks a formal people-management mandate, they can support collaboration and involve the appropriate owner in decisions beyond their scope.
Guided application
In a fictional scenario, a shift handover omitted a pending request and the next team repeated work. Instead of saying the colleague never communicates, describe the event and effect and ask what made handover difficult. The response may reveal an ambiguous field, an interruption, or an unagreed expectation. Define a concrete improvement and check its result in another handover. When two people disagree, hear both and distinguish facts from interpretations before seeking agreement. Making room for questions does not remove accountability for commitments; it helps reveal problems early and agree proportionate support, correction, and follow-up.
A request omitted from a handover is an observation; saying someone does not care is an interpretation.
Common pitfalls
Personal labels; assumed intentions; conversations only about tickets; sensitive feedback on a public board.
Related topics: Mandate, responsibilities, and agreements · Capacity, priorities, and flow · Delegation and development
Explain the observed effect, hear context, and agree a verifiable change.
Reference: Guidance on feedback · Atlassian Team Playbook, GitLab leadership handbook, Google SRE, Kanban Guide May2025 and DORA five-metric model; inspected 2026-10-01