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:25] hilda [Sources] |
en:prototyping [2019/07/08 10:19] hilda |
||
|---|---|---|---|
| Ligne 14: | Ligne 14: | ||
| ==== Types of prototyping ==== | ==== Types of prototyping ==== | ||
| - | If we classify prototypes based on their purpose, we can identify three big groups of prototypes: | + | The agency nod-A identifies three big groups of prototyping based on their purpose {{ :fr:fiche-choisir_son_protorevu.pdf |}} |
| - | **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" | + | **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. |
| - | **Explore-ing** and analysing design solutions | + | * Scenarios |
| + | * [[en:protostoryboard|Storyboard]] | ||
| + | * [[en:blueprint|Blueprint]] | ||
| + | * Pitch | ||
| + | |||
| - | **Communicating** ideas to your project stakeholders | + | **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 allow you to convey experiences and particular forms of interactions with your project. They are normally thought to be tested/experienced/manipulated by users. |
| + | |||
| - | The agency nod-A identifies three big groups of prototyping in a similar classification system | + | * Digital prototypes |
| + | * Physical prototypes | ||
| + | * Role Playing | ||
| + | * [[en:protomockup|MockUp]] | ||
| + | * [[en:proto3dprint|3D printing]] | ||
| + | * [[en:protoscales|Scales]] | ||
| + | |||
| + | **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 dimensions: user experience, technological aspects, business 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 Nasta & Thinkpublic and Penny Hagan, who have identified the different stages when developing a service prototype. Hagan proposes a great grid to reflect on the purpose of your prototype {{ :en:steps_to_developing_penny_hagan.pdf |}}: |
| - | * [[en:protostoryboard|Storyboard]] | + | 1. **Choosing what to prototype**: Focus on prototyping the bits of your idea that are most important to learn about at the given time. |
| - | * [[en:protomockup|MockUp]] | + | |
| - | * [[en:proto3dprint|3D printing]] | + | |
| - | * [[en:protoscales|Scales]] | + | |
| - | * [[en:blueprint|Blueprint]] | + | |
| + | * 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? | ||
| - | ==== What to keep in mind when prototyping for testing ==== | + | 2. **Choosing how to prototype**: |
| - | The d.school suggests some useful tips for prototyping for testing: | + | Different methods can help you explore, understand and test different things. |
| - | **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. | + | Visual methods can help you to communicate ideas, stories and possible outcomes. |
| + | Tangible prototypes and role play bamethodshods can help you to convey a experiences or forms of interaction core to your project. | ||
| - | **Don’t spend too long on one prototype**: Move on before you find yourself getting too emotionally attached to any one prototype. | + | 3. **Evaluating your 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. | + | Prototyping is successful when its aims and purposes are clear for you. Before using your prototype for communicating or testing your idea, think and list what you want to understand through the prototyping process. |
| + | How are you going to get feedback on these different elements you want to test? | ||
| + | |||
| + | |||
| + | ==== What to keep in mind when prototyping for testing ==== | ||
| + | |||
| + | The d.school suggests some useful tips for prototyping for testing: | ||
| - | **Identify a variable**: Identify what’s being tested with each prototype. A prototype should answer a particular question when tested. | + | * **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 anyone prototype. | ||
| + | * **Build with the user in mind**: What do you hope to test with the user? What sorts of behaviour do you expect? Answering these questions will help focus your prototyping and help you receive meaningful feedback in the testing phase. | ||
| + | * **Identify a variable**: Identity what’s being tested with each prototype. A prototype should answer a particular question when tested. | ||
