On Fri, Oct 26, 2012 at 9:54 AM, Mark McCullough <[email protected]> wrote: > > > The time to change things is not when you have made the mistake, but when > there is no serious mistake under review, or if there is, something for > someone not in your team. Then you aren't seen as protecting your team when > pushing for the change. >
I agree with this. Yes, if there is already a blameless culture, it's much easier to own a mistake. In terms of helping to create that culture, timing is definitely everything. I track all maintenance events and outages as they are scheduled/occur. I then regularly present them to my team and boss. I do this to reinforce a feedback loop for both the bad and the good times. In other words, I want everyone to know how many outages we've had and how many controlled maintenance events we've had. We perform and present postmortem analyses for outages. We also write and present design documents for projects and maintenance plans for upgrade/install events. Doing this __consistently__ builds a level of trust and confidence that facilitates creating/maintaining a blameless culture. Otherwise, it won't happen. It takes time, but like all good things, the effort is worth it. > Mark McCullough > [email protected] > -- Twitter: @Ryan_Frantz Blog: http://www.ryanfrantz.com _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
