Why Canva Killed Pitch Decks for Working Prototypes

Key Takeaways

• Canva banned internal pitch decks, UX roadmaps, and milestone documents in favor of immediate, working software spikes.
• Small teams build functional prototypes with AI tools to test real customer interactions before asking for budget or headcount.
• Stripe president John Collison points out that traditional tech companies overengineer their product development loops with unnecessary planning.
• Obrecht made this prototype-first mindset a non-negotiable interview filter, rejecting product managers who rely on traditional planning frameworks.

The Death of the 30-Slide Roadmap

For years, standard tech orthodoxy dictated how new features got built. A product manager ran weeks of user research, drafted a PRD, assembled a slide deck with chronology and resource estimates, and pitched leadership for headcount.

Canva threw that entire process away.

“We used to come with a customer research, here is a pitch deck that includes the why, how we're going to build it, the chronology of how we're going to build it, how many resources it's going to take, the different milestones, etc., etc. Like that's kind of the old way,”▶ 32:12 Canva COO Cliff Obrecht explained.

The problem with the old way is simple: documents create the illusion of certainty while delaying actual user contact. Teams spend weeks arguing over slide decks and abstract wireframes before writing a single line of production code. By the time users touch the feature, the team has already sunk months of budget into unverified assumptions.

Stripe president John Collison agreed with the shift, noting that founders and product leaders regularly trip over their own process: “I think people really overcomplicate and overengineer the product development loop.”▶ 30:29

Small Teams, Fast Spikes, Real Feedback

Instead of asking for permission with slides, Canva teams build immediate software spikes. AI tools now allow engineers and designers to assemble interactive prototypes in hours rather than quarters.

“AI has totally transformed the way we do product and our expectations of that product loop,”▶ 32:03 Obrecht said. “Now it's come to me with a prototype and the smallest team possible to get a first spike out and get customer feedback and then if it's doing well, we can scale it from there.”▶ 32:24

This approach changes internal economics. When building a prototype costs days instead of quarters, you do not need executive committees to greenlight experimentation. The team ships a minimal spike directly to real users. If customer data shows actual engagement, leadership allocates more engineers. If the spike flops, Canva discards the code without having wasted six months of engineering roadmaps.

This model also exposes a hard truth about corporate hiring. Product managers trained at mature tech companies often specialize in consensus-building, slide creation, and timeline management. When dropped into a rapid prototyping environment, those skills become dead weight.

Obrecht now uses this distinction as a primary hiring filter. “Now, we filter it in the interview process,”▶ 32:55 he said. Canva asks candidates directly how they approach building software. If a candidate starts outlining multi-stage approval processes and deck-driven roadmaps instead of building quick prototypes, Canva passes on them immediately.

What to Do With This

Cancel your next feature kickoff deck. Assign two people: one designer and one engineer: to build a live, clickable spike by Friday using AI coding tools. Test it with five customers next Monday before you write a single milestone document.