WeDash: Mandatory Dogfooding as a Culture Governor
Make every employee do frontline work, then advertise it in interviews to self-select hires.
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 93%
DoorDash requires all employees, including executives, to perform deliveries at least four times a year. The obvious payoff is product empathy and a steady stream of found bugs. The non-obvious payoff is that the requirement acts as a 'governor' at the top of the hiring funnel: it is publicised during interviews, and candidates unwilling to do humble frontline work opt out before you ever have to reject them.
Origin
DoorDash's internal WeDash program, described by Keith Yandell. Yandell notes Airbnb ran a comparable 'everyone should host' program under Brian Chesky, which proved harder to enforce because not everyone can host.
Core principles
- 01Empathy for the customer is manufactured by doing their work, not by reading their tickets.
- 02A visible, slightly uncomfortable requirement is the cheapest hiring filter you own — it screens for humility before an application is submitted.
- 03The program must be genuinely universal, including the CEO and executives, or it becomes a status marker instead of a culture carrier.
- 04Frontline exposure must be routed into a fix channel or it decays into a photo-op.
How to run it
- 1
Pick the frontline job that IS your product
Choose the single operational role where the product's promise is actually delivered — for DoorDash, doing the deliveries. Not an adjacent or symbolic activity.
Pro tip If the core role is impractical for everyone (Airbnb's hosting), define an alternative of comparable humility — DoorDash lets people do customer support instead.
- 2
Set a mandatory floor, not an aspiration
Make it a required minimum cadence — DoorDash's is four times a year for all employees — rather than an encouraged option. Optional programs are done by people who already have the empathy.
Watch out 'Encouraged' dogfooding produces zero culture signal because non-participation carries no cost.
- 3
Build the fix channel before the first shift
Stand up a dedicated Slack channel for what people find on the frontline, and route findings to the owning team. Yandell says he almost always finds something broken; one WeDash shift surfaced a routing bug where the app calculated straight-line distance instead of road distance.
Pro tip Executives doing frontline shifts together with the functional owner (Yandell dashes with the head of Engineering) shortens the fix loop to one conversation.
Watch out Findings with no owner and no follow-up teach employees the program is decorative.
- 4
Announce it loudly during hiring
Be explicit in the interview process that this is expected of everyone. This is the governor: the engineer unwilling to drive fast food to a stranger self-selects out before you spend a loop on them.
Pro tip Frame it as a description of the culture, not a warning — the people you want will hear it as an attraction.
- 5
Have leadership over-participate visibly
Leaders should exceed the floor. Yandell dashes roughly monthly against a four-times-a-year requirement, and the CEO does customer support daily. Over-participation by the top is what stops the floor from being treated as a tax.
Watch out If executives are exempt or perform token shifts, the program inverts into evidence of hierarchy.
In the wild
On a WeDash shift with his eight-year-old daughter, Yandell was assigned a delivery of a sandwich and a coffee requiring an 18.5-mile drive — bad for the customer and bad for the dasher. His daughter insisted on calling Tony Xu directly. Xu picked up on the first ring, listened as she argued the coffee wouldn't be hot after 36 minutes, and thanked her for one of the most insightful pieces of feedback he'd received recently.
→ Before Yandell got home, Xu had emailed the product organisation naming the problem and proposing a fix, and the team was already working on it — the frontline-to-fix loop closing inside a single afternoon.
Dashing regularly, Yandell found the app was routing dashers by straight-line distance rather than by road, producing nonsensical assignments. He posted it into the WeDash Slack channel devoted to shift findings.
→ The routing logic was fixed — a defect surfaced by an executive doing the frontline job, not by a metrics dashboard.
Common mistakes
Making dogfooding optional
Voluntary programs are done by the people who least need them. The mandatory floor is what creates both the universal empathy and the hiring filter.
Hiding the requirement until after the offer
The governor effect only works if candidates hear about it during the interview process. Sprung on them at onboarding, it reads as a bait-and-switch and breeds resentment.
Collecting frontline findings with nowhere to send them
Without a channel and an accountable owner, shifts become performative. The reason WeDash generates fixes is that findings land in a dedicated channel that product teams action.
Is it for you?
Best for
Founders and executives at marketplace, logistics, or consumer-ops companies where a frontline role exists that employees can physically perform, and who want a culture filter that operates before the hiring decision.
Not ideal for
Deep-tech or B2B businesses with no accessible frontline role, regulated roles employees can't legally perform, or companies unwilling to have executives do the work first.
From the transcript
“we have a program called we Dash where four times a year all employees are required to go do deliveries”
“it's just about making people have empathy and get closer to the product”
“it takes a certain level of humility a certain amount of customer Obsession to even sign up for that”
From the episode
Leading with empathy
Keith Yandell (DoorDash, Uber)