Disclaimer: I work for a small e-commerce firm named after a large river, opinions are my own. Writing in response since the company I work at is one whose values is quoted in the article.
My initial approach to the values was a similar "Who cares, these are bland corporatese" one. It wasn't until a 10+ year senior engineer on my team discussed the trade-offs between the values in an architecture meeting that I really understood the purpose. Take two of the values[1]:
"Dive deep" vs "Bias for action" - these have an inherent tension between the two. You can justify any action with either one, but it is about knowing when to apply what. You do not want to be Diving Deep as your first action when you are oncall and your alarms are going off in every direction, but it may need to be your third.
"Have Backbone; Disagree and Commit" has opposite ideas written into it! Having backbone is about being able to back up your position with as much data and research as you can. Disagree and Commit is about not being emotionally invested in your position and not taking things personally when the team chooses to go another way. It is recognizing the fact that you may be working in an area of ambiguity where no one side can be proven right before the fact.
Like most worthy things in life, there is a lot of nuance to these that cannot be expressed in a pithy 140 (or 280) character limit. But the idea that you should have "anti-values" is a very, very useful one. It allows you to think through different scenarios and explain what your team/organization/company would prioritize when there are competing priorities.
[1] - https://www.amazon.jobs/en-gb/principles
My initial approach to the values was a similar "Who cares, these are bland corporatese" one. It wasn't until a 10+ year senior engineer on my team discussed the trade-offs between the values in an architecture meeting that I really understood the purpose. Take two of the values[1]:
"Dive deep" vs "Bias for action" - these have an inherent tension between the two. You can justify any action with either one, but it is about knowing when to apply what. You do not want to be Diving Deep as your first action when you are oncall and your alarms are going off in every direction, but it may need to be your third.
"Have Backbone; Disagree and Commit" has opposite ideas written into it! Having backbone is about being able to back up your position with as much data and research as you can. Disagree and Commit is about not being emotionally invested in your position and not taking things personally when the team chooses to go another way. It is recognizing the fact that you may be working in an area of ambiguity where no one side can be proven right before the fact.
Like most worthy things in life, there is a lot of nuance to these that cannot be expressed in a pithy 140 (or 280) character limit. But the idea that you should have "anti-values" is a very, very useful one. It allows you to think through different scenarios and explain what your team/organization/company would prioritize when there are competing priorities.
[1] - https://www.amazon.jobs/en-gb/principles