From Design Sprints
to Proof Sprints

How Bottle Rocket is helping its clients battle project ambiguity and move faster with even greater clarity.

Bottle Rocket Dallas Innovates Silver Sponsor

“Will this reliably integrate with our app?”

“Would users even want to use this feature?”

“How will we notify users?”

Simple questions, at face value. But any seasoned product or project manager knows there are no such luxuries. These inquiries could have sweeping implications for the duration and cost of a project. Even a simple “yes” or “no” can be followed by a storm of follow-up questions that cast a fog over future estimations or derail a feature set entirely.

At Bottle Rocket, we utilize a proven methodology to help clients investigate the unknowns and get answers in as little as one week. Our Proof Sprint methodology — a process for solving and testing ideas in as little as five days — is inspired by Google’s Design Sprint. Although the two processes are similar, one key difference is that Bottle Rocket’s Proof Sprints are specifically designed to answer questions beyond experience design (XD) and always begin with a hypothesis and end with a proof where Google’s Design Sprints center around XD.  Whether the result is accepting or rejecting the hypothesis, the exercise can provide key insights into a major project without pulling valuable resources from other teams.

4 TYPES OF PROOF SPRINTS

We’ve identified four types of Proof Sprints, each covering distinct project challenges and providing answers where our clients need them the most:

Foresight: As the name implies, a foresight Proof Sprint is forward-looking. It takes into account OS updates, upcoming technologies or trends in mobile, as well as digital services, to rapidly prototype a new offering or to find out how the new tech meshes with existing technologies.

Feature: These sprints test assumptions around new features in a product or roadmap. The outcome of a feature sprint might even find that a feature needs to be reduced, rethought, or possibly even removed.

Focus: A focus sprint is similar to a feature sprint but is based around the product’s user or workflow. As such, focus sprints work to reduce friction and improve efficiencies within the application.

Feasibility: A feasibility sprint is the most tactical Proof Sprint. The ultimate goal is to find out, “Does this work?” Does this SDK work in that technology stack? Does this database technology hook into this front-end tech via that API? Rather than making assumptions, a feasibility sprint quickly offers a definite answer on whether a technology approach works or not.

Photo provided by Bottle Rocket

The result of a Proof Sprint can range from proof-of-concept for an idea, a prototype for a challenging spot within a project, or even shutting off a path the project was heading down because the sprint uncovered the idea wasn’t going to work. Proof Sprints aren’t intended to just validate an idea – knowing when to stop pursuing an idea can save valuable work hours and investments exploring possible solutions.

While every Proof Sprint is different, each follows a five-step template that is typically executed over a five-day workweek and includes a combined team from Bottle Rocket and client stakeholders.

  • Mapping the scope of the sprint, determining what success looks like and how the topic of the sprint impacts the customer.
  • Sketching and hands-on micro solutioning using whiteboards, sticky notes and 3×5 cards followed by looking at, discussing, and voting on the results.
  • Determining which of the sketched solutions move forward and modifying them to meet project requirements.
  • Actually building a prototype from the sketches that moved forward in the sprint.
  • Testing with a series of actual users.

Photo provided by Bottle Rocket

BUILT FOR RESULTS

Many things can be simplified through collaboration and uninterrupted thinking – which often is hard for fast-moving teams to accomplish. Roadblocks can cause projects to stall, or maybe six months into a project an issue arises that seems impossible to overcome. By leveraging Bottle Rocket’s Proof Sprint methodology, we are able to help our clients gain understanding quickly and with certainty in a matter of five days rather than what could take up to six months to uncover. It’s always less expensive to fail fast rather than to fail slowly. One Bottle Rocket client has even cited that via our Proof Sprint methodology, they were able to uncover more insights in just two days of the process than they had been able to on their own over the course of three months.

Proof Sprints have proven to be very effective in a variety of engagements across a range of industries and clients. Through Proof Sprints, we have investigated the optimal way to present information to a listener that is driving or traveling in an automobile. We have worked with a retailer to better understand their in-store customer flow, ultimately proposing more than forty ideas to optimize customer experiences and created four prototypes to test. Some clients have leveraged Proof Spints to test backlogged innovation ideas and validate them with users while others have examined the feasibility of integrating new technologies with mobile devices.

“Proof sprints are just another technique that’s consistent with our values, our culture and the way that we work. We love that our clients look to us to help them overcome these obstacles, and ultimately help them be more successful on their daily journeys,” said Monte Masters, SVP Solutions and Delivery.

Get on the list.
Dallas Innovates, every day. 

Sign up to keep your eye on what’s new and next in Dallas-Fort Worth, every day.

One quick signup, and you’re done.   
View previous emails.

R E A D   N E X T

Comments are closed.