In several earlier articles I have talked about aspects of prototypes. I’ve talked about using them as the basis for your product spec, and how to use them to test out your ideas on target users, and why I prefer high-fidelity prototypes to their lower-fidelity cousins. In this article I’d like to highlight the top 10 major benefits of prototyping, and talk about some of the mechanics of building and using prototypes.
In earlier articles I have discussed the key roles in the product organization – product managers, project managers, interaction designers, visual designers, usability engineers, prototypers, engineers, architects, QA and product marketing – and I’ve also discussed the ratios between the roles, but many organizations also struggle with the organizational structure that contains these people.
I’m not sure how many of you have heard the phrase, “we eat our own dog food,” but for several years at least, companies especially in Silicon Valley have used this phrase in order to impress their customers that their product is so good that they run their business on it and use it themselves. This was practically a mantra at Netscape, and I can’t count how many times I’ve said this myself.