Great article Fran and Orel. I've found myself implementing the "Working backwards" framework so much more as I've tried to increase how much I better prioritize.
For example, we want to ship to customers by <x> date, that means we need to internally experiment by <y> date, which means we need to be eng complete by <z> date, and have comms ready by another date, etc. once we do all of that planning backwards, we know exactly when we need to do each step, and if we stack rank into p0s, p1s, p2s, etc. we know what we can cut if we're not meeting it, and what good vs. great looks like.
It's cool to see how Amazon makes the working backwards practice part of the cultural norms
Great article Fran and Orel. I've found myself implementing the "Working backwards" framework so much more as I've tried to increase how much I better prioritize.
For example, we want to ship to customers by <x> date, that means we need to internally experiment by <y> date, which means we need to be eng complete by <z> date, and have comms ready by another date, etc. once we do all of that planning backwards, we know exactly when we need to do each step, and if we stack rank into p0s, p1s, p2s, etc. we know what we can cut if we're not meeting it, and what good vs. great looks like.
It's cool to see how Amazon makes the working backwards practice part of the cultural norms
It's so cool that you get a chance to implement those things and see how they work in practice! :)
And what's even more amazing is that Amazon is keeping its' culture as it grows even though it's scary to set such high expectations of:
We want to do X. What do we need to make it work?
Because it puts you in a situation where you probably need to get out of your comfort zone to make things happen.
Nice article ,well written found it quite insightful
:)