Making decisions in a large organization is hard, startups too get caught up in this sometimes energy-draining activity. How does Amazon do it?
Emphasis on the long term
Because of our emphasis on the long term, we may make decisions and weigh tradeoffs differently than some companies. Accordingly, we want to share with you our fundamental management and decision-making approach so that you, our shareholders, may confirm that it is consistent with your investment philosophy:
We will continue to focus relentlessly on our customers.
-
We will continue to make investment decisions in light of long-term market leadership considerations rather than short-term profitability considerations or short-term Wall Street reactions.
-
We will continue to measure our programs and the effectiveness of our investments analytically, to jettison those that do not provide acceptable returns and to step up our investment in those that work best. We will continue to learn from both our successes and our failures.
-
We will make bold rather than timid investment decisions where we see a sufficient probability of gaining market leadership advantages. Some of these investments will pay off, others will not, and we will have learned another valuable lesson in either case.
-
When forced to choose between optimizing the appearance of our GAAP accounting and maximizing the present value of future cash flows, we'll take the cash flows.
-
We will share our strategic thought processes with you when we make bold choices (to the extent competitive pressures allow), so that you may evaluate for yourselves whether we are making rational long-term leadership investments.
-
We will work hard to spend wisely and maintain our lean culture. We understand the importance of continually reinforcing a cost-conscious culture, particularly in a business incurring net losses.
-
We will balance our focus on growth with emphasis on long-term profitability and capital management. At this stage, we choose to prioritize growth because we believe that scale is central to achieving the potential of our business model.
-
We will continue to focus on hiring and retaining versatile and talented employees, and continue to weight their compensation to stock options rather than cash. We know our success will be largely affected by our ability to attract and retain a motivated employee base, each of whom must think like, and therefore must actually be, an owner.
We aren't so bold as to claim that the above is the "right" investment philosophy, but it's ours, and we would be remiss if we weren't clear in the approach we have taken and will continue to take.
"Bold Bets"
In this 2000 letter, Bezos talks of making bold bets given this was the era of the1999 technology bubble.
Many of you have heard me talk about the ''bold bets'' that we as a company have made and will continue to make---these bold bets have included everything from our investment in digital and wireless technologies, to our decision to invest in smaller e-commerce companies, including living. com and Pets.com, both of which shut down operations in 2000. We were significant shareholders in both and lost a significant amount of money on both.
We made these investments because we knew we wouldn't ourselves be entering these particular categories any time soon, and we believed passionately in the ''land rush'' metaphor for the Internet. Indeed, that metaphor was an extraordinarily useful decision aid for several years starting in 1994, but we now believe its usefulness largely faded away over the last couple of years. In retrospect, we significantly underestimated how much time would be available to enter these categories and underestimated how difficult it would be for single-category e-commerce companies to achieve the scale necessary to succeed.
Online selling (relative to traditional retailing) is a scale business characterized by high fixed costs and relatively low variable costs. This makes it difficult to be a medium-sized e-commerce company. With a long enough financing runway, Pets.com and living.com may have been able to acquire enough customers to achieve the needed scale. But when the capital markets closed the door on financing Internet companies, these companies simply had no choice but to close their doors. As painful as that was, the alternative---investing more of our own capital in these companies to keep them afloat---would have been an even bigger mistake.
Decisions in the context of customer experience.
As we design our customer experience, we do so with long-term owners in mind. We try to make all of our customer experience decisions---big and small---in that framework.
For instance, shortly after launching Amazon.com in 1995, we empowered customers to review products. While now a routine Amazon.com practice, at the time we received complaints from a few vendors, basically wondering if we understood our business: "You make money when you sell things---why would you allow negative reviews on your website?" Speaking as a focus group of one, I know I've sometimes changed my mind before making purchases on Amazon.com as a result of negative or lukewarm customer reviews. Though negative reviews cost us some sales in the short term, helping customers make better purchase decisions ultimately pays off for the company.
Making data-driven decisions.
Many of the important decisions we make at Amazon.com can be made with data. There is a right answer or a wrong answer, a better answer or a worse answer, and math tells us which is which. These are our favorite kinds of decisions.
Math-based decisions command wide agreement, whereas judgment-based decisions are rightly debated and often controversial, at least until put into practice and demonstrated. Any institution unwilling to endure controversy must limit itself to decisions of the first type. In our view, doing so would not only limit controversy ---it would also significantly limit innovation and long-term value creation.
Type 1 and Type 2 Decisions
One common pitfall for large organizations -- one that hurts speed and inventiveness -- is "one-size-fits-all" decision making.
Some decisions are consequential and irreversible or nearly irreversible -- one-way doors -- and these decisions must be made methodically, carefully, slowly, with great deliberation and consultation. If you walk through and don't like what you see on the other side, you can't get back to where you were before. We can call these Type 1 decisions. But most decisions aren't like that -- they are changeable, reversible -- they're two-way doors. If you've made a suboptimal Type 2 decision, you don't have to live with the consequences for that long. You can reopen the door and go back through. Type 2 decisions can and should be made quickly by high judgment individuals or small groups.
As organizations get larger, there seems to be a tendency to use the heavy-weight Type 1 decision-making *process *on most decisions, including many Type 2 decisions. The end result of this is slowness, unthoughtful risk aversion, failure to experiment sufficiently, and consequently diminished invention.1 We'll have to figure out how to fight that tendency.
High-Velocity Decision Making
Day 2 companies make high-*quality *decisions, but they make high-quality decisions slowly. To keep the energy and dynamism of Day 1, you have to somehow make high-quality, *high-velocity *decisions. Easy for start-ups and very challenging for large organizations. The senior team at Amazon is determined to keep our decision-making velocity high. Speed matters in business -- plus a high-velocity decision-making environment is more fun too. We don't know all the answers, but here are some thoughts.
First, never use a one-size-fits-all decision-making process. Many decisions are reversible, two-way doors. Those decisions can use a light-weight process.
Second, most decisions should probably be made with somewhere around 70% of the information you wish you had. If you wait for 90%, in most cases, you're probably being slow. Plus, either way, you need to be good at quickly recognizing and correcting bad decisions. If you're good at course correcting, being wrong may be less costly than you think, whereas being slow is going to be expensive for sure.
Disagreements and commitment
Third, use the phrase "disagree and commit." This phrase will save a lot of time. If you have conviction on a particular direction even though there's no consensus, it's helpful to say, "Look, I know we disagree on this but will you gamble with me on it? Disagree and commit?" By the time you're at this point, no one can know the answer for sure, and you'll probably get a quick yes.
This isn't one way. If you're the boss, you should do this too. I disagree and commit all the time. We recently greenlit a particular Amazon Studios original. I told the team my view: debatable whether it would be interesting enough, complicated to produce, the business terms aren't that good, and we have lots of other opportunities. They had a completely different opinion and wanted to go ahead. I wrote back right away with "I disagree and commit and hope it becomes the most watched thing we've ever made." Consider how much slower this decision cycle would have been if the team had actually had to *convince *me rather than simply get my commitment.
Misalignment
Fourth, recognize true *misalignment *issues early and escalate them immediately. Sometimes teams have different objectives and fundamentally different views. They are not aligned. No amount of discussion, no number of meetings will resolve that deep misalignment. Without escalation, the default dispute resolution mechanism for this scenario is exhaustion. Whoever has more stamina carries the decision.
I've seen many examples of sincere misalignment at Amazon over the years. When we decided to invite third-party sellers to compete directly against us on our own product detail pages -- that was a big one. Many smart, well-intentioned Amazonians were simply not at all aligned with the direction. The big decision set up hundreds of smaller decisions, many of which needed to be escalated to the senior team.
"You've worn me down" is an awful decision-making process. It's slow and de-energizing. Go for quick escalation instead -- it's better.
Back to code! ✌🏾