It'll be interesting to call back to that article in a year's time because, internally, that's not what I am seeing at all.
Customer-centricity? We're losing customers hand over fist because of pricing and an awful customer experience, the latter led by middle and upper management making bad decisions that directly impact the customer with respect to architecture, technology and even design decisions in the applications.
Outcome-orientation: just a buzzword for nonsense.
Empowered-leadership: No-one's empowered. Zulfi and Kamal's ego means that everyone's a "yes" person. They don't want to hear "no". They don't want bad survey results. Decisions are made to placate those two, not to benefit our customers or create better ways of working or improve internal morale, and this mindset is what's driving ev everything else.
Speed-thru-structure: We're pushing out code that's barely tested, defects are not being fixed because "speed" [of new code] is more important. Tech debt is unimportant. Release new functionality! More! More! Add new states! Add new products! Who cares if there are 1000 defects?
It all sounds good from the outside, but look closer and it really doesn't stack up. I can pick out any number of quotes from McKeown's article and prove it's nothing but rubbish. It's a puff piece, and I bet even he knows it.
But it's a published piece in Forbes, and I bet Zufli and Kamal fu--ing love it.