Skip to main content

Change is scary or is it?

DevOps is about continuous improvement.  Sometimes changes are easy and everyone loves them.  You implement them quickly and everyone is happy.  Sometimes people hate the change and it dies.  Most of the time it is a combination of fans, skeptics and who cares.
How should you present changes you are passionate about?  Here are some steps to successfully proposing changes.

1. Start with the goals your are trying to achieve.  Unless your goals are way off base, people usually can't argue with goals that make the future better.
2. Present solutions to the goals as a "recommendation".  Who knows, someone may have a better idea or improvement in your change.
3. Draw a picture, workflow, diagram or something that you can show people.
4. Watch your audience to see who is getting your message and who are not.
5.  Ask who understands the resolution.  Don't ask if anyone has questions or who doesn't get it.  Ask a question that makes people get involved.
6.  Finally ask for feedback, ask if anyone else needs to provide input and what are next steps.

Now the fun part.  If you want to build up credibility, you need to quickly implement the changes so everyone sees you are serious.

Comments

Post a Comment

Popular posts from this blog

2020 State of DevSecOps by Accurics

 This is an excellent report for all IT Pros and Engineers.   Highlights: Storage is most impacted solution Open security groups or network configuration Secrets are not so secret Unused resources are not secure. Take a look at these.  Look again.  These are not highly skilled problems.  They just need guidelines and proactive management.  The article uses policy as code as a solution for many of the problems.  I will drill into each of these more in the future.  I wanted to get the awareness out first and then, come back to solutions.  
Post a Comment
Read more

Learn Anti-Leadership from Basecamp

 There are many different articles out there and Twitter comments about the Basecamp drama.  I am not going to post any here because it might seem biased depending on the article.  Google them yourself.  In short, Basecamp made a policy to not allow political discussions at work.  Coinbase did this previously too and applauded Basecamp for it.   Apparently, for years there has been a list of funny customer names at floating around Basecamp.  This list or even the knowledge that Basecamp had a list, was disturbing to some employees.  Also, some employees tried to start a Diversity and Inclusion practice.  Despite how much the founders of Basecamp promoted DI, they didn't feel they were being taken serious.  They felt the company was only about the founders and not about employees.    If this isn't enough, the founders debated and even called out employees for their comments regarding the topics, publicly.  This is my s...
Post a Comment
Read more

Cloud Ops: The New IT for the Cloud Era

Over the past few months of interviewing and researching dozens of companies—particularly small to mid-sized SaaS businesses—one pattern keeps emerging: the desire to stand up a Cloud Operations (Cloud Ops) organization. It makes sense on the surface. Cloud is now the infrastructure of choice, so naturally, someone needs to “own” it. But what’s unfolding in practice often misses the mark. Many companies are attempting to solve growing cloud complexity by taking all their DevOps, SRE, and platform engineering talent and consolidating them into a Cloud Ops team. The idea? Share them across product teams so no one gets overwhelmed. If that sounds familiar, it should. It’s the same centralization tactic used by traditional IT for decades. And it's creating the same problems. When Cloud Ops Becomes Old IT in Disguise Here’s the playbook we’re seeing: Move DevOps, SRE, and Ops into a central Cloud Ops team. Let them handle infrastructure, CI/CD, monitoring, and cloud securit...
Post a Comment
Read more