A skills course raises the skill of people who then go back to their own desks. A five-day sprint answers one question while the decision-maker and a customer are still in the room. Match the purchase to the gap you actually have, or you will pay for a week that cannot do the job.
Blue Bottle Coffee is the public case. After a funding round, founder James Freeman spent a week with Jake Knapp, John Zeratsky and Braden Kowitz of Google Ventures, as Wired's excerpt from Sprint records. The online store would take time and money, and the team did not know where to start. Freeman brought the programmer, the chief operating officer, the chief financial officer, the communications manager, customer service lead Serah Giarusso and executive chairman Bryan Meehan. The hard case was a new customer choosing among similar bags of beans, with no barista to help.
A week that ends on a customer
Giarusso asked what the cafes already did when a customer was unsure. Freeman's answer was the question baristas ask: how do you make coffee at home? On Wednesday the group had fifteen sketches. Freeman, as the decision-maker, picked three. On Thursday they built three fake stores in Keynote, realistic enough to click and too thin to be a real site. On Friday, customers called the beautiful cafe-style version cheesy and not trustworthy. They responded to a store organised by brew method, and to a text-heavy version that sounded, in one shopper's words, like people who knew coffee. A few months later the site launched, and online sales growth doubled.
The same excerpt names when the format earns the calendar. The stakes are high and the build will consume time and money, which was Blue Bottle. The deadline is close, which was Savioke preparing a delivery robot for a hotel pilot. A third case is a project that has stalled. David Lowe, a vice president at pump maker Graco, faced an industrial pump that would take eighteen months and millions of dollars. The team tested a brochure of the new features in sales conversations, before the engineering spend.
Where the tools belong in the week
An AI design sprint keeps that spine. Research notes, extra options and the facade of a prototype can move faster with the tools. The customer reaction and the decision stay with the people who will live with the result. Keep that reaction as the thing the week has to produce, and hold a model comparison for a separate purchasing conversation. The AI design sprints workshop is built to finish on a tested concept and a call to proceed, change or stop. What the team should hold on the way out is in what an AI design sprint should leave you able to ship. How one corporate team spends the days is in how a Melbourne team runs an AI design sprint.
AI design sprint versus a training course
Collective Campus builds high-performance teams for the AI world. Use a training course when the gap is skill across a group. People need reps on the tools, a check they can repeat, and a workflow they will run next week in their own jobs. Use a sprint when you can name one question, one decision-maker who can kill an idea, and customers or operators who can react before the week ends. Blue Bottle could clear a founder, a finance lead and a customer-service lead for five days because a wrong store would be expensive. A course would have sent that same group back to their jobs with a method and no shopper in the room.
If the team has never used the tools, give them a short skills session first so the sprint week is spent on the question. If you cannot name the customer and the person who may stop the work, wait until you can. Without those two, the week tends to keep every idea alive. Bring the question in one sentence and the name of the decision-maker. We will shape the days around that test.
