The UI/UX design and user testing of a new business idea, which results in evidence driven documentation used for development of a new product or feature, greatly reducing risk of new product development.
Time & Effort
- 1 to 2 weeks
- 1 to 2 designers
- Business Model Canvas
- User Story Map
- Success Metrics
- Focus on Customer Experience
- Visual solutions
- Testing mindset
- Potential invalidations
- Non-critical placeholders
Goals & Deliverables
- Hi-fi interactive prototype
- Product testing plan
- Consolidated test results
- Prototype iteration
- Development reference design
Vaporware’s process works. The way they frame questions and drive the narrative really gets you to see the full picture. What I got was much better than I expected.
Mark Hennessy, Co-founder, Evalus
Using the prototyping storyboard, designers work hand-in-hand with product owners to mood, mock, visualize and prioritize features in the product.
Screens and sections are then interactively tied together using a prototyping tool like Invision to simulate a functional software product.
These high-fidelity designs serve as development reference files to provide pixel-perfect specifications to guide development.
We then validate the prototype that was created with Usability Testing, Surveys, and Fake Landing Pages. Usability testing brings 4-6 potential customers into the room to evaluate the prototype.
It's key to test our assumptions on how users react to the prototype. We'll have a plan on what we're testing and what success criteria we can use to measure against.
A fake landing page can collect email or pre-payment (refundable) to judge market interest with design of an app. This lean test is ideal for A/B testing of marketing messages.
Based on the feedback received and consolidated, we pull critical themes and recommendations directly from customers. We then integrate this feedback into the original design, making small changes or even large pivots.
Sometimes an idea is completely invalidated at this point. This is a great point to pivot, as no code has been written and it's much easier to revisit the Plan with actual customer feedback.
If the original feedback was positive but needed small changes, we head back to testing in the field with users, to make sure we're continuing in the right direction and interpreted user feedback correctly.
This process can often continue indefinitely, but 2 rounds of validation is often the sweet spot for development to move in the right direction for real customer use.