Not the people who developed the prototype, but people who have no idea what it is, or what it is for. Depending on your spending plan, time and ready subjects, it is really useful if you can get at least 3 different testers. Even much better if you have closer to ten such guinea pigs to try and use your product.
If you can get these experiences tape-recorded and documented by a neutral observer this will supply you with even better feedback in terms of how your prototype is being experienced. Also Found Here as Usability, Hub provide access to real users who can supply feedback on your prototype. Exercise a series of core tasks that the model need to allow you to do.
This will extremely rapidly help you to discover if the model can actually help people to attain the goals that you think it ought to help them to accomplish. It's ok to mark off areas, and have non-functioning buttons, 404 pages and white space. Simply explain that 'this will do X or Y' your testers will generally understand, especially if you indicate to them which areas you are most concerned with them screening.
Even with prototypes and dummy information, if we see something that doesn't make good sense, or is too near to something in the real world it will frequently sidetrack and divert our attention. Goal to create sensible, non-attention diverting data so that your testers can focus on the prototype itself. They fast to produce, however deal enough realism that your testers will typically understand what you are trying to show.
The whole method through nevertheless do attempt to keep following the KISS principle (keep it easy foolish!). Tools such as In, Vision and Balsamiq allow you to rapidly and easily design standard wireframes. Make sure your testers have a lot of chance to communicate with you the thoughts that are going through their minds, the frustrations they experienced, and the 'what ifs' that concerned them.
0 
Star