<commit_before>---
layout: post
title: "Part 3 - You can’t buy DevOps, but you may need to sell it: Actions to spread DevOps Adoption"
type: post
author: <NAME>
excerpt: "In part 3 of the series, You can’t buy DevOps but you may need to sell it, we'll explore some of the actions to spread change."
title_tag_of_header: "Actions to spread DevOps Adoption | GoCD Blog"
meta_description: "This post explores ways to spread Devops adoption."
meta_keywords: "devops, what is devops, continuous delivery open source, convince your team to adopt devops, devops misconceptions, devops benefits"
summary_image: "/assets/images/blog/driving-change-devops/spreading-devops-adoption.jpg"
tags: Selling DevOps
---
<% content_for :banner do %>
<figure>
  <img src="/assets/images/blog/driving-change-devops/spreading-devops-adoption.jpg" alt="Part 3 - You can’t buy DevOps, but you may need to sell it: Spreading DevOps Adoption"/>
</figure>
<% end %>

This is part 3 of my blog series, ‘You can’t buy DevOps but you may need to sell it’. Previously, we looked at some ways to get buy-in on driving DevOps changes. In this post, we will explore some of actions to take to spread change. 
    
## **Actions to Spread Change**

At this point, you’ve convinced people to start learning more about DevOps and maybe even driving some change. But how do you go from simply sharing your ideas to getting other involved? Here are a few ways. <commit_msg>draft mode<commit_after>---
layout: post
title: "Part 3 - You can’t buy DevOps, but you may need to sell it: Actions to spread DevOps Adoption"
type: post
author: <NAME>
excerpt: "In part 3 of the series, You can’t buy DevOps but you may need to sell it, we'll explore some of the actions to spread change."
title_tag_of_header: "Actions to spread DevOps Adoption | GoCD Blog"
meta_description: "This post explores ways to spread Devops adoption."
meta_keywords: "devops, what is devops, continuous delivery open source, convince your team to adopt devops, devops misconceptions, devops benefits"
summary_image: "/assets/images/blog/driving-change-devops/spreading-devops-adoption.jpg"
tags: Selling DevOps
draft: true
---
<% content_for :banner do %>
<figure>
  <img src="/assets/images/blog/driving-change-devops/spreading-devops-adoption.jpg" alt="Part 3 - You can’t buy DevOps, but you may need to sell it: Spreading DevOps Adoption"/>
</figure>
<% end %>

This is part 3 of my blog series, ‘You can’t buy DevOps but you may need to sell it’. Previously, we looked at some ways to get buy-in on driving DevOps changes. In this post, we will explore some of actions to take to spread change. 
    
## **Actions to Spread Change**

At this point, you’ve convinced people to start learning more about DevOps and maybe even driving some change. But how do you go from simply sharing your ideas to getting other involved? Here are a few ways. 
{'fraction_non_alphanumeric': 0.0817391304347826, 'fraction_numerical': 0.002782608695652174, 'mean_word_length': 4.446969696969697, 'pattern_counts': {'":': 0, '<': 15, '<?xml version=': 0, '>': 15, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1695975', 'n_tokens_mistral': 855, 'n_tokens_neox': 810, 'n_words': 413}