Prototyping and testing

I can help you in defining the prototype that can result in the most appropriate feedback, conduct testing and suggest iterations that will make your product better.  

The prototypes are low-resolution models of the product or service you would like to offer. In order to have meaningful information about your concept or product idea you have know what is the key element that will sell the concept and make sure that it works properly and can be demonstrated flawlessly on the prototype during tests - otherwise you not be able to decide that frustration comes from the concept itself or it is just because the prototype does not work properly.

The better you can model the context of the usage and the key functions of the concept when testing the prototype the more accurate guidelines you will get on what to change.

Creating the right prototype is a delicate balancing with costs, time and quality. It should be good enough that people think it can be real, but you do not have to waste too much time and money on them as in most cases they will be thrown away and not used in the final product. Digital prototyping can nowadays be an exception as some low-code platforms promise that you can actually reuse the code of the prototype in the final product if you remain among their walled garden. 

The type of the prototype and the method for testing depends on the nature of your product /service and the questions you need to answer

There is no single recipe for what you can use to make a prototype. Sometimes paper and pencil mockup will do, sometimes you have to simulate a mobile application. The most important is that you create a model that you can get the most information from for a reasonable cost in a possibly short time. In design sprints you can get to a testable prototype from an initial idea from Monday to Friday, but the timeframe very much depends also on the availability of the minds working on it.