AWS re:Invent 2020: Working backwards: Amazon’s approach to innovation
AWS Events1 HN recommender · recommended in 1 month, 2021-2024
80K views · 5 years ago · talk · evergreen
An AWS re:Invent session explaining Amazon's Working Backwards process, where teams start from customer needs and write a press release and FAQ (PR-FAQ) before building. It covers the five customer questions that frame the process.
HN cites it as the primary source for Amazon's Working Backwards method whenever product-definition approaches come up.
15:14Velocity 2011: Jon Jenkins, "Velocity Culture"
O'Reilly
52K views • 15 years ago
59:13AWS re:Invent 2019: [REPEAT 1] Amazon DynamoDB deep dive: Advanced design patterns (DAT403-R1)
AWS Events
115K views • 6 years ago
5:40Jeff Bezos 1997 Interview
Chuck Severance
1.9M views • 12 years ago
1:33:27AWS re:Invent 2016: Tuesday Night Live with James Hamilton
Amazon Web Services
133K views • 9 years ago
59:13AWS re:Invent 2018: [REPEAT 1] A Serverless Journey: AWS Lambda Under the Hood (SRV409-R1)
Amazon Web Services
72K views • 7 years ago
8:10Video from Jeff Bezos about Amazon and Zappos
07272009july
943K views • 17 years ago
53:43AWS re:Invent 2018: Amazon DynamoDB Under the Hood: How We Built a Hyper-Scale Database (DAT321)
Amazon Web Services
112K views • 7 years ago
47:51AWS re:Invent 2014: AWS Innovation at Scale with James Hamilton (SPOT301)
Amazon Web Services
70K views • 11 years ago
59:56AWS re:Invent 2018: Amazon DynamoDB Deep Dive: Advanced Design Patterns for DynamoDB (DAT401)
Amazon Web Services
468K views • 7 years ago
46:15AWS re:Invent 2014 | (SPOT302) Under the Covers of AWS: Its Core Distributed Systems
Amazon Web Services
10K views • 11 years ago
1:02:53Gabe Newell: Reflections of a Video Game Maker
The LBJ School
919K views • 13 years ago
1:05:06AWS re:Invent 2018: Powering Next-Gen EC2 Instances: Deep Dive into the Nitro System (CMP303-R1)
Amazon Web Services
57K views • 7 years ago
1:02:04Gabe Newell: On Productivity, Economics, Political Institutions, and the Future of Corporations
blogphilofilms
714K views • 13 years ago
27:58GraphQL: The Documentary
CultRepo
603K views • 7 years ago
18:48Steve Jobs - NeXT marketing strategy video 1991
Vickin Kane
59K views • 12 years ago
2:31Designer's Digest - Steve Jobs on the role of product and marketing people.
Designer's Digest
212K views • 7 years ago
42:26AWS re:Invent 2015 | (NET403) Another Day, Another Billion Packets
Amazon Web Services
55K views • 11 years ago
0:55Steve Jobs - Apple Product Matrix Strategy 1997
JackIsBack15
42K views • 16 years ago
5:50Steve Jobs : Great idea doesn't always translates into great product
Investors Archive
106K views • 6 years ago
47:42What's It Really like Working at Valve?
People Make Games
643K views • 3 years ago
3 comments from Hacker News
This is just Amazon's "Working Backwards" methodology [1] expressed simplistically. There's also a book about written by key Amazon people. [2] A core part of the Working Backwards idea is to start out by writing a fake press release, even for internal projects. This helps crystallize exactly what is important and what isn't, as it forces you to express your goal precisely and succinctly as well as define what it brings to the table. [1] ▶ this video [2] link
Sounds good. Thank you for taking this the right way - I found it hard to articulate the criticism in a constructive way with few words, so it was verbose and I hoped for the best. Amazon, for all its faults, has this process well defined. These links may be helpful to you. Good Luck link link A nice video: ▶ this video
With all due respect to the author, I think the article kind of romanticizes start-up founders and their perils. Amazon famously dubs itself with being the biggest startup in the world. There's a company that espouses Clay Christensen's philosophy of building enduring businesses. Over the years, a lot has been said and written about how Amazon manages to do it, I mean, this is better demonstrated by Jeff, its founder, whose wealth went from $10B in 1997 to $1B in 2002/3, but still bet big on AWS (2003), Prime (2005), and Kindle (2007) in an unprecedented run of series of innovations that'd could have killed the company. -- "working backwards" I want to draw some parallels to the YC application process with how Amazon operates, from what I've read and what I've experienced as an ex-employee: A lot of product development is funded at Amazon after review of what's called a PR/FAQ doc [0] (this is the "working backwards from the customer" part). The PR needs to clearly articulate in a headline or two what the product is about; whilst the first paragraph must present a complete summary of what the product would be in its v1 form at launch. The next few paragraphs detail the current problem and the proposed solution interlaced by imaginary quotes from would-be customers; and the concluding paragraph has a clear call-to-action on exactly how customers can make use of the proposed solution. If you've ever filled out a YC form, you'd find yourself going through a similar exercise. And