Cycle-Time Is the Enemy (Ship Ship Ship)
The gap between knowing something is good and users seeing it is your biggest enemy — attack the decision time, not the work time.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 4
- Confidence
- 93%
A shipping philosophy built on the observation that only shipped code has impact — documents, meetings, and Figma designs don't. The core lever is cycle time: the time from 'we know this is a good thing' to 'our users see it.' Kansal notes the actual work (writing requirements, designing, coding) is time well spent; the waste is the align/discuss/regroup-next-week time in between, and that's what you compress.
Origin
Sachin Kansal's operating motto at Uber, which colleagues repeatedly cited as 'ship ship ship.' He traces its roots to lessons from failure at Palm about speed and urgency.
Core principles
- 01You don't ship documents, meetings, or Figma designs — you ship code in the product
- 02Ship ship ship is not mindless shipping; it applies once you know you're solving a real problem
- 03The work itself is well spent; the waste is the decision latency between work steps
- 04Classify decisions as one-way or two-way doors to set the right speed
How to run it
- 1
Confirm you're solving a real problem
Establish that the work matters and solves an actual user problem — this is the precondition that separates deliberate shipping from mindless shipping.
Watch out Ship-ship-ship applied to work you haven't validated is just mindless shipping.
- 2
Attack the between-steps decision latency
Identify time lost to aligning, discussing, deferring decisions, and 'let's regroup in two weeks.' The requirements/design/code time is fine; the inter-step delay is the target.
Pro tip Use recurring product reviews and force decisions to come out of them rather than deferring.
- 3
Classify the decision: one-way vs two-way door
If it's a two-way door (reversible), make the call quickly — try to make a good one, but if it's wrong you can turn it back. Reserve deliberation and executive review for genuine one-way doors like a massive launch.
Pro tip Most decisions are two-way doors; treating them as one-way is where teams bleed cycle time.
- 4
Step in to unblock when stalled
When a team is stuck in a loop of good and not-so-good ideas with nothing being decided, a leader can go hands-on to catalyze a decision — set a stake in the ground people can agree or disagree with.
Pro tip Keep this an exception, not the rule — otherwise you have no time for hiring, reviews, or your other job.
Watch out If you're writing PRDs to unblock teams every week, that's a signal of a deeper process problem.
In the wild
A risky, high-stakes driver-facing concept had accumulated ~20 conversations, brainstorms, and documents but no clear answer on what to actually ship. One Sunday night Kansal spent two hours writing a 15-page PRD saying 'this is my stake in the ground, agree or disagree.'
→ The product eventually shipped was at least 50% different from what he wrote, but the document catalyzed the team to converge on a shippable endpoint.
Coming out of Covid with a severe driver shortage and no shortage of ideas but a cycle-time problem, Kansal declared the cycle time would be 24 hours and ran daily standups for ~6 months to unblock decisions.
→ Uber shipped a lot, and over 9-12 months rebuilt driver/courier supply; that funnel work is still paying off, with the network roughly doubling to ~8 million drivers and couriers.
Common mistakes
Mistaking activity for shipping
Documents, brainstorming meetings, and Figma designs feel like progress but have no impact on the end user; only code shipped into the product does.
Making a leader intervention the norm
Kansal is clear that writing an unblocking PRD or running daily standups every week means something is broken — done routinely it consumes the leader's capacity for hiring, performance reviews, and their actual role.
Is it for you?
Best for
Product and engineering leaders whose teams are bottlenecked on decisions and alignment rather than on execution capacity
Not ideal for
Genuinely irreversible one-way-door launches that warrant slower, executive-level deliberation
From the transcript
“you don't ship documents. You don't ship brainstorming meetings. You don't even ship designs in a Figma. What you ship is code in your product.”
“My biggest enemy is the cycle time of we know it is a good thing all the way to our users seeing it. You have…”
“you have to operate in a one-way door versus two-way door concept”
“this is my stake in the ground we can completely change it but this is the product we will ship agree or disagree”
From the episode
Why Uber’s CPO delivers food on weekends
Sachin Kansal