yeti logo icon
Close Icon
contact us
Yeti postage stamp
We'll reply within 24 hours.
Thank you! Your message has been received!
A yeti hand giving a thumb's up
Oops! Something went wrong while submitting the form.

Yeti Presents: “The Definitive Guide to Product Design Sprints”

By
Tony Scherba
-
August 30, 2016

San Francisco, CA - August 30, 2016 - Today, San Francisco-based design and development firm, Yeti LLC (www.yeti.co), has released “The Definitive Guide to Product Design Sprints,” a comprehensive, start-to-finish manual covering why, when, and how a proper design sprint can take an idea to tested prototype in just five days.

The Definitive Guide to Product Design Sprints” begins with identifying a key component: who should be involved in a product design sprint, and how they should be involved. “Hosting a strategy workshop ahead of the sprint has been crucial in getting our clients and our team on the same page,” said Yeti founder and CEO, Tony Scherba. “Once we’ve nailed down who needs to be involved in which part of the process - from creative input to buy-in at certain stages - we can move into the work.”

Yeti identifies 5 Stages to Design Sprints, which take place across five business days: Understand, Diverge, Converge, Prototype, and Test. “It’s best to start a design sprint on a Monday so you have everything time-boxed into one week,” added Scherba.

In addition to outlining the 5 Stages to Design Sprints, Yeti also includes key tips to make the overall experience a successful one, including:

“The point of the sprint isn’t to build a working prototype; it’s to prove a concept,” said Scherba. “Once you’ve done that, you can move into a more formalized prototyping process.” For more information on prototyping, check out Yeti’s “Ultimate Guide to Prototyping Success”.

To download the whitepaper, please visit “The Ultimate Guide to Product Design Sprints.”

For more research and resources from Yeti, please visit the company’s Resources page.

Tony Scherba is a CEO + Founding Partner at Yeti. Tony has been developing software since high school and has worked on digital products for global brands such as Google, MIT, Qualcomm, Hershey’s, Britney Spears and Harmon/Kardon. Tony’s writing about innovation and technology has been featured in Forbes, Huffington Post and Inc. At Yeti, Tony works on strategy, product design and day to day operations, hopping in and working with the development teams when needed.

Connect with Tony on LinkedIn

You Might also like...

When Software Projects Go Wrong: How to Recover From (and Avoid) Technical Debt

You hired a team to build your app, but instead of a reliable product you got endless crashes, bugs, and mounting costs. You’re stuck in technical debt - here’s how to save your project and get back on track.

Has Technical Debt Stalled Your Software Project? Here's How to Fix It

Experiencing bugs, missed deadlines, and constant delays? Your software project could be stuck technical debt. Here's how to spot the warning signs, fix the root problems, and get development back on track!

What's an MVP? : Read THIS Before Building Your App

When you have a brilliant idea for an app, it can be incredibly tempting to dive straight into building the full-featured version right away. But if you want to give your idea the best possible shot at success, there’s a smarter, safer way to start: with a Minimum Viable Product, or MVP.

Browse all Blog Articles

Ready for your new product adventure?

Let's Get Started