Coach a strong contributor back into incident structure without shaming urgency or initiative.
Leo LE Staff engineer, moving fast outside the channel The tension Leo has already pushed one emergency config change without announcing it first. He thinks formal coordination is slowing the team down. You need his speed, but you also need incident command to remain real. solo changes outside shared visibility Sev 1 coordination cost is high key contributor you cannot alienate Redirect initiative into structure ICS is built on clear roles and common operating pictures. The coaching task is to channel urgency into that structure, not extinguish it. Bad pattern Either shame the person or let them freeload the command…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in