Learn proven scaling strategies from DoorDash's former COO. Master unit economics, team building, and rapid expansion tactics that drive market dominance.
How to Scale a Business Like DoorDash: COO Strategies for Growth
Executive Summary
Scaling a marketplace business from zero to market dominance requires a fundamentally different approach than managing a traditional software company. Christopher Payne, the former Chief Operating Officer of DoorDash, reveals the critical strategies that transformed a struggling food delivery startup into a multi-billion dollar empire. His journey from Microsoft to Amazon to DoorDash demonstrates how executives can master the complex interplay between unit economics, geographic expansion, team leadership, and strategic pivots. This comprehensive guide distills decades of operational expertise into actionable frameworks that any executive or founder can apply to accelerate business growth.
Key Insights
- Unit economics trump growth velocity: Profitable unit economics in even one market enable rapid, capital-efficient expansion across hundreds of geographies
- Atoms-based businesses require financial rigor: Unlike software companies, marketplace and delivery businesses demand mastery of unit-level profitability before scaling
- The "crawl, walk, run" methodology works: Proving profitability in one city (Palo Alto), then adapting the playbook to multiple markets, then scaling nationally eliminates wasted capital
- Executive versatility matters more than specialization: Generalist leaders who understand finance, product, operations, and customer needs outperform narrow specialists at scale
- Details drive strategy, not vice versa: Successful executives maintain the ability to examine granular data and operational details while extracting broader strategic insights
Understanding Atoms Versus Bits: The Fundamental Business Difference
When Christopher Payne joined DoorDash as Chief Operating Officer, he brought experience from two seemingly different worlds: Microsoft, a software company, and Amazon, a marketplace business. The distinction between these types of companies—bits (software) versus atoms (physical logistics)—fundamentally shapes how leaders must approach operations and growth.
The atoms-oriented business model, like DoorDash or Amazon, requires an entirely different financial mindset than software companies. At Microsoft or other pure software businesses, the financial strategy is straightforward: build the right product, achieve product-market fit, and unit economics typically follow. But with a physical business model, the math is intentionally difficult and requires constant optimization.
When DoorDash launched in a new geography, the company initially lost money. This wasn't a sign of failure—it was expected. The key insight is that as volume increases in each market, unit economics improve through two mechanisms: first, the cost of delivery decreases per order as density increases and routing becomes more efficient; second, merchants agree to pay higher commissions when they see more customer demand. Only after these optimizations take effect can a market become profitable.
This contrasts sharply with the narrative that circulated during DoorDash's early growth: "We're giving away dollars for 90 cents." This was categorically false, Payne explains, because a company without substantial capital reserves couldn't sustain such losses. Instead, DoorDash followed a disciplined growth cycle. New markets required six months of volume to achieve gross margin positivity, then twelve months of volume at a certain scale to achieve contribution margin profit that flows to the bottom line. Once this playbook was validated in each market, expansion could accelerate rapidly without wasting capital on unprofitable growth.
The lesson applies broadly: executives transitioning between atoms-based and bits-based businesses must develop financial rigor and an almost obsessive focus on unit economics. This skill set is learnable, but it requires a fundamental mindset shift from those trained in pure software environments.
The Art and Science of Building New S-Curves
One of Payne's first strategic moves at DoorDash was recognizing that the company's future extended far beyond restaurant delivery. While DoorDash was still young and struggling to survive, Payne had witnessed similar transformations at Microsoft and Amazon. He founded DoorDash's first new S-curve: the platform business model.
The platform business eventually evolved to encompass restaurants, grocery, alcohol, retail, and DoorDash Drive (the logistics infrastructure for any merchant). Today, each of these categories represents a multi-billion dollar business. But building them required protecting them from the gravitational pull of the core business.
In any growing organization, new initiatives face existential threats from the established business. Teams responsible for the main revenue stream inevitably view new ventures as resource thieves. Without deliberate protection, these nascent businesses get starved of capital, talent, and attention. Payne's solution was to operationalize this protection through what he calls the "10% principle."
He reserves dedicated resources—people, budget, and focus—for new S-curves and explicitly tells the core business team: "You can manage the 90%, but you can't touch the 10%." This separation must be physically and organizationally real. The new business needs enough autonomy to experiment, fail, and iterate without the core business's metrics and constraints pulling it toward short-term optimization.
The process also requires different financial metrics. The core business is evaluated on near-term profitability and revenue growth. New S-curves should be evaluated on customer acquisition, product-market fit signals, and long-term potential. Bring the right finance people into the room who understand the difference and can help establish appropriate goals and measurement frameworks.
Once a new S-curve achieves product-market fit and demonstrated scalability, it can be "graduated" into a full business unit with dedicated executives. DoorDash's success with this model—creating multiple billion-dollar categories—proves that protecting and nurturing new businesses within larger organizations is not just possible; it's essential for sustained growth.
Details, Data, and the Illusion of 30,000-Foot Leadership
Many executives believe that as they rise in the organization, they should spend less time in operational details. This is precisely the opposite of what separates exceptional operators from mediocre ones.
Payne's philosophy is unambiguous: if you lose the ability to get into the details of your business and understand the base metal of operations, you become irrelevant. This doesn't mean micromanaging or spending all your time on granular tasks. Rather, it means maintaining the capacity to dive deep into areas where the business is struggling or where major decisions are being made.
His approach at DoorDash illustrated this principle perfectly. When building the grocery business—an entirely new operational domain—he didn't just review reports and attend planning meetings. He ordered groceries through the DoorDash app and tracked his orders through an internal tool that showed real-time status updates. When something went wrong (like missing ciabatta bread), he didn't delegate the investigation to a subordinate. Instead, he replicated the customer experience himself, drove to the store as a Dasher, and walked the aisles to understand why the system failed.
This wasn't busywork. The investigation revealed a structural problem: the app directed Dashers to correct grocery sections, but because many categories (bread, meat, dairy) had multiple locations within stores, Dashers frequently grabbed items from the wrong section. A simple data query confirmed the hypothesis: these multi-location categories had defect rates 35% higher than single-location items.
Now equipped with data-driven evidence of the problem's scope, Payne could make a strategic decision. The solution required obtaining planogram information for virtually every grocery item globally and directing Dashers to the precise shelf location. This was a massive undertaking, but it was based on evidence, not intuition.
This example illustrates the correct use of executive details. The pattern is: observe specific detail → generalize using data → extract strategic insight → make resource allocation decision. Many executives skip the middle steps and jump from specific observation directly to strategy, often missing the true scope of problems.
When you're diving into details for an important initiative, you're simultaneously training the next generation of leaders. Your team learns not just what you're looking for but how to look for it—what anomalies matter, when to dig deeper, and how to connect dots between operational details and strategic implications. This mentorship through example is irreplaceable.
Adaptive Management and the Principle of Fit
Early in his career, Payne approached management with a one-size-fits-all philosophy. He believed there was one right way to set goals, structure one-on-ones, and motivate teams. This approach produced mediocre results because people are fundamentally different.
Over time, he developed what he calls adaptive management: the recognition that each team member requires different inputs, support structures, and motivational approaches to succeed. For some people, success means clear boundaries and decision-making authority. Others thrive on frequent feedback and mentorship. Some are driven by ambitious stretch goals; others need smaller wins to build confidence. The manager's job is to diagnose what each person needs and architect their environment for success.
This philosophy extends to promotion and career development. When a brilliant individual contributor—a star engineer, exceptional salesperson, or outstanding analyst—gets promoted into management, they often struggle. Not because they lack intelligence or capability, but because the skills required for their previous role don't transfer to the new role. A top coder doesn't automatically become a great engineering manager.
Payne's advice to organizations is to treat promotions into new roles as serious transitions requiring explicit training and mentorship. If a person wants to move from individual contributor to manager, they need to study management the way they studied their original discipline. This should include formal training, mentorship from experienced managers, and honest feedback about progress.
But there's an equally important corollary: not everyone should move up the traditional ladder. Some people are exceptional at their current level and prefer to stay there. Rather than viewing this as a limitation, organizations should celebrate it. The best individual contributor on your team performing at the highest level is more valuable than a mediocre manager. Create career pathways for people to advance in scope, impact, and compensation without leaving their domain of excellence.
The Crawl, Walk, Run Framework for Market Expansion
DoorDash's expansion from a struggling startup in Palo Alto to a company operating in thousands of cities followed a deliberately structured progression. This "crawl, walk, run" methodology proved that rapid scaling without understanding operational mechanics leads to wasted capital and strategic mistakes.
The crawl phase involved picking one market—Palo Alto—and solving for unit economics entirely. This meant understanding customer acquisition costs, merchant acquisition and retention, Dasher availability and efficiency, and all the variables that affect profitability in a single geography. The goal wasn't quick scaling; it was proof that the unit economics worked.
Once Palo Alto achieved sustainable profitability, DoorDash moved to the walk phase: expanding to a handful of additional markets. This revealed crucial insights. Boston, Philadelphia, and Palo Alto turned out to be quite different from one another in terms of geography, consumer preferences, merchant density, and Dasher availability. Each market taught different lessons.
The critical insight was that while markets are different, an 80% common playbook could be developed and adapted with a 20% market-specific customization. This became the foundation for the run phase: rapid expansion across the country.
But the expansion strategy faced a scaling challenge. The original go-to-market model relied on sending teams of college students into new cities to recruit Dashers, sign up restaurants, execute marketing campaigns, and manage launch locally. This worked when launching dozens of cities. When Tony Xu set the goal of launching thousands of cities, this approach became impossible.
Payne and his team faced a forced choice: continue the old model and limit growth, or build a new go-to-market model that enabled remote expansion. They chose to do both simultaneously—maintaining the old model while dedicating resources to building a new remote-first expansion playbook. Within six months, they had to transition from the old model to a new model that didn't require on-the-ground teams.
The new model involved identifying the specific bottlenecks in each market (merchant density, Dasher availability, customer demand) and solving them through remote business development, data-driven targeting, and optimized unit economics. This enabled DoorDash to expand to suburban and rural markets efficiently without maintaining local teams.
The lesson for any scaling business is that the methods that work for 10-50 cities won't work for 500+ cities. You must anticipate these transitions and build new models while simultaneously running the old business. This requires clear goal-setting, resource allocation, and team prioritization.
Goal-Setting as Strategic Leverage
One of Payne's most powerful tools for accelerating business progress is his philosophy of top-down goal-setting. Many organizations prefer bottom-up goal-setting, where teams propose what they believe they can achieve. Payne finds this approach often caps ambition prematurely.
When you ask a team, "What can you achieve?" they propose targets they're confident in hitting. This leads to incremental progress and missed opportunities. Instead, Payne sets ambitious top-down goals and forces teams to work backward from the target to identify what's actually required.
Here's an example from his work with student entrepreneurs at the University of Oregon. One team was building a marketplace in a healthcare-related field. When Payne asked about their growth goals for the next six months, they proposed a 20% increase. He responded by setting a 10x growth target—knowing it was ambitious but believing it was worth pursuing.
The team's reaction was initially skeptical, but they asked the right follow-up question: "What would we actually have to do to achieve 10x growth?" This forced them to think about their core bottleneck. If their constraint was medical approvals, they couldn't get there with incremental improvements to existing processes. They'd need business development partnerships with large healthcare providers. If their constraint was user acquisition, they'd need to explore paid channels, partnerships, or viral mechanics they hadn't previously considered.
The team didn't hit the 10x goal. They achieved 8x growth—which Payne celebrated as extraordinary progress. The key insight was that by setting an ambitious target and forcing them to work backward, they moved far faster than they would have with a bottom-up 20% goal. They fundamentally changed how they approached the problem.
Payne emphasizes that this goal-setting approach must be applied thoughtfully. Goals should be ambitious but not impossible. Teams should have defined resources (Y dollars and Z people) to work with. If they return saying they can reach 80% of the goal with a compelling explanation of the limiting factors, that's often a win worth celebrating and even rewarding.
One crucial element of this framework is alignment across the organization. In a company like DoorDash, if the restaurant business has one goal, the grocery business has a different goal, and the platform team has yet another, you create internal competition. Instead, Payne structures high-level goals that unite teams around shared outcomes. At DoorDash, this meant aligning around DashPass (the subscription product). Whether you run restaurants, grocery, or alcohol, your success metric includes how you contribute to DashPass subscriber growth and retention.
Building and Evaluating Executive Teams
The strength of an organization ultimately rests on the quality of its executive team and how effectively they function as a cohesive unit. Payne has observed a simple diagnostic test: ask an executive, "What team are you on?" If they say "I'm on the engineering team" or "I'm on the product team," you have a dysfunctional leadership team. If they say "I'm on the executive team" or name the company's leadership group, you have a healthy team structure.
Dysfunctional executive teams are characterized by silos, politics, and competing agendas. Functional teams share information openly, work problems collaboratively, and genuinely support one another's success. This doesn't happen by accident; it requires deliberate cultural work and intentional team design.
Early in Payne's career, he was something of a "wrecking ball"—willing to push hard across organizational boundaries to get things done. He later realized this approach, while sometimes effective in the short term, undermined executive team cohesion. His inability to work collaboratively within the leadership structure was holding back his career progression and the organization's effectiveness.
Feedback from a mentor at Microsoft was transformative: Payne recognized that his individual drive to move fast was being perceived as self-serving politics rather than organizational benefit. He learned to reframe his approach: instead of pushing through obstacles, he worked to align the executive team, understand competing constraints, and find solutions that everyone could support.
This realization had immediate impact. Once Payne learned to function effectively within executive team dynamics, his ability to drive change actually increased dramatically. He could accomplish more through aligned leadership than through individual force of will.
The implication for any growing organization is that executive hiring and team dynamics deserve enormous attention. You can have brilliant individual executives who create more drag than forward momentum if they can't function as a team. Conversely, a functional team of reasonably capable executives can outperform a group of brilliant individuals who aren't aligned.
Scaling Through Uncertainty and Market Cycles
Payne's career has spanned multiple economic cycles and market disruptions. He was at Amazon during the dot-com boom and bust. He led initiatives at Microsoft during periods of dominance and struggle. He joined DoorDash during a period of skepticism about the food delivery market. These experiences have given him perspective that's invaluable during turbulent times.
One lesson from his Amazon years came directly from Jeff Bezos during a walk: "They build you up, they want to tear you down, and the best you can hope for is a comeback story." This reframing changed how Payne interprets market cycles and media narratives.
When DoorDash's stock price fell, or when the delivery market faced skepticism, Payne's internal response wasn't panic. It was perspective. Stock prices and media narratives move in cycles. What matters is whether the fundamental business is viable and whether the team has the resources and resolve to execute.
This perspective became particularly valuable during downturns. When most executives are in defensive mode, companies with leadership perspective and capital can gain market share. The companies that remain focused on their long-term vision while competitors contract often emerge as market leaders.
Payne has observed that a generation of leaders who haven't experienced a downturn often struggle when one occurs. They've only known growth environments where execution and momentum are nearly enough. In downturns, the ability to maintain team morale, make disciplined capital allocation decisions, and stay focused on the long-term vision becomes essential. Experience with cycles provides confidence that "this too shall pass" and that the downturn is actually an opportunity.
From Specialist to Generalist: Career Progression for Leaders
One of Payne's most important insights is that career progression typically requires moving from specialist to generalist expertise. Early in a career, specialization is necessary and valuable. You develop deep expertise in one domain—engineering, product, finance, marketing. This expertise makes you valuable and often leads to promotions within your specialty.
But at some point, further advancement requires generalist skills. A great engineering manager needs to understand product, business metrics, and customer needs. A successful finance executive needs business acumen, not just accounting expertise. A CEO needs to be conversant across all functions.
The challenge is that the path from specialist to generalist is uncomfortable. You're moving from a domain where you have deep expertise to areas where you're a relative novice. Many talented people plateau at the specialist level because they're unwilling to take this journey.
Payne's advice is to embrace the discomfort. Early in your career, deliberately move to roles where you're learning new functions. If you're an engineer, spend time in product management or business operations. If you're in finance, lead operations or business development. The specific domain matters less than the diversity of experience.
This produces several benefits. First, you develop a mental toolkit for solving problems that transfers across domains. Payne finds that unit economics, for example, is a framework that applies whether you're analyzing a transportation business, a healthcare company, or a marketplace. The specific numbers change, but the way of thinking translates.
Second, you build empathy for different functions. When Payne runs operations and understands engineering challenges, he can work more effectively with the engineering team. He knows their constraints and can help them succeed rather than simply pushing directives.
Third, you develop the language and frameworks that allow you to move into senior roles. A CEO needs to be conversant with product managers, engineers, finance leaders, and business development. If your entire career has been spent in one function, you'll struggle to operate at that level.
The best way to develop these skills is through a combination of deliberate role changes and mentorship from leaders who have already made these transitions successfully. Organizations that create pathways for talented people to move across functions and that pair them with mentors in new domains accelerate leadership development significantly.
The Role of Data in Executive Decision-Making
Throughout his career, Payne has observed the evolution of decision-making approaches. At Microsoft in the 1990s, data was limited, and leadership relied heavily on intuition, persuasion, and big ideas. At Amazon in the late 1990s and early 2000s, the culture shifted entirely toward data. Everything was measured, A/B tested, and optimized based on empirical evidence.
This evolution taught Payne important lessons. First, intuition is often wrong. When he moved to Amazon and subjected his instincts to data-driven testing, he was frequently surprised by results that contradicted his expectations.
Second, not all data is equally useful. The ability to look at vast amounts of data and identify what matters is itself a skill. Payne uses the metaphor of a grocery store where there's a milk spill on aisle seven. You could run an A/B test to determine whether cleaning up the spill is more productive than restocking aisle four. But judgment and common sense tell you to clean up the spill immediately.
The modern approach to decision-making, particularly in the AI era, requires integrating data and human judgment. Data should inform decisions, but judgment about which questions to ask and how to interpret results remains essential. This is particularly true for novel situations where historical data doesn't exist or where the context has fundamentally changed.
For any executive joining a business, the first instinct should be to understand the data infrastructure. What metrics are being tracked? How frequently is data updated and reviewed? What stories is the data telling? At DoorDash, Payne spent his first weeks building dashboards that showed key metrics across all cities and quality dimensions. This wasn't busywork—it was the foundation for understanding what was actually happening in the business.
Lessons for Scaling Executives
For someone stepping into an operational role at a scaling company, Payne offers several pieces of concrete advice:
Study the business thoroughly. Spend your first weeks (even months) understanding the business at the lowest level of detail. At DoorDash, Payne used Dispatch, an internal tool showing real-time order status. He'd place orders, watch them through the system, and see exactly what happened. This taught him more about the business than a hundred strategy documents.
Build a data dashboard immediately. Identify the key metrics for your business and create a daily (not monthly or quarterly) view of how you're performing. Look for anomalies, trends, and surprises. If something unusual happened (a holiday, weather event, or unexpected change), investigate it.
Don't try to solve everything at once. When you inherit a business with multiple problems, the temptation is to address all of them simultaneously. This is a recipe for dilution and failure. Pick one significant problem, solve it completely, then move to the next. Sequencing your work is as important as the work itself.
Get into the organization physically if possible. If you're running a distributed business, visit local teams early. Understand how they operate, what they're optimizing for, and what problems they face. This builds credibility and gives you insights that you'd never get from headquarters.
Be willing to do any job. In a scaling company, organizational lines are often blurry. Be willing to step into whatever role is needed. If local operations need a leader, step in. If product needs input, contribute. This flexibility accelerates your learning and demonstrates commitment to the team.
Hire for versatility over specialization. As you build your team, prioritize people who have worked across functions and who are comfortable learning new domains. These people are rarer than deep specialists, but they're more valuable for building a resilient organization.
Maintain the ability to go deep. As you move up, resist the temptation to stay entirely at the strategic level. Continue diving into details on important initiatives. This keeps your mental models accurate and identifies emerging problems before they become crises.
The Future: Generalist Leaders in an AI-Driven World
Payne observes that the pace of change in business is accelerating, particularly with the emergence of powerful AI systems. The ability to adapt, learn, and respond to change is becoming the most valuable leadership quality.
He also believes that organizational structures will likely flatten in the future. With AI as a tool to amplify human capability, executives will be able to accomplish more with fewer people. This suggests that organizations may need fewer management layers and more highly capable, versatile individual contributors.
But regardless of how technology changes, the fundamentals of leadership remain constant. You need people who understand customer needs deeply. You need teams that can execute reliably. You need leaders who can make judgment calls in ambiguous situations. These are distinctly human capabilities that technology amplifies rather than replaces.
The advantage goes to organizations led by generalists—people who understand multiple functions, have diverse experience, and can make integrated decisions across domains. In a more complex, faster-moving world, narrow specialists are increasingly constrained. Generalists can see connections across domains and respond to emergent problems more flexibly.
For ambitious leaders building their careers, this suggests clear guidance: develop versatility. Seek experiences in different functions and industries. Work for leaders and organizations that push you beyond your current capabilities. Build mental models that transfer across domains. The specific role or company matters less than the growth and learning trajectory.
Conclusion
Christopher Payne's journey from Microsoft to Amazon to DoorDash to the COO role demonstrates that operational excellence and business acumen are learnable skills. They require curiosity, humility, a willingness to learn from mistakes, and the discipline to maintain focus on what matters.
The most important takeaway is that scaling a business successfully requires mastering multiple domains simultaneously: unit economics and financial rigor, team leadership and development, strategic vision and execution discipline, and the ability to maintain perspective through market cycles. No single skill is sufficient; the best leaders integrate all of them.
If you're building a team, hiring leaders, or planning your own career trajectory, apply these principles: prioritize adaptability over specialization, dive deep while maintaining strategic perspective, set ambitious goals and hold teams accountable to them, and invest in building functional executive teams aligned around shared outcomes. These practices compound over time and create the foundation for scaling businesses that can compete and win at any scale.
The businesses that dominate their markets aren't built by lone geniuses or narrow specialists. They're built by diverse teams of versatile people led by executives who understand the whole business deeply and can make integrated decisions. If you want to scale your business like DoorDash scaled to market dominance, start by building that kind of team and developing those kinds of leaders.
Original source: Scaling DoorDash to market dominance | Christopher Payne (Former COO, DoorDash)
powered by osmu.app