Prototyping services
Learn fast, learn early
A prototype will help you test ideas without building them.
Introduction
In the days before digital, agencies and clients made animatics to test T.V. script ideas before making the ad. You could say these were the prototypes of their day.
In our agile age, and with the array of tools available, we can prototype ideas of any description. Whether a desktop or mobile app, or some wearable tech, it’s a fast and cost-effective way to test assumptions, validate a hypothesis, or road test flows.
What is a prototype?
Reduce risk and test effectiveness
A prototype is a quick and cheap way to simulate a product experience to reduce risks. Prototypes can be close to the final product, including key features, and can refine flows and user experience without building the product.
Rapid prototyping refers to techniques used to simulate the experience or the whole experience of using the software. In most cases, these techniques involve no coding to optimize speed and minimize cost. The goal is still to reduce risks, increase the efficiency and effectiveness of the product rollout.
Why is this useful?
Proof of concept and testing
A prototype provides excellent value when testing the experience of using a product. Different testers provide essential input on areas to refine and the value of the product experience.
A completed prototype can also help the idea creators to explain their concept. Nothing is better than showing exactly how the product will look and work.
How do you start?
What problem are you solving?
Before we even start working on any prototype, we first need to understand the problem we’re trying to solve. Whether fixing a pain point or adding value to an everyday experience, every prototype needs to have an intention. Then get into more in-depth questions such as who is this product for? When will it be used? How often?
Answering these questions helps build a foundation.
The core functionality
Determining the main features
Once we have a better idea of the background, we start thinking of the prototype’s main features. The team will have different views on approaching these features, so we encourage a collaborative effort to get the best ideas. We then identify the critical flows we want the prototype to have, as this helps make the designing of the final product more efficient.
Building the prototype
Focus on the core
We always recommend not deviating from the intention of the prototype. After the flows are selected, we will flush out the entire experience and keeps the exercise contained and focused. To test one critical flow, we design for that experience and forget about any secondary flows such as login or admin features. On other occasions, we might only want to test the functionality of the admin flow or the onboarding experience.
It all depends on what the prototype is trying to accomplish.
