This message was deleted.
# general
s
This message was deleted.
s
My primary thought is that there are three important take-aways from this. 1. You are more likely to be using Platform Engineering if you are in the high-performance group 2. 35% of the high performance group don't use Platform Engineering 3. Platform Engineering didn't stop 40% of organizations falling into the lower performance group Why is this interesting? Because it tells us that just like all previous ideas, Platform Engineering isn't a panacea. This isn't good or bad news, it's neutral. We need to add experience onto this... in the right circumstances, Platform Engineering really unlocks performance. It is likely to benefit situations where there is a need to scale, or a level of necessary complexity that is adding cognitive overload to a team. Instead of solving it by trying to remove the work from the team (the traditional approach) it simplifies the surface area to allow the team to continue to own the whole thing.
h
Also without the cultural change component that devops brings platform engineering only gets you so far