I was the PM on point for the launch of the original @AmazonKindle Fire tablet a decade ago, and today I want to share one of the many war stories I collected from that experience
a 🧵on how Amazon leverages compound interest in decision making
First, let us hear from famous ex-Amazonian Albert Einstein:
“Compound interest is the 8th wonder of the world. He who understands it, earns it; he who doesn't, pays it.”
There are 2 takeaways from this, product-wise:
1/ you can layer product choices over time to compound value
2/ you can exacerbate product debt over time by carrying it
If you spend enough time at Amazon, you start to to build this pattern-matching / decision-making muscle. And occasionally you get to flex.
When I was working on the original Fire tablet as a PM in the Kindle org, the execs would do weekly reviews with Jeff (Bezos) and I’d get forwarded notes to decipher.
One throwaway comment I read early on was “Jeff thinks everyone that buys the tablet gets Prime”, and with all Jeff ideas it’s worth understanding…why?
So I ambled over to the desk (pre COVID / remote work era) where the Kindle SVP / VPs sat and just asked one of them…why?
Here was the story:
•you buy the tablet (not an e-reader) and you expect a kick-ass video experience
•we were already planning to put a version of our Android video app on the Fire
•the concern was the OOBE* (out of the box experience) on the video tab because (contd)
•you probably would have no content in your purchased / rental library to view but
•there was a deal being worked on with studios to create a video library for Prime (contd)
•so, let’s “grant” a (time-boxed) Prime subscription to everyone who buys the Fire
•and then they’ll have some popular titles to watch the first time they boot up
The ambition was mind-boggling. Kindles till that point had been a gateway to selling more books, with the average Kindle owner being a 10x reader.
But with the Fire tablet:
•you start to sell more types of long-form content (comics, textbooks, audiobooks)
•you create a more compelling visual experience for a slice of content (magazines)
•(contd)
•you are able to sell your existing digital media (music, video) via another channel
•you are creating a new subscriber funnel for a very lucrative service (Prime**)
It was like a flywheel, within a flywheel, kickstarting another flywheel.
And we had to get the CX right.
I sought out the PM on point and asked to understand the gameplan. The MVP was apparently to get a list of Kindle buyer emails, then send a subset an offer to sign up for Prime.
What?!? No…
So, I put on my (unofficial) Customer Experience Bar Raiser (CXBR) hat and redefined it.
Note: CXBR’s are like Amazon’s version of the Pixar Brain Trust
What was my improved CX pitch?
1you auto-magically get a Prime subscription when you buy the Kindle Fire
2unlike every Prime plan (e.g. student, mom) you don’t enter credit card (friction)
330 days later you get a letter on your Kindle explaining expiration / subscription
Here’s what that meant in practice:
1the Subscriptions Service PM had to get on board with “granting” (vs buying)
2the Prime Offers PM had to get on board with a plan w/o payment (blasphemy)
3the Kindle Campaigns PM had to get on board with non-Kindle messaging (huh?)
What authorized / qualified me to take things back to the drawing board?
As I said in my recent post* :
“you can make any decision with a cogent plan for why/how”
So let’s talk about the how, and this is where the compounding value of product decisions comes in.
We had a service in place to trigger actions based on events (e.g. purchase event -> welcome email). The quick (&functional) solution was to hack this up to talk to Prime service, b/c Jeff’s ask was explicitly “everyone that buys the tablet gets Prime”, & this met the requirement
But there was a pattern here.
Were we giving temporary Prime without payment to Kindle buyers? Or were we granting digital benefits with deferred purchase for physical orders?
With a higher-leverage architecture, setup for scale, and some incremental effort, we could build the latter. There was no specific use case to prioritize a more foundational solution, but I made the call anyway.
Hindsight is 20/20, so when I go over this story in my head now, I honestly don’t know…
1Was it foresight? (unlikely, although it will read like it)
2Was it instinct? (not really, although it sounds very cool)
3Was it culture? (probably, I’d internalized this from others)
All this solutioning happened in the early days of the product, but a few weeks before launch 3 crazy things happened in succession…
1/ the music team asked if there was a way to nudge customers to download their MP3 library to their Kindle tablet (music was the 1st type of digital content Amazon sold, even before e-books, and many customers had huge libraries)
2/ the appstore team showed up in a panic, saying Jeff wanted to give away the app of the day for free to a device buyer as a promotion option for game developers
3/ the Prime video library idea had been expanded from studios to publishers, and now a book library was possible in addition to a video library
All 3 ideas, which would create a delightful experience and insane buzz, needed some sort of generic digital benefit entitlement service. Was there such a thing? At scale?
What?!? Yes…
By layering your product choices and thinking long-term, you can build up to moments of immense pay-off in terms of customer value.
I’ll leave you with a quote (from Algorithms to Live By) and a request to hear about your own experience with decisions compounding in serendipitous ways…
If you enjoyed this 🧵, check out my newsletter runthebusiness.substack.com which has a bunch more Amazon war stories
You can also follow me @ibscribe on Twitter/ Instagram
And I’m teaching a class in a few weeks on product strategy / execution
Strategy is the glue that keeps teams oriented - so any systemic practices designed to prevent organizational drift have to lean on strategy as the foundation.
But what makes one strategy better or worse than another in terms of keeping oriented?
The answer is coherence. 🧵
What I mean by coherence is that the strategy clicks for an organization, like all the puzzle pieces coming together; conversely, an incoherent strategy has one or more aspects due to which it doesn’t quite fit.
we all suffer from imposter syndrome at work - one of the biggest instances for me when switching into PM was product vision
a 🧵on “instincts”
I had a hard time keeping up with folks who would just rapid-fire toss out product ideas and debate pros/cons in a brainstorming session.
I had a hard time keeping up with folks who would just rapid-fire toss out product ideas and debate pros/cons in a brainstorming session. (I much prefer to spend some time forming my thoughts, writing them down, and iterating on my point of view vs jumping in off-the-cuff.
I’ve been doing a lot of interviews lately (hiring PMs for my team), and all the phone screens reminded of how much I enjoy a good back and forth. I’m especially a fan of open-ended, multi-layered, tangent-spawning questions that can fill up the allotted time. 🧵
here are some examples, along with the why? behind each of them
1/ “walk me through an instance of you disagreeing and committing with an executive or peer on what direction to take your product in”