Différences
Ci-dessous, les différences entre deux révisions de la page.
| Les deux révisions précédentes Révision précédente Prochaine révision | Révision précédente Prochaine révision Les deux révisions suivantes | ||
|
en:prototyping [2019/06/24 17:27] hilda [Types of prototyping] |
en:prototyping [2019/06/25 10:30] hilda [Prototyping tools] |
||
|---|---|---|---|
| Ligne 18: | Ligne 18: | ||
| **Understanding** the context and people's experience in connection with your idea/subject. This type of prototyping is also called by d.school "Prototyping for empathy" | **Understanding** the context and people's experience in connection with your idea/subject. This type of prototyping is also called by d.school "Prototyping for empathy" | ||
| - | **Explore-ing** and analysing design solutions | + | **Exploring** and analysing design solutions |
| **Communicating** ideas to your project stakeholders | **Communicating** ideas to your project stakeholders | ||
| - | The agency nod-A identifies three big groups of prototyping in a similar classification system {{ :fr:fiche-choisir_son_protorevu.pdf |}} | + | The agency nod-A identifies three big groups of prototyping {{ :fr:fiche-choisir_son_protorevu.pdf |}} |
| + | |||
| + | **Shape prototypes**: early in the creative process and with little resources, they will allow you to better understand the value of your ideas and to communicate them to the stakeholders of your project. | ||
| + | |||
| + | **Usage prototypes**: when your ideas have a more defined shape, usage prototypes will allow you to test a particular function, use or technology of your concept or idea. They are normally thought to be tested by users and therefore manipulable. | ||
| + | |||
| + | **Beta prototypes**: at a more advanced stage of your idea development and after a first usage prototype, you can test and communicate the overall concept at different scales and dymensions: user experience,technological aspects, bussiness model... | ||
| ==== The prototyping process ==== | ==== The prototyping process ==== | ||
| + | The prototyping process starts from the very moment in which you decide to let your ideas out. It is very important that you make the right choice of the aspect of your idea that you want to prototype and how you want to prototype it. But do not spend too much time planning for it, Start and improve it as it goes... | ||
| - | ==== Prototyping tools ==== | + | Here some tips from Penny Hagan, who has resumed Penny Hagan has resumed the different stages when developing a service prototype. She proposes a great grid to reflect on the purpose of your prototype {{ :en:steps_to_developing_penny_hagan.pdf |}}: |
| + | |||
| + | 1. Choosing what to prototype: Focus on prototyping the bits of your idea that are most important to learn about at the given time. | ||
| + | |||
| + | * What do you want to learn through prototyping? | ||
| + | * What questions need to be answered? | ||
| + | * What assumptions in your idea need to be tested? | ||
| + | * What aspects need further thinking and exploration? | ||
| + | * What needs to be communicated in order to enable feedback from users and stakeholders? | ||
| + | |||
| + | 2. Choosing how to prototype: | ||
| + | |||
| + | Different methods can help you explore and test different things | ||
| + | |||
| + | |||
| + | 3. Evaluating your prototype | ||
| + | |||
| + | ==== Prototyping methods ==== | ||
| * [[en:protostoryboard|Storyboard]] | * [[en:protostoryboard|Storyboard]] | ||
| Ligne 41: | Ligne 65: | ||
| The d.school suggests some useful tips for prototyping for testing: | The d.school suggests some useful tips for prototyping for testing: | ||
| - | **Start building**: Even if you aren’t sure what you’re doing, the act of picking up some materials (paper, tape, and found objects are a good way to start!) will be enough to get you going. | + | * **Start building**: Even if you aren’t sure what you’re doing, the act of picking up some materials (paper, tape, and found objects are a good way to start!) will be enough to get you going. |
| - | + | * | |
| - | **Don’t spend too long on one prototype**: Move on before you find yourself getting too emotionally attached to any one prototype. | + | * **Don’t spend too long on one prototype**: Move on before you find yourself getting too emotionally attached to any one prototype. |
| - | + | * | |
| - | **Build with the user in mind**: What do you hope to test with the user? What sorts of behavior do you expect? Answering these questions will help focus your prototyping and help you receive meaningful feedback in the testing phase. | + | * **Build with the user in mind**: What do you hope to test with the user? What sorts of behavior do you expect? Answering these questions will help focus your prototyping and help you receive meaningful feedback in the testing phase. |
| - | + | * | |
| - | **Identify a variable**: Identify what’s being tested with each prototype. A prototype should answer a particular question when tested. | + | * **Identify a variable**: Identify what’s being tested with each prototype. A prototype should answer a particular question when tested. |
