Prototype or Die
Description
Why doesn’t your product look and work right?
Early designs painted an interface paradise filled with exotic features, but something went terribly awry and nothing quite works the way you thought it would. People can’t find even your most basic controls.
Prototyping to the rescue! Product Managers get to dream big, and see their ideas brought to life. Usability study participants can share natural reactions without suspending disbelief. Engineers can experiment with a working example, and recreate the smallest detail in production code.
In this talk, we’ll cover: which types of projects benefit from prototyping; how to choose the right fidelity (from paper, to interactive, to functional); mobile prototyping; fringe benefits of prototyping (like stakeholder buy-in); when not to prototype; and how designers, prototypers, and researchers can work together effectively.
Questions Answered
- How is prototyping different from engineering?
- Which projects need a prototype, and which don’t?
- How can you add prototyping to an existing design, research, and development process?
- What’s the right fidelity for your prototypes (from paper, to interactive, to functional)?
- Which Google Docs features started with a prototype, and what were the pitfalls and benefits?
Tags
product design, prototyping, design process
Meta
Speakers
- Vance Vagell Google, Inc.
- Hendrik Mueller Google, Inc.
- Jonathan Yu Google, Inc.
- Ian Gunn Google, Inc.
Organizer
Vance Vagell Google, Inc.
Add Comments
comments powered by Disqus