Prototyping
Prepared By
Adit Jha
Prototyping
• Prototypes are early samples, models, or releases of products
built to test a concept or process. There are many contexts in
which semantics can be used, for example, in design,
electronics, and software programming
• Prototyping allows you to build simple, small-scale prototypes
of your products, and use them to observe, record, and assess
user performance levels or the users' general behavior and
reactions to the overall design
Why
• Evaluate Technical Feasibility
• Enhance Website Quality
• Effectively Present Idea to Customers
• Reduced Risks
• Iterate at Lower Costs
• Simulate the Future Product
• Provide Focused Feedback
• Planning
• Quick and Easy
Types of Prototyping
• Sketches and Diagrams
• Storyboards
• Role-Playing
• Physical Models
• Wizard of Oz Prototypes- Prototypes with faked functions that
you can use to test users are called Wizard of Oz Prototypes
Co-creation
Co-creation defined
• Co-creation is the practice of collaborating with other
stakeholders to guide the design process.
• “An individual can’t create anything itself. All of our dreams
come true with the cooperation and co-creation of other
souls.”
Value co-creation
Iterate
Iteration
• The iterative process is an approach to continuously improving
a concept, design, or product.
What Is the Iterative Design
Process?
• A variation of the iterative model, the iterative design
process allows designers to create, test, analyze, and refine
ideas quickly during any phase of the design process
• Step One: User Observation and Research
• Step Two: Ideate
• Step Three: Prototype
• Step Four: Analyze
When Do I Use Iterative
Design?
• Iterative design can be used at any phase of the
design process, including when the product has
already been launched in the market and you are
looking to create improvements in that product
Design Cycle: An Iterative
Design Thinking Model
The Benefits of Iterative
Design
• It allows for rapid resolution of misunderstandings within the
project team and established clarity early in the development
lifecycle.
• It brings out user feedback to ensure that system
requirements meet user needs.
• It can help with client relationships to show the evolution of a
design rather than “dumping” a finished product on them.
• It gives the development team some certainty that their
efforts are being focused on adding value for users.