I thought it was pretty straight forward, nothing groundbreaking for anyone who already had a good understanding of this "stack", which I don't see as a stack,

I thought it was pretty straight forward, nothing groundbreaking for anyone who already had a good understanding of this "stack", which I don't see as a stack, more of a organization/management framework that has been used for many years, and lectured in many degrees. The thing is that a lot of people always thought much of this business "fluff" was there just to justify some obsolete positions and tasks, like: vision and mission statements... that's not for the cool cats - those are wandering and then make a blog post like they made some amazing finding and try to give it a catchy name, but when you squeeze it you find out it's just something some dude in the 60's already defined/coined that thing, that you learned about 10 years ago. And then they try to mash everything into product strategy...which is also the business strategy...which is not even a strategy when you peal it off. So the article serves it's purpose, for people who never learned any of this, or for those who took it for granted/overvalued, or those who simply got it wrong from the start. No shame in any of this.