It seems odd to put this as the first tip in an article about how to prototype. But what happens a lot is that many designers are trapped in a working ‘inertia’: whatever a client requests, they simply accept it, do the work, without questioning whether it is needed. Yet, there is always a voice in the mind asking, ‘Hold on! Are you sure about that?’.

When a (potential) prototype request comes, first assess if it is truly needed. A prototype is NOT the goal, it’s just a tool. Whether or not to prototype should mainly be determined by the objective(s) of the project and your capacity. Try not to be a prototyping Sisyphean, ask yourself:

What are your objective(s) and expectation(s) of this prototype?

Who is the audience?

How much effort and time can you afford?

Do you have anything in hand that does the same thing?

However, the story does not simply end with a ‘NO’ answer if you see prototyping is not needed. Share your decision-making path with the clients and make them think like you. If your client loves data, show him/her some figures e.g. the estimated ROI (return on investment). You can also search for some reputable sources to support yourself.

Most importantly, do remember to propose an optional solution to solve the issue without prototyping. All roads lead to Rome, you just chose a better way.