03.18
Jonathan Arnowitz
If you are a PM interested in Prototyping, you must understand how engineers and designers define and address prototyping. In this interesting Blog post, Jonathan Arnowitz provides a great introduction to prototyping.
From the Blog post:
“…
A prototype is a model of a design that is:
- utilized for a specific planned purpose
- illustrating specific content and fidelity
- articulating defined requirements and assumption
- specified with prototyping characteristics
- customized for a specific audience(s)
- created with a specific tool
- performed in a specific method
Here is a less verbose but more specific version of the same definition:
A prototype is a model of a design with:
- purpose
- content
- content fidelity
- requirements and assumption
- prototyping characteristics
- defined audience (s)
- toolset
- method
…”
This post and Jonathan’s Blog are a great introduction to how designers thinks of Prototyping.
In the book – Effective Prototyping – you will find many examples as wells as ideas and tools he and his co-authors have.
As a PM, you may have another way of looking at Prototyping, due to your background, perception of the product and development processes, tools set, etc.
It is important to understand how other professionals in your team, in this case, designers and Ux architects, address the challange.
In the “Prototyping for PM” workshop, I provide real-life examples of these differences and methods to harvest the differences and building prototypes in an efficient, productive and fun way.
