So, we brainstorm a product, iterate through ideas, build lo-fi wireframes, then hi-fis, a prototype or two, and then launch it. Seeing the process through is rewarding, exciting — and we admit, sometimes a relief. We love seeing people use our products. But before we reach that point, we have to test. We want to find the bugs. The gaps in user interaction flow. One missing </div> can make a world of difference. That’s why we always [test, test and test again](https://zurb.com/university/lessons/50 "ZURB U | Save Your Product From Launch Failures | how-to lesson at ZURB University") to make sure everything works before launch. And while we always test with real devices, testing workflow begins long before we touch code. ### Testing With Clickable Paper Mockups We import our scanned sketches into [Solidify, our prototyping app](https://solidifyapp.com/ "Solidify | Quick way to build prototypes for user testing"), to create a series of graphics with *hotspots* — areas of an image we can tap or click to visit other sketches. This simple technique helps us work out workflow hiccups long before they reveal themselves in code, when they’re more costly to fix. Sure enough, our web team discovered a few areas that needed work in the new SHCS website. They iterated several times until the prototype hit [the right mood](https://zurb.com/wired/884/creative-direction-uncovers-a-visual-stor "Creative Direction Uncovers a Visual Story | article by ZURB") from our earlier opportunity and ideation sketches. Taking time to scan a stack of paper, sift through images and link up hotspots may seem like a waste of time — especially since we’re on a 24-hour deadline. But we’ve found that sketched prototypes *save* time in the long run… even when “long run” means early the next morning. [Stroll through the wireframe yourself.](https://new.influenceapp.com/projects/172-zurbwired/pages/e2e14135b7299a8b6fa2 "Sacred Heart CS mockup | prototype by ZURB")
