Frequently asked questions
The single biggest lesson from Jeff Bezos is this: build your business around the long-term interests of your customers, not the short-term demands of the market, and be willing to be misunderstood for years while you do it. Everything else, from hiring to product design, follows from that discipline.
Jeff Bezos founded Amazon in 1994 as an online bookshop run from his garage in Bellevue, Washington. He grew it into one of the most valuable companies in the world, spanning retail, cloud computing, logistics, devices and media. He also founded Blue Origin, bought The Washington Post, and stepped down as Amazon chief executive in 2021 after nearly three decades at the helm. His track record is instructive because it spans multiple decades, multiple industries and multiple economic cycles, giving entrepreneurs a rare, tested body of decision-making to study rather than a single lucky break.
Put Customer Obsession Above Competitor Obsession
From the earliest days of Amazon, Bezos insisted that the company should be customer-obsessed rather than competitor-obsessed. He famously kept an empty chair in meetings to represent the customer, a physical reminder that decisions should be judged by their effect on the person buying the product, not by what a rival was doing. This showed up in decisions such as introducing customer reviews, even negative ones about products Amazon sold, because it built trust even though it occasionally hurt short-term sales. Bezos argued repeatedly in his shareholder letters that watching competitors too closely leads to reactive strategy, while watching customers leads to invention. Amazon’s willingness to lower prices, add free shipping thresholds and expand return policies, often before competitors forced its hand, came directly from this obsession with the buyer’s experience rather than the scoreboard against other retailers.
How to apply this to your business: Build a simple habit of asking, before every major decision, whether it makes life better for the customer or merely responds to a competitor. Create a standing agenda item in leadership meetings dedicated purely to customer pain points, separate from competitive analysis, so the two conversations never blur into one.
Think in Decades, Not Quarters
In his 1997 letter to shareholders, written in the year after Amazon’s initial public offering, Bezos stated plainly that all decisions would be weighed against long-term market leadership rather than short-term profitability or Wall Street reactions. This letter was reprinted in every subsequent annual report during his tenure as a reminder to investors and staff alike. Amazon ran at thin margins or losses for years while it built out warehouses, logistics networks and technology infrastructure, a strategy that drew heavy criticism from analysts throughout the late 1990s and early 2000s. That patience eventually paid off as the infrastructure became the foundation for both retail dominance and, later, Amazon Web Services. Bezos was explicit that he expected the company to be misunderstood for long stretches, and he treated that misunderstanding as evidence the strategy was genuinely long-term rather than a comfortable illusion.
How to apply this to your business: Write down, in plain language, what you are willing to sacrifice in the short term for a stronger position in three to five years, and share it with your team so short-term pressure does not quietly override the plan. Revisit that statement annually rather than letting quarterly noise rewrite your strategy by default.
Treat Every Day Like Day One
Bezos used the phrase “Day 1” so consistently that Amazon’s Seattle headquarters building is named Day 1. He warned that Day 2 was stasis, followed by irrelevance and painful decline, and that large companies could take decades to die but the outcome was inevitable if they stopped acting like a nimble newcomer. His 2016 shareholder letter set out specific defences against Day 2 thinking, including genuine customer obsession, resistance to proxies such as process for its own sake, fast decision-making, and staying alert to changing external trends rather than internal habits. This was not just rhetoric. Amazon repeatedly cannibalised its own successful products, such as allowing third-party sellers to compete directly against its own retail listings, because Bezos believed protecting a comfortable current business was more dangerous than disrupting it first.
How to apply this to your business: Regularly audit your own processes and ask whether each one still serves the customer or has simply become “how things are done here.” Encourage teams to challenge your most profitable product line as if a competitor were about to copy it, and act on genuine threats before they become emergencies.
Use a Regret Minimisation Framework for Big Decisions
When Bezos was deciding whether to leave a secure, well-paid job at the hedge fund D. E. Shaw in 1994 to start an online bookshop, he used what he later called a regret minimisation framework. He imagined himself at eighty years old looking back on his life, and reasoned that he would regret not trying far more than he would regret a failed attempt, since a business failure would fade quickly while the regret of never having tried would last a lifetime. This framework helped him overcome the obvious short-term risk of leaving stable income and status for an unproven idea in a garage. It is a deliberately simple mental model, but it gave him clarity at a genuinely difficult fork in his career, and he has referenced it publicly many times since as the reasoning behind Amazon’s founding.
How to apply this to your business: Before a major decision, such as launching a new venture or leaving stable employment, imagine yourself decades later assessing the choice, and weigh long-term regret rather than short-term comfort or fear. Write both possible outcomes down honestly, since the exercise of articulating them often clarifies a decision that feels foggy in the moment.
Work Backwards from the Customer, Not Forwards from Capability
Amazon institutionalised a planning method known internally as “working backwards.” Rather than starting with existing engineering capability and asking what could be built, teams were required to write a mock press release and frequently asked questions document describing the finished product from the customer’s point of view before a single line of code was written. This forced clarity on what problem was actually being solved and for whom, and exposed weak ideas early, since a genuinely underwhelming product is obvious when described plainly rather than dressed up in technical detail. Amazon Prime, the Kindle and Amazon Web Services all went through versions of this process. The discipline meant that internal excitement about clever technology was never allowed to substitute for a genuine customer benefit.
How to apply this to your business: Before building anything new, write the customer-facing announcement first, in plain language, as if the product already existed and was being launched tomorrow. If the resulting document would not excite a real customer, treat that as a signal to rethink the idea rather than pushing ahead on momentum alone.
Set a High Hiring Bar and Protect It
Bezos wrote extensively about hiring discipline in his shareholder letters, describing three questions interviewers should ask themselves about any candidate: will you admire this person, will this person raise the average level of effectiveness of the group they are joining, and along what dimension might this person be a superstar. Amazon also used a formalised system of designated “bar raisers”, interviewers trained specifically to protect hiring standards and empowered to veto a hire even if the hiring manager wanted to proceed, precisely to stop standards slipping under pressure to fill a role quickly. Bezos argued that a consistently rising hiring bar compounds over time, since strong people attract other strong people, while a declining bar compounds in the opposite direction just as quickly.
How to apply this to your business: Introduce a second, independent interviewer whose only job is to protect your hiring standard, separate from the hiring manager who is naturally under pressure to fill the vacancy. Ask explicitly what unique strength a candidate brings that the existing team lacks, rather than only assessing whether they can competently do the job.
Make Reversible Decisions Quickly and Irreversible Ones Carefully
Bezos distinguished between what he called Type 1 and Type 2 decisions. Type 1 decisions are consequential and irreversible, like a one-way door, and deserve careful, often slow deliberation with wide input. Type 2 decisions are reversible, like a two-way door, and should be made quickly by small groups or even individuals, because the cost of a wrong decision is low and easily corrected. He warned in his 2015 shareholder letter that most decisions in a growing organisation are actually Type 2, yet many companies mistakenly apply the same heavy process to both categories, which slows everything down and discourages the experimentation that drives innovation. This distinction gave Amazon staff a practical filter for deciding how much analysis a decision genuinely warranted before acting.
How to apply this to your business: Before debating any decision at length, ask whether it can realistically be undone if it turns out wrong. If it can, delegate it and move quickly, reserving your slowest, most consultative decision-making for the genuinely irreversible calls that deserve it.
Disagree and Commit
Bezos popularised the phrase “disagree and commit” within Amazon, describing situations where he personally disagreed with a proposal, such as a particular television or film project pursued by Amazon Studios, but told the team clearly that he disagreed and then committed fully to supporting their decision rather than stalling it with continued argument. He described this as a genuine commitment, not a passive-aggressive compromise, since dragging out disagreement after a decision has been made wastes energy and signals a lack of trust in the people responsible for delivery. This approach let Amazon move faster on decisions where reasonable people disagreed and full consensus was unlikely, without forcing every disagreement to escalate into a prolonged standoff that delayed action.
How to apply this to your business: When your team has debated a decision thoroughly and a leader still disagrees but the group wants to proceed, state the disagreement openly once, then commit fully rather than quietly undermining the plan afterwards. This keeps decision-making fast while still surfacing genuine concerns before they are overridden.
Keep Teams Small Enough to Move Fast
Amazon adopted what became known as the “two-pizza team” rule, the idea that a team should be small enough to be fed by two pizzas, roughly six to ten people. Bezos pushed this structure because larger groups tend to slow decision-making, dilute ownership and require more coordination overhead than actual output. Small autonomous teams were given clear ownership of a specific product or service and were expected to operate with minimal need for cross-team sign-off, which suited Amazon’s later move towards independently deployable microservices in its technology architecture. The approach was not without friction, since coordinating dozens of small independent teams brought its own complexity, but it reflected a consistent belief that bureaucracy grows automatically unless actively resisted through structural choices.
How to apply this to your business: As your business grows, resist the automatic urge to grow single teams indefinitely. Split functions into smaller units with clear, singular ownership of a specific outcome, and give them the authority to make most decisions without waiting for approval from above.
Reinvest Aggressively to Build a Flywheel
Amazon’s growth strategy has often been described using the metaphor of a flywheel, an idea associated with Bezos and Amazon’s early strategy sessions with business thinker Jim Collins. Lower prices attract more customers, more customers attract more third-party sellers wanting access to that audience, more sellers and volume create economies of scale, and those economies allow prices to fall further, turning the wheel again. Rather than extracting profit early, Bezos consistently chose to reinvest cash into lower prices, faster shipping and broader selection, accelerating the flywheel rather than slowing it to book short-term earnings. This is visible in Amazon’s historically low reported profit margins relative to its revenue for many years, a deliberate consequence of reinvestment rather than a sign of weak underlying economics.
How to apply this to your business: Identify the two or three factors in your own business that reinforce each other, such as customer volume, unit cost and service quality, and be deliberate about reinvesting profit into strengthening that loop rather than withdrawing it too early. A flywheel only builds momentum if it is fed consistently over time rather than interrupted for short-term gain.
Accept Failure as the Price of Genuine Invention
Bezos was open about Amazon’s failures, describing them plainly in shareholder letters rather than burying them. The Fire Phone, launched in 2014, was a costly commercial failure that led to significant write-downs and layoffs in that division. Earlier ventures such as Amazon Auctions and zShops in the late 1990s also failed to gain traction. Bezos argued in multiple letters that a company willing to fail occasionally at a large scale is also a company capable of occasionally succeeding at a large scale, and that avoiding all failure usually means avoiding all meaningful experimentation too. He pointed to Amazon Web Services and the Kindle as bets that could easily have failed but instead became transformative, arguing that a portfolio of experiments, most of which fail modestly, is how a handful of genuinely large successes get produced.
How to apply this to your business: Set aside a defined budget or time allowance specifically for higher-risk experiments, and judge that allowance by its overall portfolio return rather than expecting every individual bet to succeed. Talk openly with your team about failed initiatives rather than hiding them, so people stay willing to propose ambitious ideas rather than only safe ones.
Frequently asked questions
What is Jeff Bezos’s most famous piece of business advice?
His most repeated idea is “Day 1” thinking, the belief that a company must keep acting like a nimble newcomer, obsessed with customers and willing to make fast decisions, because the alternative, which he called Day 2, leads to stagnation and eventual decline regardless of a company’s size or past success.
How did Jeff Bezos decide to start Amazon?
He used what he called a regret minimisation framework, imagining himself at eighty years old and reasoning that he would regret never having tried to build the business far more than he would regret a failed attempt. This gave him the clarity to leave a stable job at a hedge fund in 1994.
What is the two pizza team rule?
It is a guideline used at Amazon stating that a team should be small enough to be fed with two pizzas, typically six to ten people, on the basis that smaller teams make decisions faster and take clearer ownership than large ones burdened by coordination overhead.
Why did Amazon operate at low profit margins for so long?
Bezos chose to reinvest cash into lower prices, logistics infrastructure and new services rather than reporting higher short-term profit, believing this built a stronger long-term competitive position through what is often described as a flywheel effect, where scale and reinvestment continuously reinforce each other.
Did Jeff Bezos ever fail at Amazon?
Yes, and he wrote about it openly. The Fire Phone launched in 2014 was a significant commercial failure, and earlier ventures such as Amazon Auctions did not succeed either. He argued publicly that a willingness to fail at scale was a necessary condition for occasionally succeeding at scale.
More business lessons
- Business Lessons from Mark Cuban
- Business Lessons from Coco Chanel
- Business Lessons from Satya Nadella
Related reading: I Asked AI to Audit My Own Blog. It Told Me to Delete Half of It. and I Write Client Proposals With AI in 20 Minutes. Here’s the Bit Nobody Tells You.
