Knapp, J., Zeratsky, J., & Kowitz, B. (2016). Sprint: How to solve big problems and test
new ideas in just five days. Simon and Schuster.
Chapter 1.
Blue Bottle Coffee: From Potting Shed to Premium Online Experience — A Case Study
in Design Sprints
In 2002, James Freeman, a professional clarinetist, made a life-changing decision to leave
behind his music career and pursue a passion for freshly roasted coffee. Dissatisfied with
the availability and quality of roasted beans—especially the lack of roast dates on
packaging—he started roasting his own beans at home. Cooking coffee in a potting shed,
James sold freshly brewed coffee out of a cart named Blue Bottle Coffee at farmers' markets
across Berkeley and Oakland, California. His meticulous attention to detail, quality, and
warm hospitality quickly won customer loyalty.
By 2005, James opened his first permanent Blue Bottle café in a friend's San Francisco
garage, laying the foundation for what would become a celebrated chain. Over the next few
years, Blue Bottle Coffee expanded to several locations, including Oakland, Manhattan, and
Brooklyn. The brand earned a reputation for some of the best coffee in the country, paired
with knowledgeable and friendly baristas. The cafés themselves had a distinctive
aesthetic—natural wooden shelves, tasteful ceramic tiles, and a simple, elegant sky-blue
logo—that conveyed a welcoming yet refined atmosphere.
Despite this success, James Freeman’s ambition extended beyond physical cafés. He
envisioned delivering the same Blue Bottle experience—freshly roasted coffee and attentive
hospitality—to customers anywhere, including those living far from the physical store
locations. To support this expansion, Blue Bottle raised $20 million in October 2012 from
Silicon Valley investors, notably GV (Google Ventures). A key goal for this capital infusion
was to create a robust, intuitive online store that could replicate the café experience digitally.
However, Blue Bottle was not a technology company, nor did James have the expertise to
drive such an online transformation alone. To navigate this challenge, GV introduced the
concept of a five-day design sprint—a concentrated, cross-disciplinary workshop aiming to
rapidly prototype and test solutions. The sprint team included key stakeholders: James
Freeman (founder and decision-maker), COO, CFO, communications manager, customer
service lead, a programmer, executive chairman Bryan Meehan (an experienced retail
entrepreneur), and GV sprint facilitators Braden Kowitz and John Zeratsky.
The sprint began with a critical focus: how to help first-time online customers purchase
coffee beans without any prior knowledge of Blue Bottle or access to barista
recommendations. This was a tough user journey due to the similarity of coffee bags and the
complexity of coffee origins and flavor profiles, which many customers found confusing.
,The team initially considered organizing the coffee selection by geographic region—Africa,
Latin America, Pacific—as customary in the industry. Yet surprisingly, even the coffee
enthusiasts on the team admitted limited understanding of these regional distinctions. This
revelation shifted attention to Blue Bottle’s café practice: baristas ask customers, "How do
you make coffee at home?" based on which they recommend beans tailored to the brewing
method.
Armed with this insight, the sprint aimed to translate this personal interaction to an online
setting. The team mapped the buyer’s journey, created numerous sketches proposing
different website structures and interfaces, and then narrowed down fifteen ideas to three
promising prototypes:
1. Café-like Design: A literal replication of the café ambiance online, featuring wooden
shelves and aesthetic touches designed to echo physical store warmth.
2. Text-rich Design: Heavy on detailed copy and explanations, mimicking the in-depth
barista conversations that help customers learn about coffee beans.
3. Brew-Method Organization: A functional approach that posed the question, "How do you
make coffee at home?" upfront, letting users select beans best suited for their brewing
equipment (e.g., French press, Chemex).
Instead of choosing a single concept, the team built clickable prototypes using Keynote
slides—no back-end programming—to simulate real websites. On the final sprint day, they
organized customer interviews in which users navigated these prototypes alongside
competitor sites disguised with fake names. Observing the users’ reactions facilitated a rare
window into actual customer behavior and preferences.
Customer feedback was illuminating. The café-like design, though visually appealing to the
team, was perceived by users as “cheesy” and untrustworthy. On the contrary, prototypes
emphasizing brew-method organization and detailed textual explanations both performed
well. Users appreciated the straightforward guidance of the brew-method approach and
engaged willingly with the textual content, which conveyed Blue Bottle’s expertise and
hospitality authentically. They trusted and felt comfortable buying coffee through these
interfaces.
This sprint provided Blue Bottle’s leadership with confidence and clarity. They realized that
replicating café aesthetics was less important than delivering clarity, trust, and helpful
guidance online. With this validated direction, Blue Bottle quickly built a new website
incorporating these insights. The results were striking: online sales doubled in the months
following the launch. Capitalizing on this momentum, Blue Bottle acquired a coffee
subscription service to facilitate recurring deliveries and expanded their web offerings further.
Broader Lessons and Implications
The Blue Bottle design sprint illustrates the power of rapid, focused experimentation when
tackling complex challenges. Whether designing software, retail experiences, or even
industrial products, no challenge is too large for a sprint if approached wisely. By focusing on
“solving the surface”—the customer-facing experience—teams can quickly validate core
assumptions before investing heavily in backend infrastructure or full product development.
,This approach reduces risk and accelerates learning by narrowing in on the most important
customer problems and questions. Blue Bottle demonstrated how an intense, one-week
sprint involving diverse expertise—from finance to customer service to programmers—can
align stakeholders, spark creativity, and produce actionable results that accelerate growth.
Additionally, the case highlights the value of humility and openness during design:
well-intentioned assumptions (such as expert understanding of coffee regions) may not hold
true for actual users, even those involved in product development. Adapting by listening
carefully and leveraging real user insights leads to more effective, trusted solutions.
Summary of Key Steps in the Sprint Process
- Assemble a decision-maker-led, cross-functional team focused on a key customer
scenario.
- Map out the user journey and define success metrics.
- Generate and sketch multiple, diverse solution concepts.
- Use structured voting and decision-making to select prototypes.
- Build low-fidelity, clickable prototypes to simulate the product experience.
- Conduct blind, comparative user tests to gather objective feedback.
- Analyze results and prioritize designs that build trust, are easy to use, and align with the
brand.
- Launch a solution promptly and iterate based on ongoing data.
In conclusion, Blue Bottle’s journey from a potting shed startup to a digitally-savvy coffee
company exemplifies how traditional hospitality values combined with modern design
methodology can create a winning product experience. The use of design sprints enabled
the company to minimize uncertainty, engage critical voices, and launch an online platform
that customers loved and trusted—paving the way for sustained success in an evolving retail
landscape.
, Chapter 2
Sprint Team Foundations and the Role of the Decider
A successful sprint depends on two foundational elements: securing a committed Decider
and building a small, focused, and diverse sprint team. The Decider is the person with real
decision-making authority over the project—this could be the CEO, project owner, or product
manager—who ensures that the sprint’s results guide the project’s future rather than being
overturned afterward.
Convincing the Decider to join the sprint is often the first challenge. To persuade them,
emphasize:
- Rapid Progress: The sprint generates a realistic prototype in just one week, offering
visible, tangible results quickly.
- It’s an Experiment: Position the sprint as a trial run that provides data on whether the
process is effective.
- Clear Tradeoffs: Outline what meetings or work items the team will miss during the sprint
week and why this focused interruption is worthwhile.
- Focus on Quality: Explain that the sprint allows the team to concentrate intensely on one
challenge, improving quality over spreading efforts thinly across many tasks.
If the Decider cannot attend the sprint full-time, it is crucial they participate in key moments:
Monday (sharing insights and framing the problem), Wednesday (helping select the idea to
prototype), and Friday (observing customer reactions). In such cases, the Decider must
officially designate one or more delegates with clear decision-making authority to be present
for the rest of the sprint. Without Decider support—even in cameo form—it is a strong
warning sign the project may be a poor fit.
Assembling the Sprint Team
Once the Decider's commitment is secured, assemble the sprint team that will work together
full-time throughout the sprint week. The ideal team size is **seven people or fewer**. Larger
teams tend to slow processes and dilute focus, while smaller teams enable fast, efficient
decision-making and collaboration.
The team should blend core roles with domain experts. Core roles often include engineers,
designers, and product managers—people who understand the product and can build or
prototype solutions directly. Experts are invited to bring specialized knowledge and external
perspectives that are vital to shaping realistic, customer-focused prototypes.
Typical roles and their contributions include:
- Decider: Holds final authority on choices and project direction. May be CEO, founder, or
product manager.
- Finance Expert: Explains financial implications, budget constraints, and business viability.
- Marketing Expert: Crafts messaging, customer communication strategies, and ensures
brand consistency.
- Customer Expert: Has direct customer insights from sales or support roles, bringing
stories and context.
new ideas in just five days. Simon and Schuster.
Chapter 1.
Blue Bottle Coffee: From Potting Shed to Premium Online Experience — A Case Study
in Design Sprints
In 2002, James Freeman, a professional clarinetist, made a life-changing decision to leave
behind his music career and pursue a passion for freshly roasted coffee. Dissatisfied with
the availability and quality of roasted beans—especially the lack of roast dates on
packaging—he started roasting his own beans at home. Cooking coffee in a potting shed,
James sold freshly brewed coffee out of a cart named Blue Bottle Coffee at farmers' markets
across Berkeley and Oakland, California. His meticulous attention to detail, quality, and
warm hospitality quickly won customer loyalty.
By 2005, James opened his first permanent Blue Bottle café in a friend's San Francisco
garage, laying the foundation for what would become a celebrated chain. Over the next few
years, Blue Bottle Coffee expanded to several locations, including Oakland, Manhattan, and
Brooklyn. The brand earned a reputation for some of the best coffee in the country, paired
with knowledgeable and friendly baristas. The cafés themselves had a distinctive
aesthetic—natural wooden shelves, tasteful ceramic tiles, and a simple, elegant sky-blue
logo—that conveyed a welcoming yet refined atmosphere.
Despite this success, James Freeman’s ambition extended beyond physical cafés. He
envisioned delivering the same Blue Bottle experience—freshly roasted coffee and attentive
hospitality—to customers anywhere, including those living far from the physical store
locations. To support this expansion, Blue Bottle raised $20 million in October 2012 from
Silicon Valley investors, notably GV (Google Ventures). A key goal for this capital infusion
was to create a robust, intuitive online store that could replicate the café experience digitally.
However, Blue Bottle was not a technology company, nor did James have the expertise to
drive such an online transformation alone. To navigate this challenge, GV introduced the
concept of a five-day design sprint—a concentrated, cross-disciplinary workshop aiming to
rapidly prototype and test solutions. The sprint team included key stakeholders: James
Freeman (founder and decision-maker), COO, CFO, communications manager, customer
service lead, a programmer, executive chairman Bryan Meehan (an experienced retail
entrepreneur), and GV sprint facilitators Braden Kowitz and John Zeratsky.
The sprint began with a critical focus: how to help first-time online customers purchase
coffee beans without any prior knowledge of Blue Bottle or access to barista
recommendations. This was a tough user journey due to the similarity of coffee bags and the
complexity of coffee origins and flavor profiles, which many customers found confusing.
,The team initially considered organizing the coffee selection by geographic region—Africa,
Latin America, Pacific—as customary in the industry. Yet surprisingly, even the coffee
enthusiasts on the team admitted limited understanding of these regional distinctions. This
revelation shifted attention to Blue Bottle’s café practice: baristas ask customers, "How do
you make coffee at home?" based on which they recommend beans tailored to the brewing
method.
Armed with this insight, the sprint aimed to translate this personal interaction to an online
setting. The team mapped the buyer’s journey, created numerous sketches proposing
different website structures and interfaces, and then narrowed down fifteen ideas to three
promising prototypes:
1. Café-like Design: A literal replication of the café ambiance online, featuring wooden
shelves and aesthetic touches designed to echo physical store warmth.
2. Text-rich Design: Heavy on detailed copy and explanations, mimicking the in-depth
barista conversations that help customers learn about coffee beans.
3. Brew-Method Organization: A functional approach that posed the question, "How do you
make coffee at home?" upfront, letting users select beans best suited for their brewing
equipment (e.g., French press, Chemex).
Instead of choosing a single concept, the team built clickable prototypes using Keynote
slides—no back-end programming—to simulate real websites. On the final sprint day, they
organized customer interviews in which users navigated these prototypes alongside
competitor sites disguised with fake names. Observing the users’ reactions facilitated a rare
window into actual customer behavior and preferences.
Customer feedback was illuminating. The café-like design, though visually appealing to the
team, was perceived by users as “cheesy” and untrustworthy. On the contrary, prototypes
emphasizing brew-method organization and detailed textual explanations both performed
well. Users appreciated the straightforward guidance of the brew-method approach and
engaged willingly with the textual content, which conveyed Blue Bottle’s expertise and
hospitality authentically. They trusted and felt comfortable buying coffee through these
interfaces.
This sprint provided Blue Bottle’s leadership with confidence and clarity. They realized that
replicating café aesthetics was less important than delivering clarity, trust, and helpful
guidance online. With this validated direction, Blue Bottle quickly built a new website
incorporating these insights. The results were striking: online sales doubled in the months
following the launch. Capitalizing on this momentum, Blue Bottle acquired a coffee
subscription service to facilitate recurring deliveries and expanded their web offerings further.
Broader Lessons and Implications
The Blue Bottle design sprint illustrates the power of rapid, focused experimentation when
tackling complex challenges. Whether designing software, retail experiences, or even
industrial products, no challenge is too large for a sprint if approached wisely. By focusing on
“solving the surface”—the customer-facing experience—teams can quickly validate core
assumptions before investing heavily in backend infrastructure or full product development.
,This approach reduces risk and accelerates learning by narrowing in on the most important
customer problems and questions. Blue Bottle demonstrated how an intense, one-week
sprint involving diverse expertise—from finance to customer service to programmers—can
align stakeholders, spark creativity, and produce actionable results that accelerate growth.
Additionally, the case highlights the value of humility and openness during design:
well-intentioned assumptions (such as expert understanding of coffee regions) may not hold
true for actual users, even those involved in product development. Adapting by listening
carefully and leveraging real user insights leads to more effective, trusted solutions.
Summary of Key Steps in the Sprint Process
- Assemble a decision-maker-led, cross-functional team focused on a key customer
scenario.
- Map out the user journey and define success metrics.
- Generate and sketch multiple, diverse solution concepts.
- Use structured voting and decision-making to select prototypes.
- Build low-fidelity, clickable prototypes to simulate the product experience.
- Conduct blind, comparative user tests to gather objective feedback.
- Analyze results and prioritize designs that build trust, are easy to use, and align with the
brand.
- Launch a solution promptly and iterate based on ongoing data.
In conclusion, Blue Bottle’s journey from a potting shed startup to a digitally-savvy coffee
company exemplifies how traditional hospitality values combined with modern design
methodology can create a winning product experience. The use of design sprints enabled
the company to minimize uncertainty, engage critical voices, and launch an online platform
that customers loved and trusted—paving the way for sustained success in an evolving retail
landscape.
, Chapter 2
Sprint Team Foundations and the Role of the Decider
A successful sprint depends on two foundational elements: securing a committed Decider
and building a small, focused, and diverse sprint team. The Decider is the person with real
decision-making authority over the project—this could be the CEO, project owner, or product
manager—who ensures that the sprint’s results guide the project’s future rather than being
overturned afterward.
Convincing the Decider to join the sprint is often the first challenge. To persuade them,
emphasize:
- Rapid Progress: The sprint generates a realistic prototype in just one week, offering
visible, tangible results quickly.
- It’s an Experiment: Position the sprint as a trial run that provides data on whether the
process is effective.
- Clear Tradeoffs: Outline what meetings or work items the team will miss during the sprint
week and why this focused interruption is worthwhile.
- Focus on Quality: Explain that the sprint allows the team to concentrate intensely on one
challenge, improving quality over spreading efforts thinly across many tasks.
If the Decider cannot attend the sprint full-time, it is crucial they participate in key moments:
Monday (sharing insights and framing the problem), Wednesday (helping select the idea to
prototype), and Friday (observing customer reactions). In such cases, the Decider must
officially designate one or more delegates with clear decision-making authority to be present
for the rest of the sprint. Without Decider support—even in cameo form—it is a strong
warning sign the project may be a poor fit.
Assembling the Sprint Team
Once the Decider's commitment is secured, assemble the sprint team that will work together
full-time throughout the sprint week. The ideal team size is **seven people or fewer**. Larger
teams tend to slow processes and dilute focus, while smaller teams enable fast, efficient
decision-making and collaboration.
The team should blend core roles with domain experts. Core roles often include engineers,
designers, and product managers—people who understand the product and can build or
prototype solutions directly. Experts are invited to bring specialized knowledge and external
perspectives that are vital to shaping realistic, customer-focused prototypes.
Typical roles and their contributions include:
- Decider: Holds final authority on choices and project direction. May be CEO, founder, or
product manager.
- Finance Expert: Explains financial implications, budget constraints, and business viability.
- Marketing Expert: Crafts messaging, customer communication strategies, and ensures
brand consistency.
- Customer Expert: Has direct customer insights from sales or support roles, bringing
stories and context.
