Intentional Prototyping

Get Started. It's Free
or sign up with your email address
Intentional Prototyping by Mind Map: Intentional Prototyping

1. Social Prototypes

1.1. Design Thinking

1.2. Contemplating the Ideal

1.2.1. A quest for self-improvement

1.2.2. Prototyping products and processes of an ideal world

1.3. Opposite of specification-led, planning-driven abstract thinking; NOT thinking with your hands

1.4. Designers need to embed prototypes in their stories to have a real and relatable impact to stakeholders and customers

1.4.1. Helps designers keep their end-users in mind

1.4.2. Helps potential customers imagine what they might do with the objects and processes being prototyped

2. Prototyping Spectrum

2.1. Low fidelity

2.1.1. Paper sketches

2.1.2. Ideal during brainstorming

2.1.3. Static, low visual and content fidelity

2.1.4. Focuses on how users use the system, rather than how it will look like

2.1.5. Makes designers more open to change based on user feedback

2.1.6. No learning curve, allows for rapid-testing and iterations quickly and easily

2.2. Medium fidelity

2.2.1. Visio, Balsamiq, Figma, Axure, Adobe XD

2.2.2. Wireframes, task flows, scenarios

2.2.3. Focuses on behaviours and interaction design

2.2.4. Can be clickable/interactive

2.2.4.1. Some visual and functional fidelity

2.2.5. Are users needs being met?

2.2.6. Is the user experience optimal?

2.3. High fidelity

2.3.1. Photoshop, Illustrator

2.3.2. The most realistic and most easily mistaken as the final product

2.3.3. Users can be more reluctant to give proper feedback if starting from here

2.3.4. Time intensive

2.3.5. High visual and functional fidelity

2.3.6. Websites or apps with content and clickable interfaces

3. Rapid Prototyping

3.1. Process of quickly mocking up the future state of a system

3.1.1. Validating it with users, stakeholders, developers, and designers

3.1.2. Website or application

3.1.3. Service, events, etc.

3.2. Rapid and iterative feedback

3.2.1. Improves the final design and reduces the need for changes during development

3.3. STEPS

3.3.1. Prototype

3.3.2. Review

3.3.3. Refine

3.4. How much should be prototyped?

3.4.1. Focus on the 20% of the functionality that will be used 80% of the time (key functions)

3.5. Find the story

3.5.1. Scenarios, coherent paths, etc.

3.6. Plan your iteractions

3.7. FIDELITY

3.7.1. Visual

3.7.1.1. Sketched

3.7.1.2. Styled

3.7.2. Functional

3.7.2.1. Static

3.7.2.2. Interactive

3.7.3. Content

3.7.3.1. Lorem ipsum

3.7.3.2. Real content