You wouldnt mention jaeger or istio either to decision makers.

You would say we can cut operational costs and modernize big data infrastructure while making our data warehouse more accessible(BigQuery). We can save money when APIs arent being used (Cloud Run). We can process real time data without increasing operational costs (Cloud Dataflow). We can debug systems failures faster (Stackdriver). We can launch products and iterate faster with a lightweight frontend team (Firebase). We can build conversational interfaces rapidly (Dialogflow).

You reword in terms of results rather than tools for decision makers. Of course this is all moot because you have to convince them google cloud wont shut down by 2023.

Most major decisions aren’t made by what is cheaper - it’s made by which is safer.

Making operations google’s problem is precisely what drives BigQuery, FaaS and Dataflow adoption. Its operationally safer when you dont need a hadoop team to maintain your data infrastructure.

See Nytimes, Twitter and Spotify for examples.

Now if you’re talking about future-safety there was an argument...until a few hours ago.

Again, you’re talking about what’s “operationally safer” not what’s “reputationally safer”. If AWS goes down, no one is going to question your decision - and you’re in the same boat as a lot of other people. If GCP goes down and everyone else is up, people are going to ask a million question.

Every company you named isn’t the same thing as just arguing to the powers that be - AWS is what Netflix uses. AWS has many more “referencable clients” that matter.