Innovation sprint: plan

An innovation sprint is a short, focused burst of creative work — usually one to two weeks — where a team moves from a fuzzy "wouldn’t it be great if..." idea to a working prototype. The sprint only works if the team does careful planning first. Bad planning means the team argues about direction, duplicates effort, or builds something nobody wanted. Good planning means every member knows the problem, the goal, the idea, the tools, and their own milestones before the first line of code or first sketch is made.

Step 1: Define the real problem

Most teams rush to a solution before they understand the problem. A real problem has three parts: (1) a specific group of people (the USER) who (2) experience a frustration or gap (the PAIN) and (3) currently have no good solution (the GAP). A vague problem like "people waste food" becomes a real problem when you say: "Kids at a day camp who bring packed lunches throw away roughly half their meal because there is no way to reheat it and cold food is unappetizing." You can now design for THAT.

Step 2: Identify the user

Every solution has a primary user — the person who will actually use what you build. Write one short "user profile": their age or role, what they are trying to do, and what gets in their way. If you are designing a study app, the user might be "a Grade 6 learner who wants to check practice due-dates without scrolling through a messy group chat." Knowing your user stops the team building features that only the designer would find useful.

Step 3: Frame a clear goal

A clear goal answers: what will you build, for whom, and what success looks like. Use the pattern: "We will build [THING] for [USER] so that [OUTCOME]." Then add a measurable success criterion: "We will know it worked if [METRIC]." Example: "We will build a browser extension for learners so that overdue practice is flagged in red. We will know it worked if a friend can use it without any instructions from us." A good goal rules out dozens of irrelevant features and focuses the sprint.

Step 4: Brainstorm without criticism

The brainstorm phase has one rule: no idea is too silly to say out loud. Criticism during brainstorming kills ideas before they can be developed. Write EVERY suggestion on a sticky note or shared doc. Go for quantity first — ten rough ideas beat one polished one at this stage. After ten minutes of open brainstorming, group similar ideas and then vote: each person gets three votes to put on their favorite notes. The top-voted cluster becomes your starting idea.

Step 5: Pick a feasible idea

The best idea is not always the most impressive — it is the one you can actually finish in the time you have. Rate each idea on two scales: IMPACT (how much does it help the user?) and FEASIBILITY (can we build it with the tools and skills we have?). A simple 2x2 grid works: put ideas in the High Impact / High Feasibility quadrant first. Avoid the "amazing but impossible" quadrant; you can always build a bigger version later.

Step 6: List tools and skills needed

Once you have chosen your idea, make a T-chart: on the left, the tools and skills you already have; on the right, the tools and skills you still need. This gap list tells you what to learn, what free resources to find, or which teammate to ask. Common tools for school sprints include: Figma (design), Scratch or Python (coding), Google Slides (presentation), Canva (graphics), and Google Sheets (data). Knowing the gap early stops the team hitting a wall on day three of a five-day sprint.

Step 7: Split work and set milestones

A milestone is a checkpoint: a specific piece of work that must be done by a specific day. Good milestones are small enough to complete in one sitting. Bad milestones are vague: "work on the app" is not a milestone. Good milestones: "By Tuesday: paper sketch of three screen layouts. By Wednesday: working login screen in Figma. By Thursday: one coded button that opens the practice list. By Friday: demo ready." Each team member owns at least one milestone so that no one coasts and no one is overloaded.