Chris Payne on Operating Cadence

Relevant Links From the Session

• DoorDash's WBR Template

How Chris Led DoorDash

DoorDash was founded in 2013 and has grown into one of the world’s leading local commerce platforms, operating in over 30 countries. In 2025, the company generated roughly $13.7B in revenue, ended the year with over 56M monthly active users, and generated nearly $75B in sales for local merchants and over $20B in earnings for Dashers. Chris joined in late 2015 / early 2016, initially expecting to help Tony Xu for only a few months, but ultimately stayed for one of the most important chapters of his career and remains involved today as an advisor. He said the experience that most directly prepared him to help build DoorDash’s operating system was Amazon, where he learned how to operate in chaos, make things up as he went, and build the systems a company needs before they fully exist.

Chris started his career at Microsoft right out of college. He then joined Amazon from 1998 to 2001 during its early chaotic years and said that, more than any other company in his background, Amazon was what most directly prepared him to be effective at DoorDash. He was the first GM beyond books at a time when Amazon was still primarily known as a bookseller, and said the experience taught him how to build systems in real time without pretending the company already knew how everything should work. Later, after selling a startup to eBay during the Great Recession, he joined eBay and described that period as his “marketplace baptism,” where he learned how marketplaces actually work, including what power an operator has and does not have.

1. Operating Systems

How Chris Sets Up Operating Systems

• Chris is known as "the WBR guy" at DoorDash - the person who set up the weekly business review and the company's operating cadence. He said he is not someone that likes processes for its own sake, and that is precisely why he is good at them.
  
  • He likes building things and getting into the substantive work. But he recognized that when you manage tens, then hundreds, then thousands of people, you need a system for setting plans, goals, and execution cadence.
• Christopher's design principle for operating systems is that they should require very little of his time once set up. He set up the system, appointed people to run it, and then it consumed progressively less of his time over the years. He noted that many founders and leaders he coaches complain that their operating cadence consumes all of their time and that they are stuck in endless meetings. His response: set it up so it does not require much of your time.

 Goal Setting Is One of the Most Important and Most Underrated Parts of Running a Company

• Chris said one of the lessons he learned the hard way over the course of his career is that founders and leaders often do not spend nearly enough time thinking about priorities, goals, and how those goals should actually be measured. 
  
  • In his view, this matters far more than many people realize because the entire operating system of a company ultimately sits on top of those choices.
• DoorDash’s planning cadence evolved as the company scaled:
  
  • early on, the company planned quarterly
  • then it moved to half-year planning
  • and eventually it moved into an annual planning cycle
  • The underlying question stayed the same at each stage: what are we actually trying to accomplish, and what goal or metric would tell us we are on track?
• Chris said this was something he and Tony Xu debated constantly. Tony often pushed for extremely ambitious goals, influenced in part by the kind of “reality distortion field” style of leadership that prizes maximal aspiration. 
  
  • Chris’s pushback was that if goals are detached from what the company can realistically execute, the downstream effect is often destructive. People begin asking for huge amounts of headcount and resources to hit a target that was never grounded in reality, and the whole planning process becomes distorted.
• His view was that the right answer is not timid goals, but aggressive and achievable goals.
  
  • the goal should be a real stretch
  • but it should still be credible enough that the company can organize around it coherently
    
    • he explicitly rejected the idea that a 70% failure rate on goals is inherently healthy
    • Chris said that if he wanted to, he could easily set goals that failed 100% of the time, but that would not make them good goals or make the company better run.

Example: The Hardest Part of Goal Setting Is Choosing the Right Metric

• Chris said that picking the right metric is often much harder than leaders expect. You want goals to be simple enough that people can understand and operate against them. But you do not want them to be so simple that they miss the real underlying system and create incentives that damage the business.
• His advice was:
  
  • Spend much more time upfront thinking through what the actual goal should be, ask yourself what could go wrong if the organization optimizes hard against that metric, and try to design the metric so that it captures not just the immediate outcome, but also the important constraints around it
  • He was explicit that leaders will still make mistakes, but leaders should measure twice and cut once as much as possible when setting goals, because once the company starts optimizing around the wrong number, the damage can be significant.
• Chris gave a story from eBay, where he had been asked to go fix Search. At the time:
  
  • 92% of queries on eBay went through Search
  • 90% of sales went through Search
• So in principle, improving Search looked like one of the highest-leverage things he could possibly do. Chris’s initial instinct was straightforward: optimize for conversion in a way that would maximize overall sales value, essentially price times quantity sold. That seemed like the obvious right metric.
• But the technical and analytics teams told him that eBay’s systems at the time could not properly optimize around that more complete metric because of the complexity of auctions and the way the system was instrumented. They said they could, however, run experiments to optimize for quantity.
  
  • Chris knew even then that this was not fully right, because it was possible to increase quantity without increasing overall sales. But he rationalized that it was good enough for the short term and that the more complete system could be built in parallel.
• A quarter later, Chris found himself explaining exactly that failure mode to the CFO. The “bought items” metric had improved significantly and was up roughly 8% but total sales had stagnated because the system had learned how to game the target.
  
  • Search was surfacing more low-priced goods at the top. Those converted better on the narrow metric, but they did not increase total economic value in the way the business actually cared about
• Chris said he was furious with himself because he had seen the danger upfront and still convinced himself he could get away with it temporarily. He was then left trying to explain to senior leadership why an apparently positive metric was actually not good news.
•  He then worked with the team to build the better optimization system around price times quantity. That fixed the first issue, but exposed a second one: he had still missed the role of trust in the eBay marketplace.
  
  • eBay had a trust problem, which meant that even if the system increased total sales value, it could still do so by favoring bad actors or low-trust experiences.
    
    • The short-term metric improved but the long-term quality of the marketplace degraded which would eventually show up later in customer churn and lower trust in the platform
• Chris said this was the moment he realized the metric also needed a quality threshold. The right goal was not just price times quantity. It was price times quantity subject to a minimum level of marketplace quality and trust. It took him roughly nine months to get to that more complete formulation

Revenue Targets Are Not Good Goals

• Chris said one of the biggest mistakes founders make is treating the company’s top-line growth target as if it is specific enough to actually run the business. 
  
  • In his view, a goal like “grow revenue 2x” or “go from $25M to $50M” is fine as an objective, but it is far too high a level to be the thing the company actually manages against.
• Once you set that kind of top-line target, the real question is: what is the growth formula that gets you there?
  
  • Which specific growth pillars will drive that outcome
  • How much of the growth should come from each one
  • What has to improve operationally for those pillars to work
  • What constraints need to be held at the same time
    
    • He used DoorDash as an example. For a long period, one of the biggest drivers of growth was geographic expansion. So the real operating question was not just “grow faster”, it was: how much growth should come from geo expansion, how much more efficient should that expansion be than the last cohort, and what resource envelope should the team have to make that happen
    • In his view, that is where the real battle is won or lost - not in the high-level target itself, but in the next layer down where the company turns that target into a concrete, constrained growth plan.

Founders Should Name the Real Priority 

• Chris said one of the most common things he sees when talking to founders is that they say their top priority is “growth,” but have not actually made the next layer of decisions underneath that.
  
  • A pattern he sees often is that a founder says growth is the top priority then lists eight different things the company is doing but cannot answer what the true number-one priority is inside that set. They can’t explain how many people are actually working on it and cannot clearly define what success would look like
• In his view, that is not real clarity. It means the founder is still operating at too high a level. The company may feel busy and urgent but it is not actually aligned around the thing that matters most
• Chris said he does not like when founders respond to questions by saying they will let the team figure it out. His view is that leaders do need input from the team, but they still need to do the hard work of defining the real priority and shaping what success looks like
  
  • The founder should be able to answer:
    
    • what is our top priority
    • what specifically are we trying to achieve
    • how many people are actually focused on it
    • what would success look like in concrete terms

Tactic: Chris’ 70/30 Resource Allocation Framework

• Chris said one of the most important top-down things he does in goal setting is define a resource allocation framework upfront. He suggests a 70/30 split:
  
  • 70% of the company’s resources go to the main thing
  • 30% go to the next thing (the next S-curve you will climb)
• He said founders can change the exact percentages, but the principle matters a lot. If leadership does not allocate this upfront, the company will constantly get trapped in the same question: is the main thing more important, or is this new idea more important?
  
  • In the short run, the main thing always wins and as a result, the company starves the next S-curve and never builds its future businesses
• Chris said this was exactly why he liked making the allocation explicit. For example, at DoorDash, he might tell the team to grow Restaurants by a certain amount this quarter but also make clear that they were only getting 70% of the resources for that work. The remaining resources were protected for things like Grocery or Drive (new initiatives), even if the core team wanted to pull them back
  
  • He acknowledged this gets harder when the new businesses still need support from the core system. In those cases, he tries to keep the overlap as small and controlled as possible
• If a founder does not make these tradeoffs explicitly, the core business will naturally consume everything and the company will fail to invest in what comes next.

Goal-Setting Should Be Top-Down

• Chris believes leaders should set goals top-down. He said founders should not ask the team what the goal should be.
  
  • In his view, that process usually leads to watered-down goals. He described the failure mode of bottom-up goal setting: the finance team is nervous, the legal team is nervous, the product team does not think they can ship on time, and the result is a 5% growth target that everyone can agree on. Then the founder rejects it for being unambitious, and the process devolves into a doom loop where you end up being tops-down anyway, but after wasting time and goodwill.
• His view was that if the founder is going to end up pushing the goal upward anyway, they should just be honest and do that from the start.
• He described his own approach as:
  
  • Tell the team the goal
  • Tell them the resource constraint
  • Ask them to come back with a plan to achieve it
• Sometimes, he said, he literally just makes the number up - this is not random but based on his understanding of the business and what a strong stretch should look like
  
  • He might say, “you need to grow 20%,” even if the business is currently growing at some lower rate, and then the team’s job is to respond to that target, not negotiate it downward by default
• He emphasized that once you teach people what good goals look like, the best people on your team will come back with goals more ambitious than you would have set. At that point, you can step back and trust them

Constrain Goals With Resources

• Christopher stressed that when setting a top-down growth target, you must simultaneously constrain the resources available to achieve it. 
  
  • Do not just hand someone a 20% growth target and say "come back with a plan." They will come back asking for the goal to be the top priority for the entire company and for 400 new hires immediately.
• Instead, he says:
  
  • Here is the growth target
  • Here is the amount of people / dollars / resources you get
  • Come back with a plan to do it within those constraints
• That forces the team to make actual tradeoffs.
  
  • It also forces the founder to be good at the next stage of the conversation. Because when the team says it cannot be done, the founder has to push on the plan intelligently:
    
    • What about this path
    • What about that tradeoff
    • Have you tried this alternative
    • Why is that assumption fixed
• Chris said he still reserves the right to back down if the team really proves the target is too aggressive, but he wants that conclusion to come after pressure-testing the plan instead of as the team’s starting point

Example: How Constraints Led to Creating DoubleDash

• He gave a DoorDash example around trying to grow Grocery. The Grocery team might say: to grow Grocery, we need more new customers, then conclude: the best way to get those customers is to put more Grocery promotion on the homepage
  
  • But that would immediately create conflict with the Restaurants team, which also depends on homepage real estate. Now the company is stuck in a messy prioritization fight over a shared input
• Chris said that in situations like this, he prefers to step in and constrain the shared input directly. For the shared-resource team, he will define the allocation
  
  • For example: you must grow Restaurants by this amount, and grow the new business by that amount, within this resource envelope
• Then the shared-resource team is expected to optimize within that constraint rather than repeatedly escalating the tradeoff upward
• Once he does that, he goes back to the team owning the new business and says, effectively:
  
  • This is all you are getting from that shared resource, now go figure out another way to hit your goal without hurting the core business
  • That means he is still giving the team an output goal, but he is removing one of the obvious inputs and forcing them to experiment their way to another solution.
• He said this is exactly what led to the creation of DoubleDash.
  
  • The new verticals team needed another way to grow Grocery without cannibalizing restaurant GMV. They noticed that after customers placed a restaurant order, many of them kept reopening the app to check where the order was
  • That created a new surface where DoorDash could offer an add-on order without taking homepage inventory away from Restaurants. DoubleDash was originally invented to solve that specific output problem

Input vs. Output Goals

• Chris said that where possible, he prefers to set input goals rather than output goals. His reasoning is that input goals are often easier to manage directly.
  
  • If leadership understands which inputs actually drive the result and can verify that the connection is real, then those are often better operational levers than a distant output target
• But he also acknowledged that sometimes that is not possible. In those cases, the company may need to set output goals and then run more experiments underneath them to learn what the right input levers actually are
  
  • His broader point was that founders should not be dogmatic about one type of metric. They should use the kind of goal that best lets the team manage toward the business outcome they actually care about
• Chris said he generally finds input goals easier to measure and manage.
  
  • they give the team more immediate clarity on what to optimize
  • they are often more concrete
  • they reduce ambiguity in day-to-day execution
• But the tradeoff is that input goals can be wrong. The founder may think a given input should drive the result but it may turn out not to actually connect cleanly to the output that matters
  
  • Chris said that when he chooses to use an input goal, he often sees that as a risk he is personally taking as the founder or executive. He is choosing to simplify the team’s optimization problem even though he knows there is some chance the input is not perfectly connected to the real business outcome
• By contrast, output goals are more useful when the company does not yet know the right path and wants the team to go discover it. In those cases, the team has to experiment, find alternative levers, and prove what actually drives the result
• The choice between input goals and output goals is fundamentally a judgment call. His default view is that output goals can be risky because many different factors often contribute to the final result.
  
  • If you give a team a high-level output target, they may immediately latch onto the most obvious lever, but that lever may depend on shared resources, create internal conflict, or damage another part of the business

Finance Goals vs Real Stretch Goals

• Chris said another important nuance is that he often wants two layers of goals.
  
  • In his view, Finance will naturally gravitate toward goals that the company knows it can hit. Those may be useful for planning or forecasting but they are not necessarily the goals that will push the company forward
• So he liked having a more aggressive set of operating goals as well. These are the real stretch goals, the ones that may not be hit but that force experimentation, urgency, and creative problem-solving
• He said he was explicit with teams that this was okay. Missing one of these stretch goals was not inherently bad if the team ran strong experiments, learned quickly, and operated with urgency, that could still be excellent performance

Creating Accountability Through DRIs

• Chris said another key principle is that every important goal-setting process needs a clear DRI. That person should: own the goal-setting process for that work, make decisions, and be accountable for driving the plan forward
  
  • The DRI should not be allowed to hide behind “the team.” If they are leading the work, they own it
• He also said that every function involved in that work should share the same underlying outcome.
  
  • He used Finance as an example of where this often breaks down. Finance can drift into thinking its job is just to police cost and say no, but in Chris’s view, Finance should also be accountable for the actual business outcome
• His framing is: the team needs to hit the goal and hit it at the right cost / quality / efficiency level. If Finance thinks the plan is too expensive, then Finance should help build the alternative plan rather than just stand outside it and criticize it

Move Fast, but Make Sure You’re Running Up the Right Hill

• Chris said he is fundamentally obsessed with moving fast. He said there are two principles he talks about constantly:
  
  • focus on the customer
  • bias to action
• He described both as deeply shaped by Amazon, but said bias to action in particular has been one of the defining operating principles across his career. If something can be done today, do it today. If it can be done right now, do it right now
  
  • Chris said this was a major reason DoorDash ultimately pulled ahead of Uber in US food delivery. In his view, the simplest explanation is not that DoorDash had more money, more people, or some grand strategic advantage, it is that DoorDash moved faster
  • The company found many of the things that later looked brilliant precisely because it was moving quickly enough to discover them first
• At the same time, Chris said speed by itself is not enough. Moving quickly is only valuable if the company is headed up the right hill. If the company is sprinting in the wrong direction, that is not a virtue
  
  • When he says “measure twice, cut once,” he does not mean build a heavy decision process or delay action unnecessarily, he means leaders should spend just a bit more time thinking before committing the company to a path
• ● He described this as going away for a few hours (or a couple of days if needed) and really think through what the company is trying to do and what success would actually look like
• A small amount of extra thinking at the beginning can save a company from running very hard toward the wrong thing

2. The Importance of Good Data

Keeping Close to Execution Through Daily Data Reviews and a Weekly Business Review

• Chris said his default management instinct is to stay extremely close to the business through data. He described data as his lifeblood, and said the more frequent and the better the data, the more useful it is to him as an operator.
• His favorite format is daily. Every morning while at DoorDash he would wake up, make a cup of coffee, and sit down in front of a large daily report
  
  • He would often have new leaders do this with him at 7 AM so they could learn how he read the business
  • His goal was not to stare at data for its own sake, but to look for anomalies, insights, and things that were unexpectedly positive or negative. He would then email the DRIs with questions or suggestions.
• Chris said that over time this became an “insight machine.” Once he knew the business well enough, it became easy for him to see what looked different and what deserved follow-up

The Absence of Clean Analytics is Not an Excuse 

• Chris said that when he joins a company, one of the first things he does is make sure he has the people around him to build the operating system he wants. 
  
  • One part of that is finding the right strategy-and-operations type person who can help run planning, goals, and the broader management machine. 
    
    • In smaller companies, this often isn’t a formal role yet, so a good heuristic is a former consultant or highly organized operator who can help implement systems as you scale.
  • But the second, equally important part is finding the person who understands the data best and deciding whether that person is someone he can work with directly or whether he needs to work around them.
• In today’s world, this is something Chris would likely do with AI or agent tooling 
• His view is that if the company does not have the data foundation locked down, the leader is in trouble very quickly.
  
  • People start debating the numbers instead of debating the business
  • The company cannot see issues early enough
  • And operational problems stay hidden until they have already become expensive
• He said that for founders in particular, this is one of the areas where they have to change the conditions of the test if needed - if they cannot get the data they need, they are effectively doomed to fail as operators
• Chris does not passively accept whatever standard dashboard the data or metrics team already has. Instead, he starts by finding the smartest person in the company who really understands the data.
  
  • At DoorDash, he found someone who ran analytics and whom he thought was fantastic. He liked both her philosophy and the way she approached the problem. Once he trusted her, he asked for her best person and had that person build the daily report with him
  • If the existing data organization is not actually helping him get what he needs, he does not just accept that constraint.
    
    • For example, when he joined eBay, he felt that the analytics team’s job was more about controlling things than enabling operators. Instead of trying to fight that system indirectly, he identified the brightest data mind in the company and simply put him on his own team. He just wanted that capability directly attached to the business because once that person was with him, he could trust that the data foundation under his decisions was solid
• In the first week, he sits down with the person, he draws the report he wants, and he decides what sections it should have, what comparisons matter, and what he wants to see each morning
  
  • For example, he said he liked looking at eight days of data so that if he was reviewing a Monday, he could compare it directly with the previous Monday. He already had a strong instinct for the kinds of sections he wanted — for example, a merchant section — and then had the team build exactly that.
  • In an earlier-stage company, this is less about a formal report and more about forcing clarity early. In the first week, sit down with whoever owns the data (or do it yourself) and define the handful of metrics that matter, how they should be segmented, and what comparisons actually drive decisions. The goal is to establish a simple, consistent view of the business you can review regularly
• Today, with better AI tooling, he would likely do much more of this himself. Now he would mostly just ask for access to the data and build the thing directly
  
  • At the time, he still needed the right technical partner to pull the report together in the way he wanted

Example: How Chris Uses Daily Reports to Go Down to the Micro, Then Back Up to the Macro

• Chris walked through the way he used the report at DoorDash.
• One section looked at large merchant performance.
  
  • He would review major brands like McDonald’s, Chick-fil-A, Taco Bell, and others, then look at sales, subtotals, and week-over-week changes
  • At this level, he was looking for anything that did not belong, like a merchant newly breaking through, a merchant suddenly faltering, an unusual change that might signal a problem or opportunity
• But he said the section he liked even more was the one that ranked the busiest individual stores in the country. He acknowledged that at first this can seem like the wrong level of detail - why would a CEO care about the single busiest store in Philadelphia or Los Angeles? 
  
  • Chris’s point was that this is often where the real insight starts.
• He gave an example of seeing a Philadelphia Chick-fil-A unexpectedly high on the list.
  
  • When he dug in, it turned out the location had a very large service area and fewer nearby Chick-fil-A stores. That specific answer was not especially important, but it was still useful to understand why the anomaly existed
• A more interesting example was John & Vinny’s in LA, which suddenly appeared unusually high on the list. Chris said this triggered immediate curiosity because it was not normally one of the busiest stores in the country
  
  • He sent an email asking what had happened and the answer was that the team had run a special promotion or local tactic that dramatically exceeded expectations
• For Chris, that was exactly the point of the daily report.
  
  • spot the anomaly
  • ask why it happened
  • convert the local learning into a company-wide best practice
• He said in a case like that, the local team would then be invited to the next WBR to share what they learned with the broader leadership group.

Look At The System’s Edge Cases

• Chris said one of his strongest habits was to look at the edge of the system rather than only at aggregates.
• He gave quality as the clearest example. At DoorDash, quality was measured through things like lateness, incorrect items, and missing items
  
  • If you only look at aggregate averages, the team can improve the headline number while still starving the edge cases. So Chris would look specifically at the worst-performing tail of the distribution.
  • For example, orders that were more than 20 minutes late, then sort by the markets with the worst outcomes yesterday
• He said this was where much of the useful learning came from.
  
  • Valdosta, Georgia might show up unusually bad because of a freak snowstorm
  • Boston might show up because the marathon had disrupted delivery zones
  • A smaller market might reveal a structural problem with how the local area had been laid out or staffed
• In each case, Chris would send an email asking what happened. The point was not to punish the team for every anomaly, but to understand whether this was a one-off, a recurring operational pattern, or something DoorDash should build a more proactive system around
  
  • Chris also described using the same pattern in more financial and fraud-oriented parts of the business. At one point he had a section of the daily report showing the worst gross profit orders from the previous day.
    
    • In practice, many of these were fraudulent or otherwise clearly problematic orders. Every morning, he would review them and send emails to the relevant teams
    • This became so effective that it annoyed the incoming CFO who eventually started getting his team up at 6 AM just to get ahead of Chris’s emails.
    • Chris believes that if a leader starts looking at these issues every morning and asking questions, the team will improve quickly
  • Chris cautioned that because people know he is reading the report closely, they can overreact when he asks about something. A team may assume that anything he emails about at 7 AM has suddenly become the company’s top priority, so he said he has to be somewhat judicious about when he follows up and how he frames those questions, especially when he is new in the role
• If you only manage off averages, teams can hit the main number while leaving important failures untouched. By going to the edge, he forced the organization to solve the full problem, not just the easiest part of it
  
  • If leadership only says vaguely “make fraud better,” it is much easier for the issue to float around unresolved

3. The Weekly Business Review

Using The Weekly Business Review For Performance Against Goals 

• The WBR is the process people often associate most strongly with him, but he was clear that it only works if it is focused on the right thing. In his view, the WBR should be about performance against goals, not performance against whatever Finance has re-forecasted most recently.
• He gets frustrated when companies spend too much time on:
  
  • top-line aggregates
  • ARR dressing
  • comparisons to last year without context
  • long discussions about what competitors did last week
• He said all of that may matter at some level, but it is not the point of the WBR. The key question is: what did you say you were going to do, and are you doing it?
  
  • What experiments are you running?
  • What new actions are you taking to drive that goal?
  • Is it working?
• Chris disliked this so much that he said he eventually split out a separate “forecast WBR” for finance-oriented discussions and let Finance run that one. Then the real WBR could stay focused on what the company itself was doing to hit its strategic goals

Showing Your Work During the WBR

• Chris said one of the biggest anti-patterns in WBRs is when teams keep bringing the same content week after week just to act as though something happened.
• His standard was:
  
  • show your work
  • bring what is actually new this week
  • if you have nothing meaningful to say, then say less rather than padding the deck
• He wants the team to come in and explain:
  
  • what it is trying
  • why it is trying that
  • whether it is working
  • what it has learned
• Often, that means demos, experiment results, or concrete examples rather than abstract status updates.

How Chris Runs the WBR

• Chris said one thing that helped him a lot as a leader was the shift during the pandemic toward more written culture.
• Teams would write up the WBR materials in advance.
  
  • Chris would read them the day before, make one pass to write down his reactions, then make a second pass to highlight the most important questions he wanted to discuss live
• This was important to him because he hated the way many meetings devolved into going line by line through comments in a Google Doc.
  
  • In his view, that format does not distinguish between the one thing the company really needs to talk about and a bunch of small issues that can be handled offline
• Chris said very clearly that the WBR was his meeting.
  
  • He ran it
  • The DRI of the topic was expected to answer the questions
  • Others could contribute, but the meeting was not meant to be a vague egalitarian discussion with no clear driver
• For years, Chris resisted letting too many people into the WBR. He wanted to keep it small, be able to challenge people directly, and he did not want it to feel performative
  
  • Eventually, he gave up on that fight and let the meeting become much more open.
• In hindsight, he said that was the right decision. The WBR became a cultural moment for DoorDash
  
  • It helped teach the organization how the company actually thought and operated and it made the business review process more of a shared operating forum rather than a closed executive mechanism
• Chris said he generally prefers not to have Finance own the WBR. At DoorDash, he preferred to have a strategy and operations person run the mechanics of the meeting.
  
  • His concern was that Finance can tilt too far toward the controller mindset. While that mindset is valuable in the right context, it is not the right energy for the company’s main operating review
  • He wanted the WBR to be about driving the business, not just measuring it conservatively.

The WBR Is a Forum for Follow-Up, Help, and Accountability

• Chris said the WBR is not just a status meeting. It is a mechanism for action.At the end of discussions, there should be follow-up. 
• He said it is also important that teams feel they can ask for help in the WBR. It should not feel like a pure judge-and-jury setting. It should also be a place where teams can surface blockers, get input, and get help moving a goal forward
• It is also a strong accountability mechanism. Each initiative or area should have a visible red, yellow, or green status
  
  • The DRI’s name should be attached to it
  • People should not be allowed to hide behind “the team” or put ten names on the project
• Chris said he particularly disliked removing the DRI’s name from the page or listing everyone so that no one is clearly accountable

 Red Is Not Automatically Bad

• In his view, a red status is not automatically a bad thing. If the team took on something hard, ran experiments, learned a lot, showed urgency and creativity, then the effort may still have been highly successful, even if the numeric goal was missed
  
  • He said that in some cases he might even promote or highly rate a leader who missed the target, if the way they went about it was strong and the company learned a lot.
• What he does not want is the opposite:
  
  • People avoiding hard goals because they are afraid of getting a red mark or choosing only safe goals that protect optics instead of building the company
• His message to the team was that the best place to be is actually close to the hard goals. That is where people learn, grow, and that is how they learn to build a company like DoorDash

How Christopher Scales Himself

• Christopher described his approach to scaling himself across many teams using a plate-spinning metaphor. He thinks of each initiative or team as a plate spinning on a pole.
• His method for spinning a plate is to set up the goal, appoint a DRI, provide clarity, and then step back. He stays in touch through the WBR and daily report but is not involved in the day-to-day and is counting on the team to deliver.
• When a plate starts to wobble - a team misses its goal, the experiment flow is weak, the pace is too slow - Christopher intervenes directly. He called this the "Special Chris Project."

Example: The Special Chris Project

• When a team flounders for an extended period (e.g., six months), Chris elevates the initiative to a special project where he personally joins as a team member. 
  
  • His approach when dropping in: He meets with the team weekly and reviews daily operational data with them. He positions himself as a team member, not the president: "I want you to hide nothing from me. My job is to help you all succeed."
  • He retains the ability to put the "president hat" back on if the team needs help from the broader company.
• Chris shared an example from DoorDash. The DRI of a struggling initiative blamed the legal team for blocking progress. Christopher attended the meeting and discovered that the lawyer was right - the team's approach was genuinely a bad idea.
  
  • The real problem was that the team had reached an impasse and stopped. No one was asking: "What else could we do? Why exactly is this legally problematic? Are there alternative approaches that do not violate the constraint?"
• The team came back with new ideas. Chris also discovered the product person assigned to the initiative did not believe in it, so he "repotted" that person elsewhere and brought in someone who did.
  
  • The initiative was focused on making order fulfillment faster. Chris told the team specifically where to find the time savings and asked for one minute of improvement. They ended up delivering two minutes, which he described as a game-changer.
• The key to this approach is that it is temporary. The next quarter, Chris graduates the team and moves on to the next problem. This high-low oscillation is how he scales himself while still getting deep into the details when it matters.
  
  • A secondary benefit: when Christopher drops into a team five or six levels below him, he gets to evaluate the next generation of talent firsthand.

4. People Management

Reorgs Are Almost Never the Answer

• Chris said he is extremely reluctant to reorganize. The bar for him to approve a reorg is "off the charts high."
• He described the failure mode: everyone in a company believes that if only everyone reported to them, everything would be great. 
  
  • At Microsoft, the joke was: if you do not like the org you are in, wait six months, because there will be a reorg. Christopher said this was true and that an enormous amount of time was wasted on it.
• His position is not that reorgs are never necessary - they sometimes are - but that they are not the answer to most questions. If you have the right people, you can make any organizational structure work. 

Grounding 1:1s in the Person’s Actual Work 

• Christopher said he hates one-on-ones. His litmus test for whether he enjoys working with someone is whether he feels excited or drained when their one-on-one comes up on his calendar.
  
  • He acknowledged that eliminating one-on-ones entirely is a mistake. You have to meet with your people. But with 30 direct reports, one-on-ones can consume one to two full days per week, which is unsustainable.
• Christopher's solution is to restructure the one-on-one around the DRI's goals. Since most of his direct reports are DRIs running specific initiatives, the one-on-one becomes an extension of the WBR. 
  
  • The direct report shares things they would not say in the larger WBR forum: why they are off plan, what is going wrong, what they need help with. They provide written materials in advance and Chris and the direct report work the problem together.

• Chris said that one of the biggest step-function improvements in his management style came when he realized he needed to be much more explicit about connecting someone’s career development to the work they were already doing.
• His key insight was that career development and goal execution are the same conversation, not separate ones. Many direct reports think of career development as a distinct discussion, but Chris explicitly ties them together.
  
  • For example: a direct report's development area (identified in their review) is that they struggle to work effectively with the product and engineering organization. 
  • Christopher gives them a DRI assignment that requires exactly that cross-functional collaboration. 
  • In the one-on-one, they work through the blockers together: Why does the product person not want to do this? What is their motive? Have you figured that out yet?
• Sometimes Christopher has to get personally involved to diagnose whether the blocker is a personnel problem or a skills gap. But the coaching happens in service of the business goal, not as a separate agenda item.
• The result: by connecting career development to real, ongoing work, the dreaded "let's talk about career development" conversation disappears because it is happening every week as part of goal execution.

Creating Space for Vulnerable Conversations

• A founder asked how Chris handles one-on-ones that become a space for venting, complaining, or seeking motivation - what the founder described as "executive therapy."
• Chris said he has become more of a therapist over the course of his career and that he welcomes these conversations. He finds them an opportunity to be real about his own limitations and struggles.
  
  • Having seen most problems before makes it easier to share relevant experience with direct reports. When someone asks how to maintain work-life balance while building a company that is growing rapidly, he can share how he has tackled it and where he has struggled.
• He said the conversations that drain his energy are not the vulnerable ones but rather the ones that are not focused on being constructive - particularly interpersonal grievances with peers. 
  
  • Even those, however, are an opportunity to share examples and help people navigate lateral relationships.
• His overarching point was to create a safe space for these conversations. They are an important part of the manager-report relationship. Just do not let them replace the goal-oriented substance of the 1:1.

4. Leading Through Adversity

Retaining Talent During DoorDash's Hardest Days 

• DoorDash from 2017 to 2020 was one of the toughest companies to run. It was a distant number two. No one wanted to fund it. The market was crowded with Uber Eats, Instacart, Postmates, and Amazon. 
• Christopher said this is leadership 101: your job is to be the Pied Piper. You have to set the vision and be an optimist in the face of adversity.
  
  • He drew on his experience at prior companies. Microsoft had more money than everyone else circa 1998, but that did not mean Microsoft won every market it entered. 
  • He gave this framing to his team at DoorDash: just because Uber has more money and more people does not mean they win. Hard problems are good because incumbents cannot win just by showing up. DoorDash could out-execute them.
  • He pointed to the specific competitive dynamic: Uber was not spending his time on the restaurant business in 2017-2018. Meanwhile, Tony Xu and Chris Payne were personally visiting Cheesecake Factory and other key merchants. At the individual market level, DoorDash would win those relationships.
• Christopher acknowledged that not everyone stayed. Some people were deeply pessimistic - he described one employee constantly predicting doom after every Uber move. Some employees left and did not exercise their DoorDash options. 
  
  • His point was that not everyone will stay during dark periods, and leaders should not expect perfect retention. The job is to keep the people who believe and help the others see the reasons to believe, not to assume everyone will make the journey with you.
• When asked whether DoorDash had to make special compensation adjustments to retain people during that period, Chris said yes, the company did some of the normal things - refreshing grants, signing people up again, and using the fact that some employees were leaving options behind. 
  
  • But he was clear that he saw those as secondary. His view was that the real driver was belief over compensation engineering. 
  • Leaders had to convince people that the company could win, that the team knew why it was winning in certain places, and that there was a real playbook underneath the chaos. 
    
    • Once people started to see those local wins and understand why DoorDash was beating competitors in actual markets, morale became easier to sustain.

How Doordash Pitched Hires

• DoorDash lost 28-30% of its people during this period. When the external narrative was that DoorDash was dying, DoorDash instead pitched learning and personal growth, not certainty of outcome: 
  
  • You are going to learn an enormous amount.
  • You are going to get responsibility way beyond your years.
  • You are going to have a lot of fun.
  • Whether DoorDash wins or loses, this experience will accelerate your career faster than anything else you have ever done.
• Ultimately, the belief must be in the people, not just the idea. Christopher said he joined DoorDash because of Tony Xu - he liked him, thought he was great, thought he was humble, and was impressed that Tony was a mathematician tackling a deeply complicated logistics problem. 
  
  • The problem space appealed to Christopher's own brain: he described it as a puzzle, the same way Amazon had been.
• Chris said one of the broader lessons here is that founders and leaders are always selling. Recruiting, retaining talent, keeping morale up, and sustaining conviction all require leaders to keep selling the mission, the company, and the possibility of winning.
  
  • Selling was especially important because the period really was dark. Chris said there were genuine late-night conversations between him and Tony about running out of money and what the company was going to do. 
  • He emphasized that those moments are real but the more times you go through moments like that and survive them, the more conviction you build that a company can make it through.

DoorDash' Kept Morale Up By Making Local Wins Visible

• Christopher noted that DoorDash's city-by-city expansion model provided a natural source of morale even when the macro narrative was bleak.
  
  • The company might have been losing in aggregate market share or struggling to raise funding, but at the city level, DoorDash was beating Uber in Palo Alto, Houston, and Atlanta."
  • The playbook was working: DoorDash had more restaurant selection than anyone else, and quality was undeniably better.
    
    • Uber's problem was strategic: they had a higher defect rate, and with customers placing only five or six orders per month, every defect was felt acutely. Uber was spending more on marketing but had a leaky bucket. DoorDash was outperforming on quality and retention.
• Christopher said he was constantly selling this internal narrative to the team, even when external investors and commentators did not believe it.

5. Tony Xu's Leadership

Tony Xu's Two Greatest Strengths

• Chris, who has worked with Bill Gates, Jeff Bezos, and other prominent leaders, said Tony is "in the very, very, very top of the people that I've worked with in my career."
• Strength 1: Tony is both confident and humble simultaneously. He has conviction about what he is doing but enough humility about himself to know he could be wrong. This creates the conditions for employees to rise up and thrive.
  
  • Tony's humility creates an environment where the expectation is that employees will take ownership and make the company better. He is demanding and brilliant, so people must bring their A-game, but the company is not a dictatorship.
• Strength 2: selling ability. Tony can sell at an extraordinary level. Chris described a complementary division of labor: Tony handled the high-level selling - fundraising, partnerships, pitching - while Chris built the operating system and the product. They came together on software and product decisions.

• Christopher's broader insight for founders: find a partner who complements your strengths rather than duplicating them. Tony created the space for Christopher to operate with full authority, and Christopher built the systems that allowed DoorDash to out-execute every competitor.

‍