Build fast. Learn fast. Hack a shortcut to your solution.
Google Ventures piloted a popular rapid prototyping method for digital hackathons described as a “Sprint“.
Ampersand has adapted this method, adding user research as a vital input. Apply this shortcut method to quickly iterate an innovation prototype, moving beyond just digital, to the physical and conceptual (e.g. new business models).
Pre-Game: Research & Setup
SET THE STAGE
- Define the challenge.
- Field the right team.
- Reserve and setup space.
- Conduct primary user research and secondary assessment of competition and alternatives. (Recommended supplemental activity)
Module 1: Target
DON’T JUMP UNTIL YOU KNOW WHERE YOU WANT TO LAND
- Run structured discussions; create a path for the sprint.
- Set a long-term goal.
- Map the challenge.
- Experts share insights.
- Present summary of user findings, competitive analysis and market scans. (Recommended supplemental activity)
- Pick a target: an ambitious but manageable piece of the problem that you can solve in one week.
Module 2: Sketch
SCRIBBLE YOUR IDEAS—MANY AND FAST
- Discover user needs, frustrations with current state and alternatives.(Recommended supplemental activity)
- Inspire with a review of existing ideas to remix and improve.
- Each person sketch, following a 4-step process that emphasizes critical thinking over artistry.
- Recruit customers that fit target profile (for feedback in Module 5.
Module 3: Storyboard
TELL YOUR STORY
- Review your stack of solutions. Critique each solution, ranking the best chance for achieving your long-term goal.
- Storyboard scenes from your sketches. Weave them into a step-by-step plan for your prototype.
Module 4: Prototype
- Design the customer-facing surface of your product or service as a low resolution prototype just sufficient for customer test and feedback.
- Confirm Day 5 schedule.
- Review the prototype.
- Design research protocol – setting, observation, recording, interview script.
Module 5: Test
WATCH, LISTEN AND LEARN
- Observe customer reactions to prototype.
- Interview customers.
- Document pain points and design changes.
- Chart your development schedule.
Know if you’re a “Go”.
Learn faster. Save time and money. Give decision makers a tangible concept for a more concrete commitment. Know if you’re a go.