So the reason is to 1. Create a prototype, and 2. Get respect from developers. Re: #2—Let's reverse this, specifically for marketing. Developers (and pretty m

So the reason is to 1. Create a prototype, and 2. Get respect from developers. Re: #2—Let's reverse this, specifically for marketing. Developers (and pretty much anyone) who know a little marketing can be harder to work with than those that believe they don't understand it. They over-rely on cliches and stereotypes without realizing it. And what about the scenario where you end up with a person with limited technical knowledge micro-managing a tech worker? Not a good thing. Re: #1—I find creating mock-ups shows functionality more accurately and in much, much less time than creating working prototypes. I'm a business/marketing guy who loves coding. I usually avoid it because it's incredibly time-consuming to do even half-assed well, and you can re-use little of what you learn when it's just a one-off experience to creating something to show. (I realize that if you are always learning and creating things, your experience builds in more reusable ways.)