Key Insights on Creating Products That “Click”

Click!

Click: How to Make What People Want synthesizes a systematic methodology for developing successful products, services, and projects that “click” with customers. The core premise is that most new products fail due to a flawed, chaotic development process, which leads to a colossal waste of time, money, and energy. The proposed solution is a structured, focused system built around “sprints”—intensive, time-boxed work sessions that compress months of strategic debate and validation into a matter of days or weeks.

The centerpiece of this system is the Foundation Sprint, a two-day workshop designed to establish a project’s strategic core. On Day 1, teams define the Basics (customer, problem, advantage, competition) and craft their Differentiation. On Day 2, they generate and evaluate multiple Approaches before committing to a path. The output is a testable Founding Hypothesis, a single sentence that encapsulates the entire strategy.

Once a hypothesis is formed, the methodology advocates for rapid validation through Tiny Loops of experimentation, primarily using Design Sprints. These are weeklong cycles where teams build and test realistic prototypes with actual customers. This process allows teams to see how customers react and de-risk the project before investing in a full build, transforming product development from a high-stakes gamble into a series of manageable, low-cost experiments. The ultimate goal is to find what resonates with customers, pivot efficiently, and build with confidence.

——————————————————————————–

The Core Problem: Why Most New Products Fail

The source material identifies a fundamental challenge in product development: turning a big idea into a product that people genuinely want is exceedingly difficult. The conventional approach to launching new projects is described as chaotic, inefficient, and reliant on luck.

• The “Old Way”: This process is characterized by endless meetings, debates, political maneuvering, and the creation of documents that are rarely read. Strategy development can take six months or more, often culminating in a decision based on a hunch, leading to a long-term commitment of resources with no real validation.
• Cognitive Biases: Human psychology exacerbates the problem. Teams are tripped up by cognitive biases such as anchoring on first ideas, confirmation bias, overconfidence, and self-serving biases. These biases lead to a “tunnel vision” that prevents objective analysis of alternatives.
• The Cost of Failure: The result is that most new products don’t “click”—they fail to solve an important problem, stand out from competition, or make sense to people. This failure represents a significant waste of time, energy, and resources.

The Solution: A System of Sprints

To counteract the chaos of the “old way,” the document proposes a systematic, focused approach centered on “sprints.” This method replaces prolonged, fragmented work with short, intense, and highly structured bursts of collaborative effort.

Lesson 1: Drop Everything and Sprint

The foundational principle is to clear the calendar and focus the entire team on a single, important challenge until it is resolved. This creates a “continent” of high-quality, uninterrupted time, which is more effective than scattered “islands” of focus.

• Key Techniques for Sprinting:
  • Involve the Decider: The person with ultimate decision-making authority (e.g., CEO, project lead) must be part of the sprint team. This ensures decisions stick and eliminates the need for time-wasting internal pitches.
  • Form a Tiny Team: Sprints are most effective with five or fewer people with diverse perspectives (e.g., CEO, engineering, sales, marketing).
  • Declare a “Good Emergency”: The team should use “eject lever” messages to signal to the rest of the organization that they are completely focused and will be slow to respond to other matters.
  • Work Alone Together: To avoid the pitfalls of group brainstorming (which favors loud voices and leads to mediocre consensus), sprints utilize silent, individual work followed by structured sharing, voting, and debate.
  • Get Started, Not Perfect: The goal is not a perfect plan but a testable hypothesis that can be refined through experiments.

——————————————————————————–

The Foundation Sprint: Building a Strategic Core in Two Days

The Foundation Sprint is a new format designed to establish a project’s fundamental strategy in just ten hours over two days. It provides clarity on the core elements of a project and culminates in a Founding Hypothesis.

Day 1, Morning: Establishing the Basics

The sprint begins by answering four fundamental questions to create a shared understanding of the project’s landscape. The primary tool for this is the Note-and-Vote, a process where team members silently generate ideas on sticky notes, post them anonymously, vote, and then the Decider makes the final choice.

Lesson 2: Start with Customer and Problem

The most successful teams are deeply focused on their customers and the real problems they can solve. This requires moving beyond jargon-filled demographics to plain-language descriptions of real people and their challenges.

“It’s hard to make a product click if you don’t care about the person it’s supposed to click with.”

• Example (Google Meet): The customer was “teams with people in different locations,” and the problem was that “it was difficult to meet.”

Lesson 3: Take Advantage of Your Advantages

Teams should identify and leverage their unique advantages, which fall into three categories:

• Capability: What the team can do that few others can (e.g., world-class engineering know-how).
• Insight: A deep, unique understanding of the problem or the customer.
• Motivation: The specific fire driving the team, which can range from a grand vision to frustration with the status quo.
• Example (Phaidra): The startup combined deep expertise in AI (Capability), real-world knowledge of industrial plants (Insight), and a drive to reduce energy waste (Motivation).

Lesson 4: Get Real About the Competition

A successful strategy requires an honest assessment of the alternatives customers have.

• Types of Competition:
  • Direct Competitors: Obvious rivals solving the same problem (e.g., Nike vs. Adidas).
  • Substitutes: Workarounds customers use when no direct solution exists (e.g., manual adjustments in a factory before Phaidra’s AI).
  • Nothing: In some cases, customers are doing nothing about a problem. This is a risky but potentially high-reward opportunity.
• Go for the Gorilla: Teams should focus on competing with the strongest, most established alternative (e.g., Slack positioning itself against email).

Day 1, Afternoon: Crafting Radical Differentiation

With the basics established, the focus shifts to creating a strategy that sets the solution far apart from the competition.

Lesson 5: Differentiation Makes Products Click

Successful products don’t just offer incremental improvements; they create radical separation by reframing how customers evaluate solutions.

• The 2×2 Differentiation Chart: This visual tool is used to find two key factors where a new product can own the top-right quadrant, pushing competitors into “Loserville.” The axes should reflect customer perception, not internal technical details.
  • Example (Google Meet): Instead of competing on video quality or network size, the team differentiated on “Ease of Use” (just a browser link) and being “Multi-Way,” creating a new framework where they were the clear winner.

Lesson 6: Use Practical Principles to Reinforce Differentiation

To translate differentiation into daily decisions, teams create a short list of practical, actionable principles.

• “Differentiate, Differentiate, Safeguard”: A recommended formula is to create one principle for each of the two differentiators and a third “safeguard” principle to prevent unintended negative consequences.
• Example (Google): Early principles like “Focus on the user and all else will follow” and “Fast is better than slow” were not vague platitudes but concrete decision-making guides that reinforced Google’s differentiation.
• The Mini Manifesto: The 2×2 chart and the project principles are combined into a one-page “Mini Manifesto” that serves as a strategic guide for the entire project.

Day 2: Choosing the Right Approach

The second day is dedicated to ensuring the team pursues the best possible path to executing its strategy, rather than simply defaulting to the first idea.

Lesson 7: Seek Alternatives to Your First Idea

First ideas are often flawed. Before committing, teams should generate multiple alternative approaches to force a more measured decision. This “pre-pivot” can save months or years of wasted effort.

• Example (Genius Loci): The founders’ first idea was a GPS-based app. By considering alternatives like a website and physical QR-code signs, they realized the app was a “fragile” solution. They ultimately chose the more robust website-and-sign combination, which proved successful.

Lesson 8: Consider Conflicting Opinions Before You Commit

To evaluate options rigorously, teams should simulate a “team of rivals” by looking at the approaches through different lenses.

• Magic Lenses: This technique uses a series of 2×2 charts to plot the various approaches against different criteria. This makes complex trade-offs visual and easier to debate.
  • Classic Lenses: Customer (dream solution), Pragmatic (easiest to build), Growth (biggest audience), Money (most profitable).
  • Custom Lenses: Teams also create lenses specific to their project’s risks and goals.
• Example (Reclaim): The AI scheduling startup used Magic Lenses to evaluate three potential features. The exercise revealed that “Smart Scheduling Links,” an idea that was not initially the team’s favorite, consistently scored highest across all lenses. They built it, and it became their fastest-growing feature.

——————————————————————————–

From Hypothesis to Validation

The Foundation Sprint does not produce a final plan but rather a well-reasoned, testable hypothesis. The final phase of the methodology is about proving that hypothesis through rapid experimentation.

Lesson 9: It’s Just a Hypothesis Until You Prove It

A strategy is an educated guess until it makes contact with customers. Framing it as a hypothesis encourages a mindset of learning and adaptation, helping teams avoid the “Vulcan” trap—becoming so attached to a belief that they ignore conflicting evidence, as astronomer Urbain Le Verrier did.

• The Founding Hypothesis Sentence: All the decisions from the sprint are distilled into one Mad Libs-style statement:

Lesson 10: Experiment with Tiny Loops Until It Clicks

Instead of embarking on a long-loop project (which takes a year or more), teams should use “tiny loops” of experimentation to test their Founding Hypothesis quickly.

• Design Sprints as the Tool for Tiny Loops: The recommended method is the Design Sprint, a five-day process to prototype and test ideas with real customers.
  • Monday: Map the problem.
  • Tuesday: Sketch competing solutions.
  • Wednesday: Decide which to test.
  • Thursday: Build a realistic prototype.
  • Friday: Test with five customers.
• The Power of Prototypes: Prototypes allow teams to get genuine customer reactions and test core strategic questions in days, not years. This allows for hyper-efficient pivots before significant resources are committed.
• When to Stop Sprinting: A solution is ready to be built when customer tests show a clear “click”—unguarded, genuine reactions of excitement, where customers lean forward, ask to use the solution immediately, or try to pull the prototype out of the facilitator’s hands.

Study Guide for “Click”

This study guide provides a review of the core concepts, methodologies, and case studies presented in the source material. It includes a short-answer quiz with an answer key, a set of essay questions for deeper analysis, and a comprehensive glossary of key terms.

——————————————————————————–

Short-Answer Quiz

Instructions: Answer the following ten questions in two to three sentences each, based on the information provided in the source context.

1. What are the three essential characteristics of a product that “clicks” with customers?
2. What is the primary goal of the two-day Foundation Sprint?
3. Explain the concept of “working alone together” and why it is preferred over traditional group brainstorming.
4. What are the three distinct types of “advantages” a team can possess, as outlined in the text?
5. According to the source, what does it mean for a product to be “competing against nothing,” and what are the risks associated with this situation?
6. What is the purpose of creating a 2×2 differentiation chart, and what is the ideal outcome for a project on this chart?
7. Describe the “Differentiate, differentiate, safeguard” formula for creating practical project principles.
8. What is the purpose of the “Magic Lenses” exercise performed on Day 2 of the Foundation Sprint?
9. Why is a project’s strategy referred to as a “hypothesis” rather than a “plan,” and what cognitive biases does this mindset help overcome?
10. Explain the concept of “tiny loops” and how they contrast with the “long loop” of a traditional product launch or Minimum Viable Product (MVP).

——————————————————————————–

Answer Key

1. A product that “clicks” solves an important problem for a customer, stands out from the competition, and makes sense to people. These elements must fit together like two LEGO bricks, creating a simple, compelling promise that customers will pay attention to.
2. The primary goal of the Foundation Sprint is to create a “Founding Hypothesis” in just ten hours over two days. This process helps a team gain clarity on fundamentals, define a differentiation strategy, and choose a testable approach, compressing what would normally take six months of chaotic meetings into a short, focused workshop.
3. “Working alone together” is a method where team members generate ideas and proposals silently and in parallel before sharing and voting. It is preferred over group brainstorming because it produces more higher-quality solutions, ensures participation from everyone regardless of personality, and leads to faster, better-considered decisions by avoiding the pitfalls of groupthink.
4. The three types of advantages are capability (what a team can do that few can match, like technical know-how), motivation (the specific reason or frustration driving the team to solve a problem), and insight (a deep understanding of the problem and customers that others lack).
5. “Competing against nothing” occurs when customers have a real problem, but no reasonable solution exists yet, so they currently do nothing. This is the riskiest type of opportunity because it is difficult to overcome customer inertia, but it can also be the most exciting if the new solution offers enough value.
6. A 2×2 differentiation chart is a visual tool used to state a project’s strategy by plotting it against competitors on two key differentiating factors. The ideal outcome is to find differentiators that place the project alone in the top-right quadrant, pushing all competitors into the other three quadrants (referred to as “Loserville”), thus making the choice easy for customers.
7. The “Differentiate, differentiate, safeguard” formula is a method for writing three practical project principles. The first two principles are derived directly from the project’s two main differentiators to reinforce the strategy, while the third is a “safeguard” principle designed to protect against the unintended negative consequences of a successful product.
8. The “Magic Lenses” exercise uses a series of 2×2 charts to evaluate multiple project approaches through different perspectives, such as the customer, pragmatic, growth, and money lenses. This structured argument helps the team consider conflicting opinions and make a well-informed decision on which approach to pursue without getting into political dogfights.
9. A strategy is called a “hypothesis” because, until it clicks with customers, it is just an educated guess that is intended to be tested, proven wrong, and updated. This mindset helps overcome cognitive biases like anchoring bias (loving the first idea) and confirmation bias (seeking only data that confirms a belief), encouraging a scientific process of learning and adaptation.
10. “Tiny loops” are rapid, experimental cycles, such as one-week Design Sprints, where teams test prototypes with customers to get feedback before committing to building a product. This contrasts with a “long loop,” which is the year-or-more timeline it typically takes to build and launch even a Minimum Viable Product (MVP), making it too slow for effective learning.

——————————————————————————–

Essay Questions

Instructions: The following questions are designed for longer-form answers that require synthesizing multiple concepts from the source material. No answers are provided.

1. Describe the complete system proposed in the text, from the initial Foundation Sprint through multiple Design Sprints. Explain how each stage addresses specific challenges in product development and how the ten key lessons are integrated into this overall process.
2. Using the case study of Phaidra, analyze how the startup embodied the principles of defining advantages, using “tiny loops,” and testing a Founding Hypothesis. How did their sprint-based approach allow them to de-risk their ambitious project before fully building their AI software?
3. The text uses the story of astronomer Urbain Le Verrier and his search for the planet Vulcan as a cautionary tale about cognitive biases. Explain the specific biases Le Verrier fell prey to and detail how the methodologies of the Foundation Sprint and Design Sprint are explicitly designed to counteract these human tendencies.
4. Compare the strategic challenges faced by Nike in the movie Air with those faced by the startup Genius Loci. How did each entity use differentiation and the evaluation of alternative approaches to craft a winning strategy against very different types of competition?
5. The author states, “Differentiation makes products click.” Argue why differentiation (covered in Day 1 of the Foundation Sprint) is the most critical element for a project’s success, more so than choosing the right approach (covered in Day 2). Use examples like Google Meet, Slack, and Orbital Materials to support your argument.

——————————————————————————–

Glossary of Key Terms

Term	Definition
Advantage	A unique strength a team possesses, composed of three elements: Capability (what you can do that few can match), Insight (a deep understanding of the problem and customers), and Motivation (the specific reason or frustration driving you to solve the problem).
Basics	The foundational questions addressed on Day 1 of the Foundation Sprint: defining the target Customer, the Problem to be solved, the team’s unique Advantage, and the strongest Competition.
Click	The moment a product and customer fit together perfectly. A product that “clicks” solves an important problem, stands out from the competition, and makes sense to people.
Cognitive Biases	Predictable patterns of mistakes humans make when thinking, such as Anchoring bias (falling in love with the first idea) and Confirmation bias (seeking only data that confirms our beliefs). Sprint methods are designed to counteract these.
Competition	The alternatives a customer has to a product. This includes Direct competitors (similar products), Substitutes (work-arounds), and “Do nothing” (customer inertia).
Decider	The person on the sprint team responsible for making final decisions on the project. Their presence is mandatory for a sprint’s decisions to be effective and stick.
Design Sprint	A five-day process for solving big problems and testing new ideas. It involves mapping a problem, sketching solutions, deciding on an approach, building a realistic prototype, and testing it with customers. It serves as the primary method for testing a Founding Hypothesis.
Differentiation	What makes a product or service radically different from the alternatives in the customer’s perception. It is the essence of a strategy and the reason a customer will choose a new solution.
Foundation Sprint	A two-day, ten-hour workshop designed to create a team’s foundational strategy. It compresses months of debate into a structured process that results in a testable Founding Hypothesis.
Founding Hypothesis	A single, Mad Libs-style sentence that distills a team’s complete strategy: “For [CUSTOMER], we’ll solve [PROBLEM] better than [COMPETITION] because [APPROACH], which delivers [DIFFERENTIATION].” It is an educated guess intended to be tested.
Long Loop	The extended timeframe (often a year or more) required to build and launch a real product, including a Minimum Viable Product (MVP). This lengthy cycle makes learning from real-world data slow and expensive.
Magic Lenses	A decision-making exercise using a series of 2×2 charts to evaluate multiple project approaches from different perspectives (e.g., customer, pragmatic, growth, money). It facilitates a structured argument to help a team make a well-informed choice.
Mini Manifesto	A document created at the end of Day 1 of the Foundation Sprint that combines the project’s 2×2 differentiation chart and its three practical principles. It serves as an easy-to-understand guide for future decision-making.
Minimum Viable Product (MVP)	A simpler version of a product that is just enough to be useful to customers, launched to test product-market fit. The text argues that even MVPs typically constitute a “long loop.”
Note-and-Vote	A core sprint technique for “working alone together.” Team members silently write down ideas on sticky notes, post them anonymously, and then vote on their favorites before the Decider makes a final choice.
Practical Principles	A set of three-ish project-specific rules designed to guide decision-making and reinforce differentiation. They are practical and action-oriented, not abstract corporate values.
Prototype	A realistic but non-functional fake version of a product created rapidly (often in one day) during a Design Sprint. It is used to test a hypothesis with customers without the time and expense of building a real product.
Skyscraper Robot	A metaphor from the movie Big for a product idea that focuses on company metrics (like market share) or creator ego, rather than what is actually fun or useful for the customer.
Tiny Loops	Short, rapid cycles of experimentation, like a one-week Design Sprint, that allow a team to test a hypothesis with a prototype and get customer reactions quickly. This allows for hyperefficient pivots before committing to a long development cycle.
Work Alone Together	A core collaboration principle in sprints where individuals are given time to think and generate ideas in silence before sharing them with the group. It is designed to produce higher-quality ideas and avoid the pitfalls of group brainstorming.
2×2 Differentiation Chart	A visual tool consisting of a two-axis grid used to map a project’s key differentiators against the competition. The goal is to define axes that place the project alone in the top-right quadrant.

Contact Factoring Specialist Chris Lehnes