Not Everyone Gets It

A Series on Beginning DevOps /part three

“short-coated white and brown dog” by Agatha on Unsplash

Be Prepared to Repeat Yourself

Saying it once doesn’t mean anything. Sometimes saying it twice doesn’t mean anything. It’s okay: the concepts that you’re talking about can be hard to comprehend, and it takes time. Be patient.

Be Collaborative, But Don’t Be Afraid to Call Bullshit

I’m really not a big fan of the words “troublemaker”, or “luddite”, and it’s going to be your responsibility to prove yourself that this transition is worthwhile. You can even recommend that people go to related conferences like Velocity, local DevOps Days, or your regional DevOps Enterprise Summit. At some point, though, it’s important to work with them on the root of their concerns and have difficult conversations.

Build Trust

Trust doesn’t usually come overnight. Some people have a high default level of trust, and will go along with what you’re saying, others will not. Some of this is about conversation and understanding each other’s perspectives, but it may be that you can truly only gain trust as you start to deliver on promises, and people see the fruits of the transition first hand.

Bring the Organization With You

Really, just communicate. Make sure that the company leadership understands what you’re doing, and make sure that you’re announcing and celebrating wins as broadly as you can as they come about. This is something that I wish I’d done far more extensively.

Be Multi-Modal

People ingest ideas differently. Research suggests that there are a number of distinct modes of learning, such as Visual (what you see), Textual (what you read), Linguistic (language), Spatial (what you experience), Gestural (visible body actions), and Aural (what you hear).

Express Empathy

There are people whose lives will be impacted positively from day one, but there are also those whose careers will be called into question as they realize that their job is changing, that they may not be as integral to the software delivery workflow as they are today.

Shared Responsibility

As developers begin to use the tooling, they will make mistakes.

Zero Unicorns Killed

This transformation isn’t magic, but it’s easy to see it that way. There are a lot of things that a cultural transition to DevOps won’t give your organization, for example:

  • Availability is typically significantly higher, but going multi-region won’t come for free
  • It’s possible to standardize the way that some logs and metrics are generated and collected, but thought still needs to be put int application telemetry and observability
  • Poor design and architectural decisions will still be poor design and architectural decisions, as will poorly implemented code

Software and Technology Nerd, DevOps Ninja, Maker of Things, Aerospace Enthusiast.