This is good feedback that ideally, Amazonians should read and reflect on but I worry the machine is too big at the moment for anyone there to care. Would take a big event and a reset for things to change.
My time at Amazon made me realize that while LPs probably were written with the best intent during their inception, in practice in the more recent years, it ended up often misinterpreted and weaponized internally for personal gains or to speed things up to meet unrealistic deadlines and false promises. "Disagree and commit", "Bias for Action" were popular amongst some of the management I knew.
There are very detailed internal wiki pages written with examples on the right ways to interpret them but I doubt many bothered to go through all that beyond the material presented during onboarding — which is also not always completed. It was frustrating to see LPs overused by employees in every meeting, document and discussions without much thought as to what they were meant to convey.
That said, there were a _handful_ of teams and individuals I met who exemplified these but it was a rare occurrence during my time unfortunately. And even in the moments where someone went above and beyond w.r.t channeling the LPs and the internal process to bring forth a proposal (e.g. famous corp-wide one was the push against RTO), I saw them get shot down unceremoniously while low-effort work and planning with a dusting of LPs got the go-ahead.
I hence echo what a few folk here have already said — don't always expect the work environment to reflect the values and principles you read on the about page. Reality is often (sadly) disappointing.
I wonder if overall team size has something to do with how the principles are dealt with? Mobile Shopping is huge. Some teams are tiny, experiencing massive growth or winding down. If a team has a super mature code base or market, and the team feels like they are caretakes as opposed to innovators, how does that impact them? How can it really always be Day One?