Book SummaryClick, by Jake Knapp

1-Page Summary1-Page Book Summary of Click

Most new products fail because they’re built on the wrong foundation. Teams spend months debating what direction to take, lock onto an idea, and start building something before confirming whether anyone wants it. By the time problems become clear, course-correcting is expensive. In Click (2025), Jake Knapp and John Zeratsky argue that such waste is preventable—if you start by thinking about who your customer is, what problem they need solved, and what makes your solution better than what those customers are already using. Once you’ve articulated these core assumptions, you can test them quickly and cheaply.

Knapp and Zeratsky write from years of experience in the tech industry and venture capital. Knapp helped build Gmail, cofounded Google Meet, and created the “Design Sprint”—a five-day method for prototyping and testing new products—which he and Zeratsky documented in...

Click Summary The Foundation Sprint—and Why You Need One

Knapp and Zeratsky argue that every new product begins with a series of guesses about who the customer is, what problem they need solved, how to solve it, and why they’d choose a new solution over what they’re already using. What distinguishes projects that succeed from those that fail is whether the team articulates those guesses early enough to test them rigorously. Knapp and Zeratsky’s Foundation Sprint is aimed at making that happen.

In this section, we’ll explain the Foundation Sprint and the Founding Hypothesis it produces. We’ll look at a concrete example of one and make the case for why treating your opening strategy as something to be tested—not one you execute right away—leads to more successful products.

What a Product Needs to Click

A product clicks when it solves a problem for a customer—and does so better than the alternatives. Knapp and Zeratsky argue that this only happens when you create clarity about who you’re building for, what problem you’re solving, and what makes your solution worth adopting. Knapp and Zeratsky’s method for getting clear before you build anything is the Foundation Sprint:** a focused two-day workshop that produces a single...

Click Summary How to Run a Foundation Sprint

The Foundation Sprint takes place over two focused days with a small team of no more than five people, including the person with final decision-making authority (whom Knapp and Zeratsky call the Decider). The authors emphasize that everyone on the team needs to set aside all other work for the duration of the sprint: no meetings, no email, and no distractions.

Throughout the sprint, you’ll use a structured working method called “Note-and-Vote.” Instead of brainstorming aloud, each person writes their ideas silently, the group reviews them together, and everyone votes individually. This keeps good ideas from getting drowned out and produces sharper decisions more quickly.

The Hidden Cost of Waiting Your Turn

Knapp and Zeratsky’s three requirements—a small group, cleared calendars, and silent brainstorming—address a problem called “production blocking,” which is what happens to thinking when a group conversation imposes a mandatory queue. A spoken discussion requires that only one person speaks at a time, which [puts everyone else in a holding...

Click Summary How to Test Your Founding Hypothesis

By the end of the Foundation Sprint, you should have a completed Founding Hypothesis—a statement like, “For parents of young children, our email digest service is better than group text threads because it’s organized and reaches every family member.” But a hypothesis is only as good as the evidence behind it. In this section, we explain why testing your hypothesis before development begins is essential, what kind of testing Knapp and Zeratsky recommend, and how to recognize when your solution is ready to build.

Remember That Your Hypothesis Is a Set of Guesses

Knapp and Zeratsky emphasize that even though it’s easy to lose sight of after two focused days of strategic work, every slot in your Founding Hypothesis is a prediction, and predictions can be wrong. For example, you might have identified the right customer but the wrong problem. The points of differentiation you chose might matter less to real customers than you expected. Your chosen approach might work in theory but fall short in practice. Until you test it, you don’t know which parts of your hypothesis are right.

The risk you incur by skipping the testing stage is significant. Teams that commit directly to...

Shortform Exercise: Draft Your Founding Hypothesis

Think about a project you’re currently working on or one you’re considering launching. Knapp and Zeratsky argue that the most important thing you can do at the start is to make your core assumptions explicit. Work through the questions below to draft your Founding Hypothesis.

Who is your target customer? Describe them in plain language, as specifically as you can.

Shortform Exercise: Plan Your First Test

Knapp and Zeratsky argue that a Founding Hypothesis is a set of educated guesses, and that the biggest mistake teams make is treating those guesses as a plan rather than a starting point for experimentation. Use the questions below to think through how you’d begin testing yours.

Which element of your Founding Hypothesis feels most uncertain? Is it whether you’ve correctly identified the customer, whether the problem is painful enough to make them switch to a new solution, or whether your differentiation will actually matter to people?