DOES20

You don't. If you're starting with a position that you want others to "buy into", you've already lost. If you want someone to change, you have to make it *there* idea.

Have them read the Accelerate State of DevOps report and furnish them with a handout of the financial figures of the respondents. “That’s what they do. This is how they’re winning.” Really have them read it though, stand by their shoulder. Sending links won’t do!

Convince them with real use cases! Living examples of other enterprises doing great transformations works the best!

All leaders (and humans!) want to know what's in it for them and the business. Now that we've got great stuff like Accelerate, that's not hard to do!

I've had the most success with the "roadshow" : meeting the members of the senior leadership team in 1on1 settings. You are more likely to be able to target your pitch to their individual interests and questions, and you can often get more candid feedback this way.

by focusing on business problems with the transformation as the means, not the end.

@jon_moore I'm so excited that you're sharing your philosophies about the role of the Chief Architect at #does20 — it's fascinating for me to see the spectrum of "gentle nudge" to "everyone must."

I don't see buy in as a huge challenge (who doesn't want move value, cheaper, better, faster). It's the lean in that leaders need to do, their words, actions, etc., to champion and support the change throughout the org thats a bit harder.

helping leaders understand how their role and approach needs to change will help with the lean in..

Small and quick wins might get you some interest from sponsoring parties, however when it comes to bigger changes and sustained efforts, it'll be easier if you find a strong champion that is already promoting other isolated initiatives to solve the issues that DevOps addresses

Ji everyone

Glad to be here!

@realMattKParker glad to have you!

@Ben_Grinnell hey Ben!