What is the difference between a product manager and a project manager?

The accountability line

Ask what each person fails at. A product manager fails when the team ships something customers don't want. A project manager fails when a committed delivery slips without warning or mitigation.

Those are different failures with different skills attached, and they can occur independently. Shipping precisely on schedule something nobody needed is a product failure and a project success.

Quibi as the illustration

Quibi executed. The app was built, the content slate was produced, the launch happened on time with enormous funding behind it. By project standards it was a success.

What was missing was the product question — whether anyone wanted premium short-form video on a phone-only app with no sharing. Excellent delivery of an unvalidated bet produces an expensive, well-run failure, and the schedule can look green throughout.

Where they overlap in practice

At small scale the same person does both, and that's fine — coordination for one team is a few hours a week. The trouble starts when scale grows and the delivery load quietly consumes the discovery time. The calendar fills with status, dependencies and unblocking, all urgent, all visible, while the customer conversations quietly stop happening.

That's the moment to add a delivery role, not because the PM can't run a schedule, but because the two jobs compete for the same hours and only one of them has a deadline attached.

Choosing which you want to be

If you're energised by shipping complex things reliably, project management is a real craft and undersold. If you're energised by deciding what's worth shipping and living with being wrong, that's product. Neither is a stepping stone to the other.