Prototypes

← Back to Method Diagram

Purpose of a Functional Prototype 

Prototypes have a number of important uses, but chief amongst them is the ability to test the solution hypothesis, to each use case, with a real user, in such a way that it acts like the real thing – no explanations should be necessary in order for the user to interact with the prototype successfully (or unsuccessfully). Any failures should be in the solution design, not in the prototype’s ability to emulate a real solution

“If a picture is worth a thousand words, a prototype is worth a thousand meetings.” – IDEO

Value of a Functional Prototype 

1. Show layout, interaction and behaviour of solution – per use case or over all
2. Communicate layout, interaction and behaviour of solution – per use case or over all to stakeholders, developers, designers and users.
3. Demonstrate conditional logic within solution
4. Emulate a working twin that can be accessed via any form factor, for each use case, so they can be usability tested with representatives of each user type
5. Allow stakeholders to see functional progress toward solution from anywhere, in real time – building trust and visibility
6. Usability test the solution hypothesise thoroughly and reliably – iterating any failures – so that undeliverable or undesirable solutions are not developed and delivered to the user at increased development cost and reputational damage.

Examples

NB. For security clearance and NDA reasons, some elements of the example files may be redacted, changed or removed.