Extreme Dogfooding and Rapid Shipping Culture at Uber

Feel the visceral emotion of your end user by doing their exact job under real conditions.

Kansal drives and delivers 10-12 times per session, once or twice a month, to experience the dopamine of an offer, the frustration of an awkward passenger interaction, and the cost of every micro-inefficiency on earnings.

Why: Numbers and surveys flatten users into MAUs; only lived experience surfaces the emotional intensity that motivates teams to fix problems.

"until I get behind the wheel... what I miss is the visceral reaction that you get when something happens"

Turn every dogfooding session into a traceable artifact that forces accountability.

After each ride or delivery, Kansal screenshots flows, writes 40-page reports with fixes, tags owners, and tracks resolution in six-month OKRs (e.g., "fix 300 driver issues").

Why: Without documentation and numeric targets, dogfooding becomes performative; with them it scales across hundreds of employees.

"I take a lot of screenshots and then I come back and I write documents... I tag people because I know who works on what"

Minimize the cycle time from insight to code in production.

Institutional mantra is "ship, ship, ship"—not mindless speed, but ruthless reduction of decision latency. Daily stand-ups, 15-page weekend PRDs, and two-way-door decisions unblock teams.

Why: Documents and meetings don’t improve user lives; only shipped code does. Shorter cycles compound learning and judgment.

"you don't ship documents, you don't ship brainstorming meetings... What you ship is code in your product"

Leaders must visibly do the uncomfortable work they ask of others.

Kansal, CEO Dara Khosrowshahi, and execs personally drive; quarterly "Driving & Delivery Week" gamifies participation with prizes; OKRs guarantee resources for fixes even at the expense of pure growth projects.

Why: Culture sticks when it’s rewarded and resourced, not just preached.

"I want to set an example with my team... every leader is doing that as well"

Classify decisions as one-way or two-way doors and act accordingly.

Two-way-door choices (reversible) are made in the room during product reviews; one-way-door choices (irreversible) may escalate but still have explicit timelines.

Why: Most product delays come from intermediate alignment loops, not from building.

"you have to operate in a one-way door versus two-way door concept... if you get it wrong, it's okay. We can turn it back"

Live-demo the product on stage to force narrative clarity and pre-launch rigor.

Kansal insists on real, working demos for external launches; teams rehearse until flawless, creating pride and ensuring the story centers on user value, not slideware.

Why: Users care about their 10-minute experience, not the feature list; live demos prove the story and harden the product.

"no one actually really cares about the feature that you want to talk about... You have to tell a story... that story comes from actually showing the product in action"

Optimize for number of shipped product cycles, not prestige or title.

Early-career PMs should choose environments where they can complete 3-5 full cycles in 2-3 years; judgment emerges from the thousand micro decisions (button placement, copy, market roll-out), not five big strategies.

Why: Repetition under time pressure builds the intuitive "product sense" that AI can’t replace.

"go to a job where you can ship multiple products as fast as possible... what makes a great product manager is not five amazing strategic ideas... it's the thousand micro decisions"

Erase org boundaries and co-create instead of waiting for perfect specs.

Engineers are encouraged to whiteboard with PM/design and start building without a finalized PRD; Kansal openly critiques engineering, marketing, and ops work alike.

Why: Waiting for documents creates artificial bottlenecks; shared ownership speeds shipping.

"I hate... when they say, I can't do anything because I do not have a PRD... the best engineers... can have a white boarding session... and they should co-create"