Opening with strengths and observed contributions created psychological safety. Then, the manager described specific incidents by date and channel, linked to downstream effects on delivery and teammates. The conversation ended with choices, support options, and visible checkpoints, signaling respect for autonomy alongside clear accountability and measurable progress.
In a one‑to‑one, the manager listened for values under the edge: fear of slipping standards, frustration with rework, desire for recognition. Reflecting these back softened posture. Together they tested pairing sessions and clearer acceptance criteria, which lowered friction without dulling the engineer’s creative intensity.
Day one, identify a lingering conflict; day two, map interests; day three, script questions; day four, test reframes; day five, practice a pause; day six, design follow‑ups; day seven, reflect publicly. Repetition builds confidence, while visibility invites allies and mentoring relationships.
Share your plan with a trusted senior colleague and ask for red‑team questions. Clarify where you might overreact. Agree on a debrief cadence and escalation pathway. Knowing you are not alone reduces anxiety, enabling bolder empathy and steadier judgment under pressure.
Post a short reflection on what worked, what surprised you, and what remains hard. Ask readers for parallel experiences and practical scripts. Your vulnerability normalizes learning in public, builds connections across disciplines, and keeps valuable wisdom circulating where emerging leaders can find it.