nice post! I just read the first snti pattern, but I already have to reply 😀.
I think one problem is that product doesn’t understand the building blocks and doesn’t care about it. I see it in my org and we did it right in the beginning. Nowadays we do it imo wrong: during the phase of “platform as product” we had few but team based product management and now because of “money savings by reducing employees”, we have a generic product team. The product team does only understand the UI. Rest of it is black magic. I also don’t think that they care and they pushed everything on principal engineers, which is even worse.
I think nothing really serious comes from the product team. At least I only see buzz words with little understanding.

@sszuecs as a product manager, I can assure you that we do :) But every PM is different, indeed. You need to have a person who values the platform engineering and can turn it into a "product".

I don’t want to question that they care about the Platform.
I just don’t see they understand it.
Focusing only on integrating $whatever into backstage is not the right thing to do. I think the article says that, too.
And having a bit of understanding about statistics would be helpful. Not sure if this is a general problem, I see this also in engineering, but normally engineers seem more open to learn.
Sigh, sry for my half kind of a rant. 😊

@sszuecs no, I get it!