3. Enterprise DevOps: Context is King Nigel was manning a booth at an internal DevOps it is very easy, and dangerous, for DevOps adoption to conference, and this conversation transpired: become synonymous with the rollout of automation via a set of tools. Automation is key, but it’s certainly not NIGEL: the sole task and a monomaniacal focus on tool adoption “So, how can I help you?” introduces many risks. TECHNOLOGIST: “I need all the DevOps tools.” One of the key aims of DevOps is the delivery of NIGEL: consumable content to the business more rapidly. As “Why do you need all the tools?” such, the product backlog will be more dynamic and TECHNOLOGIST: the need to be in communication with the business is “My manager has put it in our objectives to adopt increased. It is critical that the technologist understands all the DevOps tools by the end of this quarter.” their product from a business perspective as that will drive value from your investment. Nigel knew he had a communications issue; whenever targeting a mass market, his message needed to be One of the key concepts that can be used when talking simple. He also knew he had an issue about nuance to technicians is the Gartner Pace Layer principle. This and context. is not new or radical, but we believe it is very useful as a means of introducing context into discussions. We now have two issues that need to be addressed. In this section, we’ll concentrate on the criticality of contextual knowledge. In a technology company 6.