Excuses for bad spelling! Seems my spellchecker made things worse than I really am 🙂 (coming from Germany).

cc: @rdaitzman

I don't have one straightforward answer to this, because it continues to be a challenge even today. Early evangelism efforts were focused around the long-term benefits, and we did our best to roll-out the DevOps approach iteratively so that we could demonstrate small successes and build a better business case. For example, we brought applications on to the private cloud microservice platform really slowly at first, just a few teams at a time. After overcoming the initial learning curve, the deployment frequency of those teams skyrocketed, and developer productivity was up. By the time we were halfway through rollout of the microservice platform, leaders were practically begging to have their teams be part of the next wave.

Will try to adopt this (find small areas where you can show success and then take the next step)! Seems you did a pretty good job there! Congrats!🎉

I would add that we have a key role in this journey as story tellers and explorers. So framing the steps forward as bets or experiments and gathering data about the before and after is very impactful. Obviously avoid baselining for months at the cost of progress, but a combination of the human and cultural narrative and as much data as possible is a powerful tool to gain trust and build momentum

Agree with @ben.dodd that being able to frame out the story as a journey you're on is invaluable to help manage expectations. This is also a situation where having technical engineering managers who have lived it also are so important 😃

A marketing / sales hat of some size that you can put on every now and then is going to be important...to the extent that some basic training in sales / marketing / negotiation isn't a bad investment

I also remember doing 2 days training with https://www.amazon.co.uk/Donald-G-Reinertsen/e/B001H6UEJS/ref=dp_byline_cont_book_1 and he saying that his first port of call was with finance & the FD. I also had this experience at a global financial organisation, in that because DevOps spans OpEx and CapEx and challenges the financial models organisations use, at some point someone is going to have to understand / interact with that part of the business when thinking about planning / finances / outputs / targets / throughput