I've also consulted and worked with a few different orgs, over the past 5 years, and have been pleasantly surprised to see that COE culture has spread. There are orgs that don't know what "P90" means when we talk about latency, and think "multi-AZ" means we need to run a second datacenter in Arizona. But they recognize the value of a good RCA (root cause analysis) process, and have document templates with a very familiar structure (the "five whys" and "lessons learned" etc).
(RCA, root cause analysis, seems to be the consensus acronym -- I think most folks outside of the Amazon universe interpret COE as "center of excellence".)
Thanks Shawn! I knew there was another name I was forgetting. I updated my draft post about COE's with that nomenclature. I wrote up some thoughts about how to make things a little easier on oneself while filling out such docs. But I'm waiting a week or so to post it - after I get this Star Wars stuff out of my system. ;-)
I've also consulted and worked with a few different orgs, over the past 5 years, and have been pleasantly surprised to see that COE culture has spread. There are orgs that don't know what "P90" means when we talk about latency, and think "multi-AZ" means we need to run a second datacenter in Arizona. But they recognize the value of a good RCA (root cause analysis) process, and have document templates with a very familiar structure (the "five whys" and "lessons learned" etc).
(RCA, root cause analysis, seems to be the consensus acronym -- I think most folks outside of the Amazon universe interpret COE as "center of excellence".)
Thanks Shawn! I knew there was another name I was forgetting. I updated my draft post about COE's with that nomenclature. I wrote up some thoughts about how to make things a little easier on oneself while filling out such docs. But I'm waiting a week or so to post it - after I get this Star Wars stuff out of my system. ;-)