{"id":555,"date":"2022-04-26T21:18:03","date_gmt":"2022-04-26T11:18:03","guid":{"rendered":"https:\/\/sysmit.com\/cf22\/?p=555"},"modified":"2023-12-13T15:28:02","modified_gmt":"2023-12-13T05:28:02","slug":"googles-site-reliability-engineering-hierarchy-remixed","status":"publish","type":"post","link":"https:\/\/sysmit.com\/cf22\/googles-site-reliability-engineering-hierarchy-remixed\/","title":{"rendered":"Review of Google’s Site Reliability Engineering Hierarchy"},"content":{"rendered":"\n
Google’s book on SRE, Site Reliability Engineering <\/em>(2016), has captured wide acclaim in the software operations world. <\/p>\n\n\n\n One of the most discussed aspects in SRE circles about the book is its SRE hierarchy. The hierarchy has merit, but it’s also flawed in a way that would prevent you from educating people about SRE. <\/p>\n\n\n\n I’ll get into this flaw later in the article. <\/p>\n\n\n\n First, let’s see this hierarchy. Looks more like a pyramid, right?<\/p>\n\n\n\n That’s why I call it the SRE pyramid. The ‘hierarchy’ term is used because it plays on Maslow’s hierarchy of needs<\/strong>, also visualized as a pyramid.<\/p>\n\n\n\n This article will analyze the different layers in the pyramid. <\/p>\n\n\n\n I have visually remixed the pyramid into a pathway map with the hope that it’s easier to unpack and explain each layer’s properties. Here’s a quick peek at the visual remix:<\/p>\n\n\n\n Before I analyze further, let’s cover background information on the SRE book’s hierarchy design choice…<\/p>\n\n\n As I mentioned earlier, Maslow’s hierarchy of needs<\/em> inspires the design of the SRE hierarchy. I will assume you have no knowledge of the former. Let’s see what it looks like:<\/p>\n\n\n\n You may be able to tell that Maslow’s hierarchy is grounded in behavioral psychology. Let’s explore this hierarchy because it will help us understand Google’s SRE hierarchy better:<\/p>\n\n\n\n Maybe now, you can make better sense of the design function of Google’s SRE This is where the hierarchy’s design flaw sets in.<\/p>\n\n\n\n Remember that some stakeholders control the budget and organizational capacity of your SRE efforts. People like executive sponsors and upper management. <\/p>\n\n\n\n My experience shows that people like these want a straight answer. “Don’t make me think<\/em>“.<\/p>\n\n\n\n Many non-technical stakeholders will not admit it, but the pyramid formation will not make much sense to them<\/strong>. I’ve tested this out in real world conversations. People will not be named!<\/p>\n\n\n\n For example, I learned that some senior leaders <\/strong>looked at the hierarchy and interpreted capacity planning as more urgent and important than incident response<\/strong>. <\/p>\n\n\n\n Here’s the SRE hierarchy once again for quick reference:<\/p>\n\n\n\n Seeing that capacity planning was higher in the pyramid than incident response, their interest then prioritized that aspect rather than paying for on-call engineers. <\/p>\n\n\n\n In most situations, incident response is an earlier and more fundamental need in software operations than setting more resources on capacity planning. <\/p>\n\n\n\n See the problem with a misinterpreted “hierarchy”?<\/p>\n\n\n\n The seminal book on change management, Switch<\/em> by Dan and Chip Heath, highlights how a pyramid shape hierarchy needs to be more clearly defined to make sense.<\/p>\n\n\n\n The problem with the pyramid? Only a [qualified person] could look at it and determine what a person should be [doing] on a day-to-day basis.<\/p>\nfrom Switch by Chip and Dan Heath <\/cite><\/blockquote>\n\n\n\n I’ve changed the terminology in the quote from [nutritionist] and [eating] to emphasize the general problem with the pyramid, of which the book goes into deep detail. <\/p>\n\n\n\n\n\n What’s Chip and Dan’s suggestion for a more impactful way to drive change and action? <\/p>\n\n\n\n A clear visual picture.<\/p>\n\n\n\n In a Forbes interview, the interviewer noted a key message that Chip Heath repeated several times:<\/p>\n\n\n\n Throughout our interview, Chip used the word \u201cpicture\u201d nearly a dozen times. And I realized how easy it is to visualize a group of doctors talking, rather than just writing in a medical chart. <\/p>\n‘Decisive’ Author Chip Heath On Doctors, Diets And The Dangers Of Overconfidence<\/a> by Robert Pearl MD<\/cite><\/blockquote>\n\n\n\n<\/figure>\n\n\n\n
An explainer of the “hierarchy” design<\/h2>\n\n\n
\n
pyramid<\/s> hierarchy. But you may not have the luxury of explaining it like this to your peers.<\/p>\n\n\n\n\n
\n