Conversation

Oh yes: I'm super super super excited to dig into Working Backwards. goodreads.com/book/show/5313 My one sentence pitch: it's the first book that describes how Amazon REALLY works internally, written by insiders who were in the room when the techniques were invented.
5
58
The most interesting thing about Amazon’s decentralised execution style is how different it is from, say, Apple’s, which is tightly coupled vertical teams. But Amazon’s business necessitates it; they are in more industries and in more product categories than Apple.
1
5
Amazon isn’t fully decoupled, of course: Some teams, like Payments, must be coupled (they see this as a necessary tax). The STL idea worked best with product dev teams (doesn’t apply to legal, retail, HR, etc) Transitioning to this model was painful as hell.
1
2
Quick update on this: Working Backwards is everything I wanted it to be. Bryar and Carr make a coherent, believable case for how Amazon is able to do the things it does. (They also give enough context, and tell enough colourful stories, to tell you how each technique emerged!)
1
10
Replying to
I’ve written a comprehensive summary of Chapter 6, on how Amazon measures its business here: holistics.io/blog/how-amazo I’m still thinking of ways to apply some of these ideas. Oh, and, yes: I THOUGHT I was operationally rigorous. I no longer think so.
1
3
Replying to
Well, if you want to know how Amazon works, or how their org design is done, then you’ll probably want to read the full thing. You can’t apply some of their ideas without knowing the stories of how they invented them/what problems they were originally designed to solve.
Show replies
Replying to
do you have a list anywhere of books you really liked/recommend that you didn't end up summarizing? only just occurred to me that you probably have much larger space of books you think are cool than summaries you have on your site
1