Set context: two quarters of delayed deliverables and frustrated stakeholders. Practice naming concrete misses, exploring root causes, and aligning on forecasting standards that protect credibility. Avoid moralizing. Replace Why are you unreliable with What obstacles are we underestimating and How shall we signal risk earlier. Finish with timelines, check-ins, and shared dashboards. In debriefs, capture phrasing that upheld respect while restoring reliability, because consistency fuels trust and allows creativity to flourish without collateral damage.
High performers may resist feedback when identity feels threatened. Craft a scenario where code quality dazzles but collaboration frays. Practice acknowledging excellence, then connecting specific behaviors to team friction and delivery risk. Invite the employee’s lens on trade-offs, and co-create norms that protect both velocity and partnership. Avoid hero narratives that excuse harm. Role-plays reveal language that honors mastery while insisting on collective standards, turning lone brilliance into shared momentum that compounds week after week.