LEARN. PRACTICE. GROW.Prepare the conversation and allow correction
A comment such as “you are disorganized” does not identify a task the person can improve. In a fictional example, yesterday’s update lacked an owner and deadline, so the team interrupted work to confirm them. This observation supports discussing context and effect. It does not prove a permanent personal characteristic. Bring the example and ask what happened before concluding its cause. If history shows the information was included and removed later, acknowledge the attribution error and correct the record. The operational omission still deserves analysis, but individual feedback should follow facts. In a three-month review, gather examples across the period and consider agreed criteria. The latest error can matter without representing the entire contribution. Keep individual information in a channel appropriate to its use. A lead should be able to revise an interpretation when stronger evidence appears.
Choose between instruction, exploration, and follow-up
A person who has never seen the procedure may need initial instruction. Asking only open questions does not provide information they do not yet possess. After showing an example, ask them to explain the next step and identify questions. In another case, the colleague already knows the procedure but always asks the senior engineer to decide. Explore the blocking point and alternatives they can assess. Do not use a question merely to disguise a solution already chosen. At the conversation’s end, “I will communicate better” needs to become a concrete action: present status, ownership, and deadline in an agreed handover, then review the result with the colleague. Support should respect the mandate. Coordinating tasks permits discussion of facts and difficulties; it does not automatically give the Team Lead formal assessment or career decisions.
Create opportunity and observe application
The objective “improve facilitation” can become a bounded part of a risk meeting with preparation, support, and observation. Completing a course is a useful activity, but alone does not establish that the person can facilitate discussion. Confirm the practice opportunity and the observer’s time. If three sessions are canceled to cover incidents, record missing opportunity instead of rating three failed attempts. Do not mark the skill acquired to compensate for cancellations either. Renegotiate capacity or find a comparable task. If the project disappears, update the plan while retaining its connection to the person’s objective. Observation can check whether they clarified the decision, involved relevant participants, and recorded understood actions. A supervised demonstration supplies evidence within that scope; it does not guarantee autonomous performance in every future meeting. Agree a realistic next application instead of treating development as a completed document.
Feedback rehearsal with new facts
Organize a 30-minute rehearsal with a lead, colleague, and observer. During the first five minutes, the lead receives a final handover missing a contact and prepares the conversation. During the next ten, the colleague presents history showing the contact in her version; observe whether the lead revises attribution. Reserve ten minutes to agree a practice objective and introduce cancellation of the opportunity for support work. Use the final five for debrief. Each participant produces a corrected factual note and short plan containing task, support, opportunity, and observation. The rubric uses three states: not observed, observed with help, and observed in rehearsal without help. Assess listening, factual correction, action clarity, and mandate boundaries separately. Do not add the states to produce a certification. The guide was authored, but no session with human participants has occurred; no individual rehearsal results exist.
Factual note: contact present in initial version; absent after consolidation.
Previous interpretation: attributed omission to the colleague; corrected after checking history.
Proposed practice: facilitate the opening of a supervised risk meeting.
Support: advance agenda review and an observer during the session.
Evidence: decision clarified, participants heard, and actions understood.
Status: practice not yet performed; no formal assessment assigned.The colleague shows a version containing the contact. The lead responds: “I attributed an omission to you that the history does not support. I will correct the note and investigate where the information was lost.”
Common pitfalls
Label instead of observation; latest event treated as the whole assessment; questions without needed instruction; completed training treated as guaranteed capability.
Related topics: Individual conversations · Delegation and learning
Facts can correct feedback; development needs opportunity, practice, and observation within a clear scope.
Reference: Guidance on feedback · Atlassian Team Playbook, GitLab leadership handbook, Google SRE, Kanban Guide May2025 and DORA five-metric model; inspected 2026-10-01