The Value — and Limits — of Eating Your Own Dog Food
DoorDash engineers will find out what it’s like schlepping food around town. But it might not help.
In software development, there’s a phenomenon known as “eating your own dog food.”
“Dogfooding,” as it’s often called, is the act of using your own software — even as you’re building it — so you can figure out what’s good and bad about it. When you eat your own dog food, you become your own customer: You more quickly spy the bugs, the hassles, and the missing features.
I’ve spoken to all sorts of software engineers and entrepreneurs who’ve dogfooded their products. It was often incredibly eye-opening for them. For example, my friend Fred Benenson worked for Kickstarter in the early days; he would run his own campaigns, discover firsthand the problems faced by users of Kickstarter, and then help to build fixes. (I wrote about this for Wired a few years ago.)
I thought about dogfooding this week when a debate erupted over the delivery-service DoorDash.
At an all-hands meeting, DoorDash executives announced that all employees would have to do at least one delivery a month. The company had previously run this program, called “WeDash,” but put it on hold during the early pandemic. Now they were…
